About Quality of Service Requirements
Thanks.
Thanks.
Our quality of service requirement format was inspired by Jeromy Carriere. It takes the form of <<context>> <<stimulus>> and <<response>> such as "During a catalog search, return the search results in under 3 seconds." There are other forms such as deployment platform that are simple lists.
Randy
MSF
Generally the process of collecting an appropriate set of scenarios requires a large stakeholder group donig brainstorming. The utility tree provides the context, but each stakeholder should reflect their specific perspective as one or more scenarios - developers, testers, operations staff, users, project managers, etc. all provide their input via scenarios.
See the sidebar on pages 54-55 of "Evaluating Software Architectures" for an interesting treatment of scenarios. Also see Step 7 "Brainstorm and Prioritize Scenarios" of the ATAM method on page 59 of the book.