DECO2300/7230 Digital Prototyping Arindam Day : [email protected] Page 1 of 8 DECO2300/7230 Digital Prototyping Semester 2, 2019 Prototype Suite Type: Suite of prototypes in variety of formats Weighting: 70% DECO2300 65% DECO7230 Other marking information: Failure to attend mandatory Prototype Testing sessions will result in a grade of zero for the corresponding deliverable. Deliverables Due Dates Weight (of Suite) Prototype Testing (mandatory) Submission Video Prototype Week 4 Workshops (Thurs 15/08 & Fri 16/08) Prototype on day of testing Turnitin 10:00am 19/08/2019 25% Interactive Prototype I Week 7 Workshops (Thurs 05/09 & Fri 06/09) Prototype on day of testing Turnitin 10:00am 09/09/2019 25% Interactive Prototype II Week 10 Workshops (Thurs 26/09 & Fri 27/09) Prototype on day of testing Turnitin 10:00am 08/10/2019 25% Interactive Prototype III Week 13 Workshops (Thurs 24/10 & Fri 25/10) Prototype on day of testing Turnitin 5:00pm 25/10/2019 25% Overview In this course, you will develop a number of prototypes as a means of evaluating conceptual & functional aspects of an idea. Your prototypes will be used to evaluate aspects of your responses to the stimuli described below. • Video prototype – Kickstarter or explainer style video (see page 6) • Interactive prototype I – basic interface/interactive prototype (see page 7) • Interactive prototype II – physical input prototype (see page 8) • Interactive prototype III – refinement/rethink/iteration OR dark-horse prototype (see page 9). The Challenges In order to generate concepts for use in the prototyping process, you are asked to respond to one of the challenges below. All responses should consider novel/alternative methods of interaction as part of the concept: moving beyond standard touch/swipe, keyboard & mouse interactions. For inspiration on what this might entail, look to tech genres such physical computing, tangible interfaces, wearable computing, internet of things, ambient computing, embodied interaction, augmented reality. 1. Social Interventions Our everyday world is filled with potential for embarrassment, awkwardness &/or social faux pas. Take a moment to think about the behaviours of others that irritate you or that you exhibit that might irritate others. These could be obnoxious or insidious, silly or serious, unique to you or a well established social faux pas. DECO2300/7230 Digital Prototyping Arindam Day : [email protected] Page 2 of 8 DECO2300/7230 Digital Prototyping Semester 2, 2019 Your challenge here is to generate concepts for novel technology that allow for the subtle, or not so subtle, correction or transformation of socially unacceptable or awkward behaviours. These interventions can be made against the carrier, or those around them. The device should provide at the least a basic user interface – either in-device or by connecting with another personal device. 2. Augmenting Everyday Life Everyday we encounter little things that we wish were better, different, enhanced, connected. Your challenge here is to generate concepts for devices/interactions/experiences that enhance or augment the little things in life. These can be practical, playful, useful, silly, small-scale or large – it’s up to you. They can connect you with other people, near or far, strange or familiar. It might be letting a loved one know you are thinking of them, or connecting with a random stranger over a shared hatred of queues. Remember these concepts should incorporate a physical/tangible element as well as a basic user interface (either in the device itself, or by connecting with another device). 3. Make it a Game Using the statement provided to you by the Game Generator at http://orteil.dashnet.org/gamegen , design a game that encapsulates those concepts & ideas. Your game should combine both physical and digital media and consider alternative forms of interaction – specifically non-traditional, novel physical interactions (no keyboard, mouse or existing game controller). 4. Make it Better This is your opportunity to solve a problem, to make the world a better place for someone or for many – but NOT yourself. Your challenge here is to generate concepts for novel technology or for technology interventions that might provide access and/or reduce negative impacts for marginalised groups or communities; boost engagement with and/or raise awareness about a particular issue or problem; to simplify a complicated process … the possibilities are endless. Your concepts should incorporate both physical/tangible form and digital form. Prototype Process Once you have an initial concept, you will need to, for each of the prototype deliverables: 1. Decide what aspect of your idea you want to test & how you will test it using that prototype (Testing Agenda) 2. Decide what form the prototype will need to take to enable you to test that aspect ensuring it meets the requirements for each prototype deliverable. This will be informed by what you want to test and how you plan to test it in order to get the most useful feedback from participants. 3. Build the prototype 4. Document (in your journal) the process of designing and creating the prototype 5. Conduct testing and evaluation of your prototype in the workshop session in the week it is due. Testing sessions are mandatory for each prototype & failure to attend these will result in a zero mark for that deliverable. 6. Submit a Statement of Delivery (see page 3 for document requirements) & prototype files to Blackboard. 7. Iterate based on the outcomes of your evaluations – go back to Step 1 & repeat. DECO2300/7230 Digital Prototyping Arindam Day : [email protected] Page 3 of 8 DECO2300/7230 Digital Prototyping Semester 2, 2019 Prototype Submission Requirements For each of your deliverables, you are required to submit: 1. Your interactive prototype/s as a a single .ZIP file to Blackboard to the Assignment link on Blackboard: I. Development files (ie. Unity, HTML/JS/CSS …) II. Any additional required assets (images, video, audio etc) III. If you have multiple prototypes (variations), these should be placed into individual directories & clearly explained in the Statement of Delivery 2. Your Statement of Delivery in PDF format to the TurnItIn link on Blackboard NOTE: for the Video Prototype, you only need to submit your Statement of Delivery to Blackboard – the link to your video online must be included on the front page of your S.O.D. Please name .ZIP files and Statement of Delivery PDF files with your surname and full 8 digit student number (ie. JONES_43211234.zip). Please use only the ZIP format for compression (not .rar, not . 7zip – just .zip) Statement of Delivery Requirements (for each prototype) Before creating a prototype, you should have a clear idea of your: • Testing Agenda – what questions or issues you are seeking to gather information about; what aspects of the concepts you intend to test using the prototype. • Testing Process – what process you will follow when testing so that each time you test with a new user you follow the exact same process; • Evaluation Method – how you are going to conduct the evaluation so that you collect the information you need; Your Statement of Delivery will document this information, describing each prototype, how it allows you to achieve the above and your evaluation outcomes. The document needs to include the following content: • Statement of Originality: a statement identifying and acknowledging the sources of content used in your prototype (see the accompanying document Statement of Originality for how to do this). • Basic Details: Full name, student number, practical session & tutors name & document title. • The Concept: A brief description of the overall/original idea. Unless significant changes have occurred to the concept, this can be achieved by linking to a previous description of the concept (ie. if you have a blog entry, you can provide a URL to the relevant entry). Regardless of changes, a minimum one sentence “blurb” should be included as a reminder for markers. • Recap: For each interactive prototype, key changes that have occurred in re
sponse to work carried out between now & the last round of testing should be described here. This might describe changes to the idea, to the approach to testing, to the form of the prototype, if the aspect tested differs from original plans. The recap should highlight the iterative nature of the process. (Note: this is not required for the Video Prototype Statement of Delivery) • The Purpose of this testing round : A description of the aspect/s of the concept that are to be evaluated and what you hope to find out through people using the prototype. Including a discussion of what was important to include & exclude in the construction of the prototype, in order to meet the requirements of the evaluation. DECO2300/7230 Digital Prototyping Arindam Day : [email protected] Page 4 of 8 DECO2300/7230 Digital Prototyping Semester 2, 2019 • The Form of the prototype: A description of the prototype itself. Remembering that prototypes are not always representative of the finished product. Screenshots, photographs of physical artefacts, interaction diagrams should be included here – these should also be accompanied by explanatory text. • The Testing Approach A description of what you asked the users to do, what feedback you asked for and how you asked it. This should cover the agenda, process & method for evaluation. • Evaluation Outcomes & Reflection What were the results of the evaluation? What conclusions can you draw about the concept from the results? Data collected as part of the testing process should be synthesised & presented as an overall analysis. If required, you may include your raw data as a appendix. You should also describe the changes will you make to your concept in response to the evaluation. And finally, discuss whether the prototype you created was sufficient to test what you wanted to test. • Testing Plan: For each remaining prototype, you should describe what aspects of your concept you intend to test using the remaining prototypes. Note that you need to be specific in your descriptions & relate them directly back to detail within your design concept. The aim of this is for you to plan for the remaining prototypes with the understanding that changes will be made in response to the evaluation of each. You will have the opportunity in future Statement of Delivery documents to discuss where you have deviated from this original plan and why. (Note: this is ONLY required for the Video Prototype Statement of Delivery) Criteria • Prototype is clearly described in terms of its intentions, purpose & form and appropriate to the testing agenda. • Testing approach (agenda, process & evaluation method) is clearly outlined. • Evaluation outcomes are clearly described and discussion of suggested improvements is insightful & relevant to outcomes. • Well-written with a clear flow of concepts. • All other required content is present with sufficient, relevant detail. • For video prototype SOD only: Intention for each remaining prototype is clearly described and specifically related back to the original concept. DECO2300/7230 Digital Prototyping Arindam Day : [email protected] Page 5 of 8 DECO2300/7230 Digital Prototyping Semester 2, 2019 Video Prototype (Week 4) Due dates & submission Tested in Workshop Sessions (Thursday 15 August and Friday 16 August) Statement of Delivery (PDF) to Blackboard by 10:00am Monday 19 August Video YouTube/Vimeo link to be posted to Workshop Slack channel BEFORE your testing session See page 3 for full description of prototype submission requirements. See page 3 for a full description of Statement of Delivery requirements. Description Prototypes can be used not only to test implementation of an idea or part of an idea, but the idea itself. In this task, you will produce a video that communicates your idea/s for one of the above challenges described on page 2. This concept will be used as the basis for your remaining prototypes. This assessment is designed to assess: • skills in the use of technology & method used to create the video • ability to clearly communicate design ideas • ability to reflect critically on appropriateness of prototype for testing intended idea Video Requirements Your video should be between 1 minute 30 secs and 3 minutes long and should: • Describe your concept: • What does it do? • What problem is it solving? What challenge is it meeting? What opportunity is it exploiting? Simply, why does it exist? • Who would use/interact with it? • How would they interact with it? What would be needed for that interaction? • Demonstrate your skills in creating the video • choosing &/or creating content that is suitable for both video & for concept • ensuring clarity in image & audio production It is not necessary to create polished images in Photoshop, scanned & edited copies of sketches can be used for visual elements within your video. We do not expect you to use production-standard cameras in the filming of your video, however we do expect you to follow the tips/guides available on Blackboard to maximise the quality of both your imagery & audio. All videos must include closed captioning for content-based audio. YouTube makes this process simple through its auto-transcribing & script uploading tools – you will have to confirm that the transcription is accurate. Criteria • Video clearly & effectively communicates the concept • Video production is of a high standard (focussed, well lit and clearly discernible imagery; crisp & clear and easily discernible audio) DECO2300/7230 Digital Prototyping Arindam Day : [email protected] Page 6 of 8 DECO2300/7230 Digital Prototyping Semester 2, 2019 Interactive Prototype I (Week 7) Due dates & submission Tested in Workshop Sessions (Thursday 5 September and Friday 6 September) Prototype Files (.zip) to Assignment link on Blackboard within 2 hours of your testing session. Statement of Delivery (PDF) to Turnitin link on Blackboard by 10:00am Monday 9 September See page 3 for full description of prototype submission requirements. See page 3 for a full description of Statement of Delivery requirements. Description You will create a interactive prototype of your application interface that considers the key user functions, tasks and/or interactions. You should not be aiming to implement a complete or polished interface. However, functionality should be completed to a level that allows for clear understanding of the elements being evaluated. When deciding on the aspect to be prototyped, consider what it is you want to know about how people will engage/interact with the interface. This will help to decide A) your testing approach and B) the requirements for your prototype. You can create multiple prototypes to evaluate variations in functionality, task flow and/or interaction methods. As this is an early prototype, the design of the interface is not expected to be polished and it is acceptable to use placeholder or wireframe graphics to represent interface elements. Criteria In addition to the criteria outlined for the Statement of Delivery, this prototype will be marked according to the following criteria: • Highly appropriate prototype for testing intended interactions • Functionality completed to a standard that allows unimpeded testing of interactions • Demonstrates technical proficiency in programming DECO2300/7230 Digital Prototyping Arindam Day : [email protected] Page 7 of 8 DECO2300/7230 Digital Prototyping Semester 2, 2019 Interactive Prototype II (Week 10) Due dates & submission Tested in Workshop Sessions (Thursday 26 September and Friday 27 September) Prototype Files (.zip) to Assignment link on Blackboard within 2 hours of your testing session. Statement of Delivery (PDF) to Turnitin link on Blackboard by 10:00am Tuesday 8 October See page 3 for full description of prototype submission requirements. See page 3 for a full description of Statement of Delivery requirements. Description You will develop a prototype to evaluate the intended physical (non-digital) inputs/outputs of your application. Physical interactions should be appropriate to your application concept and should be prototyped to a standard that
allows for useful evaluation. Remember that your prototype can be an approximation of the intended physical interaction. It is a means of testing out the essence of an idea for physical interaction and doesn’t necessarily have to implement the final intended form. When deciding on the form of the prototype, consider what it is you want to know about how people will engage/interact with the interface. You might want to test the physical interaction/input method separate to the interface, or you might want to test how that physical input is represented back to the user through the interface. This should be outlined in your Statement of Delivery. You can create multiple prototypes to evaluate variations in physical inputs, interaction methods and/or interface response to input. As this is an early prototype, the design of the interface is not expected to be polished and it is acceptable to use placeholder or wireframe graphics to represent interface elements. Criteria In addition to the criteria outlined for the Statement of Delivery, this prototype will be marked according to the following criteria: • Highly appropriate prototype for testing intended interactions • Novel approach to physical interaction using appropriate physical input/output • Functionality completed to a standard that allows unimpeded testing of interactions • Demonstrates technical proficiency in programming DECO2300/7230 Digital Prototyping Arindam Day : [email protected] Page 8 of 8 DECO2300/7230 Digital Prototyping Semester 2, 2019 Interactive Prototype III (Week 13) Due dates & submission Tested in Workshop Sessions (Thursday 24 October and Friday 25 October) Prototype Files (.zip) to Assignment link on Blackboard within 2 hours of your testing session. Statement of Delivery (PDF) to Turnitin link on Blackboard by 5:00pm Friday 25 October See page 3 for full description of prototype submission requirements. See page 3 for a full description of Statement of Delivery requirements. Description Your final prototype can take one of the following forms: • Refinement/redesign of original interactions from either I or II. If feedback received in testing was negative or indicated that aspects needed serious reconsideration, use this prototype to iterate & refine according to that feedback. • Dark-horse prototype. Dark-horse prototypes are about testing the impossible, implausible & down-right outrageous. If you feel that your concept is suffering from a lack of inspiration, you could create a dark-horse prototype for your concept that explores an implausible scenario. • Addition of new features OR testing of features previously not tested. If your feedback was mostly positive from prior testing, this final prototype can be used to test additional aspects of your concept. When deciding on the form of this final prototype, consider what more you would want to know about users perceptions of your application. Are there lingering issues that need solving based on previous evaluations? Is there something you haven’t yet been able to test that you feel would be important to the concept development? Criteria In addition to the criteria outlined for the Statement of Delivery, this prototype will be marked according to the following criteria: • Highly appropriate prototype for testing intended interactions • Prototype offers new insights into the concept (refinement, addition, rethink) • Functionality completed to a standard that allows unimpeded testing of interactions • Demonstrates technical proficiency in programming
