User Interface Architecture Diagram

Definition

A user interface architecture diagram is a low-level architecture diagram work product that documents the primary flow of content between the databases and the users and the communication protocols and transformations that are used and that take place between them.

Objectives

The typical objectives of a user interface architecture diagram is to:

• Document the user interfaces of an application.

Benefits

The typical benefits of a user interface architecture diagram are to:

• It drives the user interface design subactivity.

Contents

The typical contents of a user interface architecture diagram are:

• TBD

Stakeholders

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

User interface 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 user interface architecture diagram include:

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

Guidelines

• TBD

Conventions

User interface architecture diagrams are typically constrained by the following conventions:

• Work Flow
• Content and Format Standard
• Inspection Checklist

Examples

• Example User Interface Architecture Diagram