Architectural allocation
The recipes for functionally analyzing use cases have multiple outcomes. The primary outcome is a set of high-quality requirements. The second is identifying a number of system features – system functions, data, and flows. The third outcome is identifying interfaces necessary to support the behavior outlined in the use case. This recipe focuses on allocating the first two of these to the subsystem architecture.
Purpose
The purpose of this recipe is to detail the specification of the subsystems so that we can hand off those specifications to the interdisciplinary subsystem teams for detailed design and development.
Inputs and preconditions
A set of requirements and system features have been identified, and a subsystem architecture has been created so that each subsystem has a defined mission (scope and content).
Outputs and postconditions
The primary outcome of this recipe is a specification for each subsystem. This includes the following...
