ITC508 Object Modelling: University Enrolment System Design

Desklib provides past papers and solved assignments for students. This project details a university student enrolment system.

ITC508 - Object Modelling
Assessment item 2
Elaboration phase

Table of Contents
Introduction......................................................................................................................................3
Functional Requirements.................................................................................................................4
Non-Functional Requirements.........................................................................................................5
Use case Diagram............................................................................................................................7
Domain Model Class Diagram......................................................................................................10
Event Partitioned System Diagram................................................................................................12
Conclusion.....................................................................................................................................14
References......................................................................................................................................15
Table of Figures
Figure 1: Use Case Diagram............................................................................................................7
Figure 2: Domain Model Class Diagram.......................................................................................10
Figure 3: Event Partitioned System Diagram................................................................................12
2 | P a g e

Introduction
In this assessment, the student enrolment system is going to develop and all the functional and
non-functional requirements according to the software development life cycle are defined
clearly. With the help of UML diagrams such as a class diagram, the system functionalities are
provided diagrammatically. The system should be accurate in order to interact with university
students with reliability, accuracy, and portability. After gathering requirements, the use case
diagram will be developed according to the case scenario. In the overall report, the event
partitioned system diagram and the domain model class diagram will be developed which
depends on the use case diagram.
3 | P a g e

Functional Requirements
Functional Requirements are the requirements that define the system functionality or their
components. Each function has its own behavior specification between inputs & outputs. In other
words, it specifies the particular system results (Bedjeti, et al., 2017).
There are some functional requirements for the Enrolment system which provides basic
functionalities of admin, teachers and the students.
 Student Functionalities:
o Can log in into the system.
o Can upload assignments into the system.
o Can also download the assignments and the lectures by the system.
o Can print and view the grade’s report.
o Can view courses available into the plan of students.
o Can solve examinations by webpages in the given time posted into the system.
o Can view timings available for the courses that were recently selected.
o Can update or enter the personal information with the help of the system.
o Can select the payment method which is suitable from the available list of payment
methods.
 Teacher Functionalities:
o Can log in into the system.
o Can grade examinations of students.
o Can upload assignments into the system.
o Can post assignments with due date or time.
o Can pot lectures of courses.
o Can post examination schedule including date and time.
 System Functionalities:
o Can remove the timing of classes for enrolled or registered students when it was
overloaded.
o Can check the payment timings and the process.
4 | P a g e

o Can display class locations, course details, timings, orientational details and the
assessment details to enrolled or registered students who were using dashboard.
o Can update student information or the extra information before paying for the
available courses.
 Admin Functionalities:
o Can log in into the system.
o Can make an account for the teacher or the student.
o Can perform operations for the enrolled students for making track of their interested
students.
o Can add courses for students.
o Can delete courses for students.
o Can update courses for students.
o Can assign teachers for the available courses.
o Can delete courses from the teachers.
o Can swap teachers that were assigned to the courses.
o Can swap courses that were assigned to the students.
Non-Functional Requirements
Non-Functional requirements are the quality attributes of the system. These attributes act as
constraints for the system. It defines how the system should perform at a very certain event. It
also defines the limits on functional requirements of the system (Engiel, et al., 2017).
There are some non-functional requirements for the Enrolment system:
 Availability: System is to be available for 365*24*7. It will work endlessly without any
failures.
 Performance: It includes the information of resources that required accurately. Response
time and date of each operation and query that was performed by end users have to be low
and the system will respond quickly. Rates of the transaction have to be fast and the
throughput of the system is to be high.
 Security: The system has to be more secure for securing the user’s (admin, tutors, and
students) personal information. This information includes the contact detail, payment history,
5 | P a g e

card details and many more. The passwords of the user’s information are should be in an
encrypted format. The system has to make a unique id for the identification of users.
 Usability: It can make easy access for the users for operating or maintaining the system.
 Operating system: The system resources and software should work according to the system
functionality because they are working with runtime limitations.
 Portability: With the growing technology, the system should be compatible with all the
changes in the technologies.
 Reliability: It defines the time which is faced between the failure and recovering from that
failure. So, in this meantime, the system will be able to find the threats or risks and the
techniques to protect the information and also avoid that failure in the future.
 Modifiability: The changes should be acceptable by the system and the capability to
implement that changes in system design.
6 | P a g e

Use case Diagram
Figure 1: Use Case Diagram
Name of Use Case Add Personal Details
Scenario Student can add their personal details for enrolment into the system.
Triggering Event For selecting their required courses, students have to add their
personal details first then only they can select the courses.
Description Use case of adding personal details provides the functionality to the
students for adding their personal details such as their name, address,
7 | P a g e

identity, course details, and the payment details. For using the extra
functionality of the system, the student requires their personal details.
Students can add select their courses with their requirements and
after selecting courses, they can make payment with the different
payment modes. Student can also edit their details which were
provided in the time of registration (Custodio & Castro, 2016).
Actors Student
Related Use cases Register, add personal details, select courses, edit details, and pay
fee.
Stakeholders System Admin, student and tutor
Pre-Conditions  Students can register themselves in the system.
 They have to provide their personal details in the system.
 They can edit their personal details from the system.
 They can select their courses with their timings.
 They can make a payment from different payment modes.
Post-Conditions For further activities, students have to save their personal details in
the system.
Activities Flow S.
No.
Student System
1. Student can register
themselves into the system.
The system will display the
registration form.
2. Student can enter their
personal details.
System will display the list
of available courses.
3. Student can select their
courses with their timings.
System will provide the
options of updating details.
4. Student can make payment System will provide
8 | P a g e

for selected courses. different available payment
modes.
Expected conditions  Student didn’t register themselves into the system.
 Student failed to select courses for finalizing payment
process.
9 | P a g e

Domain Model Class Diagram
Figure 2: Domain Model Class Diagram
EnrolStudent Class
This class introduced to store the details of the students. To store the details of the student admin
has to enter the personal details of the Student like student ID, password, address, mobile
number, and email id. Functions are also defined to perform the specific function. ShowDetails()
method is created in order to show the student’s details. UpdateDetails() is created to update the
student details. DeleteStdent() is created to delete the student from the system.
Tutors Class
This class is created to store the details of the tutors like his/her tutor ID, password, name,
address, mobile number, email id. Several methods are also created in this class. RegisterTutor()
is created to register the student in the system. UpdateDetails() is created to update the details of
the tutor. DeleteTutor() is created to delete the tutor from the system (Dahiya, et al., 2016).
Registration Class
10 | P a g e

Registration class is introduced to store the registration details of the system members like the
registration ID, registration time and registration fee. Some methods are also defined in this
class. AddDetails() is created to add the registration details in the system. Register() is created to
register the student and tutor in the system.
AvailableCourses Class
This class is introduced in order to store the details of the courses which are available in the
system. To store the details of the courses admin has to enter the code of the course, name of the
course, tome period of the course and the tutor code who will teach that code. Some methods are
also defined in this class in order to perform the specific functions like UpdateTiming() method
is used to change the time period of the courses. RemoveCourse() is defined in order to remove
the course from the system. UpdateDetails() method is created in order to update the details of
the courses.
SystemAdmin Class
SystemAdmin is created to store the details of the admin like admin id and password. Several
methods are also defined in this class. AddCourses() is created to add the new courses in the
system. Addnewstudent() is created to introduce new students in the system. AssignedTutor() is
created in order to assign the tutor for the particular course. Keeprecord() is created to track the
record of the student, tutor, and courses.
11 | P a g e

Event Partitioned System Diagram
Figure 3: Event Partitioned System Diagram
In this Event diagram the system functioning is defined which includes the student and the
admin. The student has to enter the personal details in order to register in the system. After
entering the personal details system verified the registration process. Then the user has to select
the term which is verified by the system to select the courses. After selecting the term system
shows the number of courses which a student can choose in that term. The student has to select
the timing which is mentioned in the course database. After selecting the course student has to
12 | P a g e