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

Project Portal
| ### Next Steps Prioritize Functionality |
| Define Operational Requirements ( 3 : RD : 3 : 3.1 ) ( 3 : TS : 1 : 1.2 ) ( 3 : RD : 3 : 3.2 ) Solution Architect
Activity: Define Operational 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 Operational requirements specify instrumentation to administer the product. These requirements detail how the product incorporates into the Microsoft Operations Manager. # Entry Criteria 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. When: After the input requirements are available. # 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.
© 2005 Microsoft Corporation. All rights reserved. MSF for CMMI Process Improvement: 1.00.0000.00 |