Overview |  | Roles |  | Work Items |  | Views |  | CMMI |  | Index |  | Glossary |

Project Portal
| ### Next Steps Prioritize Quality of Service Requirements |
| Brainstorm Quality of Service Requirements ( 1 : REQM : 1 : 1.1 ) ( 3 : RD : 1 : 1.1 ) ( 3 : RD : 1 : 1.2 ) Business Analyst
Activity: Brainstorm Quality of Service Requirements
Business Analyst
Solution Architect
|  |  |  | Planning |  |
|  | Participating Roles Responsible: Business Analyst Solution Architect
### Overview To brainstorm quality of service requirements, consider quality of service categories and determine which goals to apply to each category. Then analyze each scenario and goal, and determine which interactions need quality of service requirements. While brainstorming, identify aspects of the system that may need quality of service requirements not captured in scenarios. The quality of service requirements list identifies and collects the non-functional requirements of the product. It is a list of constraints on the functionality of the product. The business analyst re-evaluates and modifies the quality of service requirements list as new requirements emerge through testing and as project needs change. # Entry Criteria Scenarios The scenarios are prioritized, written, and validated. Personas The personas describe fictional users and provide understanding of product interaction in scenarios. When: Scenarios for current iteration are created. # Sub-Activities
1 | Determine Quality of Service Goals | Open the quality of service requirements list. Be sure the list is up-to-date. If any new quality of service requirements have been created since the list was created, be sure to import them into the list. Both the architect and business analyst brainstorm the quality of service goals. Brainstorm goals that improve each of the following categories: performability, affordability, features and function, deliverability, usability, maintainability, durability, and branding. Brainstorm goals that prevent or reduce quality of service issues in the following categories: complexity, required precision, variability, sensitivity, immaturity, danger, and high required skill level. If security is a concern, create a risk work item and assign it to an architect to lead the threat modeling effort.
2 | Determine Quality of Service Requirements | Both the architect and business analyst continue brainstorming to determine the quality of service requirements. Analyze the scenarios and apply the quality of service goals to service levels and usage at each point where the product responds to a persona. Express the quality of service requirement as an observable measurement in the format of context, stimulus, and response. For example, "under normal operation, perform a catalog search in less than 3 seconds." Add each quality of service requirement to the quality of service requirements list, and assign each to a business analyst. Publish the quality of service requirements list to the work item database and then save the list spreadsheet on the project portal.
# Exit Criteria
| The quality of service requirements are determined and published to the work item database. The quality of service requirements list is up-to-date and saved on the project portal.
© 2005 Microsoft Corporation. All rights reserved. MSF for CMMI Process Improvement: 1.00.0000.00 |