Reference no: EM134018857
Advanced Programming
Project
Your Task
This is a group assessment which involves an in-class hackathon where you as a team will develop code. Then, individually, you will, write a documentation, and record a summary video presentation.
Assessment Description
This assessment focuses on an in-class software development hackathon. A hackathon is a time-constrained, high-intensity event that demands collaborative teamwork among peers. Below is a scenario describing a hackathon that simulates the real hackathon you will be participating in.
Imagine that you are participating in a software development hackathon organised by Kaplan Business School.
In this fictional scenario, you and your team are given with a task of developing a new data analytic or machine learning application that addresses a critical real-world challenge: e.g., reducing food waste, predicting a stock price, face detection application. Concepts related to Data Mining may be useful when designing data-driven solutions.
Your hypothetical task is to create a software that allows users to accomplish their tasks.
Your next tasks are to write a documentation and deliver a presentation for the software you have developed.
While this scenario is not a real hackathon, it will serve as the basis for your assessment, allowing you to apply your software development and explanation skills related to data analytics and machine learning applications. You will be evaluated individually on your ability to design, develop, and present your innovative solution within a limited time frame.
Rules to Follow on Hackathon Day
Participation and team formation
Every student enrolled in the subject must be a member of precisely one team.
The facilitator is responsible for officially constituting the team. Students cannot influence this formation process.
Selection of the project
On the day of the hackathon, the facilitator will provide each team with a project title along with a brief description.
Dos and don'ts before the hackathon week?
Dos
You are allowed to have regular in class discussions to collaboratively plan and design a project within a closely related domain.
As a team, it's recommended to explore the development of a comprehensive software system using Python.
Review relevant course material and any prerequisites for the hackathon, ensuring you have a good grasp of the concepts and skills needed.
Familiarise yourself with the tools, software, or Python language that will be used during the hackathon.
Plan how you will allocate your time during the hackathon, making sure to balance coding, testing, and documentation.
Don'ts
Strictly, you should not begin working on the project, writing code, or designing solutions before the hackathon officially starts. The goal is to create within the defined time frame.
Avoid seeking external help from sources not permitted during the event, as hackathons typically rely on the knowledge and skills of the participants.
Timeframes
Introduction by the facilitator - 15 minutes
Begins with a brief introduction, explanation of the rules, and any questions you may have.
Hackathon Kick-off - 15 minutes
The hackathon officially begins. You'll receive your project assignment and can start coding!
Coding Session - 150 minutes
This is the core of the hackathon. Work with your team to develop your Python project.
Assessment Instructions
The instructions for this hackathon assessment are as follows. Stage 1)
During the hackathon, work diligently as a group to implement the required code to complete the software project. Applying principles from Software Engineering can help teams organise development and testing activities effectively.
One student from each group will submit your code by the conclusion of the hackathon event. This will be a group mark.
Stage 2)
Each student then submits a comprehensive code documentation within one week from the date of the hackathon. See the Appendix A - Formatting Guidelines and Appendix B - Document Template for the documentation guidelines.
Each student should explicitly state their individual contributions to both code development and documentation.
Stage 3)
Submit a recorded 5-minute presentation:
Explaining your code's features and functionalities
Reflecting on your team's success and your own individual contribution.