How much it cost
Guide to Project for Supervisors ITECH1101 – IT Problem Solving 2005 CRICOS Provider No. 00103D ITECH1101 Hackathon Assignment Specification 2005.docx Page 1 of 10 Hackathon Assignment Specification Overview This is an individual assignment that requires you to devise and attempt to implement a game using block-based coding. You will design algorithms for your game, attempt to implement the algorithms 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 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*: Wednesday 6th May, 2020, 23:59 (Week 8) Peer Review: Sunday 10th May, 2020, 23:59 (Week 8) Part 2: Hackathon Report: Sunday 31st May, 2020, 23:55 (Week 11) Part 3: Hackathon Presentation: Sunday 31st May, 2020, 23:55 (Week 11) Hackathon Peer Reviews: Sunday 7th June, 2020, 23:55 (Week 12) Minimum time expectation: 20 hours * Note: The design documentation is due as a draft at this time so it can be peer reviewed, however it will not be marked until the conclusion of Part 3. 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 2005.docx Page 2 of 10 Assessment Details Assignment Scenario Your local council would like to release some resources to assist the community during the ongoing COVID- 19 pandemic. Your task is to design and develop an original computer game using Scratch v3 that in some way relates to the pandemic situation. Some ideas for this could include: • A supermarket frenzy game in which the player attempts to obtain as much toilet paper as possible, or, alternatively, races madly around the screen trying to obtain a single pack of toilet paper before it disappears. • A “virus attacks” game where the player tries to avoid being infected with the virus being spread around by computer players that infect each other whenever they touch or stay within close proximity for a predetermined time. • A maze game where the player attempts to move through an increasingly crowded space without touching anything The idea for the game is entirely your choice within this scope, provided it can be implemented in Scratch v3. Important Note Before You Begin This assignment takes the form of a hackathon, meaning that you have a short period of time in which to work on your idea and you may not have a finished product when it ends. This is absolutely fine – you do not need to fully implement your game, but you do need to make some progress towards your goal. The key here is that you are applying problem solving skills to work on your game. Some of you have never coded in your lives, while others have had quite a bit of experience. You are not being assessed on how good your game is, or how complicated its design, or anything else that assumes you already have a level of coding ability. Instead, the focus is on your problem solving skills. When you encounter a challenge, how do you respond? What strategies do you employ? How do you proceed when your first (or first several) attempts are unsuccessful? For your assignment, this means two key things: 1) Even though you are able to freely see and access existing Scratch games, copying someone else’s work does not provide you with any benefit. Copying existing code does not allow you to practise your problem solving skills, and so you would not receive high marks for the submitted work. It is what you, personally, achieve that counts, not what you’re able to source from someone else. 2) The complexity of your game idea allows you to control the level of problem solving you need to perform. If you are a novice coder, pick a simple idea, or an idea that starts simply but can easily be expanded. Conversely, if you are an experienced coder, your game will need to include some complexity. Only you know your current capabilities, and so it is up to you to choose an idea that interests you and that pushes you just beyond your current capabilities so that you have the opportunity to demonstrate your problem solving skills. If, when you get to the coding activities, you find that your choice was too simple, you can add further complexity. You will not be penalized for submitting an incomplete implementation of your game, but you will be penalized if you have chosen a task that does not provide you the opportunity to problem solve appropriately. Using Scratch v3 Scratch (https://scratch.mit.edu/) is available for both online and offline use. Download Scratch from here: https://scratch.mit.edu/download. Save your work to your computer as you go. Some interactive tutorials are available within Scratch; and others are available here: https://projects.raspberrypi.org/en/codeclub/scratch-module-1 to help you learn how to use the Scratch interface and create programs. https://scratch.mit.edu/ https://scratch.mit.edu/download https://projects.raspberrypi.org/en/codeclub/scratch-module-1 ITECH1101 IT Problem Solving CRICOS Provider No. 00103D ITECH1101 Hackathon Assignment Specification 2005.docx Page 3 of 10 Part 1: Design Documentation and Peer Review This stage requires you to create some initial draft documentation for your game. You will create and document rules for your game, and develop algorithms for its implementation. These rules and algorithms may continue to evolve throughout the course of the hackathon, so they do not need to be perfect, but you do need to try to make these as complete as possible to get the best value out of the peer reviews and simplify the coding stage of the hackathon. Your documentation will continue to be updated as needed throughout the hackathon. You will also peer review the designs of two other students in the course. Peer reviews will be completed individually. Game Idea You can select any game within the scope outlined in the Assignment Scenario section on page 2. Your game must: • Be challenging for you, so that you are able to demonstrate your problem solving skills. • 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 using Scratch v3, and be within the capabilities of Scratch v3. You may not use any other programming environment for this assignment. Your game must also not be something that you can solve by following previously created instructions (even with minor modifications) or downloading existing programs. For example, you cannot find a similar game on Scratch and copy it as your own, or use a Scratch tutorial to provide your code. Looking at other examples and completing tutorials to help you learn is fine, but copying other work is not counted as using problem solving skills. You need to think through what your code requires for yourself. Design Documentation Once you have chosen your game, you must create documentation that outlines the rules and breaks down the logic of the gameplay into algorithms you can use to implement your game. You may need to break your gameplay down into smaller sub-tasks to achieve this, and should include statements that make the purpose of each task or subtask clear. Your documentation must clearly describe an overview of your game, the game rules and include algorithms and a UML model to represent the full functionality of the game you intend to implement during the hackathon. Your documentation must be saved in .pdf format. Note: You MUST upload your documentation before the due date and time documented on Page 1 of this specification. The submission box will automatically allocate peer reviews based on the files submitted at the due date and time, without any grace period. If you are late with your submission, an alternative submission box will be available, however you might not be able to participate in the peer review process and would therefore not be eligible for the marks associated with this task. Contact your lecturer for advice if you are in this situation. Peer Reviews As soon as the submission deadline has passed, you will have access to conduct a peer review on two other students’ design documentation. These reviews will be allocated to you automatically. You will also review your own design. 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 game under review, how clearly algorithms represent and address the game tasks and how effectively the UML diagrams describes the gameplay. You will also have the opportunity to provide your own comments, and should take care to provide specific comments that highlight both positive aspects and any potential issues with the proposed game and documentation. ITECH1101 IT Problem Solving CRICOS Provider No. 00103D ITECH1101 Hackathon Assignment Specification 2005.docx Page 4 of 10 Note 1: Your mark will not be impacted