|
|
 |
 |
 |
 |
Activity:
Define Operational Requirements (CMMI Level 3 : RD 3.1 )
 |
|
Participating Roles
Responsible:
Architect
Business Analyst
Accountable:
Architect
Consult:
Subject Matter Expert
Informed:
Development Manager
Project Manager
Test Manager
Release Manager |
Operational requirements specify instrumentation to administer the product. These requirements detail how the product incorporates into the Microsoft Operations Manager.
Entry Criteria
When:
- After the input requirements are available.
Dependencies:
- User Scenarios Complete: User scenarios have been created, reviewed, and approved.
- Quality of Service Requirements Complete: The quality of service requirements have been created, reviewed, and approved.
- Domain Model Complete: The domain model has been created, reviewed, and approved.
Sub-Activities
|
|
1 |
Analyze Input Requirements |
- Analyze the scenarios and quality of service requirements for input requirements specific to operations.
|
|
2 |
Draft Operational Requirements |
- Create a draft of the operational requirements from initial input.
|
|
3 |
Review Safety Requirements |
- Review the draft operational requirements. Update the requirements based on feedback.
|
|
4 |
Baseline Requirements |
- Baseline the reviewed and approved operational requirements for the project. This baseline is used in change management and revising project estimates during replanning.
|
Exit Criteria
 |
The operational requirements are reviewed, approved, and baselined. | |
 |
 |
 |
 |
(C) 2005 Microsoft Corporation. All rights reserved.
MSF for CMMI Process Improvement: Build 050707 |
|
Program Management
