Operational Availability Architecture Diagram

Definition

A operational availability architecture diagram is a low-level architecture diagram work product that documents the major operational availability components and mechanisms of an application and their relationships.

Objectives

The typical objectives of a operational availability architecture diagram is to:

• Document the largest logical elements (layers and partitions) in the application.

Benefits

The typical benefits of a operational availability architecture diagram are to:

• It drives the remainder of the architecting activity.

Contents

The typical contents of a operational availability architecture diagram are:

• Layer Icons
• Partition Icons

Stakeholders

The typical stakeholders of a operational availability architecture diagram are:

• Producers:
  • Architecture Team
• Evaluators:
  • Project Manager
  • Technical Leader
• Approvers:
  • Project Manager
  • Technical Leader
  • Customer Representative
• Maintainers:
  • Architecture Team
• Users:
  • Software Development Team

Phases

• Business Strategy: Not Applicable
• Business Optimization: Not Applicable
• Initiation: Completed
• Construction: Maintained
• Delivery: Maintained
• Usage: Maintained
• Retirement: Archived

Preconditions

Layer diagrams can typially be started if the following preconditions hold:

• The initiation phase has started.
• The architecture team is adequately staffed and trained in logical architecture production.

Inputs

The typical inputs to a layer diagram include:

• Work Products:
  • Application Vision Statement
  • System Requirements Specification
• Stakeholders:
  • TBD

Guidelines

• TBD

Conventions

Layer diagrams are typically constrained by the following conventions:

• Work Flow
• Content and Format Standard
• Inspection Checklist

Examples

• Example Operational Availability Architecture Diagram