Content Management Architecture Diagram

Definition

A content management architecture diagram is a low-level architecture diagram work product that primarily documents the content management activity in terms of its associated databases and software components, and the dataflows between them.

Objectives

The typical objectives of a content management architecture diagram is to:

• Document the logical software and data components involved in content management.
• Document the data flow relationships between them.

Benefits

The typical benefits of a content management architecture diagram are to:

• It clearly describes the logical architecture of the content management environment.

Contents

The typical contents of a content management architecture diagram are:

• Node Icons:
  • Role Icons
  • Data Component Icons
  • Software Component Icons
• Arcs:
  • Data Flow Arcs
  • Role Uses Software Arcs

Stakeholders

The typical stakeholders of a content management architecture diagram are:

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

Content management 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 a content management architecture diagram include:

• Work Products:
  • Application Vision Statement
  • System Requirements Specification
• Stakeholders:
  • Content Management Team
  • User Experience Team

Guidelines

• TBD

Conventions

Content management architecture diagrams are typically constrained by the following conventions:

• Work Flow
• Content and Format Standard
• Inspection Checklist

Examples

The following example content management architecture diagram illustrates a typical content management activity in terms of its associated roles, data components (databases and repositories), and logical software components (i.e., tasks). The thin (black and red arrows) are dataflows, whereby the red arrows show the primary dataflows of the content from when it is created, acquired, or migrated to when it is presented to the user or archived. The thick black lines with the open arrowhead represent inheritance relationships that show the subclasses of content creators.

The legacy content source can include legacy applications, legacy databases, product catalog databases, and knowledge management systems (KMS).