Unformatted text preview:

Exam 1 Grade Distribution and AnswersSlide 2Waterfall vs. PrototypingProblems with WFMeasuring UsabilityDesign Model and User ModelSummary (continued)Make Things Visible (1/2)Provide Good MetaphorsDesign SpecialtiesPhysiology of the EyeSlide 12Implication of ChromostereopsisSlide 14The Aging ProcessHeuristics of Good GUI Design (Jakob Nielsen)Task Analysis QuestionsContextual InquiryPrinciplesWhat Should Scenarios Look Like?Slide 21Slide 22Exam 1 Grade Distribution and AnswersIS 485, Professor Matt Thatcher2Mean:81.24Std Dev: 12.59Median: 83Min: 42Max: 953Waterfall vs. PrototypingApplication DescriptionRequirementsSpecificationSystemDesignProductInitiationAnalysisDesignImplementDesignPrototypeEvaluate4Problems with WFWF lacks user’s perspective –technology-driven–focus is on the “client”, not the “user”–does not involve user until “implementation” stage»sees user role as finding “bugs” in the code or other minor problemsWF has no feedback (sequential, not iterative)–groups “hand off” discrete deliverables to the next group in the WF process»functional specs are frozen early in the process–high cost of fixing errors »increases by factor of 10 at each stage »iterative design finds these earlier5Measuring UsabilityEasy to learn–how long does it take for typical users to learn relevant tasks?Easy to remember–how easy is it to remember from one session to the next?Efficient to use–how long does it take to perform benchmark tasks?Minimal error rates–how many and what kinds of errors are commonly made?–if they occur, is good feedback provided so users can recoverHigh user satisfaction (subjectively pleasing)–confident of success–visually pleasing6Design Model and User ModelDesign ModelUser ModelSystem UIUsers gets model from their background, experiences and the design elements of the UIWhat if design & user models don’t match?7Summary(continued)Design ModelUser’s ModelSystem UIDesigner’s UI design choicesUser sees the design choicesUser interprets UI elements based on her characteristics and experiences8Make Things Visible (1/2)Affordances–physical properties (shape, texture, color, etc.) of an object that show functionality–appearance indicates how the object should be used without the need for words, labels, instructions, etc.–the user know what to do instinctively–examples: chair, scissors, staple remover, “buttons” (clickable), knobs, doors, British Rail partitionComplex things may need explaining, but simple things should not9Provide Good MetaphorsUse of a concept or word from one setting (e.g., real world) to convey meaning in another (e.g., digital world)–physical analogies (e.g., trash, spreadsheet, file cabinet)–cultural standards (e.g., color, words)Help reduce cognitive load for userUse of metaphors in design should be based on an understanding of user’s modelCommunicate that metaphor to the user through the UI10Design SpecialtiesInformation Architecture–encompasses information & navigation designUser Interface Design–also includes testing & evaluationInformation ArchitectureUser InterfaceDesignUsability EvaluationInformation DesignNavigation DesignGraphic Design11Physiology of the EyeLens is not color corrected chromostereopsis, produces 3D effectWhite LightLensRetina(separated wavelengths)12Focus on Blue LightLensRetinaFocus on Red LightLensRetina13Implication of ChromostereopsisSpectrally extreme colors produce eye strain (refocusing)14Physiology of the EyeComposition of the eye (retina), wavelength sensitivity65%2%33%RodsB&WConescolor15The Aging ProcessLens tends to yellow and absorbs shorter wavelengths–causing increased insensitivity to blueFluids in the eye suffer from reduced transparency–Perceive a lower level of brightnessImplications–don’t rely on blue for text or small objects–older users need brighter colors16Heuristics of Good GUI Design(Jakob Nielsen)H2-1: Visibility of system statusH2-2: Match between system and real worldH2-3: User control and freedomH2-4: Consistency and standardsH2-5: Error preventionH2-6: Recognition over recallH2-7: Flexibility and efficiency of useH2-8: Aesthetic and minimalist designH2-9: Help users recognize, diagnose, and recover from errorsH2-10: Help and documentation17Task Analysis QuestionsWho is going to use system?What tasks do they perform?What new tasks are desired?How critical are the tasks?How often do the users perform the tasks? What are the time constraints on the tasks?How are the tasks learned?Where are the tasks performed?How do users communicate with each other?What happens when things go wrong?18Contextual InquiryWay of understanding users’ needs & work practicesMaster – apprentice model allows user to teach us what they do!–master does the work & talks about it while working–we interrupt to ask questions as they goThe Where, How, and What expose the Why“Think aloud” and “probing questions”19PrinciplesContext–go to the workplace & see the work as it unfolds–people summarize in interviews, but we want detailsPartnership–master-apprentice relationship, yes; other models, no»avoid interviewer/interviewee (stops work)»set expectations at the start–partnership allows more apprentice interaction»alternate between watching & probing (withdraw and return)20What Should Scenarios Look Like?Say what the user wants to do (the goal), but not how the user would do it–allows comparison of different design alternativesScenarios should say who the users are–name names (John Berry)–characteristics of the users (e.g., job title) Should be specific, short, and in the user’s words–forces us to fill out description with other details that become important–provides enough information to complete the goal (e.g., John wants to purchase a blue polo shirt - size medium - for less than $50.00. Please help him find a product that matches this description and purchase it.)Should describe a complete job21ImageHeadlineHeadline HeadlineHeadlineRelate +PromoteRelate +PromoteRelate +PromoteRelate +PromoteHigh-Level Browse CategoriesSearchLogo + value propBrowseFold22Independent EvaluationsAggregated List of ViolationsIndependent Severity RatingsSummary Report with Avg Severity Ratings (SR)Final HE Report with SR and Fix


View Full Document
Download Study Notes
Our administrator received your request to download this document. We will send you the file to your email shortly.
Loading Unlocking...
Login

Join to view Study Notes and access 3M+ class-specific study document.

or
We will never post anything without your permission.
Don't have an account?
Sign Up

Join to view Study Notes 2 2 and access 3M+ class-specific study document.

or

By creating an account you agree to our Privacy Policy and Terms Of Use

Already a member?