Information Architectures
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
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.
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
The typical stakeholders of an Information Architecture are:
Producers:
Evaluators:
Approvers:
Maintainers:
Users:
An information architecture typically is produced during the
following phases:
Preconditions
An information architecture typically can be started if the
following preconditions hold:
The typical inputs to an information architecture
include:
Work Products:
Stakeholders:
Care should be taken to minimize redundancy between the
information architecture and the database and user interface
architectures.
An information architecture is typically constrained by the
following conventions:
Work Flow
Content and Format Standard
Inspection Checklist
Example Information
Architecture
