1. Personas & Goals User Interface Design

2. Assignment You can use external libraries The XML files are up The first lecture got recorded Other questions? SWEN303: User Interface Design, 2015

3. Users Who are they? What do they want? Why do they want it? How will they use it? When will they use it?

4. Personas Composite User Archetypes. Personifications of groups of related users. Designed to capture developer empathy. Leads to designing for persona goals. Alan Cooper, Robert Reimann, Dave Cronin “About Face 3: The Essentials of Interaction Design”, published by John Wiley & Sons, 2007 SWEN303: User Interface Design, 2015

6. Behavioural Variables Example: music listening Frequency of listening to music. Listens to music to relax versus listens to music to exercise. Listens to anything versus very specific tastes. SWEN303: User Interface Design, 2015

7. Other Considerations Domain versus Technical Expertise. e.g. music geek versus tech geek. Environmental. e.g. large versus small company. e.g. different cultures. SWEN303: User Interface Design, 2015

8. Strategies Goals over tasks. Problem description over solution advocacy. Storytelling over abstract discussions. SWEN303: User Interface Design, 2015

9. Goals “Goals are not the same as tasks. A goal is an end condition, whereas a task is an intermediate step that helps to reach a goal. Goals motivate people to perform tasks.” About Face 2.0, Reimann & Cooper SWEN303: User Interface Design, 2015

10. Goals User Goals: Life goals End goals Experience goals Non-User Goals: Customer goals Corporate goals Technical goals SWEN303: User Interface Design, 2015

11. Persona Types Primary Secondary Supplemental Customer Served Negative SWEN303: User Interface Design, 2015

13. Scenarios - Context Black-box design. Focus: goals, not interface specifics. Captures the environment, day-in-the-life aspect of the system interacts with the personas’ lives. SWEN303: User Interface Design, 2015

16. What is XML? XML is a human readable data format XML is a tree It must contain two things An XML declaration An element We are using TEI which is a specified XML schema XML is like violence: if it doesn’t solve your problem, you aren’t using enough of it. - Unknown

17. XML Declaration XML declarations are very simple, and have the following form: <?xml version="1.0" encoding="UTF-8" standalone="yes"?> Note: encoding and standalone are optional

18. XML Elements Can be empty Can contain text It is very green Can have attributes Can contain other elements Or any mixture I'm pretty

19. An Example XML Document Roma Klapaukh 7 Stuart Marshall INTEGER_OVERFLOW

20. JavaScript JavaScript is a widely used programming language which runs in browsers It is NOT the same in all browsers The syntax is very similar to Java – semicolons claim to be optional We’ll be using Node.JS (available on the lab machines) SWEN303: User Interface Design, 2015

21. JavaScript variables JavaScript variables should be declared with the var keyword You should always declare variables at the start of a file or function There are only three scopes: global, function, and exception “use strict”; forces variables to need to be declared var data = [10, 20, 30, 40, 50]; var people;

22. JavaScript functions function add(z,c) { return z+c; } var f = function (z,c) { return z+c; }; (function (z,c) { return z+c; })(); Functions are first class No explicit types Functions do not check the number of arguments

23. Readings “About Face 3: The Essentials of Interaction Design” Cooper, Riemann & Cronin. Wiley Publishers, 2007 The Fable of the User Centered Designer David Travis, UserFocus Ltd SWEN303: User Interface Design, 2015