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

Version:

<1.0>

Software Architecture Document

Date: <dd/mmm/yy>

3.2

Dependencies on Data stores

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

data stores in the Enterprise.]

Use-Case View

4.1

Overview

[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

architectural elements or if they stress or illustrate a specific, delicate point of the architecture. This is

typically a use case diagram for the project.]

4.2

Use-Case Realizations

[This section illustrates how the software actually works by giving a few selected use-case (or scenario)

realizations, and explains how the various design model elements contribute to their functionality. This

would be sequence diagrams for project level use cases.]

Logical View

5.1

Overview

[This section describes the overall decomposition of the design model in terms of its package hierarchy and

layers. This is typically a diagram of the packages or subsystems of the project.]

5.2

Analysis Model

[This section describes the runtime data of the system, especially data that is shared between components

or processes. This is typically a class diagram.]

5.3

Significant Packages or Subsystems or Layers or Tiers

[For each significant package or subsystem or layer or tier, include a subsection with its name, its brief

description, and a diagram showing the responsibilities of the package or subsystem. The responsibilities

may be shown with project level use cases, interfaces, package contents (classes and nested packages), or

subsystem operations.]

Process View

6.1

Overview

[This section describes the significant processes and threads of the project, along with their relationships.

Each process or thread will include an interface showing the responsibilities of the process or thread. This

is typically a component diagram.]

6.2

Interprocess Communication Mechanisms

[Describe the main modes of communication between processes, such as message passing, interrupts, and

rendezvous. This may be text or patterns described by class and sequence diagrams.]

Deployment View

7.1

Overview

[This section describes one or more physical network (hardware) configurations on which the software is

deployed and run. This is typically a deployment diagram. At a minimum for each configuration it should

indicate the physical nodes (computers, CPUs) that execute the software and their interconnections (bus,

Confidential

<Company Name>, 2015

Page 5 of 6

Software Architecture Document 5 Page 5

Related Articles

Related forms

Related Categories