Information Architectures

Definitions

Information Architecture

an architecture that captures architectural decisions about the information ( content) about an application, component, or framework as well as its associated navigation, presentation, and dependency decisions

Responsibilities

The typical responsibilities of an Information Architecture are to:

• Document and communicate architectural decisions regarding the:
  • Structure of the associated information (content).
  • Way users will navigate to the associated content.
  • Way the associated content will be presented to its users.
  • Dependencies the content will have on related externals and work products.

Contents

The typical contents of an information architecture are:

• Content (Data):
  • Logical Data Model.
  • Physical Data Model.
  • Data Architecture Diagram(s).
• Content Navigation:
  • Summary Site Map.
  • Navigation Diagram(s).
  • Global Navigational Approach.
  • Local Navigational Approach.
• Content Presentation:
  • Metaphors (Organizational, visual, and functional).
  • User Interface Architecture Diagram.
  • Conventions (Screen/Webpage/Window):
    • Cascading Style Sheets.
    • Presentation Diagrams.
    • Standard webpage layout grid(s) or templates
    • Implementing frames or tables
• Content Dependencies:
  • Legacy Applications
  • External Applications
  • Databases
  • Business Object Model

Stakeholders

The typical stakeholders of an Information 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

An information 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

An information 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 an information architecture include:

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

Guidelines

• Care should be taken to minimize redundancy between the information architecture and the database and user interface architectures.

Conventions

An information architecture is typically constrained by the following conventions:

• Work Flow
• Content and Format Standard
• Inspection Checklist

Examples

• Example Information Architecture