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

Project Portal
| ### Next Steps Implement a Development Task Identify Security Objectives |
| ### Patterns & Practices Security Review Performance Review |
| Create Solution Architecture Architect
|  | Participating Roles Responsible: Architect
### Overview A good architecture has a clean and simple internal structure for the major elements of the application. A simple structure reduces the complexity of the application. The architecture may define structural elements that enable the application to better handle changing requirements and allow areas of the application to develop independently. Good architecture also takes advantage of layering to increase structural reliability and decrease time to market. When technology risks pose a threat, prototyping can be used to mitigate those risks and provide greater insight. Finally, security and performance are architectural concerns for which work must be done over the entire system. # Entry Criteria Dependencies: A set of written scenarios have been added to the iteration plan that require changes to the application diagram. A security objective has been created or is in place that relates to the new scenarios, quality of service requirements, or architecture changes. A technical risk has been identified and is scheduled for mitigation during this iteration. # Activities
1 | Partition the System | Choose architectural patterns. Create or update applications, endpoints, and connections. Validate the deployment. Create development tasks for architectural changes.
2 | Determine Interfaces | Design the interfaces. Define Web service interfaces. Create class interfaces.
3 | Develop Threat Model | Create an application overview. Partition your application. Identify the threats. Identify vulnerabilities.
4 | Develop Performance Model | Review the quality of service requirement. Identify the workload. Identify the performance objective. Identify the performance budget. Allocate the budget. Evaluate the budget. Validate the model.
5 | Create Architectural Prototype | Examine risks. Plan the approach. Build and execute the prototype.
6 | Create Infrastructure Architecture | Map the solution architecture. Adjust to the solution architecture.
# Exit Criteria
| The application diagram has been saved and checked in. If the solution architecture needs to be proven, an architectural prototype has validated key scenarios and quality of service requirements against the identified applications and the connections between them.
| If warranted, a prototype is completed that mitigated a technology risk or validated the identified subsystems, the interfaces between them, and any key user interactions.
| If a security objective has been addressed, any vulnerabilities have been scheduled for this or an upcoming iteration.
| If the deployment environment has been determined, the saved and checked in logical datacenter diagram reflects the current deployment environment.
(C) 2005 Microsoft Corporation. All rights reserved. Build 97 |