Member Avatar for joejo

*hello,

*Please, i would like some help with how to start with my FINAL YEAR project work dubbed "SCHOOL TRACKING SYSTEM" . I am so much lost on how it shoud be like and what to actually do .
Some support would be very much appreciated and am so much in need of any helping hand i can get .

*THANKS IN ADVANCE

  • 2 Contributors
  • 2 Replies
  • 215 Views
  • 1 Day Discussion Span
  • Latest Post Latest Post by joejo

Dani AI

Generated

For a final-year "School Tracking System" project, pick a tight minimum viable product (MVP) and map each feature to clear deliverables. Useful, testable modules that show design and coding ability include: student profiles, enrollment/class allocation, daily attendance with reports, exam/grade entry and transcript generation, timetable/room assignment, staff/guardian contacts, role-based access (admin/teacher/clerk), and basic printable/exportable reports. These map naturally to entities such as Student, Class, Enrollment, Attendance, Subject, ExamResult, Teacher, User, and Role.

A practical sequence: write 6–10 user stories (for example, "Teacher records attendance" or "Admin generates term report"), produce an ER diagram and simple UI mockups, then implement iteratively. Given the tags, platform choices are VB.NET WinForms/WPF for a desktop submission or ASP.NET for a web app; use SQL Server Express/LocalDB for the database and Entity Framework if comfortable (or ADO.NET otherwise). Start by building CRUD screens for Student and Class, add Attendance workflow next, then ExamResult and reporting. Keep a seeded test dataset and use Git for version control and backups.

Final-year artifacts to prepare: requirements specification, ER diagram, database schema and scripts, commented source code, test cases/results, a short user manual, and deployment/install instructions. A simple schedule: 1–2 weeks requirements/design, 4–6 weeks core development (MVP), 1–2 weeks testing and fixes, final week for documentation and presentation—align each item to assessment criteria like functionality, code quality, testing, and documentation.

Security and common pitfalls: never store plain passwords (use hashed+salted storage), validate and sanitize all inputs, enforce role-based access, and plan regular backups. Over-scoping and skipping tests are the most frequent causes of late submissions. Building on ’s advice to list what to track first will make schema, UI and test plans straightforward—this structure should help turn the project into a solid, defensible submission.

Recommended Answers

All 2 Replies

Member Avatar for Oxiegen

I would suggest you start by grabbing a pen and paper and begin outlining what exactly your program is supposed to track, and what informaion might be needed to show and how to handle it.

Beyond that we can be more helpful when you get stuck on specific problems during development.

Member Avatar for joejo

ok! thankx for the head start guide . . . well appreciated

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.