|
|
 |
 |
 |
 |
Activity:
Define Interface Requirements (CMMI Level 3 : RD 2.3 )
 |
|
Participating Roles
Responsible:
Architect
Business Analyst
Accountable:
Architect
Consult:
Subject Matter Expert
Informed:
Development Manager
Project Manager
Test Manager
Release Manager |
Interface requirements specify interactions between components (software-to-hardware or software-to-software). They can be grouped into features to aid allocation, prioritization, and development.
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: 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 and Architecture |
- Analyze the scenarios and quality of service requirements for input requirements specific to the system architecture.
|
|
2 |
Draft Interface Requirements |
- Create a draft of the interface requirements from initial input.
|
|
3 |
Review Interface Requirements |
- Review the draft interface requirements. Update the requirements based on feedback.
|
|
4 |
Baseline Requirements |
- Baseline the reviewed and approved interface requirements for the project. This baseline is used in change management and revising project estimates during replanning.
|
Exit Criteria
 |
The interface requirements are reviewed, approved, and baselined. | |
 |
 |
 |
 |
(C) 2005 Microsoft Corporation. All rights reserved.
MSF for CMMI Process Improvement: Build 050707 |
|
Program Management
