<Project name>
Version:
0.01
Software Architecture Document
Date:
4-1-2011
3. Logical View
[Describe the architecturally significant logical structure of the system. Think of decomposition in tiers
and subsystem. Also describe the way in which, in view of the decomposition, Use Cases are
technically translated into Use Case Realizations.]
3.1 Tiers
[Describe the tiers used and their responsibility in the system. Take the 4-tier model as point of
departure:
Presentation
Service
Domain
Data
Provide a clear picture of each tier’s responsibility and how, on a logical level, communication
between tiers will take place (its technical implementation will be described in the Implementation
View.)]
3.2 Subsystems
[Describe the decomposition of the system in subsystems and show their relation.]
3.3 Use Case Realizations
[Give examples of the way in which the Use Case Specifications are technically translated into Use
Case Realizations, for example, by providing a sequence-diagram. Explain how the tiers
communicate and clarify how the components or objects used realize the functionality.]
4. Implementation View
[This section describes the technical implementation of the logical view.]
4.1 Structure of the packages
[Provide an overview of the structure of the packages in the development environment. Try to reflect
the logical tiers in the naming conventions of the packages, like in the example below::
com.company.department.project.subsystem.ui
com.company.department.project.subsystem.service
com.company.department.project.subsystem.domain
com.company.department.project.subsystem.data
Illustrate the connection between the packages by means of a package-diagram.]
4.2 Realization of tiers
[Describe the technical realization of the tiers identified in the Logical View. Specify the rules which
apply for a component to be subsumed in a tier.]
Confidential
<Company>, 2011
Page 7 of 9
Software Architecture Document Template - ScrumUP - v. 1.00, download the latest version from