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

Project Portal
| Create Product Requirements Business Analyst
|  | Participating Roles Responsible: Business Analyst User Experience Architect Solution Architect Accountable: Business Analyst Consult: Subject Matter Expert Sponsor Informed: IPM Officer Development Manager Project Manager Test Manager Release Manager
### Overview Product requirements are derived from customer requirements. While customer requirements describe what the product will do from the user's perspective, the product requirements detail what needs to be designed to support the customer requirements from an engineering perspective. # Entry Criteria Scenarios and Quality of Service Requirements Complete User scenarios and quality of service requirements are complete and available. When: Every iteration, after scenarios and quality of service requirements are defined. # Activities
1 | Develop a User Interface Flow Model | Analyze user scenarios. Develop a user interface flow model to facilitate intended use.
2 | Develop a Domain Model | Analyze user scenarios and quality of service requirements. Develop a domain model to show interaction between objects or entities for the underlying architecture.
3 | Define Functional Requirements | Define the technical requirements to achieve the desired functionality.
4 | Define Interface Requirements | Define the software-to-hardware and software-to-software interface requirements.
5 | Define Security Requirements | Define measures to be taken to ensure the security of the software. Address any regulatory requirements specific to security.
6 | Define Safety Requirements | Define measures to be taken to ensure human safety, if applicable. Address any regulatory requirements specific to safety.
7 | Define Operational Requirements | Detail the requirements for operational instrumentation.
8 | Allocate Product Component Requirements | Create logical groupings of requirements. Allocate them to components.
9 | Prioritize Functionality | Indicate the functionality that is mandatory, preferred, or optional.
10 | Validate Requirements | Review to validate that the requirements meet the intended use of the product.
# Exit Criteria
| Product requirements are complete, reviewed, accepted, and baselined.
| The user interface flow model is complete, reviewed, and accepted.
| The domain model is complete, reviewed, and accepted.
© 2005 Microsoft Corporation. All rights reserved. MSF for CMMI Process Improvement: 1.00.0000.00 |