636-530-7776
Legend: RUP Notation
Workflow > Detail > Artifact

Artifact: Software Architecture Document

The Software Architecture Document describes the software application's internal organization, architectural mechanisms, and the principles that guide the software solution.

More detail: Purpose - Audience - Template

Click the icons for definition

Business Strategist
Software Architect
Information Architect
Subject Matter Expert
Project Manager
Requirements Analyst
Stakeholder
Business Concept (from Business Strategy)Business Use Case Model (from Business Strategy)User Research ReportBusiness Operations Plan (from Business Strategy)
Find Actors and Use Cases
Manage Dependencies		 Glossary (from Environment)
Use Case Modeling Guidelines
Supplementary SpecificationUse Case (sketch)Requirements AttributesUse Case ModelActor Catalog
Software ArchitectPrioritize Use CasesSoftware Architecture Document (updated)
Requirements Analyst Define System Wide Attributes

Purpose

The Software Architecture Document contains the most important architectural decisions made by the Software Architect and other technical leaders. It uses several 'views' to present different types decisions that define the software's infrastructure. Views are a combination of models and descriptions explaining how architecturally significant requirements will be met.

Audience

The following roles use the Software Architecture Document:

  • The Role: Software Designer uses the principles, mechanisms, patterns, components, interfaces, etc. defined in the Software Architecture Document as input to their software design.
  • The Role: Implementer uses the Software Architecture Document to understand the infrastructure that they are programming or are using when developing other features.