three deadlines check the assignment carefully please I am trusting you guys.
CMP81001_ Assignment2_ 2019_S3.pdf CMP81001 – Assignment 2 1 Assignment 2 Casual Online Game Due Dates: Part A: (Design Documentation) 11 pm Sunday Week 9 Part B: (Completed Tutorial/User Evaluation and Enhancement Design) 11pm Sunday Week 11 Part C: (Implementation of enhancements/User Testing/Completed Game) 11pm Monday Week 13 NOTE: The due dates for Part A and Part B above are progressive hand-ins - they allow us to provide you with a small amount of feedback on your game and make sure that you are on the right track. No actual marking will be done until after the final hand-in in Week 13. Description: You will showcase your User Experience design skills and develop a casual online 'jump and run' game to be deployed on the web. The core functionality of the game will be completed via a provided tutorial. You will design and develop a theme for the game, applying User Experience concepts to create an immersive and fun game using appropriate media and feedback elements. Additionally, you will find friends and family or others who are willing to be your 'end-users' who will help you to evaluate your product and give you feedback. This user-centred design approach will also utilise these users in the final product testing, providing you with their individual perspectives about your product. Objectives: The objective of this assignment is to create an enjoyable learning environment while covering a number of essential concepts that will aid you as a User Experience designer in future projects. You will learn to apply various skills, strategies and techniques covered within the provided tutorial as well as understanding the importance of having your users/clients provide input and evaluation as part of the development process. The task of developing a 'jump and run' game is broken into three project milestones to mirror real-world development where progress is required to be shown to the user/client at pre- defined dates. CMP81001 – Assignment 2 2 Details: Game Specification You will develop a 'jump and run' game by following the steps in the tutorial provided, using Google Web Designer (GWD). By following the 'jump and run' tutorial, your game will incorporate/include: � A front page; � The game play page; � A Help page; � A Credits page (may be included at the end when the user decides to quit, and should identify the source of resources not created by you). You will create a theme for your game and apply this to the tutorial. � Your theme should be applied to all visual elements of the game. � All interaction should be consistent with your theme. � Relevant feedback elements should be included that give your users a positive user experience. Your final game folder will include HTML pages, an assets folder with images and sounds and Javascript files created by GWD. User Evaluation and Testing � Users: You are required to find between 2 and 5 people who will act as your users (or potential clients) to give input and help you in your game development process. No more than one of these users can be your classmate. � User Evaluation: Once you have finalised your design documentation, you will present your design to your users and ask them to provide you with input and feedback about your design. You will find sample questionnaires for User Evaluation and Testing under the Assignment 2 details. You should select a range of appropriate questions for your users to answer when evaluating your game. � Responding to User Feedback: Responding to the input that you receive from your users, you are required to design an enhancement or change to your game. Enhancement Design Following and responding to the input that you receive from your users, you are required to design an enhancement which extends the functionality provided in the tutorial. This may include one of the following, depending on the input and feedback you received from your users: � an additional animation; � a splash animation page; � additional interactions; � the addition of a score or timer; � the addition of an enhancement of your choice. User Evaluation and Testing � User Testing: Before final hand-in of your game, you need to ask your users to test your product. As for the User Evaluation, create a Testing Questionnaire from the CMP81001 – Assignment 2 3 sample questions for testing under the Assignment 2 details. Part A: Design Documentation (10%) Your design document should include a Concept Paper and a Functional Specification with at least the sections listed below. 1. Concept Paper *** • Introduction • Background • Description • Genre and target age group 2. Concept Map - showing your ideas for your theme including graphics, interactions, etc. 3. Functional Specification *** • Simple navigation shown in a flowchart • Storyboards - Screen layout(s) showing your theme implementation; 4. Wireframe / Prototype (optional) - you may provide a link to a 1-2 pages wireframe of your design if you wish. This is optional due to the fact that some of your chosen wireframe products are on 30-day trials and may not be still available. However, as 3 suggested alternate products were suggested in this unit, and are simple to use, you may choose to create a prototype. You may prefer to present your designs to your users in this form. *** Please ensure that you read Topic 8 for details of each of these sections. The documentation should all be included within ONE Word document with an appropriate front page added. Name this file clearly, e.g. cseton10_Ass2_A.docx, and submit this via MySCU. Part B: Completed Tutorial, User Evaluation and Enhancement Design (15%) Tutorial: all of the following should be working as required: � Viewing player instructions (i.e. help); � Jump and Run game - appropriate actions to user input, able to be terminated; � All bugs eliminated. User Evaluation: � User evaluation forms filled out by your users; Enhancement Design: � Any necessary storyboards to show enhancements; � Optional pseudocode for your enhancements showing decisions, processes and structure; � Must detail desired functions, inputs, outputs, and any additional media needed. You will need to submit any new flowcharts, storyboards (if necessary) and documentation; along with your game folder via MySCU. Only include those storyboards/flowcharts/other CMP81001 – Assignment 2 4 documentation that show changes from Part A. You should zip up all the required files and name this file clearly, e.g. cseton10_Ass2_B.zip. Part C: Implementation of Enhancements, User Testing and Completed Game (15%) Final Product � Implement the enhancements following your users' feedback and input about your game. User Testing: � User testing forms filled out by your users; Please submit the full documentation for your game (includes previous two hand-ins) and your entire game folder (html and Javascript file(s) and any other associated or necessary files). You should NOT submit any files that are not necessary to the operation of your game. You should zip up all the required files and name this file clearly, e.g. cseton10_Ass2_C.zip. Referencing You may use other people's code in your assessment, but it is imperative that you acknowledge that it is not yours. The inclusion of a comment indicating the source is all that is required. For example: /* ***************************************************** Original source code by
or from Modified by on *******************************************************/ Include any of your modified code in between lines like this - which helps to identify your work additional to the tutorial: /* ******************** Modified ***************************/ // your code goes here /* ******************** end modifications ******************/ Questions_User(2)(1).pdf CAL Evaluation Template Questionnaire User (A) Biomedical Multimedia Unit University of Melbourne Designed for a CAL package user Designed to improve the CAL package while it is under development Quantitative Introduction: Instructions: 2.1 Generally the content was clearly and logically organised 2.2 Important information or key concepts were easy to identify on the screens 2.3 There was a lot of distracting or irrelevant information in the package 2.4 The flow or sequence of information from screen to screen was confusing 2.5 The content moved from more simple to more complex concepts 2.6 Generally there was too much information on each screen 2.7 The information which was presented was comprehensive 2.8 I found the information in the package repetitive 2.9 I thought the content was pitched at an appropriate level 2.10 Generally the concepts and issues which were presented were well explained 1.1 From the start it was clear what I was going to do in the package 1.2 From the start it was clear what the aims of the package were 1.3 I feel I needed to know more about the content area to get the most out of this package Biomedical Multimedia Unit /2 strongly agree neutralagree strongly disagreedisagree 3.1 The package provided feedback that was meaningful to me 3.2 I thought the package was interactive 3.3 The package encouraged me to reflect on the content area 3.4 The feedback given to me did not really help me understand where I went wrong 3.0 Interactivity strongly agree neutralagree strongly disagreedisagree strongly agree neutralagree strongly disagreedisagree strongly agree neutralagree strongly disagreedisagree strongly agree neutralagree strongly disagreedisagree strongly agree neutralagree strongly disagreedisagree strongly agree neutralagree strongly disagreedisagree strongly agree neutralagree strongly disagreedisagree strongly agree neutralagree strongly disagreedisagree strongly agree neutralagree strongly disagreedisagree strongly agree neutralagree strongly disagreedisagree strongly agree neutralagree strongly disagreedisagree strongly agree neutralagree strongly disagreedisagree strongly agree neutralagree strongly disagreedisagree strongly agree neutralagree strongly disagreedisagree strongly agree neutralagree strongly disagreedisagree strongly agree neutralagree strongly disagreedisagree 1.0 Introductory Objectives and Directions 2.0 Content and Structure 4.1 I found it easy to navigate my way around the package 4.2 There were times when I was confused about my location within the package 4.3 Sometimes I found it difficult to locate pieces of information I had previously located 4.4 The buttons and links were easy to understand 4.5 I found the navigation system easy to understand 5.1 Colour was used consistently in the package 5.2 Colour was used well in the package 5.3 The use of colour highlighting on the screen was helpful TOO LITTLE TEXT TOO MUCH TEXT READABLE UNREADABLE GRAPHICALLY CLEAR GRAPHICALLY FUZZY LABELLED CLEARLY NOT LABELLED CLEARLY RELEVANT TO THE TOPIC IRRELEVANT TO THE TOPIC HELPED MY