Rules and regulations:
1. Deadlines
- Each step has a fixed deadline (Week 3, 6, 9, 12, 16). - Deliverables must be submitted (GitHub repo updated + presentation/report if required) before 23:59 on the deadline day. - Late submissions: - Up to 72 hours late → –20% penalty on that step’s grade. - Beyond 72 hours → step graded as 0, unless documented exceptional circumstances. - Partial progress is still accepted (better to submit something than nothing).
2. Code Quality
- Code must be readable, structured, and maintainable. - Follow naming conventions (camelCase for variables/methods, PascalCase for classes). - Proper indentation and formatting (Android Studio auto-format is required). - Avoid duplicate code — use reusable functions/components where possible.
3. Commenting & Documentation
- Every class and function should include a brief comment explaining its purpose. - Complex logic must be explained with inline comments. - Check also Project Requirements. - The README file must be kept up-to-date at each step, describing what was implemented. - Final submission must include: - Short user guide (how to use the app). - Short developer guide (project structure, tools, libraries used).
4. Collaboration & GitHub Usage
- Teams must use GitHub for version control. - Every team member should contribute commits (visible in history). - Use meaningful commit messages (e.g., Add Room database for notes, not update code) and, in general, follow our Git Etiquette. - README must list all team members and their contributions.
5. Sanctions & Penalties
- Missed deadlines → penalties as stated above. - Plagiarism or copy-paste code (from other teams or online without citation) → step graded 0. - Unequal participation (only one member working) → instructor reserves right to grade individual contributions separately. - Uncommented or unreadable code → up to –50% penalty on that step.