Skip to main content

Assessment

Purpose​

The Assessment domain manages examinations, tests, evaluations, and student results.

The Assessment domain consists of:

  • Assessment
  • Assessment Subject
  • Student Assessment

This model supports:

  • Unit Tests
  • Monthly Tests
  • Half Yearly Exams
  • Annual Exams
  • Practical Assessments
  • Projects
  • Assignments

without requiring redesign.

Business Context​

Schools conduct various assessments during an Academic Year.

Examples:

  • Unit Test 1
  • Unit Test 2
  • Half Yearly Examination
  • Annual Examination

Each Assessment may evaluate one or more Subjects.

Students receive marks, grades, and remarks against the evaluated Subjects.

Assessment

Purpose​

An Assessment represents an examination or evaluation event conducted for a Class during an Academic Year.

Examples:

  • Unit Test 1
  • Half Yearly Examination
  • Annual Examination

Assessment defines the examination structure.

Assessment does not store student marks.

Relationships​

Assessment to Academic Year​

  • Each Assessment belongs to exactly one Academic Year.
  • An Academic Year may contain multiple Assessments.

Assessment to Class​

  • Each Assessment belongs to exactly one Class.
  • A Class may contain multiple Assessments.

Assessment to Assessment Subject​

  • An Assessment contains one or more Assessment Subjects.

Key Design Decisions​

Academic Year Scoped​

Assessments belong to an Academic Year.

Examples:

  • Half Yearly 2026-2027
  • Annual Exam 2026-2027

Class Scoped​

Assessments are created for a Class.

Examples:

  • Grade 5 Half Yearly
  • Grade 10 Annual Examination

Assessment Types are Configurable​

The platform does not hardcode assessment types.

Examples:

  • Unit Test
  • Monthly Test
  • Half Yearly
  • Annual Exam
  • Practical
  • Assignment
  • Project

Attributes​

Identity​

  • AssessmentId
  • AcademicYearId
  • ClassId

Details​

  • Name
  • AssessmentType

Schedule​

  • StartDate
  • EndDate

Status​

Possible values include:

  • Draft
  • Published
  • Closed
  • Archived

Audit​

  • CreatedAt
  • CreatedBy
  • UpdatedAt
  • UpdatedBy

Status Lifecycle​

Draft​

Assessment is being prepared.

Subjects and marking schemes may still change.

Published​

Assessment is available for mark entry.

Teachers may begin recording results.

Closed​

Mark entry is complete.

Assessment results are considered finalized.

Archived​

Assessment is retained for historical purposes.

Assessment Subject

Purpose​

Assessment Subject defines subject-specific evaluation rules within an Assessment.

Examples:

Half Yearly

  • Mathematics
  • English
  • Science

Assessment Subject defines:

  • Maximum Marks
  • Passing Marks
  • Weightage

Relationships​

Assessment Subject to Assessment​

  • Each Assessment Subject belongs to exactly one Assessment.

Assessment Subject to Subject​

  • Each Assessment Subject belongs to exactly one Subject.

Assessment Subject to Student Assessment​

  • An Assessment Subject may contain multiple Student Assessments.

Key Design Decisions​

Subject Specific Marking Scheme​

Maximum Marks and Passing Marks belong to Assessment Subject.

Examples:

Mathematics

  • Maximum Marks: 100
  • Passing Marks: 35

Project Work

  • Maximum Marks: 25
  • Passing Marks: 10

Weightage Support​

Weightage may be defined.

Examples:

  • Mathematics → 20%
  • English → 20%
  • Science → 30%

Weightages support future report card calculations.

Attributes​

Identity​

  • AssessmentSubjectId
  • AssessmentId
  • SubjectId

Evaluation Rules​

  • MaximumMarks
  • PassingMarks
  • Weightage

Ordering​

  • DisplayOrder

Audit​

  • CreatedAt
  • CreatedBy
  • UpdatedAt
  • UpdatedBy

Constraints​

Subject Uniqueness​

A Subject may appear only once within an Assessment.

Valid:

Half Yearly

  • Mathematics
  • English

Invalid:

Half Yearly

  • Mathematics
  • Mathematics

Student Assessment

Purpose​

Student Assessment stores an individual student's performance for an Assessment Subject.

Examples:

Rahul

Half Yearly

Mathematics

Obtained Marks: 78

Relationships​

Student Assessment to Student Enrollment​

  • Each Student Assessment belongs to exactly one Student Enrollment.

Student Assessment to Assessment​

  • Each Student Assessment belongs to exactly one Assessment.

Student Assessment to Assessment Subject​

  • Each Student Assessment belongs to exactly one Assessment Subject.

Key Design Decisions​

Student Performance Record​

Student Assessment represents the student's actual outcome.

Examples:

  • Marks
  • Grade
  • Remarks
  • Attendance Status

Marks and Grades Supported​

The model supports:

  • Marks
  • Grades
  • Both simultaneously

Different Schools may use different evaluation approaches.

Assessment Participation Status​

Supported values include:

  • Present
  • Absent
  • Exempted

Assessment participation is modeled separately from marks.

Attributes​

Identity​

  • StudentAssessmentId
  • StudentEnrollmentId
  • AssessmentId
  • AssessmentSubjectId

Evaluation​

  • ObtainedMarks
  • Grade
  • Remarks

Participation​

  • Status

Possible values include:

  • Present
  • Absent
  • Exempted

Audit​

  • CreatedAt
  • CreatedBy
  • UpdatedAt
  • UpdatedBy

Constraints​

One Result Per Student​

A Student may have only one Student Assessment per:

  • Assessment
  • Assessment Subject

Valid:

Rahul

Half Yearly

Mathematics

One Result

Invalid:

Rahul

Half Yearly

Mathematics

Two Results

Marks Validation​

Obtained Marks must not exceed Maximum Marks defined by the Assessment Subject.

Administrative Ownership​

School Administrators may:

  • Create Assessments
  • Publish Assessments
  • Close Assessments

Teachers may:

  • Enter Marks
  • Update Marks
  • Add Remarks

Permissions are controlled through School Membership roles.

Exclusions​

The following capabilities are excluded from V1:

  • Re-Evaluation Workflows
  • Moderation Workflows
  • Result Approval Workflows
  • Promotion Rules
  • Rank Calculation
  • Merit Lists

These capabilities may be introduced later.

Future Considerations​

The following capabilities may be introduced later:

  • Report Cards
  • GPA Calculation
  • Grade Calculation Rules
  • Promotion Rules
  • Re-Evaluation
  • Result Approval
  • Class Ranking
  • Merit Lists
  • Academic Analytics

These capabilities should not require redesign of the Assessment model.

Summary​

Core decisions:

  • Assessment represents an examination or evaluation event.
  • Assessment belongs to an Academic Year and Class.
  • Assessment Subject links Assessments and Subjects.
  • Maximum Marks belong to Assessment Subject.
  • Passing Marks belong to Assessment Subject.
  • Weightage belongs to Assessment Subject.
  • Student Assessment stores student performance.
  • Marks and Grades are supported.
  • Assessment participation status is tracked.
  • Report card and promotion logic are deferred from V1.