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

Project Portal
| ### Next Steps Validate Quality of Service Requirements |
| Write Quality of Service Requirements ( 3 : RD : 3 : 3.1 ) Business Analyst
Activity: Write Quality of Service Requirements
Business Analyst
Solution Architect
|  |  |  | Planning |  |
|  | Participating Roles Responsible: Business Analyst Solution Architect
### Overview Quality of service requirements identify the non-functional requirements of the product. They are the constraints on the functionality of the product. The business analyst and architect work together to write a detailed description of each quality of service requirement. The description must provide enough information that a developer can design and code functionality that meets the requirement. # Entry Criteria Quality of Service Requirements List Prioritized list that requires detailed descriptions. Disfavored Personas Identified Any disfavored personas or adversaries have been created and published to the project portal. When: Quality of service requirements are prioritized. # Sub-Activities
1 | Document the Quality of Service Requirement | Add a description of the quality of service requirement in the description field of the requirement work item. Use the following language template when developing the quality of service requirements: <context>, <stimulus>, <response>. Add a description of the security objective in the description field of the quality of service requirement work item. Security objectives determine the levels to which the solution will protect itself and its assets. There may be data that needs to be protected, regulatory requirements, or intangible assets such as company reputation, trade secrets, or intellectual property. Security objectives should be specific, testable statements about what is to be protected. They should not specify how. Security objectives usually start with a "verb;" such as "Prevent Marty (a disfavored persona) from obtaining account information for our customers." The asset should be clearly identified. Describe the quality of service requirements but leave the design to the architect and developers. If the brief description is not sufficient for complete understanding, write a more detailed form of the requirement in a requirements document, providing goals and rationale. Link the document to the requirement work item.
2 | Attach Supporting Information | Attach any scenarios that are affected by the quality of service requirement if applicable. If the quality of service requirement affects all of the scenarios or a majority of them, simply note this rather than attaching very large numbers. Attach any supporting documents such as storyboards if needed.
# Exit Criteria
| Quality of service requirements described sufficiently to enable implementation.
© 2005 Microsoft Corporation. All rights reserved. MSF for CMMI Process Improvement: 1.00.0000.00 |