PFA
Guide to Project for Supervisors ITECH1101 – IT Problem Solving 1807 CRICOS Provider No. 00103D ITECH1101 Hackathon Assignment Specification 1807.docx Page 1 of 10 Hackathon Assignment Specification Overview This assignment requires you to identify a challenging problem and attempt to solve it using a robot. You will design a possible solution, attempt to implement that solution and then present an aspect of your work to your peers. There are three separate parts to this assignment, coinciding with the stages of developing your solution: Part 1: Design Documentation and Peer Review Part 2: Hackathon Report Part 3: Hackathon Presentation Some of this assignment requires group work. However you will be assessed individually. Timelines and Expectations Percentage Value of Task: Part 1: 15%, Part 2: 15%, Part 3: 10%. Total: 40%. Due: This assignment has multiple due dates as follows: Part 1: Design Documentation: Monday 7th May, 2018, 12:00 (noon) Peer Review: Sunday 13th May, 2018, 23:55 Part 2: Hackathon Report: Sunday 3rd June, 2018, 23:55 Part 3: Hackathon Presentation: In your timetabled Week 11 lab. Minimum time expectation: 20 hours Learning Outcomes Assessed The following course learning outcomes are assessed by completing this assessment: • K2. Relate goal-setting and plan formulation to problem solving • K3. Compare and contrast commonly used problem solving strategies • K4. Describe tools and techniques that can be used to model and describe problems • K5. Describe the value of reflection, attitude and self-efficacy towards success in problem solving • S1. Decompose a problem and create goals and plans to solve that problem • S2. Devise and implement problem solving strategies which can be applied to a range of IT problems • S3. Develop and verify algorithms based on conceptual models used in programming • S4. Construct documentation describing how to solve a problem • A1. Apply problem solving strategies, tools and techniques to solve problems in a variety of domains ITECH1101 IT Problem Solving CRICOS Provider No. 00103D ITECH1101 Hackathon Assignment Specification 1807.docx Page 2 of 10 Assessment Details Part 1: Design Documentation and Peer Review This stage requires you to select a problem to solve using one of the available Mindstorms Robots, design a possible solution to this problem and submit this solution design for peer review. You are also required to peer review the designs of two other students in the course. The design documentation is to be completed in groups of 2-3 students. Your team will be allocated from your lab group. Peer reviews will be completed individually. Problem Selection Identify a problem to solve as a team. You can come up with any problem of interest (perhaps a design thinking workshop could help generate ideas?), or use the ideas below as suggestions. Your problem must: • Be challenging for you. You are being assessed on your application of problem solving skills, so any problem that is too easy will not give you the opportunity to demonstrate this. • Require you to use a variety of problem solving strategies / techniques to complete • Be creative. Fun is a huge element of a hackathon, so you want to select something that you will enjoy. • Require you to code the behaviour. Controlling the robot’s movements through a remote is not permitted (although a limited amount of this may be done in support of coded behaviours) • Work within the capabilities of your robot. You are not permitted to modify the robot builds, other than to switch between the available attachments as appropriate. You may add temporary enhancements, such as using glad wrap, putting on temporary decorative clothing or applying a rubber band, provided the changes do not affect the structure of the robot, do not impair its capacity to function, do not leave any mark or residue on the robot and can be quickly applied and removed. Your problem must also not be something that you can solve by following previously created instructions or downloading existing programs. For example, you cannot just use the code examples provided in the Mindstorms tutorials, even if you recreate them yourself, and you cannot download existing code from the internet. Ideas: • Sort objects in different locations based on colour • Build something by collecting pieces and assembling / layering them in a specific location • Play hide-and-seek, using an IR sensor to locate the IR remote • Battle another robot (two teams from one lab group could each program one robot to compete). Just remember not to damage the robots! • Follow a path through an unseen obstacle course – perhaps use colour, or object sensing (or both?) to determine movements ITECH1101 IT Problem Solving CRICOS Provider No. 00103D ITECH1101 Hackathon Assignment Specification 1807.docx Page 3 of 10 Design Documentation Once you have selected a problem, your team must create documentation that outlines the logic of a solution to your problem. You may need to break your problem down into smaller sub-problems to achieve this, and should prepare problem statements for these sub-problems. This documentation must clearly identify the problem(s) you are attempting to solve, and include algorithms and UML models to represent the full functionality of the program(s) you intend to implement during the hackathon. Your documentation must be saved in .pdf format. Completed design documentation must be uploaded to the link provided in Moodle by noon of Monday 7th May 2018 to allow time for peer reviews to be completed. Peer Reviews From noon on Tuesday 8th May 2018 (or an alternative time as advised by your lecturer), you will have access to conduct a peer review on two other students’ design documentation. These reviews will be allocated to you. You will also review your own design. These designs will be selected from different teams where possible, which means each team will usually receive feedback from six other people. You will complete the peer reviews individually. Your task is to review the documentation allocated to you and to evaluate it against a set of criteria provided in a marking rubric. You should consider how well the documentation defines the problem(s) under investigation, how clearly algorithms represent and address the problems(s) and how effectively UML diagrams are documented to solve the problem(s). You will also have the opportunity to provide your own comments, and should take care to provide specific comments that highlight both the positive aspects and the potential issues of the proposed solution(s) and documentation. Note: Your mark will not be impacted by the feedback your peers provide on your work. Your tutor will be marking your design documentation separately, and it is your tutor’s mark that will contribute to your assessment. You will be marked based on how well you complete your peer reviews. All feedback must be completed by 23:55 Sunday 13th May 2018, in readiness for the hackathon to begin in the next workshop. You should review the feedback you have received and incorporate the feedback you receive into your design, as appropriate. You may continue to update your documentation throughout the hackathon, based on your hackathon experiences, and any additional ideas you obtain through seeing the designs completed by other people (Note: this does not mean copying their work. It does mean that you can be inspired by it, and make improvements to your own design based on what you’ve learned). ITECH1101 IT Problem Solving CRICOS Provider No. 00103D ITECH1101 Hackathon Assignment Specification 1807.docx Page 4 of 10 Part 2: Hackathon Report This part of the hackathon assignment requires you to discuss, analyse and reflect upon the problem solving techniques you use during the hackathon. This will occur through a work journal, to be documented in your ePortfolio. This task is to be completed individually. You will update and maintain your work journal on a frequent basis throughout the hackathon, documenting: • an overview of the work you have been attempting • challenges or problems you encounter • the output of your work. Throughout these journal entries, you will make and analyse connections between the work you are performing and the course concepts reviewed throughout the semester. For example, if you attempt to solve a problem using a graphical model, your entry would identify the problem you were trying to solve, discuss the use of the graphical model and the reason for its use and analyse how effective the graphical model was in helping you resolve the problem. You will also reflect on your learning throughout the hackathon. This learning can include both course concepts that you understand better due to applying them during the hackathon, and learning about yourself as a problem solver. To create your Work Journal: 1) Log on to Mahara (ePortfolio System) at https://eportfolios.federation.edu.au/ 2) Select Content, then + Create journal 3) Give your journal a name, e.g. ITECH1101 Hackathon Experiences 4) Click Create Journal To present your Work Journal ready for submission: 1) Select Portfolio then Pages 2) Select + Create page 3) Give the page a name, e.g. ITECH1101 Hackathon Experiences. 4) Click Save. The Edit Content tab will load. 5) Select the Edit layout tab. Select an appropriate layout (the first option, with just a full page, will suit most people), then click Save. 6) The Edit Content tab will reload. From the menu on the left, select Journals, then drag the Journal submenu item onto the blank page layout section until the journal outline is highlighted. 7) Select the Hackathon Journal (ITECH1101 Hackathon Experiences). 8) Click Save on the Journal: Configure screen. 9) Select Share page, then select the name of your tutor using the Share with box. Click Save. https://eportfolios.federation.edu.au/ ITECH1101 IT Problem Solving CRICOS Provider No. 00103D ITECH1101 Hackathon Assignment Specification 1807.docx Page 5 of 10 The work journal does not need to document every single aspect of the work you perform during the hackathon, and does not need to address all of the marking criteria in every