Class Notes (811,170)
Canada (494,539)
IAT 201 (8)
Lecture 4

IAT201 Week 4.docx

7 Pages
Unlock Document

Simon Fraser University
Interactive Arts & Tech
IAT 201
Brian Fisher

IAT201 Week 4 SWOT analysis Strengths What advantages do you have over the competition? E.g. First-mover advantage, channels to market, IP protected, wizard programmer, killer design, etc. Weaknesses What disadvantages do you have versus the competition? E.g. No money, lack of above Opportunities Where can you potentially generate business and path to profit? E.g. Direct sales, sales through OEM/VARs Threats What changes in the environment can threaten your success? E.g. Another company is interested in doing the same thing Internal External Enhance What the company is good at Opportunities to pursue -financials -positives on the horizon -marketing Migrate What the company is not good at Threats to defend against -major problem areas -potential hazards on the horizon How it applies to design Any design project requires you to not only make decisions but also to get buy-in from stakeholder-this is why software engineering models like System W consider stakeholder interests in their design cycle Initial go-no-go decision is followed by ongoing debate about scope of the project, resources, deadlines etc. -very similar to what takes place in a start-up Design has to contend with engineering and business interests to justify taking on risk in development and increased cost necessary to deliver a great product The problem statement Supported activity -what tasks or processes are involved and how do they support the activity User(s) -who does the activity and what are their characteristics Level of support -what usability factors will we consider important Form of solution -what technologies can we employ and how can they be combined into a system Design a [form of solution] for [level of support] [supported activity] by [users] E.g. Scheduling Meetings Supported activity -locating a jointly available meeting time Users -people with tight schedules who need to participate in meetings of 2 or more participants -people with frequent online access Level of support –easy to respond quickly and completely –require no iteration –respect privacy (E.g. posting shared calendars) Form of solution –online meeting scheduler Design an online meeting scheduler for easy, no-iteration scheduling of meetings by two or more participants Personas-a documented set of archetypal people who are involved with a product or service Why Personas Tools for understanding & communicating user behaviors, needs, desires, & contexts -help to empathize & visualize who customers are, and keep them in mind while designing -help set priorities, guide, communicate, build consensus/common language What should be included Make up a full name Behavior Patterns-what does this person do on the interface? (actions & behaviors) Goals & Motivations-why do they do it? Experience goals-how does or does not they want to feel when using the interface? End goals-what would they want to accomplish with the product to be happy? Life goals-what does the product mean to the user? Expectations Contexts Relevance (primary/secondary/marginal) -make persona real & credible (name & picture, quotes/titles/motto, demographic data) -humanize persona to make it concrete, imaginable, visual, memorable, empathizable Imagine a set of individual users who span the possibilities of those you expect -give them names, personalities, jobs, hobbies -lifestyles, needs and interests -try to base them on people you have real experience with -imagine each member of your cast using your interface, and what they would want from it Context of Use-situational factors that influence the use and usability of a system Environmental/physical -space? time? dusty? noisy? vibration? light? temperature? humidity? water? Organizational -social network, management and organizational pressures, and work processes, hierarchy, IT department’s attitude and remit, user support, communications structure and infrastructure, availability of training Technical/system factors -network connectivity, system configuration, system stability Social -sharing of files, of displays, in paper, across great distances, work individually, privacy for clients, family conflicts, career aspirations, economy, ethical standards Describing the human activity Tasks -basic unit of human activity -made up of a sequence of steps (usually linear) -has a specific, single goal Processes -a linked set of tasks -tasks may be performed in serial or parallel -the process has one or more higher-level goals -tasks in a process depend on varying resources -dependencies often exist among the tasks A Hierarchic task description A sequence of steps makes up a task -steps are linearly ordered -steps can be carried out one after-the-other -all steps contribute to the parent goal of the task Tasks may be subtasks of higher level tasks -subtasks may have a sub-goal -subtasks can be carried out one after-the-other -notation can be either textual or graphical -group steps under task goal Dependencies among tasks “Task objects” are resources re
More Less

Related notes for IAT 201

Log In


Don't have an account?

Join OneClass

Access over 10 million pages of study
documents for 1.3 million courses.

Sign up

Join to view


By registering, I agree to the Terms and Privacy Policies
Already have an account?
Just a few more details

So we can recommend you notes for your school.

Reset Password

Please enter below the email address you registered with and we will send you a link to reset your password.

Add your courses

Get notes from the top students in your class.