Software Architecture Document 3 Page 4
ADVERTISEMENT
1
2
3
4
5
6<Project Name>
Version:
<1.0>
Software Architecture Document
Date: <dd/mmm/yy>
<document identifier>
Software Architecture Document
1.
Introduction
[The introduction of the Software Architecture Document provides an overview of the entire Software
Architecture Document. It includes the purpose, scope, definitions, acronyms, abbreviations, references,
and overview of the Software Architecture Document.]
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 which have been made on the system.
[This section defines the role or purpose of the Software Architecture Document, in the overall project
documentation, and briefly describes the structure of the document. The specific audiences for the
document is identified, with an indication of how they are expected to use the document.]
1.2
Scope
[A brief description of what the Software Architecture Document applies to; what is affected or influenced
by this document.]
1.3
Definitions, Acronyms, and Abbreviations
[This subsection 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.4
References
[This subsection 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.]
1.5
Overview
[This subsection describes what the rest of the Software Architecture Document contains and explains
how the Software Architecture Document is organized.]
2.
Architectural Representation
[This section describes what software architecture is for the current system, and how it is represented. Of
the Use-Case, Logical, Process, Deployment, and Implementation Views, it enumerates the views that are
necessary, and for each view, explains what types of model elements it contains.]
3.
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.]
4.
Use-Case View
[This section lists use cases or scenarios from the use-case model if they represent some significant, central
functionality of the final system, or if they have a large architectural coverage—they exercise many
Confidential
<Company Name>, 2015
Page 4 of 6
ADVERTISEMENT
0 votes
Related Articles
Related forms
Related Categories
Parent category: Miscellaneous