Client Proposal

22 modules (12 core + 10 extensions), pricing, phased delivery, health & portal.

Open proposal → Download PDF →

Requirements

All requirements documents as browsable pages — payment workflow, portal, pricing, architecture.

Browse requirements →

Core Foundation

Phase 1 — start here. Auth, org, students, files, notifications, portal shells.

Implementation plan →

Modules 13–22

Transport, boarding, chat, HR, library, e-learning — integration matrix.

Extended roadmap →

Core & Add-on Modules

Sell Core Foundation plus optional microservice modules — pricing by complexity.

Module catalog →

Payment Workflow

Option B: parent submits payment claim → bursar verifies → receipt issued.

Read spec →

Student Health Records

Parent-confirmed health data, doctor's note, nurse-only access group.

Read spec →

Architecture

14 microservices, event bus, gateway routes, deployment topology.

View architecture →

UI Samples

Static mockups for parent payment claim, bursar queue, dashboards.

View samples →

Development phases

PhaseScopeMilestone
1Registration, auth, multi-campus org, parent loginFoundation
2Fees, invoices, payment claims, bursar verification, receipts in portalGo-live for fees
3Attendance, notices, requirements checklist, stock, student health recordsOperations
4Academics, grading, report cards, homework distributionAcademic year
5Full finance (P&L, balance sheet), uniformsEnterprise
6Android app — offline attendance, fee lookupMobile
Documentation: Requirements are published as HTML pages under Requirements. AsciiDoc (.adoc) versions will be added to the git repository later.