|
Information Architecture is analogous to architecture in the non-Internet world. In order to construct a building that meets the various purposes of the people sponsoring the building and the people using the building, it is necessary to produce a detailed blueprint that illustrates as accurately as possible how the building will be laid out, and the types of motion and functions it will support. Information Architecture activities result in a detailed blueprint for site developers and stakeholders to review prior to site development. The major Information Architecture deliverables that Usography typically produces are discussed below.
Click one of the links below to read about a specific deliverable, or scroll down to read about the deliverables in order.
Navigation system specification
The navigation system shows how the web property will facilitate users’ ability to reach various points within the system. The navigation system may include special interactive components or devices such as quick links or drop down menus or cross-references that serve a special purpose that was uncovered as a need during the investigation. For example, in one system there was a search function that was very complicated, in-context interviews uncovered the fact that the most frequent users knew their project numbers, and could find the information they were usually seeking by including a program number search box at the top of every page.
The navigation system specifies what types of contextual navigation should remain on the screen to allow parallel navigation, versus situations where the contextual navigation should indicate drilling down in the hierarchy. The navigation model should include a discussion of levels of navigation, and types of navigation to be found on different types of pages.
back to top
Template system
Although the appearance of pages within a web site or application may vary widely, there are not usually a large number of completely different page types. A limited set of screen types that can support the range of pages being designed is called a template system. Relying on a template system rather than individual page designs decreases development time and makes system maintenance less arduous. Templates also facilitate dynamic generation of pages by standardizing size and placement of frequently used page components.
back to top
Page blueprints (wireframes)
Page blueprints (also known as "wireframes") are diagrams of key screens throughout the web site or application that identify all known screen components and their relative visual priority. Blueprints are often generated during the concept phase to give key stakeholders, the design team and/or users something to respond to. Later in the project, the blueprints become very specific with regard to the content and functional components on a screen, their relative priority, and the exact interactive elements needed to support user tasks, such as global navigation or various input controls. There should be a screen blueprint for every template in the system. While page blueprints may indicate some aspects of page layout and graphic design, visual design is typically a step that occurs after production of page blueprints. Page blueprints may indicate the copy that should appear on the screen to support user activities, but this copy will usually be modified extensively or replaced by the editorial team. Page blueprints continually evolve as more information about the design is gathered from team members, user testing, or shifts in scope. In many cases, screen blueprints serve as the definitive specification of what is being designed, although other documents such as functional specifications, scope matrix, data structure, etc. are required to complete the picture. Page blueprints may be the basis for user testing of interaction design.
back to top
Functional specifications
Functional specifications are usually produced as a companion document to page blueprints. The functional specifications document explains in detail how each screen component works, how it is populated, and the impact it has on other entities within the site.
back to top
Site map (future state)
The site map is a visual representation of the entire site. It identifies each screen in the site, as well as its place in the organizational structure and hierarchy. It may also indicate topical or process relationships, links, template types, data source, or typical paths through the site. Nearly every project requires at least two site maps: a map of the existing site, and a map of the site being designed. As process flows and screen blueprints evolve, the site map should be updated. For sites that are complex or content-heavy, the site map format may be unwieldly or even meaningless. In such cases, a site outline may be more useful for indicating site structure and page names.
back to top
|
|
|
