Student and Teachers Management System in Java - University of Glasgow

UoG = University of Glasgow

You have been asked to develop a system to record student attendance to teaching sessions. A teaching session can be a Lecture, a Tutorial session or a Lab session. Each session is associated with a lead member of staff and a room, lecture theatre or lab section. Courses run over periods of 13 or 26 weeks, following a set pattern.
The system should allow a course coordinator to maintain lists of students associated with the course, assign them into one of multiple lecture occurrences and into smaller tutorial/lab groups associated to tutors and rooms/labs. The list of students comes from the central AIS system that records all students registered on a course. Each student is uniquely identified by their Student ID (SID). The course coordinator can add other students to the register list. These are students who are attending the course but they have not yet registered officially to the course. These must be centrally registered UoG students to a valid programme for CIS and they are identified by their SID or their unique computer systems user ID, also maintained centrally within the AIS. These students will be attached to the course as “temporary registrations”. Once the student registers officially to the course, their inclusion into the register lists for the course will automatically become “permanent”.
Tutors on the course can print blank registers for the current week for their own sessions. Students sign next to their name on the list during the teaching session. Following this the tutor will enter the student attendance onto the system by entering a “tick” next to each attending student’s name for that session. During some lecture sessions, a lecturer can pass around the class a customised PDA with an integral barcode reader. Attending students will scan their student card barcode using the reader to record their attendance at the session. Following this, the lecturer will dock the PDA at a cradle at the school office that will record all attendances onto the register system.
The system also provides individual attendance records and attendance statistics to tutors, managers and admin staff within the school. Students can only see their own attendance record by logging onto the system. Finally, the system should provide a hyperlinked version of a register with links to other information on each system coming from the central AIS system, such as registration status, holds, student photograph, programme name and a list of courses the student is officially registered on.
You are part of a system development team to do the analysis, design and development of their new hybrid system. They have a tight deadline of 4 months for the system to go live, staff should be trained within 2 weeks and the analysis, design and development of the new system should be within the budget of 40,000
pounds as decided by the Vice Chancellor.
Your team is required to build a working prototype of SAR system. The prototype should only simulate a mobile application.

The prototype should reflect the following:

  1. It should be built in an Object Oriented way using any appropriate technology you are familiar with (The prototype can be built as a .NET application (desktop or web), as a Java stand-alone application or any other application you are familiar with).

  2. The prototype system should have enough business and UI functionality to test the business life cycle of the main use cases from your use case diagram.


Only at a later stage, after the prototype is approved, a full system app would be required by the client. A well designed prototype code could be used straight for the final app using dedicated cross platform development suites such Xamarin. The finished product app is out of this coursework scope and you are not required to create one.

Note: Your team will not be penalised for implementing more functionality than required within your prototype.


Purchase the solution now in just one minute
Powered by