Skip to main content

MSF for Agile Software Development

Go Search
Home
  
MSF for Agile Software Development > Wiki Pages > WorkDefinition - Create Solution Architecture  

WorkDefinition - Create Solution Architecture

WorkDefinition Information

Create Solution Architecture

Description

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.

Develop Performance ModelCreate Architectural PrototypeCreate Infrastructure ArchitecturePartition the SystemDevelop Threat ModelDetermine Interfaces

Attributes

GuidancePerformance Review, Security Review
Entry Criteria (Dependency)

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.

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.

Inputs and Outputs

WorkProductInputOutputAllowable States
Application Diagram(none)
Logical Datacenter Diagram(none)
Prototype(none)
RiskActive
System Diagram(none)
TaskActive
Threat Model(none)

Successors

TypeNameDependency Type
Implement a Development TaskFinish-Start

Last modified at 12/10/2007 3:34 PM  by Administrator