Skip to main content

Student

Purpose​

A Student represents a permanent academic record within a School.

A Student is the primary academic entity around which admissions, enrollment, attendance, assessments, fee management, and academic reporting are built.

A Student is not tied to a specific Academic Year.

A Student's participation in an Academic Year is managed through Student Enrollments.

Business Context​

A Student represents a person enrolled in a School.

Examples:

  • Kindergarten Student
  • Primary School Student
  • Secondary School Student
  • Higher Secondary Student

A Student remains the same throughout their academic journey within a School.

Academic progression is managed through yearly enrollments and promotions rather than creating new Student records.

Relationships​

Student to School​

  • Each Student belongs to exactly one School.
  • A School may contain many Students.

Student to Student Enrollment​

  • A Student may have multiple Student Enrollments.
  • Each Student Enrollment belongs to exactly one Student.

Examples:

  • 2025-2026 → Grade 5
  • 2026-2027 → Grade 6
  • 2027-2028 → Grade 7

The Student remains the same while the Enrollment changes.

Student to Academic Year​

Students participate in Academic Years through Student Enrollments.

Students do not belong directly to Academic Years.

Student to Parent​

Students may be associated with one or more Parents.

Parents are represented by Users.

Parent relationships are managed separately from the Student entity.

Student to User​

Student and User are separate domain entities.

Student login capability is not required in the initial version.

A Student may optionally be linked to a User account in the future.

Key Design Decisions​

Student is a Permanent Record​

Students are not recreated every Academic Year.

A Student record remains active throughout the student's life cycle within a School.

Academic progression is tracked through Student Enrollments.

Student is School Scoped​

A Student belongs to exactly one School.

Student records are owned by the School.

Student Transfer​

When a Student moves to another School:

  • The original Student record remains with the original School.
  • A new Student record is created in the destination School.

This simplifies:

  • Ownership
  • Academic History
  • Privacy
  • Data Retention

Student Login​

Student login is not a requirement for the initial version of the platform.

Future student self-service functionality may be implemented through an optional linked User account.

The Student domain must not assume that every Student has a login.

Student Identity​

Each Student should be uniquely identifiable within a School.

Admission Number serves as the primary business identifier.

Government-issued educational identifiers may be captured when available.

Attributes​

Identity​

  • StudentId
  • AdmissionNumber
  • APAARId
  • PermanentEducationNumber

Personal Information​

  • FirstName
  • MiddleName
  • LastName
  • DisplayName
  • DateOfBirth
  • Gender

Profile​

  • ProfilePhotoUrl

Medical Information​

  • BloodGroup
  • MedicalNotes

Status​

Possible values include:

  • Active
  • Inactive
  • Graduated
  • Transferred
  • Withdrawn
  • Archived

Audit​

  • CreatedAt
  • CreatedBy
  • UpdatedAt
  • UpdatedBy

Identity Rules​

StudentId​

  • System Generated
  • Immutable
  • Internal Primary Key

AdmissionNumber​

  • Mandatory
  • Unique Within a School
  • Primary Business Identifier

APAARId​

  • Optional
  • Unique When Present

PermanentEducationNumber​

  • Optional
  • Unique When Present

Status Lifecycle​

Active​

Student is currently enrolled and participating in academic activities.

Inactive​

Student record exists but is temporarily inactive.

Graduated​

Student has successfully completed schooling.

Transferred​

Student has transferred to another School.

Withdrawn​

Student has voluntarily left the School.

Archived​

Student record is retained for historical and reporting purposes.

Constraints​

Student Uniqueness​

Admission Number must be unique within a School.

School Ownership​

A Student belongs to exactly one School.

Academic Placement​

Class and Section assignments do not belong to the Student entity.

Academic placement is managed through Student Enrollment.

Exclusions​

The following information does not belong directly to the Student entity:

  • Academic Year
  • Class Assignment
  • Section Assignment
  • Attendance Records
  • Fee Records
  • Assessment Records

These belong to enrollment or other academic domain entities.

Future Considerations​

The following capabilities may be introduced later:

  • Student Self-Service Portal
  • Student Mobile Application
  • Linked Student User Accounts
  • Government System Integrations
  • Health Record Extensions
  • Transport Management
  • Hostel Management

These capabilities should not require redesign of the Student domain.

Summary​

Core decisions:

  • Student is a permanent academic record.
  • Student is not tied directly to an Academic Year.
  • Academic progression is managed through Student Enrollments.
  • Student belongs to exactly one School.
  • Student and User are separate entities.
  • Student login is optional and deferred.
  • Admission Number is the primary business identifier.
  • APAAR ID is supported.
  • Permanent Education Number is supported.
  • Medical information is supported.
  • Academic placement belongs to Student Enrollment, not Student.