Software Architecture Document Page 4
ADVERTISEMENT
1
2
3
4
5<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 should begin with a brief discussion of the system that is under development
(i.e., a product overview). Following this description, the introduction includes the purpose, scope,
definitions, acronyms, abbreviations, references, and overview of the Software Architecture Document.]
1.1
Purpose
[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 are identified, with an indication of how they are expected to use the document.]
1.2
Document Conventions
[Describe standards or formatting conventions that have particular meaning. For example, bold and
italicized words are technical terms whose definition can be found in an included glossary.]
1.3
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. Use standard
citation formatting guidelines.]
1.4
Document Overview
[This subsection describes what the rest of the Software Architecture Document contains and explains
how the Software Architecture Document is organized.]
2.
Project Overview
2.1
Project Introduction
2.2
Project Vision and Scope
2.3
Stakeholders
3.
Logical View of System Architecture
[The logical view 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.]
4.
Mid-level Models
[This section is the major technical section of this document. It presents a detailed design. For each major
part (i.e., module) identified in the logical view of the architecture, you will model the static and dynamic
view.]
Confidential
<Company Name>, 2015
Page 4 of 5
ADVERTISEMENT
0 votes
Related Articles
Related forms
Related Categories
Parent category: Miscellaneous