Description

Roles

Attributes

Steps

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.

Inputs and Outputs

WorkProduct	Input	Output	Allowable States
Requirement			Active

Predecessors

Type	Name	Dependency Type
	Prioritize Quality of Service Requirements	Finish-Start

Successors

Type	Name	Dependency Type
	Validate Quality of Service Requirements	Finish-Start