03 / Academic administration · Web
Nilai Akademik
Structured grading, with clear responsibilities.
Connects account administration, grade entry and personal reports through three roles: Admin, Teacher and Student.
01 / CONTEXT
Why I built it
Grading requires consistent calculations and clear access boundaries. I built this project to explore how user data, assessment components and reports can connect while keeping Admin, Teacher and Student responsibilities distinct.
What it does
- Admin statistics and user account management.
- Teacher entry for assignments, midterms and finals, plus profile updates.
- Students can view and print their own reports.
- Centralized calculation: assignments 30%, midterms 30%, finals 40%, passing threshold 70.
Strengths
- Role-based access guides each workflow.
- A shared calculation rule keeps report views consistent.
- Zero grades are distinguished from grades that have not been entered.
Current limitations
- Assessment weights are fixed rather than curriculum-configurable.
- No claim of adoption by a real school or institution.
- The H2 demo resets on restart; production deployment is unverified.
02 / PROCESS
Challenges & lessons
The challenge was keeping accounts and profiles consistent during CRUD, validating role-specific input and making teacher and student reports agree. It taught me to treat validation as part of the data flow, beyond individual form fields.
Evidence & demo status
Build and integration checks were run. Three-role login, user creation, grade entry and student profile editing were checked in the browser. The demo includes one fictional admin, three teachers and eight students.
03 / DOCUMENTATION
Inside the application
What comes next
Make assessment weights configurable, add academic periods and expand the grade change audit trail.
Contribution & process +
I independently developed the original application, from its logic to its interface. Codex assisted with recent refinements, testing and portfolio demo preparation. Documentation uses sample data.