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

Project Portal
| Design and Development Analysis ( 2 : PP : 1 : 1.1 ) Solution Architect
Activity: Design and Development Analysis
Developer
Solution Architect
|  |  |  | Build |  |
|  | Participating Roles Responsible: Developer Solution Architect Accountable: Solution Architect
### Overview Analyze the requirements and change requests along with the existing architecture, domain model, and user interface flow model; then determine a list of developer tasks for design and development of the code for the iteration. # Entry Criteria Scenarios A list of scenarios for the iteration. QoS Requirements A list of the quality of service requirements for the iteration. Functional Requirements A list of the functional requirements for the iteration. Operational Requirements A list of the operational requirements for the iteration. Security Requirements A list of the security requirements for the iteration. Change Requests A list of change requests accepted for the iteration. User Interface Flow Model A user interface flow or interaction wire frame model for the product or iteration. Domain Model An object or data domain model for the product. Existing Architecture Any documentation available describing the existing logical architecture and physical data center. # Sub-Activities
1 | Analyze Scenarios | For each scenario, carefully map the required functionality on to the domain model, user interface flow model, and existing architecture. Separate out concerns across architectural elements and create a task for each piece of functionality required in each architectural layer or element.
2 | Analyze Quality of Service Requirements | For each quality of service requirement, map the required functionality against the existing architecture and determine a list of tasks by which to add or create the new functionality.
3 | Analyze Functional Requirements | Consider the list of functional requirements and revisit the list of tasks from Analyze Scenarios (step 1). Add any additional tasks required to meet the functional requirements, not already covered from the scenarios.
4 | Analyze Operational Requirements | Analyze the operational requirements along with the domain model, user interface flow model, and existing architecture. Separate out concerns across architectural elements and create a task for each piece of functionality required in each architectural layer or element.
5 | Analyze Security Requirements | Analyze security requirements along with the domain model, user interface flow model, and existing architecture. Separate out concerns across architectural elements and create a task for each piece of functionality required in each architectural layer or element.
6 | Analyze Change Requests | Analyze change requests along with the domain model, user interface flow model, and existing architecture. Separate out concerns across architectural elements and create a task for each piece of functionality required in each architectural layer or element.
# Exit Criteria
| A list of tasks of type Developer describing design and coding required from the development team in the iteration.
© 2005 Microsoft Corporation. All rights reserved. MSF for CMMI Process Improvement: 1.00.0000.00 |