Bog'liq Software Engineering Architecture-driven Software Development ( PDFDrive )
18.2.1 Products of detailed architecture definition The physical architecture should be anchored on the fabrication of structural units.
Structural unit specifications are established by synthesizing the assimilated func-
tional unit specifications and resolving conflicting and redundant requirements. The
software integration strategy must be derived by synthesizing one or more levels
of structural components and assemblies that integrate structural elements to align
with the topmost conceptual structure. The following products should be generated
during the detailed architecture definition stage:
1. Structural unit block diagram. The structural unit block diagram should be
prepared to represent how structural units will interact with one another. Block
diagrams are a method of explaining complex systems in an uncomplicated
manner. They are composed of labeled blocks representing structural units that
are joined by arrows that indicate the direction of data flow for inputs to and
outputs from the blocks.
2. Structural unit inheritance hierarchy. The structural unit inheritance hierarchy
should be developed by grouping similar structural units and deriving paternal
unit characteristics. It should display how the offspring structural units inherit
common functionality and data elements and how each offspring adds addi-
tional unique characteristics. This is known as
specialization within the object-
oriented domain.
3. Software integration hierarchy. The software integration hierarchy should be
developed to provide a depiction of how structural units will be assembled and
integrated into larger components. Structural assemblies should be identified
that involve an integrated component and the test stubs necessary to support
integration testing. This integration hierarchy should depict the sequential levels
of integration necessary to result in a complete, integrated software configura-
tion item. The hierarchy should also depict where in the hierarchy integration
testing will be conducted.
4. Physical user interface hierarchy. The physical user interface hierarchy should
be developed by grouping related user interface mechanisms, synthesizing them
as structural units and components, and configuring the physical user interface.
5. Database structure block diagram. The database structure block diagram pro-
vides a graphical representation of the database tables, records, fields, and the
relationships that link records within multiple tables together.