User Interface Architecture

Definitions

User Interface Architecture

an architecture that captures architectural decisions about the user interface

Responsibilities

The typical responsibilities of a User Interface Architecture are to:

• Document the overall structure of the user interface (e.g., sitemap).
• Document the overall navigability of the user interface.
• Document standard window/screen/webpage formats.

Contents

The typical contents of a User Interface Architecture are:

• User Interface Architectural Elements:
  • Input Elements (e.g., Buttons, Keyboards, Mice, Scanners, Switches)
  • Visual Elements (e.g., Screens, Webpages, Windows)
  • Output Elements (e.g., Printers, Signs, Speakers)

Stakeholders

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

A user interface 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

A user interface 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 a user interface architecture include:

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

Guidelines

• TBD.

Conventions

A user interface architecture is typically constrained by the following conventions:

• Work Flow
• Content and Format Standard
• Inspection Checklist

Examples

• Example User Interface Architecture