interactive design 1 - med m/512 - fall 2005
Philip van Allen -
v a n a l l e n @ a r t c e n t e r . e d u
room 228, wednesday 1:00pm-5:00pm
all materials on this web site © copyright 2005, Philip van Allen
 
week 04a - prototype assignment, design doc presentations

prototype : 
assignment : 


due week 06


Develop a site prototype site and upload it to one team member's space on the server. This prototype should demonstrate the basic look and feel of the site. Specifically:

  • Test the overall visual design
  • Test the page layout and screen size for the important sections of the site
  • Test the information design and navigation system
  • Doesn't have to be fast downloading
  • Limit the number of pages to 2-4
  • Should not be a complete site - you will make many changes based on the critique
  • Throw it away when you are done

 



developing a prototype : 
  • Why do a prototype?
    • Create a tangible example and get everyone on the same page about the project
      • within the production team and between designer and client
      • define the scope of the project, visual direction, navigation, interface issues, technology, etc.
    • Create a discussion about the project
    • Test assumptions - technical, design, etc.
    • Test relationship with client
      • how long does it take for them to deliver assets?
      • what is their decision making process?
      • how well do they understand: the web, design, production, etc.?
      • are the good conceptualizers?
      • do they micro-manage
  • The prototype should be a sketch, not a fully developed application
    • Not all links need to be "hooked-up"
    • Graphics can be rough
    • Whole sections of the site can be empty
    • There are at least two types of prototypes:
      • design prototype that tests the visual and layout design
        • usually a few pages
        • often has 2-3 different visual directions
      • wireframe prototype which tests the information design and content approach
        • more pages so the info design can be fleshed out
        • does not have visual design
        • has active links to navigate around the site
  • Define the goals of the prototype
    • Test the graphic direction
    • Test user interface questions/approaches
    • Test the navigation and site layout
    • Test the screen size and layout
    • Test download times, plug-ins, or other technology issues
  • Define the audience for the prototype
    • Is it just for in-house people?
    • Will it be shown to the client? If so, you may want to wait for the second version of the prototype. Be very careful what you show the client. They often don't understand what "sketch" means, and don't have the imagination to extrapolate from a rough version to the real version.

 

 

design doc : 
presentation : 


The information should be presented by the group in a professional way, as if you were pitching your design to a real client. You should have a clear idea of what you will present and how you will present present it--rehearsing is suggested. Your presentation should follow this basic format:

  1. Overview describing the project (producer)
  2. Site map/information design (content editor)
  3. Inventory of content (content editor)
  4. Creative Brief (art director and content editor)
  5. Art direction samples (art director and all team members)
  6. Research (all)
  7. Technical plan (technical director)
  8. Production plan (producer)
  9. Set of urgent questions whose answers will help define the project better

 


all materials on this web site © copyright 2005, Philip van Allen

top