> Due Date: Turnitin, 2pm, Friday 05 May, 2017 Faculty: Science and Technology Department: Computing & Technology Module Code: MOD002591 Academic Year: 2016/2017 Semester: 2 Content The following is suggested content and structure. Please delete comments in this gold colour, these are provided to help you to structure your report. Please find detailed below an example report structure. This is not compulsory. This is only a suggested structure. Within each section I have listed the requirements from the Module Guide. There is no new information, but this structure may help to organise your ideas. The following list of contents is linked to each of the headings that follow. To update this Table of Contents, click anywhere within the contents (so they all go grey), and hit the F9 key. If you update the entire table (for example if you have added sections, or changed the wording) you may need to select the Table of Contents and update the font style and size. 1. Introduction 2 2. Critical Exploration (15%) 2 3. User Needs Analysis (15%) 3 3.1 Persona 3 3.2 Scenario 3 3.3 Task Analysis 3 3.4 Environmental Analysis 3 4. Preliminary Design (10%) 4 5. Detailed Design (15%) 4 5.1 Decisions Relating to User Needs Analysis 4 5.2 Decisions Relating to Usability 4 5.3 Decisions relating to Cognitive Issues 4 6. Implementation (15%) 5 7 Evaluation (15%) 5 7.1 Cognitive Walkthrough 5 7.2 Heuristic Evaluation 5 8 Coherence 5 9 References 6 1. Introduction You may like to provide a brief introduction to your assignment. This is not compulsory. 2. Critical Exploration (15%) [Please delete the following text] In partial fulfilment of Learning Outcome 1: define and apply relevant theory to the process of determining a user needs analysis for a specific target application. Prepare a short critical exploration of your chosen area of interaction and usability. This should be approximately 500 words in length, and use no less than six academic resources (at least 3 journal articles). 3. User Needs Analysis (15%) In partial fulfilment of Learning Outcome 1: define and apply relevant theory to the process of determining a user needs analysis for a specific target application. Based on the secondary research, present a full and relevant user profile, task analysis ( for the current system or method of achieving the goals ) and environmental analysis. The user profile and task analysis should derive from your secondary research (the reading that you have done) and relate to your chosen system; generic creations will not be accepted. The source of any persona format used must be acknowledged accordingly (using an in-text citation at the point of use, and full reference at the end of your report). 3.1 Persona [Please delete the following text] Based on your own ideas (supported by academic literature) create a persona. Check documentation and examples available online for the suggested content, as the more detailed and specific, well-presented, personae are likely to gain more marks. Examples of online include templates provided on the VLE, as demonstrated during lectures. For additional marks, you may like to check what the academic literature says about personas (for example, whether to include a photograph or a silhouette). 3.2 Scenario [Please delete the following text] This is an informal ‘story-like’ description of how the user currently performs the task with the current system. The current system may be a physical system. You may like to check the resources on the VLE for examples of scenarios. Sharp et al. (2004) has a lovely example of a scenario at [http://www.id-book.com] Remember that the ISO definition of usability describes a specific user (the persona) performing a specific task; the scenario is the first step in identifying the current task. You may like to revisit the Week 3 lecture on The Problem Space. 3.3 Task Analysis [Please delete the following text] This represents your analysis of how the task is performed currently (the logical steps). This should derive from the scenario. The analysis should demonstrate the different paths available to complete the task. For example if a product is unavailable (substitute the word ‘product’ for something that makes sense within your system.) The task analysis is represented as an Hierarchical Task Analysis structure (time left-to-right, task subdivision top-to-bottom), examples of which can be found in tutorial exercises, and the Module Textbook. 3.4 Environmental Analysis [Please delete the following text] This may be less important to your system, but consider where the interaction takes place. The environment in which an interaction takes place will have implications for the interface design. For example, an interaction on a busy commuter train will differ from that in a quiet library room. 4. Preliminary Design (10%) In partial fulfilment of Learning Outcome 2, in particular: Design a corresponding interface for target application. Submit a storyboard as an early, low-fidelity prototype, to describe the interaction of the user with the system interface. Ensure that the following are detailed: information / action / navigation components. [Please delete the following text] Hand-drawn is acceptable. Check the lecture slides and additional resources on the VLE for more information. The storyboard documents how the interaction may look with your interaction design. The storyboard should document the specific task from start to completion. The task should be consistent with the Task Analysis above. The storyboard should include (and not be limited to) information important to the interaction, any actions performed, and any navigation components (local and global). The storyboard is relatively low fidelity, and is the first design through which to communicate the look and feel (the Conceptual Model) for the interface design. 5. Detailed Design (15%) 5.1 Decisions Relating to User Needs Analysis [Please delete the following text] In thinking about your User Needs Analysis above (the specifics of the persona, scenario, task analysis and environmental analysis), what decisions did you make about the design, and why? Try to avoid re-stating the goals, or what you did, or what the user needs to do to achieve their task. This section is about linking the needs of the user (persona or scenario) to decisions made about the design. For example, if the persona is identified as a frequent and knowledgeable user, then a design decision might be to include a shortcut in navigation, or screen content to allow efficient completion of the task. 5.2 Decisions Relating to Usability [Please delete the following text] In thinking about the usability, and user experience goals identified in Component 1, what options were available, and what decisions did you make about the design, and why? Again, please avoid ‘just’ re-stating the usability goals as first identified in Component 1. Instead, describe the decisions that you took in order to ensure that these goals are met. 5.3 Decisions relating to Cognitive Issues [Please delete the following text] In thinking about the Conceptual Model, and taking into account Cognitive Issues, what decisions did you make about the design, and why? What have you done in the design to take account of Cognitive Issues such as the use of metaphors or icons. How have you taken note of memory and attention limitations, and your user’s specific mental model? Try to avoid describing what you did in the design, we are interested in the options that you considered, and the decisions that you made, and the reasons why you made that particular decision. * *Please remember that a general unstructured description of the interface with passing mention of some of the above is not sufficient for work at this level. Work must make reference to theory within the domain of interaction design and usability, from academic sources, in order to achieve a passing grade. 6. Implementation (15%) [Please delete the following text] Provide between 3 and 5 high-fidelity, screen prints (more if necessary) to demonstrate a walkthrough of the one, specific task, identified earlier in this assignment. The Implementation should be consistent with the hierarchical task analysis, storyboard and the decisions in the previous section 5. These should be in colour and high-fidelity; this should look like the final interface looks. Marks will be lost for poor presentation. 7 Evaluation (15%) 7.1 Cognitive Walkthrough [Please delete the following text] An open and honest evaluation, using the Implementation screen prints above, and a description of the task (User Action + System Response). At each User Action – System Response, ask the 4 questions required by Dix (2004). You may find it easier to present this in table form. You may like to place the Cognitive Walkthrough itself into an Appendix, and summarise the results in this section. This requires the one specific task first identified in the scenario, analysed through the task analysis, first represented in the storyboard, and implemented in the screen shots in the previous section. 7.2 Heuristic Evaluation [Please delete the following text] Based on Nielsen’s 10 Heuristics (or the revised version presented in Week 7), summarise your evaluation here. Make clear which version of Nielsen’s heuristics you are using, and ensure the source is referenced by an in-text citation. (Some sources include explanatory text. If you choose to include the exact text, put this in quotation marks in addition to the citation). You may place the complete evaluation in an Appendix. Higher marks will be awarded for evaluations which identify the severity of the usability breach, and which use this to identify and prioritise further work. 8 Coherence [Please delete this text]. This is not a required written section. In marking your assignment, we will be looking for a coherent assignment. This means that it is possible to follow the design from the design’s inception to its implementation and evaluation. Evidence of logical progression and consistency through further reading of quality, academic and up-to-date, sources, scenario, task analysis (logical representation of the task), storyboard (initial graphical representation of the interaction to achieve the task), design decisions (based on previously identified usability and user experience goals), screen captures (to illustrate the task identified in previous steps), Cognitive Walkthrough (using the screen dumps to illustrate the process). 9 References [Please delete the following text] Citations to reputable, peer reviewed, up-to-date, academic resources should be included within the text, at the place where the idea is used, and attributed. This includes any illustrations. Where the phrase is identical, or substantially similar, it should be enclosed in quotation marks (in addition) to indicate that these words are not those of the author of this report. Organise References (the work you have cited), and the Bibliography (the work you have read, to help you, but not cited), in alphabetical order by the last names of the authors. Make sure that any websites have a full reference, and not just the URL. For a professional presentation, ensure that this reference section retains a consistent font size and font style with the rest of the report. Our University Harvard Referencing format requirements can be found at: http://libweb.anglia.ac.uk </h3> <div id="footer"></div> </html>