Education Management System

A commercial platform for a graduate school: admissions, advisor assignment, coursework, and thesis milestones for master's and doctoral students, replacing a mix of forms and spreadsheets.

• Stakeholders described what they do today, not what the system should do — the requirements had to be extracted, not collected.
• Each faculty had slightly different approval routes for the same document.

1. 01

   Structured elicitation

   Ran interview sessions per stakeholder group (students, advisors, graduate office), then consolidated findings into a URS written in the client's language.

2. 02

   URS → SRS translation

   Turned user requirements into an SRS with numbered functional requirements plus non-functional targets for performance, security and auditability that the dev team could estimate against.

3. 03

   Flow validation in Figma

   Reviewed prototypes with the designers and walked the client through each approval path before development started, catching missing states early.

• Role-based access: student, advisor, committee, graduate office admin.
• Configurable approval workflow so faculty-specific routes are data, not code.

• Requirement engineering
• URS / SRS
• UX analysis
• Web platform

• The development team started from a signed-off specification instead of meeting notes.
• Scope changes were traceable back to a numbered requirement.

• A requirement is only done when it has an acceptance criterion someone can test.
• Making a workflow configurable is cheaper than maintaining a branch per faculty.