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

Project Portal
| Create a Quality of Service Requirement Solution Architect
|  | Participating Roles Responsible: Solution Architect Business Analyst Subject Matter Expert
### Overview Quality of service requirements are used to capture non-functional requirements or constraints on the functionality of the system. Quality of service requirements must be precise and not subjective in their definition. The requirements are identified, prioritized, and if scheduled for the current iteration, written. # Entry Criteria Scenarios The scenarios are prioritized, written, and validated. Personas The personas describe fictional users and provide understanding of product interaction in scenarios. Test Approach The test approach provides test goals and resource information such as potentially reusable test data. Lifestyle Snapshot The lifestyle snapshot describes personal information about each persona in a prototypical day. When: Scenarios for current iteration are created. # Activities
1 | Brainstorm Quality of Service Requirements | Optional Determine Quality of Service Goals. Determine Quality of Service Requirements.
2 | Prioritize Quality of Service Requirements | Perform Impact Analysis. Split or Reprioritize Requirements. Determine Priority. Select Requirements for Iteration.
3 | Write Quality of Service Requirements | Document the Quality of Service Requirement. Attach Supporting Information.
4 | Validate Quality of Service Requirements | Validate Quality of Service Requirements Against User Domain. Validate Quality of Service Requirements Against Project.
5 | Write User Acceptance Test Cases | Identify Preconditions. Write Steps.
# Exit Criteria
| Prioritized list of quality of service requirements.
| User acceptance tests are written.
| Quality of service requirements are described sufficiently to enable implementation.
© 2005 Microsoft Corporation. All rights reserved. MSF for CMMI Process Improvement: 1.00.0000.00 |