Project Goal▼
Build a scalable system to manage school operations through:
- Laravel API backend
- React or Blade Admin Panel
- Flutter Apps for Teachers, Students, and Parents
- Build a scalable system to manage school operations through:
Phase 1: Requirement Gathering & Planning
▼
- Define roles: Admin, Teacher, Student, Parent, Librarian
- Modules: Class, Attendance, Results, Homework, Library, Fees,
Notices
- Tools: Trello, Figma, GitHub, Postman
Phase 2: Laravel API Backend
▼
- Sanctum-based login
- RBAC system
- Models: User, Class, Subject, Attendance, Homework, Result, Fee,
Notice
- Library Models: Book, LibraryIssue, LibraryReturn, Author,
Publisher
- APIs:
- /api/books
- /api/issue-book
- /api/return-book
- /api/student-books
Phase 3: Admin Panel (Web)
▼
- Manage: Students, Teachers, Subjects, Homework, Results
- Library:
- Add/Edit Books
- Issue/Return Books
- Late return fee tracking
Phase 4: Flutter App – Teacher
▼
- Login & dashboard
- Attendance, Homework, Results
- View Library Catalog
- Receive Notifications
Phase 5: Flutter App – Student/Parent
▼
- View Attendance, Homework, Results, Fees
- Library: Issued books, return dates
- Pay Fees
- Notifications: Assignments, Book return, School News
Phase 6: Flutter App – Librarian
▼
- Login & book dashboard
- Add/Edit/Delete Books
- Issue/Return books
- Track delays and fees
- Search books by title/author
Phase 7: Notifications (FCM)▼
- FCM Topics: /topics/library, /topics/parent
- Alerts: Overdue books, Results, Notices, Homework
Phase 8: Hosting & Deployment
▼
- Host Laravel on Hostinger or AWS
- Setup MySQL, .env, SSL
- Flutter: Publish to Play Store/App Store
Phase 9: Demo, Team Workflow & Git
▼
- API docs (Postman)
- Assign modules to students
- Git Feature Branches (e.g., feature/library)
- Demos & Peer Reviews