Configuration Diagram

Definition

A configuration diagram is an architecture diagram work product that documents the hierarchical configuration that make up the top-level architecture of a system.

Objectives

The typical objectives of a configuration diagram is to document the decomposition relationships between the largest logical elements of a system:

• System of system (or network of systems)
• System
• Subsystems
• Segments
• Subsegments
• Assemblies
• Subassemblies
• Configuaration Items
• Components
• Parts (hardware) or Units (software)

Benefits

The typical benefits of a configuration diagram are to:

• It drives the remainder of the architecting activity.
• It is included in the logical architecture section of the system architecture document.

Contents

The typical contents of a configuration diagram are:

• Configuration Icons
• Partition Icons

Stakeholders

The typical stakeholders of a configuration 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

Configuration 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 configuration diagram include:

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

Guidelines

• Configurations typically depend only on nearby lower configurations (and partitions).

Conventions

Configuration diagrams are typically constrained by the following conventions:

• Work Flow
• Content and Format Standard
• Inspection Checklist

Examples

The following is a generic example configuration diagram documenting the typical configurations and partitions of an application.

• The user interface configuration contains user interface components including webpages and screens.
• The application process configuration contains the application-specific processes and transactions.
• The business objects and rules configuration contains both business objects and business rules.
• The persistence configuration obtains persistent data for the business object and business rules configuration.
• The EAI configuration provides access to legacy databases and enterprise applications.
• The system partition provides middleware (e.g., messaging, networking, and platform) services.