GitHub Classroom Submission Instructions
All students must submit their Term-II Project exclusively via GitHub Classroom.
Email submissions or ZIP uploads will not be evaluated.
1. Classroom & Repository Details
Organization: IEM_Gurukul
Classroom: Term-II Project Submission
Assignment Invitation Link:
Github Classroom Assignment
2. How to Accept the Assignment
- Click the invitation link above.
- Login using your personal GitHub account.
- Click Accept Assignment.
- Your individual repository will be automatically created inside the organization.
- Clone the repository to your local machine.
3. Repository Structure (Must Not Be Modified)
The starter template already contains:
src/ – Source codedocs/ – Design documents / UML diagramsreport/ – Final project report (PDF)slides/ – Presentation slidesREADME.md – Project description template
Do not delete required folders. Maintain the structure.
4. Commit Discipline Requirements
- Minimum 10 meaningful commits required.
- Commits must show incremental development.
- Commit messages must be descriptive.
- Development should span multiple days.
- Final submission must not be a single bulk upload.
- Single commit repository
- Commit messages like "final", "update", "done"
- All files added on the last day
- No visible development progression
Repositories with poor Git discipline will receive reduced marks irrespective of functionality.
5. README Completion Requirement
Students must complete the provided README.md template:
- Project Title
- Problem Statement (≤150 words)
- Target User
- Core Features
- OOP Concepts Used
- Architecture Description
- How to Run Instructions
Incomplete README files will affect evaluation.
6. Submission Deadline
All commits must be pushed before 29 March (11:59 PM).
GitHub Classroom records commit timestamps automatically.
Commits pushed after the deadline will be visible and treated as late submissions.
7. Important Rules
- No ZIP file submissions.
- No repository renaming.
- No external repository links.
- No deletion of commit history.
- Plagiarism detection will include commit pattern analysis.
8. Evaluation Criteria
Evaluation will consider:
- Design quality and architecture clarity
- Proper implementation of OOP concepts
- Code organization and modularity
- Commit discipline
- Documentation quality
- Presentation and report completeness
The project evaluates design maturity, not feature quantity.