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

Project Portal
| ### Next Steps Define Security Requirements |
| Define Interface Requirements ( 3 : RD : 2 : 2.3 ) ( 3 : RD : 3 : 3.2 ) Solution Architect
Activity: Define Interface Requirements
Solution Architect
Business Analyst
|  |  |  | Planning |  |
|  | Participating Roles Responsible: Solution Architect Business Analyst Accountable: Solution Architect Consult: Subject Matter Expert Informed: Development Manager Project Manager Test Manager Release Manager
### Overview 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 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. When: After the input requirements are available. # 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.
© 2005 Microsoft Corporation. All rights reserved. MSF for CMMI Process Improvement: 1.00.0000.00 |