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

Project Portal
| ### Next Steps Create Proof of Concepts |
| Design System Architecture and Deployment ( 3 : TS : 2 : 2.3 ) Solution Architect
Activity: Design System Architecture and Deployment
Solution Architect
Developer
|  |  |  | Planning |  |
|  | Participating Roles Responsible: Solution Architect Developer Accountable: Solution Architect Consult: Infrastructure Architect
### Overview The system architecture defines the groupings and configurations of elements identified in the application diagram. System diagrams are created that capture the system architecture for each possible architecture approach. Deployment diagrams show the deployment steps based on dependencies and core functionality. An infrastructure architect creates a logical datacenter diagram that describes the logical structure of the datacenter where the application will be deployed. The deployment diagrams are validated against the logical datacenter to ensure the systems can be deployed. # Entry Criteria Application diagram The application diagram for alternative designs is created. When: Alternative partitioning designs are created. # Sub-Activities
1 | Create System Diagrams | The architect and lead developer create system diagrams from the application diagram. Through system diagrams you can design reusable application systems as units of deployment by composing them from elements on the application diagram. You can also design larger and more complex systems that contain other systems so that you can use them in distributed system scenarios and abstract the details of applications in those systems. Check in each new diagram file to source control.
2 | Create Deployment Diagrams | Optional The architect and lead developer create a deployment diagram for each system diagram. The deployment diagrams shows the logical order of deployment of units, based on dependency and shared core functionality in more complex systems Check in each new diagram file to source control.
3 | Create Logical Datacenter Diagram | The infrastructure architect creates a logical datacenter diagram. Through the logical datacenter diagram, infrastructure architects can specify a logical representation of the datacenter such as the types of communications allowed, specific communication pathways, and the types of services enabled. Check in the new diagram file to source control. Only one logical datacenter diagram is required to validate all of the different system diagrams because all of the system diagrams should target deployment to the same datacenter. If the logical datacenter diagram was created in a pervious iteration, ensure it is still up-to-date and represents the actual datacenter.
4 | Validate Deployment Diagrams | The solution architect validates each deployment diagram against the logical datacenter diagram. Fix any validation errors that are identified by revising the system diagrams, bindings, or other settings as necessary. Also consider talking to the Infrastructure Architect to see if particular aspects of the datacenter can be modified. Once the deployment diagrams validate successfully, check in changes to source control.
# Exit Criteria
| The logical datacenter diagram is created or revised to represent the logical structure of the datacenter.
| A system diagram is created for each application solution.
| Deployment diagrams are created to validate against the logical datacenter diagram.
© 2005 Microsoft Corporation. All rights reserved. MSF for CMMI Process Improvement: 1.00.0000.00 |