Teams and Project Topics sheet :
https://docs.google.com/spreadsheets/d/1TS8a53XdPvk5vya1-R2iQQWykr4JaaSpVTEP_3kInZs/edit?usp=sharing
Deadline: 17th June,2026
1. End users
2. UseCases (Features)
3. High Level User Flow
Deadline: 20th June,2026
4. Modules & Workflows - Distribute the task and create issues in github repo.
5. Schema (DB Structure)
6. E2E Design (Wireframe)
7. Development (Vibe Coding,Maintain the project repo) - Web Projects
8. Test Strategy
9. Deployment (Explore tools to deploy)
Pre-requisite Technologies : React, Node, Python, MongoDB,SQL
======================================================================================
Topic-> Problem Statement (HMW) → User → Requirement → Story Boarding → Development → Prototype → Testing
What should the simulation do?
Example: Electric Circuit
Student should:
✅ Connect wires ✅ Turn switch ON/OFF ✅ Check bulb glowing ✅ See wrong connection
How should it feel?
✅ Easy to use ✅ Mobile friendly ✅ Works in low internet ✅ Fun and engaging ✅ Clear visuals
What learning outcome should happen? After using simulation, student should be able to:
✅ Explain circuit flow ✅ Identify open/closed circuit ✅ Predict outcomes
Eg : How might we help Class 7 students visually understand force through interaction instead of memorization?
Minimum Roles (can be add based on works) :
- Research Lead: Gather and analyzes information needed for the project.
- UX / Learning Designer: Designs user experience and how users will learn/interact.
- Storyboard Designer: creates visual flow and structure of the content or app.
- Frontend Developer: builds the user interface using code (UI implementation).
- Documentation Lead : Documenting the entire project workflow (maintaining Readme.md)
- Testing Lead: checks the product for bugs and ensures quality before release.
Project Structure to be maintained :
- index.html (Mandatory - Main file)
- HTML Files (Keep in folder if multiple)
- CSS Files (Keep in folder if multiple)
- JS Files (Keep in folder if multiple)
- Images (Keep in folder if multiple)
- requirements.txt (Mandatory-for team to maintain) - Get it from ## Phase 2 — Requirement Gathering
- storyboard file (PNG/JPEG/PDF)
- Userpersona
- About my team (teams.txt) - should also include details of ## Phase 5 — Task Division
- Readme.md - Documentation of simulation
Process of MVP (Minimum Viable Simulation) Example:
❌ Full Science Lab
✅ One concept only: “Bulb glows when circuit completes.”
Build small → test → improve.
Ask school students:
- Was it fun?
- Did you understand?
- Where did you get confused?
- What should improve?
Note :
- GitHub Issues created
- Tasks assigned to team members