O

OBE Platform

archived
Academic

Accreditation attainment tracker (bachelor's capstone).

Lead architect2021 – 20222-person teamGNDEC, LudhianaEdTech / accreditation
Angular 12
Node.js
Express
MongoDB
LDAP

Overview

My final-year project: a platform that works out how well a course's assessments map to accreditation outcomes (CO/PO/PSO), built to meet a real accreditation reporting requirement for the college. My earliest end-to-end full-stack app.

I was the lead architect and integrator, working with one co-author, Manjot Singh, who owned the batch and attainment-gap slice.

How it works

1

Course + outcomes

COs, POs, and mappings

2

Mark import

Excel upload

3

Attainment compute

Direct, indirect, and gaps

4

PDF report

Accreditation-ready

Faculty define courses and assessments, import marks, and the system works out attainment against the accreditation outcomes and exports the report.

Engineering challenges

01Turning accreditation rules into working math

Problem. Accreditation needs you to show how well a course's assessments map through its outcomes, course outcomes up to program outcomes, with direct and indirect attainment and the gaps between them. The hard part was the domain logic, not the screens.

Approach. I modelled the courses, outcomes, mappings and assessments, then built the attainment calculations and the gap reporting on top. One neat bit: I generated two mark collections from a single shared schema and picked between them per request, which kept the model simple.

Outcome. Faculty could define a course, import marks and get attainment computed automatically with a PDF to submit, instead of doing it by hand in spreadsheets.

02Fitting into the college's existing setup

Problem. Faculty shouldn't have to learn new credentials, and the output had to be something accreditation would accept.

Approach. I added login against the college's existing LDAP directory so staff used the accounts they already had, plus Excel import for marks and a generated PDF report for submission.

Outcome. The tool slotted into the college's existing accounts and produced submission-ready reports.

External links

What I'd do differently

  • This was my earliest full-stack app and it shows in the repetition: the same update logic copied across routes, forms duplicated between create and edit. I'd factor those into shared helpers now.
  • No tests, and secrets defaulted to placeholders. Acceptable for a college project, but the first things I'd tighten for anything real.