Activity: Perform Architectural Synthesis
This activity constructs and assesses an Architectural Proof-of-Concept to demonstrate that the system, as envisioned, is feasible.
DescriptionWork Breakdown StructureTeam AllocationWork Product Usage
Relationships
Parent Activities
Description


Properties
Event Driven
Multiple Occurrences
Ongoing
OptionalYes
PlannedYes
Repeatable
Staffing

As with Activity: Define a Candidate Architecture, this activity is best carried out by a small team staffed by cross-functional team members. Issues that are typically architecturally significant include performance, scaling, process and thread synchronization, and distribution. 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 will need to be able to synthesize a model, or even a prototype, of a solution.

Usage
Usage Guidance

This work takes place during inception, and so should be limited to one or two iterations. The purpose is to determine feasibility, not to construct the system during this workflow detail.