Operations Architecture Diagram

Definition

A operations architecture diagram is a low-level architecture diagram work product that documents the software components (e.g., traffic monitoring, exception handling, intrusion detection, data monitoring and management, and system monitoring and management) that support the operations activity and their relationship to other components.

Objectives

The typical objectives of an operations architecture diagram is to:

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

Benefits

The typical benefits of an operations architecture diagram are to:

• It drives the remainder of the architecting activity.

Contents

The typical contents of an operations architecture diagram are:

• Layer Icons
• Partition Icons

Stakeholders

The typical stakeholders of an operations architecture diagram are:

• Producers:
  • Architecture Team
  • Operations Team
• Evaluators:
  • Project Manager
  • Technical Leader
• Approvers:
  • Project Manager
  • Technical Leader
  • Customer Representative
• Maintainers:
  • Architecture Team
  • Operations 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

Operations architecture 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 an operations architecture diagram include:

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

Guidelines

• TBD

Conventions

Operations architecture diagrams are typically constrained by the following conventions:

• Work Flow
• Content and Format Standard
• Inspection Checklist

Examples

• Example Operations Architecture Diagram