MIS for Al-Beruniy International School

Context

A school management system is difficult because its users do not simply need different pages; they need different permissions and interpretations of the same academic data. An administrator manages the institution, a teacher records learning activity, a student follows personal work, and a parent views a child’s progress. Duplicating those worlds would create inconsistent records, while exposing one universal dashboard would create noise and access risk.

The ABIS MIS was designed and implemented as a shared operational product with role-aware interfaces. The scope includes people and groups, subjects and timetables, lessons, assignments, attendance, grades, support, and aggregate reports.

Domain Model

The school structure is the base layer: users and roles connect to students, teachers, groups, subjects, and scheduled learning. Lessons and assignments represent activity inside that structure. Attendance and grades then record progress, while dashboards and reports present the appropriate view of those records.

This lets one update travel through the system without becoming duplicate manual work. A teacher’s assessment belongs to the student’s academic record; the student and parent can see the relevant result; authorized administrators can inspect the aggregate picture.

Role-Aware Product Design

The administrator dashboard emphasizes school-wide records, management actions, and reporting. The teacher dashboard removes institution-wide controls and centers lessons, attendance, grading, and assignments. Student and parent views narrow the same model further to personal or child-specific schedules, work, and progress.

This separation is an interface decision and a permissions decision. Navigation, quick actions, search language, and reporting access all change according to the authenticated role. The goal is for each user to feel that the MIS was designed for their work without creating separate products underneath.

Decisions and Tradeoffs

The primary decision was to build around shared academic entities instead of feature-by-feature pages. That makes reporting possible because attendance, grades, assignments, and workload can be evaluated against the same people, subjects, and groups.

The second decision was to keep high-density administration and reporting on desktop while maintaining responsive learner access. Students and parents may check schedules or assignments from smaller screens; administrators still need broad, scan-friendly working surfaces.

The system also includes support and language selection as part of the product rather than launch-only assistance. A multi-role school system needs a clear way to recover when users cannot complete a workflow.

Screenshots and Access

The portfolio shows the aggregate administrator dashboard, analytics, a teacher workspace, and a privacy-safe student composite. Logged-in student and parent accounts contain names and academic details, so raw captures from those accounts are not published. The staging application remains private and is available through a controlled walkthrough rather than a public credential.

Result

The ABIS MIS is the strongest domain-modeling case in the portfolio. It demonstrates how PenguinDev can take a complex real-world organization, identify its shared records and role boundaries, and turn them into a coherent full-stack system rather than a collection of disconnected dashboards.