Identify a challenging problem

Reference no: EM132208184

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.

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

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.

Each student needs to submit the same version of their group design document twice (Hackathon - Solution Designs Workshop and Assignment Part 1: Design Document).

The reason for this is that the Hackathon - Solution Designs submission is where you will peer-review other design documents (including your own) and the Assignment Part 1: Design Document submission is where your tutor will mark your groups' design.

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 that you will write in Word. 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.

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 entry. Rather, the journal entries as a whole need to provide insight into your experiences in the hackathon and it is these experiences as a whole that will be evaluated. An example of the format for a single journal entry is included below:

Tasks Attempted Today: Coding of requirements 5, 8.
Finally made a breakthrough on the issue I had trying to get the robot to stop as per requirement 5. I realized it had to be an error with the logic of the code somewhere, so I revisited my activity diagram and worked through it step by step. It seemed okay, so I then compared it carefully with the code I'd created in Mindstorms. It turns out I hadn't set the switch up correctly inside the loop, so the code to stop was never being reached. I found it much easier using the activity diagram to compare with my code because I could then just concentrate on making sure the code exactly followed the activity diagram's structure. When I had tried reviewing the code directly without the activity diagram, I got lost (without realizing) trying to keep track of what the code was doing and the logic of what I wanted the code to actually do. It was such a relief to finally fix this issue and it gave me confidence that I can actually do this if I put the effort into thinking about it.

We started working on requirement 8 this afternoon in our lab. Using the sensor is tricky because we weren't sure about its working range, so we wrote a program and tried it out on the robot a few times, changing the distance setting to see what happened and recording our results, using a table as our graphical organizer. This combination of trial and error with recording the results in a table worked effectively as we now understand what the different values mean and can incorporate this into our program.

Attachments: Activity Diagram for Requirement 5 Code for Requirement 5
Code for Requirement 8
Table for Sensor Distance Results

Part 3: Hackathon Presentation

At the conclusion of the hackathon, each person must provide a short individual presentation about their hackathon experiences in their scheduled laboratory.

This presentation will:

• introduce the main problem that the team attempted to solve for the hackathon.

• identify a personally-significant moment experienced during the hackathon and discuss what made this significant. A significant moment may include events that were challenging, particularly emotive (satisfying, frustrating, etc) or that had a large impact on the work performed during the hackathon.

• identify ONE problem personally encountered during the hackathon, and discuss the problem solving techniques or strategies used personally to address this problem and how (and why) these were used. Note: team members must not choose the same problem to discuss. You will need to coordinate with your team to ensure different problems are selected.

• reflect on personal learning and responses to challenges encountered during the hackathon, including understanding of course concepts, personal skills in problem solving and the role of mindset.

Each presentation should not exceed 5 minutes. Any presentation aids readily available to students may be used, but students are responsible for ensuring these will work in the labs and having a backup available in the event of an issue.

You are also required to complete a peer review of two presentations conducted by other students in your laboratory class. You will be allocated two student presentations to review at the start of the laboratory class. Peer review forms will be provided in the class.

Reference no: EM132208184

Questions Cloud

How does a network-based ids differ from a host-based ids : What is the typical relationship between the untrusted network, the firewall, and the trusted network? How does a network-based IDS differ from a host-based IDS

How each annual goal makes sense based on the plaafp : The most recent psycho-educational evaluation report for Alicia is in her Woodcock-Johnson III Tests of Achievement scores.

Find the value of i : Mrs. B borrows an amount of $75,000 today and agrees to make monthly interest payments to the lender. Find the value of i

What type of research was conducted : Some annotations merely summarize what the source says. That is not correct for this assignment-your summary should include an analysis of the information.

Identify a challenging problem : ITECH1101 – IT Problem Solving - Identify a challenging problem and attempt to solve it using a robot. You will design a possible solution, attempt to implement

Describe how technical goals can be coupled : Describe how technical goals can be coupled with information assurance and security considerations in a network design project.

Compute straight line depreciation for each year : Expected annual costs of new product and direct materials are $455,000. Compute Straight Line depreciation for each year of this new machine's life

Define change you will need to make in day-to-day activities : Discuss the changes you will need to make in your day-to-day activities managing the network or the tools you will need. Assume the addressing scheme has been.

Identify a corresponding state standard from your state : Explain how the plan is designed to meet the needs of students at varying levels of intellectual, social, emotional, and physical development.

Reviews

len2208184

1/4/2019 10:29:49 PM

Reflection An insightful reflection analyses the hackathon experience and the student’s personal responses to the challenges encountered. The impact on learning, understanding of course concepts and the role of mindset are meaningfully reviewed. A reflection analyses the hackathon experience and the student’s personal responses to the challenges encountered. The impact on learning, understanding of course concepts and the role of mindset are reviewed. reflection is included OR A reflection is included with explanation made connections to learning, understanding of the course concepts and mindset.

len2208184

1/4/2019 10:29:42 PM

Problem Solving Techniques At least three key problem solving techniques are identified and discussed in relation to how and why they were used, in the context of the unique challenge identified. The appropriateness of these techniques for this purpose is insightfully analysed. At least three key problem solving techniques are identified and discussed in relation to how and why they were used, in the context of the unique challenge identified. The appropriateness of these techniques for this purpose is analysed but this analysis lacks depth. One or two problem solving techniques are identified and discussed in relation to how and why they were used, in the context of the unique challenge identified. The appropriateness of these techniques for this purpose is analysed. Problem solving techniques are not identified and discussed OR Problem solving techniques are identified but not discussed as to how and why used and / or not analysed.

len2208184

1/4/2019 10:29:21 PM

Supporting Files 3 2 1 0 Test Cases A comprehensive selection of test cases is provided to validate design (whether or not code is fully implemented). Test cases are provided to validate most of the design (whether or not code is fully implemented). Additional test cases would be required for confidence that the code behaves as required. Limited or no test cases are provided.

len2208184

1/4/2019 10:29:14 PM

Perseverance through Challenges Journal entries demonstrate that the problem selected for the hackathon presented many challenges. This may have been achieved by adapting the initial problem to a more difficult standard. Experiences resolving challenges are discussed and demonstrate a thoughtful approach to identifying and trialling possible solutions. A strong willingness to persist through difficulties and adapt approaches when required is evident. Journal entries demonstrate that the problem selected for the hackathon presented several challenges. This may have been achieved by adapting the initial problem to a more difficult standard. Experiences resolving challenges are discussed. A willingness to persist through difficulties and adapt approaches when required is evident. Journal entries demonstrate that the problem selected for the hackathon presented few challenges. Experiences resolving challenges are discussed. A limited willingness to persist through difficulties and adapt approaches when required is evident. Journal entries do not identify challenges encountered during the hackathon

len2208184

1/4/2019 10:28:47 PM

Work Journal 5 3 1 0 Problem Solving Techniques A variety of problem solving techniques are identified and discussed with explicit connection to the related modelling documentation, code and / or test cases. Meaningful connections are analysed between course concepts and the application of these concepts to solve problems experienced during the hackathon. Problem solving techniques are identified and discussed with explicit connection to the related modelling documentation, code and / or test cases. Attempts to relate course concepts with experiences solving problems in the hackathon are made but these lack depth and / or understanding. A limited selection of problem-solving techniques are identified and discussed. Application of problem solving techniques is not evident through the journal OR Problem solving techniques are identified and discussed but links are not made between these techniques and how they have been applied to specific modelling documentation, code and / or test cases.

len2208184

1/4/2019 10:28:37 PM

Provide appropriate UML models to represent the proposed solutions UML diagrams are provided and are appropriate for the problem statements being addressed. The diagrams appropriately reflect the algorithms. Correct notation is used, and following the diagrams would lead to implementation of appropriate solutions. UML diagrams are provided and are appropriate for the problem statements being addressed. The diagrams reflect the algorithms as appropriate. There are some issues with clarity, or logic that would cause the solutions to fail, OR some of the notation used is incorrect. UML diagrams are provided however the selection of diagrams is not appropriate for the problem statements provided. No UML diagrams provided OR UML diagrams do not clearly relate to the problem statements provided.

len2208184

1/4/2019 10:28:28 PM

4 3 2 0 Develop algorithms to solve each of the problem statements provided. Algorithms are provided. These clearly relate to the problem statements, are unambiguous, clear, complete and logical. These algorithms should successfully address the problem statements. Algorithms are provided. These clearly relate to the problem statements and mostly achieve the required solution but contain a small number of issues with clarity, completeness or logic. Algorithms are provided. These can be related to the problem statements but are a) unclear or ambiguous b) incomplete c) logically incorrect. Algorithms not provided OR algorithms are provided but the relationship between these and the problem statements is unclear.

len2208184

1/4/2019 10:28:20 PM

Complete Peer Reviews x 2 Two peer reviews of design documentation have been completed. These both demonstrate critical analysis of the design documentation and provide meaningful feedback. Two peer reviews have been completed. The analysis and / or feedback lack analysis. OR One peer review has been completed. This demonstrates critical analysis or the design documentation and provides meaningful feedback. One peer review has been completed. This lacks critical analysis of the design documentation or provides superficial feedback only. Peer reviews not completed. Complete Self Review A review of own design documentation has been completed. This demonstrates critical analysis of the design documentation. A review of own design documentation has not been completed OR A review of own design documentation has been completed but does not demonstrate critical analysis.

len2208184

1/4/2019 10:28:11 PM

Design Documentation 4 2 1 0 Problem statements clearly identify details of the problem(s) to be solved Problem statements have been provided. These clearly identify and describe the problems to be solved, enabling the development of robust solutions. Problem statements have been provided. These provide a reasonable description of the problems to be solved, but some further clarification would be needed to develop robust solutions. No problem statements have been provided OR Problem statement(s) have been provided, but these are ambiguous OR do not clearly explain the problems to be addressed.

len2208184

1/4/2019 10:28:00 PM

Your initial design documentation must be submitted in the Hackathon – Solution Designs and Assignment Part 1: Design Documentation link provided in Moodle, as a .pdf file. Your peer reviews will also occur directly in the Hackathon – Solution Designs link. Your work journal must be created in Word and submitted in Moodle in the Assignment Part 2 - Work Journal link. Your supporting documentation, including all code, models, test cases and test results, and peer reviews from week 11 presentation must be zipped into a single file and submitted in the Assignment Part 2 – Supporting Files link. This includes the final version of the design documentation, incorporating any changes to the documents that occurred during the hackathon. Your presentation will be assessed during your scheduled lab class in week 11.

Write a Review

Required(*) Message

Assured A++ Grade

Get guaranteed satisfaction & time on delivery in every assignment order you paid with us! We ensure premium quality solution document along with free turntin report!

Submit Assignment

User Account

All Pages