Developing information architecture involves organizing information and navigation mechanisms so that users may find and use that information effectively. Aesthetics are not considered here. Use the links below for an overview of these activities. For details about a role, activity, or artifact in the diagram, click on its icon.
More detail: Purpose - How to Staff

Click the Icons for definition

Workflow Detail

The purpose of this workflow detail is to:

• Organize the website's content and features into a logical structure of the whole website
• Define page structures for individual pages or page types (i.e., templates)
• Develop navigation mechanisms to facilitate users' access to information and functionality

The information architecture consists of two major artifacts, Artifact: Site Map and Artifact: Wireframes. Developing information architecture involves organizing information structure and navigation mechanisms so users can find and use that information effectively. The Site Map organizes all the pages in a website or web-based application to show the big picture of the overall structure. Wireframes complement the Site Map. A wireframe is an abstract diagram illustrating the structural aspects of a page or page template. An explanation of how a section of the page may be used or the rationale for the page structure may complement the wireframe. A wireframe defines the types of information and services (including navigation) available on a page. It does not usually contain the actual copy or visual design elements, keeping the focus on information, interaction, and navigation. Colors, imagery, shapes, aesthetics, and other graphic design elements are addressed in the Develop Creative Approach activities.

Some projects with little functionality may use information architecture as the primary requirements tool. However, the Artifact: Use Case Model and its related use cases typically serve as the anchor point for feature and functional definition because the Use Case Model illustrates why actors (roles played by users and external systems) use the website or application. Each Artifact: Use Case allows one or more actors to achieve a recognizable goal by interacting with the application.

Change, however, will be bi-directional: a desired function may be identified through the Artifact: Site Map or Artifact: Wireframes, and this will need to be reflected in the corresponding use cases. Throughout this work, the Requirements Analyst updates the Artifact: Use Case Model to reflect refined actors, use case names, and use case relationships as well as newly identified use cases.

Through close collaboration among roles and the use of a controlled set of complementary artifacts, the team specifies the functional requirements and information architecture in an optimal fashion.

Top

In early iterations, the Role: Information Architect collaborates with the Role: Content Manager to create the initial Site Map based on the Artifact: Business Concept. As the team clarifies the requirements by working with stakeholders, the Information Architect and the Role: Requirements Analyst work together or frequently review each other's work to refine the evolving Site Map and Wireframes as the Requirements Analyst refines the requirements. The Role: Graphic Designer and Role: User Interface Prototyper give the Information Architect valuable feedback on the Wireframes and interaction design while applying the visual design to the Wireframes and building the prototypes. The Information Architect uses that information to further improve the information architecture.

If the information architecture is the primary requirements tool, the Role: Subject Matter Expert or other stakeholders would be involved in helping to define the requirements.

Top