University Exam SystemPrivate

For four years I worked on the examination systems of a large private university, growing from junior analyst to senior system analyst. These systems carry the whole campus through each exam period, and the busiest hour of exam week decides how they have to be built.

 

An exam period runs from scheduling (courses, classes and time slots) to rooms and seat plans with clash checks, then exam day with attendance and proctor reports, and finally grade entry, review and published results. Students, lecturers, proctors and the academic office each use the part they need.

 

I engineered and maintained these systems with 99.9% reliability through exam weeks. Much of that came from the database: I rewrote the slowest SQL stored procedures and reworked parts of the database design, which significantly reduced server load at peak times. I also translated between the technical team and non-technical staff when gathering requirements.

 

The institution and its systems are private, so the screens here are redrawn with fake data.