Activity: Synthesize System Architecture
This activity constructs and assesses a System Architecture Proof-of-Concept, with the objective of showing that there exists, or is likely to exist, a solution which will satisfy the architecturally significant requirements, showing that the system, as envisioned, is feasible.
DescriptionWork Breakdown StructureTeam AllocationWork Product Usage
Relationships
Parent Activities
Properties
Event-Driven
Multiple Occurrences
Ongoing
Optional
Planned
Repeatable
Staffing
This activity is best carried out by a small team (playing the role of System Architect, and usually guided by one or two individuals who have deep experience in architecting systems in the relevant domain) staffed by cross-functional team members. Issues that are typically architecturally important include performance, scaling, distribution, or other specialty engineering requirements. Significant architectural constraints might also flow from physical and environmental requirements. The team should also include members with domain experience who can identify key abstractions. The team should also have experience with model organization and layering. From these inputs, the team must be able to synthesize a model, or even a prototype, of a solution.
Usage
Usage GuidanceThis work takes place during Inception, and so should be limited to one or two iterations. The purpose is to gain knowledge and determine feasibility, not to construct the system during this activity.