Ch 5 Specification page 1CS 368 Context Specification one of the most commonly cited reasons for an IT project failure is unclear objectives and requirements analysis is the activity of understanding and identifying a problem specification is the documentation of the analysis previously done by your instructor identify the stakeholders self service kiosk at Meijer identify usability expectations easy to use quick to learn highly secure enjoyable needs / functionality a rationale one sentence problem statement feature list feasibility target platform cost time

Ch 5 Specification page 2CS 368 Problem Definition identify the situation of concern finding an item at Target long lines a ticket counters there is too much litter on campus students need to pay for printing on campus One Sentence Problem Statement the activity to be supported the user the level of support a form of solution / platform Design a cash operated machine for quick and easy purchase of train tickets by passengers. Find a way to help delivery drivers reach their destinations without getting lost so often. Design an interactive system for genealogical researchers. Design a system to support concert pianists in giving recitals. Group Activity write problem statements

Ch 5 Specification page 3CS 368 User Scenarios collect problem scenarios from the stakeholders informal but detailed stories that describe typical users and their goals multiple scenarios can reveal characteristics of the environment and user expectations. Group Activity multiple scenarios for someone who needs to book travel arrangements find information on the Allendale campus

Ch 5 Specification page 4CS 368 Task Analysis (5.3) collect information from a number of stakeholders or existing systems surveys observations interviews review existing documentation include a stakeholder on the design team meticulously define all user tasks and sub-tasks as a hierarchy avoid descriptions of UI look and feel task descriptions should begin with a verb perhaps supplement an outline with a detailed description of each task consider the following is the sequence important? what is the necessary user input? what are the results / outputs? how can the tasks fail and what will be the result? error handling? specific usability expectations?

Ch 5 Specification page 5CS 368 Task Analysis (continued) use case models are popular with some professionals stick figure agents and oval tasks not a fan myself other experiences? failure to spend sufficient time and resources on this phase will cost you later! Group Activity make a PBJ sandwich document a task analysis for course registration

Ch 5 Specification page 6CS 368 User Profiles describe the intended users age gender physical characteristics frequency of use motivation required for work fun game optional for a customer computer experience novice occasional expert (power user) Poll workers average age is 72 limited computer experience

Ch 5 Specification page 7CS 368 Specification Document title page rationale one sentence problem statement functionality list user profiles usability expectations high level goals user scenarios (at least three) detailed task hierarchy (numbered outline)