IDEA9101 IDEA LAB 1 Assessment Guidelines 2020 Assessment 1: Urban Prototyping Festival 50% (individual) Description: The goal of the first assignment is for each student to demonstrate what they have learned in class by designing and implementing a novel interactive audio-visual system for urban environments, based on the ones developed in the lab exercises (Labs 01-10), which includes computer vision, wireless communication over network, sounds, data visualisation and simple media architecture prototyping. The concept for the system is up to you – it does not have to be related to your IDEA Studio group project. You can research existing work, precedents and literature to inform your concept. You should document your conceptual design, the working system and your development process as follows. Deliverables: • Code (Processing, Max, etc). • TouchOSC layout (if used), as well as any other relevant technical component. • Short demo video (3 minutes max) of working system, explaining design/implementation and process documentation. Submission instructions: • The deliverables should be collated as sections in a PDF document. Please submit any code as separate files. • Video should be hosted online (Vimeo, YouTube or shared via Dropbox, One Drive, Google Drive, etc.), with hyperlink submitted in the PDF document. • Submit the PDF document to the Assessment Submission menu on Canvas – click Assessment 1. Due Date: (Week 9) Wednesday 29 April, 11:59 pm Please read the standards-based assessment rubric for guidance on levels of performance. Note that the grade descriptors must be interpreted relative to each other. IDEA9101 IDEA LAB 1 Assessment Guidelines 2020 ASSESSMENT 1 RUBRIC Grade descriptor Fail 0-49 Pass 50-64 Credit 65-74 Distinction 75-84 High Distinction 85-100 Criterion 1. Conceptual design (30%) Lack of concept. Inadequate description of designed function and behaviour. Brief sketch and description of a basic concept. Simple explanation of designed function and behaviour, including range and type of inputs and outputs. Documentation contains essential elements, but may have some errors of notation. Description of concept clearly addresses how the device relates to the users and their surrounding physical environment. Designed function and behaviour communicated through diagrams, as well as text. Documentation contains all necessary elements, with correct notation. Description of concept is informed by existing precedents or literature. Designed function and behaviour communicated through carefully constructed diagrams, in concert with textual explanations. Relation of device to users and their surrounding physical environment clearly expressed. Novelty of concept is positioned within existing work. Interesting and complex application, addressing issues beyond the systewm-user. Concept is presented as high quality visual mockup, with clear relationship between user, system and surrounding environment. Documentation is flawless and easily comprehensible. 2. Technical competency (30%) Interactive system and code do not work correctly. Alternatively, system works, but code is adapted from elsewhere without justification. Can demonstrate a basic working system, with minimum interaction and associated Processing/Arduino code: a setup in which the sensor perceives a stimulus, resulting in one isolated and unsurprising output response. Code is a reasonable adaptation of existing code, with explanation about why it has been used. Video proof of working system. Can demonstrate a working system, with more than the minimum interaction and associated Processing/Arduino code. Code is unique, or a reasonable adaptation of existing code, with explanation about why it has been used. Video proof of working system. Can demonstrate a working system with a degree of complexity. Code is unique, with convincing explanation about the decisions made during development. Video proof of working system documenting all features and use case scenarios. Can demonstrate a working system with a high degree of complexity. Code is unique, with convincing explanation about the decisions made during development. Video proof of working system documenting all features and use case scenarios. Designed function and behaviour also demonstrated through systematic testing. 3. Process documentation (30%) Missing or unconvincing evidence of development process. Basic level of documentation of development process, containing some diagrams and photographs of working system, with minimal reflection and explanation of technical issues. Documentation of development process clearly shows the main phases of building the system and code, with some reflection and explanation of technical issues. Documentation of development process clearly shows the main phases of building the system and code, the critical decisions, with solid reflection and explanation of technical issues. Thorough and systematic documentation of development process, showing clear progression through the phases of building the system and code, informed by regular testing and experimentation. Strong knowledge of implementation demonstrated by insightful resolution of technical issues. 4. Peer feedback (10%) No peer feedback provided Basic and non-relevant peer feedback provided, with no analysis. Basic analysis and critique of work reviewed. Substantial analysis and critique of work reviewed, providing pros and cons, as well as points for improvement. Substantial analysis and critique of work reviewed, providing pros and cons, points for improvement, suggestions of how to improve, and links to external references supporting the critique. IDEA9101 IDEA LAB 1 Assessment Guidelines 2020 Assessment 2: IDEA Studio Responsive Environment – Technical Implementation 30% (group) Description: The goal of the second assignment is to implement the technical components required for the IDEA Studio project on responsive environments. It should make use of the equipment, skills and techniques learned in IDEA Lab to create one or more systems that fulfil the Studio brief (please consult the Unit of Study outline for IDEA9102). Implementations may take any creative use of the material learned in the IDEA Lab. Most importantly, each student should be able to strongly justify the reason for the set of technologies used in the context of the IDEA Studio project. Designs that illustrate important aspects of the data gathered in an aesthetic and informative way will be marked highly. You should document your conceptual design, the working circuit, the user interface, your code and your development process as follows. Deliverables: • Technical documentation, e.g. code (Processing, Max), TouchOSC layout, etc. Everything that is necessary to run the system. • Short ‘making of’ video (max 3 min) documentation the working system and its design/implementation process. environment). Submission instructions: • The deliverables should be collated as sections in a PDF document. • Submit the PDF document to the Assignment Submission menu on Canvas – click Assignment 2. Due Date: (Week 13) 29 May, 11:59 pm Please read the standards-based assessment rubric for guidance on levels of performance. Note that the grade descriptors must be interpreted relative to each other. IDEA9101 IDEA LAB 1 Assessment Guidelines 2020 ASSESSMENT 2 RUBRIC Grade descriptor Fail 0-49 Pass 50-64 Credit 65-74 Distinction 75-84 High Distinction 85-100 Criterion 1. Conceptual design (40%) Lack of concept. Inadequate description of designed function and behaviour. Brief sketch and description of a basic concept. Simple explanation of designed function and behaviour, including range and type of inputs and outputs. User interface, visualisation or generative audio-visual system contains simple, direct presentation of data. System documentation (including data flow diagrams) con
tains essential elements but may have some errors of notation. Description of concept clearly addresses how the system relates to the users and their surrounding physical environment. User interface, visualisation or generative audio-visual system contains some complex presentation of data and controls. Designed function and behaviour communicated through diagrams, as well as text. System documentation (including data flow diagrams) contains all necessary elements, with correct notation. Description of concept is informed by existing precedents or literature. User interface, visualisation or generative audio-visual system contains complex presentation of data and controls, following good UI/data visualisation principles. Designed function and behaviour communicated through carefully constructed diagrams, in concert with textual explanations. Relation of system/device to users and their surrounding physical environment clearly expressed. Novelty of concept is positioned within existing work. Interesting and complex application, addressing issues beyond the single user-device relationship; multiple users considered. Data presentation is aesthetic and informative. Concept is presented as high quality visual mockup, with clear relationship between users, user interface, device and the surrounding physical environment. System documentation (including data flow diagrams) is flawless and easily comprehensible. 2. Technical competency (30%) System does not work correctly. Can demonstrate a basic working system, which can display data and run continuously. Implementation partially satisfies conceptual design. Can demonstrate a working system, with more than minimum technical features and components, justifying the need for having or not particular features. Implementation mostly satisfies conceptual design. Can demonstrate a working system with a degree of complexity in the code, implemented following design principles and evaluated with usability heuristics. Implementation fully satisfies conceptual design. Can demonstrate a working system with a high degree of complexity in the code. Can demonstrate a working user interface, implemented by following UI design principles and evaluated with usability heuristics. Designed function and behaviour demonstrated through systematic testing, including other users. 3. Process documentation (30%) Missing or unconvincing evidence of development process. Basic level of documentation of development process, containing some diagrams, screenshots and photographs of working system, with minimal reflection and explanation of technical issues. Documentation of development process clearly shows the main phases of building the system, with some reflection and explanation of technical issues. Documentation of development process clearly shows the main phases of building the system, how critical decisions came about, with solid reflection and explanation of technical issues. Thorough and systematic documentation of development process, showing clear progression through the phases of building each component of the system, informed by regular testing and experimentation. Strong knowledge of implementation demonstrated by insightful resolution of technical issues. IDEA9101 IDEA LAB 1 Assessment Guidelines 2020 Assessment 3: Weekly reflective progress reports 20% (individual) Description: I This assessment consists in a weekly Agile-like reflective status report, delivered as an individual Canvas quiz, and providing short answers to the following questions: 1. What have I accomplished last week? 2. What will I do next week? 3. What obstacles are impeding my progress? This is an adaptation of the classical Agile stand-up meeting for the purposes of continuous self-assessment of your progress during the Lab from the perspective of making, by re re-planning your activities on a weekly basis. It also allows your tutors to become aware of any obstacles and help you overcome them before they pile up. Deliverables: Online Canvas quiz every week. Due Date: Every Thursday of the semester, with exception of Week 13 due to the final exhibition (last post Thursday 21 May, 11:59pm). Please read the standards-based assessment rubric for guidance on levels of performance. Note that the grade descriptors must be interpreted relative to each other. IDEA9101 IDEA LAB 1 Assessment Guidelines 2020 ASSESSMENT 3 RUBRIC Grade descriptor Fail 0-49 Pass 50-64 Credit 65-74 Distinction 75-84 High Distinction 85-100 Criterion C1 Documentation and reflection on learning process (100%) Fail to submit reflection on the learning process, or late submissions. Submissions on time, but containing only simplistic answers, lacking articulation and justification for points made. Submissions on time, containing somewhat articulated and well justified answers, deriving some insights from the previous week and planning for the next one. Submissions on time, with well-articulated answers, backed by reasonable arguments, deriving well- explained insights form the past week and using them to frame activities for the following week. Submissions on time with excellent articulation of answers, thorough and thoughtful reflection on the past period of learning, connecting it to the contents thought in class. Clear articulation of forward planning, justified with an objective plan of action and metrics to assess their effectiveness.
