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

Project Portal
| ### Next Steps Plan an Iteration |
| Create a Quality of Service Requirement Business Analyst
|  | Participating Roles Responsible: Business Analyst
### 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 Dependencies: The vision statement is published to the project portal. # Activities
1 | Brainstorm Quality of Service Requirements | Identify quality of service goals. Identify quality factors. Identify requirements not expressed by scenarios. Communicate the quality of service requirements.
2 | Develop Lifestyle Snapshot | Optional Identify an ideal persona time period. Identify technical opportunities.
3 | Prioritize Quality of Service Requirements List | Determine the importance of each requirement. Determine overall requirement priority.
4 | Write Quality of Service Requirement | Document the quality of service requirement. Attach supporting information.
5 | Identify Security Objectives | Document the security objective. Attach supporting information.
# Exit Criteria
| A list of known quality of service requirements such as platform, load, stress, security, and performance is published to the project portal.
| Testable descriptions of all of the quality of service requirements scheduled to be developed or prototyped in the upcoming iteration are attached to the quality of service requirement work items .
(C) 2005 Microsoft Corporation. All rights reserved. Build 97 |