Software Architecture Prototype

Definitions

Software Architecture Prototype

the application architecture work product that models a partial application that verifies the software architecture of an application

Objectives

The typical objectives of the software architecture prototype are to:

• Verify the application software architecture.
• Be evolvable into the software components of the application.
• Signify completion of the Initiation Phase.

Benefits

The typical benefits of a software architecture prototype are:

• Defects in the software architecture can be identified early in the development process when they can be fixed with less cost and less effort.
• The architecture prototype marks a major milestone in the evolution of the deliverable application.

Contents

The typical contents of a software architecture prototype are:

• Prototype software components

Stakeholders

The typical stakeholders of a software architecture prototype are:

• Producer: Architecture Team
• Evaluator: Architecture Inspection Team
• Approvers:
  • Technical Leader
  • Project Manager
  • Customer Representative
• Maintainer: Software Development Team
• Users:
  • The Project Management Team uses the completion of the software architecture prototype as major milestone of development.
  • The Software Development Team uses the software architecture prototype as an initial version of the complete application.

Phases

• Initiation: Started.
• Construction: Evolved into the complete application.
• Delivery: Maintained
• Usage: Maintained
• Retirement: Archived

Preconditions

The software architecture prototype can be started if the following preconditions hold:

• The initiation phase has begun.
• The architecture team is adequately staffed.
• A relatively complete version of the Application Vision Statement is available.
• A significant number of the architecturally significant operational and quality requirements have been specified in the System Requirements Specification.
• The Glossary exists.
• Domain experts in the relevant packages are available.

Inputs

The typical inputs to software architecture prototype include:

• Work Products:
  • A relatively complete version of the Application Vision Statement is available.
  • A significant number of the architecturally significant operational and quality requirements have been specified in the System Requirements Specification.
  • The Glossary exists.
• Stakeholders:
  • TBD

Guidelines

• The software architectural prototype should evolve into the primary software components of the application.

Conventions

A software architectural prototype is typically constrained by the following conventions:

• Architecture Guidelines
• Object Modeling Guidelines

Examples

• Example Software Architecture Prototype