Operational Availability Architecture

Definitions

Operational Availability Architecture

an architecture that captures architectural decisions for ensuring operational availability requirements

Responsibilities

The typical responsibilities of an Operational Availability Architecture are to:

• TBD:
  • TBD

Contents

The typical contents of an operational availability architecture are:

• TBD:
  • TBD.

Stakeholders

The typical stakeholders of an Operational Availability Architecture are:

• Producers:
  • Architecture Team
• Evaluators:
  • Architecture Evaluation Team
  • Customer Organization, which evaluates the architecture for feasibility and appropriateness
• Approvers:
  • Technical Leader
  • Project Manager
  • Customer Representative
• Maintainers:
  • Architecture Team
• Users:
  • Software Development Team

Phases

An operational availability architecture typically is produced during the following phases:

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

Preconditions

An operational availability architecture typically can be started if the following preconditions hold:

• The initiation phase is started.
• The architecture team has been staffed and trained in architecting.

Inputs

The typical inputs to an operational availability architecture include:

• Work Products:
  • System Requirements Specification
• Stakeholders:
  • TBD

Guidelines

• TBD.

Conventions

An operational availability architecture is typically constrained by the following conventions:

• Work Flow
• Content and Format Standard
• Inspection Checklist

Examples

• Example Operational Availability Architecture