Use Case Modeling for the Enrolment System

System modeling
USE CASE MODELING FOR THE ENROLMENT SYSTEM
Introduction
Use case modeling was first developed by Jacobson in the 1990s and was incorporated into the
first release of the UML (Pressman, 2012). Requirements specifications are acquired by the use
case modeling. A use case is what the user requests the system to do and the end result of that
request. A use case represents a single task that requires the user to interact with a system. A use
case is typically represented using an ellipse with the actors involved in the use case represented
as stick figures. The example below depicts the representation.
Figure1: Example of a use case model
Program director
Advantages of use case modeling
 The system’s functional requirements are defined at a very early stage of development
and therefore all stakeholders, including non-technical ones are able understand the
model.
 The major use cases are identified at an early stage, which helps to deduce other
preliminary use cases.
 The use case model can be used in all the other phases of the system development
lifecycle.
 The use case diagram provides a high level view of the entire system
The enrolment system
Open classes

System modeling
The proposed enrolment system comprises of four actors who include the program director, the
students, the timetabling manager and the teaching staff. Each has no less than two roles to play
in the system. They are expounded in the section below.
Actors and their roles
i.) Program director
 Survey progress of current students
 Choose students to enter program
 Schedule classes
 Allocate classes to teaching staff
 Open classes
 Access timetable
ii.) Student
 Enroll into class
 Access timetable
iii.)Timetabling manager
 Allocate classrooms to classes
 Avail classes
 Access timetable
iv.) Teaching staff
 Access timetable
Use case model

System modeling