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

Software Architecture Document 5 Page 6

Version:

<1.0>

Software Architecture Document

Date: <dd/mmm/yy>

LAN, point-to-point, and so on.) For a small project, you may choose to combine the Process View and

Deployment View onto one diagram.]

7.2

Deployment Policies

[List the significant policies or requirements affecting the deployment view. This may include items such as

maintenance down-times, backup and recovery schemes, and any required mirroring or hot-backups.]

Data View

8.1

Overview

[This subsection describes the persistent data of the system. This is typically a data model, either an ER

diagram or a class diagram.]

8.2

Data Access Mechanisms

[Describe the mechanisms by which the components of the system access the data. For example, is this by

direct SQL calls to the database, or through an object layer? This description may be text or patterns

described by class and sequence diagrams.]

Size and Performance

[A description of the major dimensioning characteristics of the software that impact the architecture, as

well as the target performance constraints.]

10.

Quality

[A description of how the software architecture contributes to all capabilities (other than functionality) of

the system: extensibility, reliability, portability, and so on. If these characteristics have special

significance, such as safety, security or privacy implications, they must be clearly delineated.]

11.

Common Patterns and Mechanisms

[A description of architectural mechanisms to be used in the project( that are not documented in other

sections of the SAD), including at least a class diagram with a text description of how to use the

mechanism. You may also include a sequence diagram showing the use of the mechanism.

These mechanisms may include, for example, error handling, data logging, or access control.]

Confidential

<Company Name>, 2015

Page 6 of 6

Software Architecture Document 5 Page 6