Software Architecture Document (Page 5 of 5) in pdf

Software Architecture Document Page 5

Version:

<1.0>

Software Architecture Document

Date: <dd/mmm/yy>

4.1

Module <Name of Module 1>

4.1.1

Static view

4.1.1.1 UML <Package or Class> Diagram

[Include UML package and/or class diagrams showing further decomposition of module and relationships and

responsibilities of class. In each class in the UML class diagram, you must show important attributes, their type,

and their visibility AND important operation/method names, their parameters, and return values, and their visibility.

In addition, give a brief textual description/justification of decomposition of module into classes shown in UML

class diagram.]

4.1.1.2 Module Interface Descriptions

[Give specifications of the module interface as it relates to important actions/functions/use cases (see detailed

design example in appendix B in textbook).]

4.1.2

Dynamic view

4.1.2.1 UML sequence diagrams

[Include UML sequence diagrams that relate to the major functions of the module and its classes.]

4.2

Module <Name of Module 2>

[And so on….]

Mid-level Design Rationale

[Describe other design options that you considered and justify the main design decisions that you made to arrive at

this architecture. Discuss only those that are crucial for fulfilling important requirements, those that will be hard to

change later, or those for which the motivation behind them is not immediately apparent. For those decisions that

are discussed, you should explain the factors influencing the decision, the alternatives considered, the evaluation of

the alternatives, and the reasoning behind the final selection]

Glossary

Confidential

<Company Name>, 2015

Page 5 of 5

Software Architecture Document Page 5