<Team Name>
<Project Name>
Software Architecture Document
Version <1.0>
[The texts in blue are guidance for filling in the information for each section. Remove everything in blue
when writing the document.
This template is a simplified version of the Software Architecture Document from the RUP model. ]
<Project Name> Version: <1.0>
Software Architecture Document Date: <dd/mmm/yy>
<document identifier>
Revision History
Date Version Description Author
<dd/mmm/yy> <x.x> <details> <name>
Confidential <Company Name>, 2025 Page 2 of 4
<Project Name> Version: <1.0>
Software Architecture Document Date: <dd/mmm/yy>
<document identifier>
Table of Contents
1. Introduction
2. Architectural Goals and Constraints
3. Use-Case Model
4. Logical View
4.1 Component: abc
5. Deployment
6. Implementation View
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.]
2. 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.]
3. Use-Case Model
[This section includes the use case diagrams that are already modeled and presented in the use-case
specification document.]
4. Logical View
[This section describes the architecture with components and relationships among them. One or several
diagrams showing the architecture are provided here. For each component, describe its responsibilities
and/or services that are provided for other components. Each relationship should also indicate the means
of communication, such as HTTP, HTTPS, Socket, LAN, Internet, etc.
The detail of each component is provided using the subsection below.]
4.1 Component: abc
[This section provides details for the component named “abc”. You need to include class diagrams for this
component and explain key classes.
For each component, create a section like this.]
5. Deployment
[Leave this section blank for PA3.]
6. Implementation View
Confidential <Company Name>, 2025 Page 3 of 4
<Project Name> Version: <1.0>
Software Architecture Document Date: <dd/mmm/yy>
<document identifier>
[Leave this section blank for PA3.]
Confidential <Company Name>, 2025 Page 4 of 4
