Software Architecture Document 3 (Page 5 of 6) in pdf

Version:

<1.0>

Software Architecture Document

Date: <dd/mmm/yy>

architectural elements or if they stress or illustrate a specific, delicate point of the architecture.]

4.1

Use-Case Realizations

[This section illustrates how the software actually works by giving a few selected use-case (or scenario)

realizations, and explains how the various design model elements contribute to their functionality.]

Logical View

[This section describes the architecturally significant parts of the design model, such as its decomposition

into subsystems and packages. And for each significant package, its decomposition into classes and class

utilities. You should introduce architecturally significant classes and describe their responsibilities, as well

as a few very important relationships, operations, and attributes.]

5.1

Overview

[This subsection describes the overall decomposition of the design model in terms of its package hierarchy

and layers.]

5.2

Architecturally Significant Design Packages

[For each significant package, include a subsection with its name, its brief description, and a diagram with

all significant classes and packages contained within the package.

For each significant class in the package, include its name, brief description, and, optionally, a description

of some of its major responsibilities, operations, and attributes.]

Process View

[This section describes the system's decomposition into lightweight processes (single threads of control)

and heavyweight processes (groupings of lightweight processes). Organize the section by groups of

processes that communicate or interact. Describe the main modes of communication between processes,

such as message passing, interrupts, and rendezvous.]

Deployment View

[This section describes one or more physical network (hardware) configurations on which the software is

deployed and run. It is a view of the Deployment Model. At a minimum for each configuration it should

indicate the physical nodes (computers, CPUs) that execute the software and their interconnections (bus,

LAN, point-to-point, and so on.) Also include a mapping of the processes of the Process View onto the

physical nodes.]

Implementation View

[This section describes the overall structure of the implementation model, the decomposition of the

software into layers and subsystems in the implementation model, and any architecturally significant

components.]

8.1

Overview

[This subsection names and defines the various layers and their contents, the rules that govern the

inclusion to a given layer, and the boundaries between layers. Include a component diagram that shows the

relations between layers. ]

8.2

Layers

[For each layer, include a subsection with its name, an enumeration of the subsystems located in the layer,

and a component diagram.]

Confidential

<Company Name>, 2015

Page 5 of 6

Software Architecture Document 3 Page 5

Related Articles

Related forms

Related Categories