• Source Code*

Teams are required to share the complete codebase of their project developed during the hackathon. 

The code should be well-organised, thoroughly commented, and adhere to best coding practices. It should be hosted on a platform such as GitHub, GitLab, or Bitbucket and include all necessary files to run the project.

• Working Prototype or Demo*

Each team must submit a functional version of the solution that demonstrates its core features and functionality.

This could be a web application, mobile application, hardware prototype, or any other medium that best represents the proposed solution. The stability of the system should be sufficient to clearly display essential features and successfully illustrate the implementation.

• Pitch Presentation or Slide Deck*

Teams must have a presentation that outlines the problem, solution, technology stack, target audience, and potential impact of the solution.

Used during the final pitch to the jury, this slide deck should convey the project's value proposition and key features. 

• Video Demo

A team can submit a short video (typically 2-5 minutes) that demonstrates the project in action.

The video can include live demos or screen recordings and should demonstrate the problem being addressed, depict the functioning of the solution, and highlight the main characteristics of the project. 

• Design Mockups and Wireframes

Provide visual representations of the user interface and experience, including design mockups, wireframes, and user flow diagrams. 

These artefacts illustrate design and user experience considerations and can be created using tools such as Figma, Sketch, Adobe XD, or even hand-drawn.

• Architecture Diagram

Teams can submit a visual representation of the system architecture, detailing components, data flow, and interactions.

This diagram helps the jury understand the technical stack and system design, including how different components interact. It may encompass diagrams for back-end architecture, front-end design, API interactions etc. 

• Test Data

List and submit all the sample test data that is necessary for the test, such as account details and credentials etc.

• Test Cases and Results

Share a set of test cases and the results of testing the project’s functionalities.

These demonstrate that the team has considered various edge cases and have tested their solution for reliability and stability.

• Usage and Installation Instructions*

Include a document or section in the README file that provides step-by-step instructions for setting up and running the solution.

This allows the jury and other users to install and evaluate the project independently.

• API Documentation*

(Mandatory if applicable)

Teams must share documentation for any APIs created or used within the project. This includes endpoint descriptions, request/response formats, authentication methods, and example use cases.

• Git Repository with Version Control History*

Team must share access to an accessible Git repository that shows the development history and contributions.

This demonstrates collaboration among team members and the progression of the project, allowing judges to see how the project evolved during the hackathon.