Program Management

User Experience

Product Management

Create a Quality of Service Requirement

Architect

Participating Roles

Responsible:

Architect

Business Analyst

Subject Matter Expert

Overview

Entry Criteria

When:

Scenarios for current iteration are created.

Dependencies:

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.

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.

(C) 2005 Microsoft Corporation. All rights reserved.

MSF for CMMI Process Improvement: Build 050707