Project+Documentation

Kelly Goto's Web Design Project Resources
[]

Search the Information Architecture Institute Library
[]

Free Time Tracking Online Application
[]

Samples of project document confidentiality and/or proprietary notices:
 * 1) Confidential & Proprietary – Reproduction by any method or unauthorized circulation is prohibited without prior approval
 * 2) Proprietary & Confidential – Unauthorized reproduction prohibited
 * 3) Confidential – Unauthorized reproduction without written agreement

=Typical Project Documents=

1. Communication Brief / Creative Brief / Statement of Work / Project Contract
A brief description of the project, overall goal, most critical objectives, requirements, description of target audience(s), basic scope of work, how a change to the project scope is handled, and anything else that is important for your project process)


 * Creative Brief** []


 * Design Brief** []


 * Statement of Work** []

2. Content Inventory
A catalog of all content for the site (what is currently available, what needs to be created, any other info regarding keeping track of the content)

3. Competitive Analysis
A look at other sites such as major competitors and / or sites that have the functionality or organization that might work for the project site

Requirements & Features List
Requirements can be organized into business, technical, design, and user types of requirements. Requirements should be clearly defined. Someone on the team should be able to read your requirements and know exactly what the project is about and how it will be designed and coded.

User Task Matrix
Using the information about the users and goals, identify tasks that the users would like to perform and create a user task matrix. The User Task Matrix is a spreadsheet or table listing all users down the left side of the grid, and all the tasks across the top of the grid. Then place an “X” in the space that matches the correct user to the correct task.

The purpose of a user task matrix:
 * User tasks often overlap
 * In large-scale websites/portals, roles and permissions dictate the user experience

5. Target Audience Persona Charts and Scenarios
Information to keep in mind about members of the target audience

A scenario is a story the describes the ultimate user experience for a member (persona) of the target audience. The persona chart is a table of additional information about the user such as name, age, comfort level with technology and any other pertinent information.

Example of vision statement in a persona scenario format.

AIDE Adaptive Integrated Driver - Vehicle Interface (vision statement/user persona/scenario)
[]

6. Concept Models/Wireframes / Flowcharts (Process Flows) / Sitemap
Tools used to organize the content, interactions and basic architecture of the project site


 * Concept models** (similar to mind mapping) are used to identify concepts and the relationships among them.These are typically sketches used to convey information about the organization of things. They also can be used to facilitate discussion about the labels/names to use when referring to things.

Tim Berners-Lee created a **simple concept model** [] when he proposed his idea for what turned into the World Wide Web []

Process flow diagrams show how a user will interact with the system to achieve a task. Process flow diagrams should be mapped for each “interactive” feature but not for simple navigation.

7. Visual Comps (Screen Designs and Logo)
Can be shown as graphic files or done in HTML

Apple Devices Vector Icons http://www.snap2objects.com/2012/03/free-photorealistic-vector-apple-products/

8. Concept Note
Summary information regarding the visual design for the web site

The concept note should support the reasoning behind the decisions made for your visual design. There should be reasons as to why the colors where chosen, certain design treatments were implemented, and the choice of fonts.

The first part should contain a reminder of the important project information such as main goal, objectives, requirements, target audiences, image, tone, etc. This information comes from the communication brief.

The concept note should also explain your navigation strategy. The navigation strategy is a description (and justification) of how the user will navigate through the site – and why. Provide a visual representation of navigation structures, rollovers where applicable, selected states, colors of text, and proximity of separate navigation bars.

9. Working prototypes (if needed)
Use to show functionality and / or do usability testing

12. Analysis
Can and should be done as needed at any point in the process

Student Examples:

[]
 * Michelle Bradley**

[]
 * Christine Marquardt (IMD 220 Jump Page)**

[]
 * Christine Marquardt (IMD 410 Jump Page)**

[]
 * Christine Marquardt (IMD 320 Project Documents)**

=Other Types of Documentation=

RFP (Request for Proposal)
Writing an RFP (Request for Proposal) [|http://ezinearticles.com/?Writing-an-RFP-(Request-for-Proposal)&id=1795]

Writing a Request for Proposal for Web Site Design and Development []

RFC (Request for Comments)
Internet RFCs []

Entertaining Internet RFCs []

.