Requirement Engineering
University Sports & Facility Booking System
A requirements specification for a campus system that lets students and staff book sports facilities in real time and gives administrators usage reports, built from a user questionnaire, an interview and an AND/OR goal model.
- Team of 7
Project Files 1
What I learned
The challenge
Balancing goals that pull against each other: more flexible booking makes double bookings more likely, and syncing data everywhere can delay instant updates. We recorded every conflict and dependency in the goal model, then traced each requirement back to a goal.
The experience
Working through requirements engineering in a team of seven, from asking users what they need to specifying 15 functional and 10 quality requirements.
Skills I developed
- Requirements elicitation
- Questionnaires & interviews
- Goal modelling (AND/OR)
- Functional requirements
- Quality requirements (ISO/IEC 25010)
01The problem
Manual booking of university sports facilities leads to double bookings, poor tracking of how facilities are used and limited access for students and staff.
02What the team built
- A 20-question questionnaire for students, staff and administrators, and an interview with a regular gym user
- An AND/OR goal diagram and a goal table that records how goals depend on, support or conflict with each other
- 15 functional requirements, each mapped to a goal
- 10 quality requirements mapped to ISO/IEC 25010, and 5 constraints
03Software engineering process
Research
A questionnaire and a short interview showed that users wanted real-time availability, booking reminders and faster confirmation, and found the system slow and hard to use on phones.
Requirements
The findings became an AND/OR goal model with a goal table, refined into a final goal diagram, then functional requirements, quality requirements and constraints, each traced to a goal.