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

Project Portal
| ### Next Steps Define Operational Requirements |
| Define Functional Requirements ( 3 : RD : 2 : 2.1 ) ( 3 : RD : 3 : 3.2 ) Solution Architect
Activity: Define Functional Requirements
Solution Architect
Business Analyst
|  |  |  | Planning |  |
|  | Participating Roles Responsible: Solution Architect Business Analyst Accountable: Business Analyst Consult: Subject Matter Expert Informed: Development Manager Project Manager Test Manager Release Manager
### Overview Functional requirements specify system behavior. They can be grouped into features to aid 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 functionality.
2 | Draft Requirements | Create a draft of the functional requirements from initial input.
3 | Review Requirements | Review the draft functional requirements. Update the requirements based on feedback.
4 | Baseline Requirements | Baseline the reviewed and approved functional requirements for the project. This baseline is used in change management and revising project estimates during replanning.
# Exit Criteria
| The functional requirements are reviewed, approved, and baselined.
© 2005 Microsoft Corporation. All rights reserved. MSF for CMMI Process Improvement: 1.00.0000.00 |