Page 85 - DCAP305_PRINCIPLES_OF_SOFTWARE_ENGINEERING

Unit 4: Introduction to Validation, Metrics

Structural and behavioural views are applicable for each of the Conceptual, Logical and Execution Notes
Architecture views (or layers), as shown in Figure 4.11.

In general, however, you would want to at least have:
• An Architecture Diagram and informal component descriptions for Conceptual Architecture,
• Interface Specifications, Component Specifications and an updated (Logical) Architecture
Diagram showing interfaces and relationships for Logical Architecture. You should also
include Collaborations Diagrams for key Use Case steps. Note that these may be used
to describe system behaviour (they are simply illustrative), or to prescribe how system
behaviour is to be accomplished, and you should be clear about which of these you intend.
In general, you should avoid being prescriptive unless you have a strong architectural
reason for curtailing the creative options open to designers and developers.

Figure 4.11: Architecture Views with Structure and Behaviour

Behavioral View Structural View

Conceptual
Architecture
(abstract)
Informal
Architecture
Collaboration trace Component
Diagram
Specs (CRC-R)
Logical
Architecture
(detailed)
Architecture Interface
Collaboration Diagrams
Diagram with I/Fs Space

Execution
Architecture
(Process View and
Deployment View)
Collaboration Diagrams Architecture Diagram
showing processes showing Active Components

4.3.1 Architecture Documentation

With the architecture drivers and various architecture views, you have the raw material from
which to compose documents and presentations targeted at different audiences (“viewpoints”,
in the parlance of IEEE1471). At a minimum, your document set should include:
• Reference Specification: The full set of architecture drivers, views, and supplements such
as the architecture decision matrix and issues list, provides your reference specification.
• Management Overview: For management, you would want to create a high-level overview,
including vision, business drivers, Architecture Diagram (Conceptual) and rationale linking
business strategy to technical strategy.

• Component Documents: For each component owner, you would ideally want to provide
a system level view (Logical Architecture Diagram), the Component Specification for the
component and Interface Specifications for all of its provided interfaces, as well as the
Collaboration Diagrams that feature the component in question.

LOVELY PROFESSIONAL UNIVERSITY 79