(:Summary:Contains the 'action' links (like Browse, Edit, History, etc.), placed at the top of the page, see site page actions:) (:comment This page can be somewhat complex to figure out the first time you see it. Its contents are documented at PmWiki.SitePageActions if you need help. :) * View * Edit * History * Print

(:nl:)!!Steps of the In-Class Project and Final Review Notes

'''In-Class Project Outline'''

#Review project requirements and existing research data #Conduct additional research (e.g., heuristics evaluation, surveys, interviews, contextual inquiry, observation, etc.) if needed #Identify and define personas (the key target users) #Identify key and common tasks to be performed on the web site or application #Write scenarios for each persona for each of the relevant tasks ##Illustrate scenarios with swim lane diagrams, journey maps, or other UX flow diagrams ##Although senarios and flow diagrams are often time-based, they may also be organized around the logical relationships among the elements of the user experience #Review the scenarios and flow diagrams and identify the information and functionality necessary to complete all of the tasks ##Organize the information and functionality into meaningful groups or clusters ##Card-sorting exercises and affinity diagrams can be used to identify and represent the logical groups ("piles" or "buckets") #Take the results of the organizational exercise and create a site map (or site architecture) ##The site architecture serves as the logical foundation of the navigational system of the web site #Create wireframes for the key pages of the web site ##If there will be a prototype, identify the tasks that will be tested, then make certain to create the wireframes necessary for users to complete those tasks during testing ##It is not necessary to create wireframes for every page on the site - wireframes are only necessary for key pages that: ###Represent layout templates for the site ###Will be included in a prototype for testing during the design phase #Once there are sufficient wireframes designed and iterated, create a prototype ##Prototypes may vary in complexity, from simple sketched paper prototypes to clickable PDFs or clickable web pages all the way up to fully coded web pages ##Simpler prototypes may be tested sooner, but complex interactivity usually requires more coding to create a prototype #Make certain the prototype contains all of the pages and page states or variations necessary for a user to complete all of the selected tasks #Write the testing script to instruct the user on how to participate in a prototype test and to define for the moderator how to give the participant step-by-step goals without actually telling them what to do #Administer the prototype test and listen and observe for errors, confusion, difficulty, and inefficiency - these are design problems that will need to be addressed and fixed #Iterate and improve the interaction and UX design based on the prototype test findings

'''Notes and Ideas'''(:nl:)

Design by N.Design Studio, adapted by solidGone.org and IDUX
Powered by pmwiki-2.2.86