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

Version:

<1.0>

Software Architecture Document

Date: <dd/mmm/yy>

Software Architecture Document

Introduction

1.1

Purpose

This document provides a comprehensive architectural overview of the system, using a number of different

architectural views to depict different aspects of the system. It is intended to capture and convey the

significant architectural decisions that have been made on the system.

This document may be used to communicate significant architectural decisions to the technical leads to

ensure that design is consistent throughout the project. The architectural views will stabilize very early in

Elaboration, but the patterns and guidelines sections of the document will continue to evolve through early

Construction.

1.2

Scope

This document describes high level views of the architecture to indicate the overall structure of the project

and its relationship to the enterprise architecture. In addition, the document will include patterns and

guidelines created by the architect for the design teams to use. These patterns and guidelines will ensure

consistency in the design of the project. Reasons for significant architectural decisions will be included

along with alternates considered. This will provide a record in case questions arise later in the project or

during maintenance of the system. If the reasons for the decisions change, this documentation will provide

a basis for revisiting those architectural decisions.

1.3

Team Members and Roles

[This section lists each team member and tells the responsibilities of each member of the team.]

1.4

Definitions, Acronyms, and Abbreviations

[This section provides the definitions of all terms, acronyms, and abbreviations required to properly

interpret the Software Architecture Document. This information may be provided by reference to the

project’s Glossary.]

1.5

References

[This section provides a complete list of all documents referenced elsewhere in the Software Architecture

Document. Identify each document by title, report number (if applicable), date, and publishing

organization. Specify the sources from which the references can be obtained. This information may be

provided by reference to an appendix or to another document.]

Bureau of Grant Applications Project Proposal November 15, 2006

Architectural Goals and Constraints

[This section describes the software requirements and objectives that have some significant impact on the

architecture; for example, safety, security, privacy, use of an off-the-shelf product, portability, distribution,

and reuse. It also captures the special constraints that may apply: design and implementation strategy,

development tools, team structure, schedule, legacy code, and so on.]

High-level Architectural Overview

3.1

Dependencies on other Systems

[This section describes (typically using a diagram) the relationships that this project has with other systems

and projects in the Enterprise.]

Confidential

<Company Name>, 2015

Page 4 of 6

Software Architecture Document 5 Page 4

Related Articles

Related forms

Related Categories