Software Architect's Handbook

Step 2 – Identifying key scenarios

Once the design objectives are identified and established, one or more design iterations will be necessary. Step 1 will only occur once, and each design iteration will begin with Step 2. Step 2 focuses on identifying key scenarios for the software application.

In this design process, a scenario is defined as a more encompassing user interaction with the software system, and not just a single use case. Key scenarios are the most important of these scenarios and are required for the success of the application. Scenarios could be an issue, an architecturally significant use case (one that is business critical and has a high impact), or involve an intersection between functional requirements and quality attributes. ...