Posts Tagged ‘Brown’

Wireframe

June 13, 2008

“A wireframe is a simplified view of what content will appear on each screen of teh final product, usually devoid of colour, typographical styles, and images. Also known as schematics, blueprints, prototypes.”

From: Brown, Dan (2007), Communicating Design, Berkeley: New Riders, p.265

Advertisements

Flow charts (vs. site map)

June 13, 2008

“Flow charts attempt to visualize a process, usually centered around a specific task or function, For web-based processes, flow charts often represent a series of screens that collect and display infromation to the users. Also known as flows, user flows, process charts.”

“What seperates a flow from a site map is that in the former, time is the defining factor. The relationships between the steps are sequential, not structural or hierarchichal . While site maps capture an information structure that may or may not match the user’s experience of the site, a flow chart defines a process from beginning to end.

From: Brown, Dan (2007), Communicating Design, Berkeley: New Riders, p. 229

Sitemap

June 13, 2008

“Sitemap is a visual representation of a web site’s structure. Also known as structural model, taxonomy, hierarchy, navigation model, or site structure.”

From: Brown, Dan (2007), Communicating Design, Berkeley: New Riders, p. 199

Content audit and content inventory

June 13, 2008

“Content inventory is a list of all the information contained in a web site, along with data that describes the information from several points of view, like target audience or location. Also known as a content analysis or content audit (…)

The main distinction between these two documents [content inventory and content audit] is the level of granularity. In essence, the distinction is how much of the site you describe. With an inventory, the intent is to capture and describe every piece of content on the site. A content audit captures and describes less, focussing perhaps on the main content areas of the site or the top two levels of navigation after the home page. An audit establishes a boundary around the scope of the investigation.”

From: Brown, Dan (2007), Communicating Design, Berkeley: New Riders, p.167

Concept model

June 13, 2008

“A concept model is a diagram that shows the relationships between different abstract concepts. You can apply the concept modeling technique in a variety of circumstances to explain different aspects of a website. Also known as concept maps or affinity diagrams.”

From: Brown, Dan (2007), Communicating Design, Berkeley: New Riders, p.137

Personas

June 13, 2008

“A summary representation of the system’s intended users, often described as real people. Any project can have one or more personas, each representing a different kind of audience for the system. Also known as: user profiles, user role definitions, audience profiles.”

From: Brown, Dan (2007), Communicating Design, Berkeley: New Riders, p.15

IA Deliverables (Brown)

June 5, 2008
  1. User needs documents
    1. Personas
    2. Task Aanalysis
    3. User Flow Scenarios
  2. Strategy documents
    1. Conceptual Model
    2. Content Inventory
    3. Design documents
    4. Site Map
    5. Wireframes (or Page-Architecture or Schematics)
  3. Evaluation documents
    1. Usability plans
    2. Usability test reports

From: Brown, Dan (2007), Communicating Design, Berkeley: New Riders