Object Oriented Modeling for University Enrollment System

This report describes the functionality and non-functional requirements of an enrollment system for a university. It includes use case description, UML domain class model, and event partitioned system model.

Running head: OBJECT ORIENTED MODELING
OBJECT ORIENTED MODELING - UNIVERSITY
ENROLLMENT SYSTEM
Name of the Student
Name of the University
Author Note

1OBJECT ORIENTED MODELING
Table of Contents
Introduction......................................................................................................................................2
About the enrollment system.......................................................................................................2
Functional requirements for the Enrollment system........................................................................3
Non functional requirements...........................................................................................................4
Use case...........................................................................................................................................6
Use Case Description...................................................................................................................6
Fully developed use case.............................................................................................................7
Use Case Diagram.......................................................................................................................9
UML domain class model..............................................................................................................10
Event partitioned system model for the use cases.........................................................................12
Conclusion.....................................................................................................................................14
Bibliography..................................................................................................................................15

2OBJECT ORIENTED MODELING
Introduction
The report aims at describing the main functioning that is going to be performed with the
university enrollment system. National University is one of the leading universities of
Melbourne, Australia that offers diploma courses, postgraduate courses and undergraduate
degree in different courses. The courses that are offered with the university includes Information
Technology, humanities, information systems, accounting, business, law and Arts. The university
includes three major semesters in every year. Thus in order to facilitate the working of the
university the administration department wants to implement an enrollment system that will help
in assisting the enrollment of students throughout the year. The report will mainly focus on the
functional and non functional requirements that are associated with this system. In addition to
this the use case diagram for the enrollment system will also be developed along with the major
use cases. With the help of UML model the functioning of the system will be described. Lastly
the report will focus on developing event partitioned system models for analyzing the major use
cases.
About the enrollment system
The enrollment system will focus on providing a better access towards the users. The
enrollment system will ensure that all the data regarding each student are being processed
effectively without any error. The system will allow the user to choose their courses and course
timing based on their interest. As soon as the user gets registered than the system will deliver
them the timings available and the course they can choose. Once every details gets registered
fulfilled the system will allow the user to make payment by choosing appropriate payment
methods. Finally the system will display the course details along with the timings so that each

3OBJECT ORIENTED MODELING
student can conduct their semesters effectively. Moreover the system will also be available
towards the administrative so that they can review the data regarding each student and will also
be able to analyze the subject that is being selected by the maximum number of students. This
will help the administrative to allocate sufficient faculty towards the course department.
Functional requirements for the Enrollment system
The main functionality that is going to be performed by the system includes gathering the
details about student credential. Once this information are being enlisted within the system than
they will be able to login within the system. These will include student id, email, name, address,
phone number. As soon as the authentication is done then the system will allow the user to
proceed with the system. The credentials will be used by the system in future for accessing the
system. The system can be accessed using these details and will be able to learn about the main
activities that is taking place within the university. After these the user needs to select their
appropriate course so that they can enroll for the course and for the upcoming semester. The
system will show the list of courses that includes accounting, business, law, arts, humanities, and
information technology and information system. The user needs to choose among these subjects.
Along with this the user needs to choose the appropriate term on which they are going to appear.
After the login is made by the student and they has chosen appropriate courses than the system
will verify the details and will check whether proper selection is made by the user or not. The
system will also check whether there is a availability of the subject or not so that they can
allocate proper specializations.After these the system will display the availability of the corses
for the users. The courses will be prepared based on the terms. Based on the terms students are
allowed to choose 3-4 courses. In addition to this the system will allow the user to choose their

4OBJECT ORIENTED MODELING
course timings. The system will only allow 40 students to get allocated within a class. This is the
limit set for each classes. As soon as the class limits reaches the system will not accept any
enrollment. After this the system will display the next class timings towards the users so that
they can choose an alternative timing. These stages are needed to be completed efficiently so that
it does not cause any hamper towards the student. Every details needs to be reviewed properly by
the student so that they can proceed with the fees structure.Once the system finds any incorrect
details than the system will ask the user to make necessary changes so that it can be processed
effectively without any error. The last function that is performed by the system is that it will
focus on displaying the necessary information about commencement dates of academic terms,
week of orientation, library and department location depending on the enrollment. This is main
functionalities that are performed by the system in order to work effectively towards the
university and their students. The main purpose behind developing this enrollment system is to
ensure effective management of the academic details so that it can offer better ways towards the
users. In addition to this the administrative department of national university has the opportunity
to use this enrollment system for the purpose or gathering the data regarding each student
enrollment data. These will help the administrative to understand the area in which student
possess maximum interest and minimum interest. The main aim behind analyzing this is that it
will help in allocating effective number of faculties so that they can have better control over the
activities going on within the university
Non functional requirements
Non functional requirements are basically referred to the requirements that are used for the
purpose of determining the activity that are performed by the system. The enrollment system is

5OBJECT ORIENTED MODELING
mainly developed for the purpose of facilitating the users with appropriate control over the
university details. This will help in analyzing the performance that are offered with the system.
The main focus is to develop an enrollment system that will help users and administrative
department to manage the courses and timings within the university. The non functional
requirements are further classified into execution qualities and the evolution qualities. The
execution qualities are referred to the qualities that are offered with the system. This checks the
security , safety and usability that are offered with the proposed system. The proposed system
here is the enrolment system that offers better durability and security towards the data stored
regarding each students. On the other hand evolution qualities are referred to testability qualities,
maintainability qualities so that they can maintain a proper static structure throughout the system
The main non functional requirements based on which a system is being analyzed includes the
efficiency that is provided by the system, the security and the reliability that are offered with the
system. The major non functional requirements are described below:
 Availability: this is used for the purpose of checking whether the implemented system is
available towards the users or not. The enrollment system developed can be accessed by
the users and by university administrative without any problem. This system is available
towards them throughout the course and can have the access at any time.
 Maintainability: it becomes essential to ensure that the developed system is able to
maintain effective criteria for proper maintenance of the system. The system will perform
the regular functioning by ensuring proper updated version. The enrollment system needs
to be updated with latest modifications in the course and timing so that it can alert their
users about the changes that are made within the course.

6OBJECT ORIENTED MODELING
 Usability: this offers that the system developed for the users are easy to use and modify
so that they can grant proper access. Usability plays a major role in the working of the
system. Enrollment system needs proper usability specifications so that they can be used
by maximums students for retrieving the data regarding all activities.
 Scalability: this is one of the crucial factor that is needed to be focused on. This mainly
aims at describing the ability of the enrollment system to get accessed by any devices.
The system needs to be developed in such a way that it can be accessed from any device
at any time. This will ensure better performance of the system.
Thus it can be stated that the functionality requirements will help in understanding the proper
functioning of the system. it becomes essential to maintain proper functionality so that the
maximum output can be obtained from the system.
Use case
Use Case Description
The Uses cases which are important to assess the performance of enrollment system are
described below:
Use Case Description
Gathering details The user provides the credential details within the system
Providing details The users are allowed to describe the details regarding email id, phone
number, student id, name
Choosing course The users can choose appropriate courses from information system,

7OBJECT ORIENTED MODELING
information technology, buisness,, laws and humanities.
Verifying details After the user enters all the details than they are verified by the system and
checks whether subject is available or not.
Displaying available
courses
System will describe the courses that are available so that they can choose
among this courses.
Choosing other time As soon as the system finds that the class limit has reached than the users
are provided with other time alternatives.
Review Details The details entered by each users needs to be reviewed properly so that the
can proceed to fees stage.
Changes needed As soon as the system finds that there is an inappropriate detail within the
system than it asks the user to modify the data.
Payment options The system will provide proper payment options so that they can proceed
with the fees. These includes choosing from debit card, master card or
designated account number.
Payment The user needs to provide card details while processing with master card or
debit cad.
Receipt generated The system process the payment as soon as all the details are being verified
and a receipt is generated towards the users.
Display information The system will display the necessary information regarding academic
terms, week orientation and department.
Administrative Checking the details of each student and understanding the course of
interest for maximum students.
Table- 2 Use Case Description

8OBJECT ORIENTED MODELING
Fully developed use case
Use case ID UC2
Use Case Name Providing Details
Description The user needs to enter all the credential data so that they fan enroll themselves
for the academic sessions.
Primary Actors Students
Secondary Actors System
Pre-condition Providing credential details
Flow Actor System
1. Logging into the system
2. Entering necessary details
3. Saving the details for
further enrollment process
1. Providing proper forms
2. Updating the details within the
forms
3. Store the details
Post-condition Enrolling the students
Exceptions An exception takes place in case the student misses out any compulsory data.
This will impact the process of enrollment and the user will need to update the
details again.
Table- 3 Fully Developed Use Case

9OBJECT ORIENTED MODELING
Use Case Diagram

10OBJECT ORIENTED MODELING
UML domain class model

11OBJECT ORIENTED MODELING

12OBJECT ORIENTED MODELING
The domain model class diagram has been developed above for the description of the
Student enrollment system of the National University. The major entities and classes has been
identified in the system for the National university. The main classes in the system are the
Student and the administrator. The student class records all the details of the students in the
system. The administrator name and the administrator ID are both recorded in the administrator
class. The course ID, and the other details of the courses are stored in the course class. The
payment records are stored in the system with the help of the payment class. The enrolment class
stores the enrolment details and the payment class is associated with the enrollment details. The
invoice is also an associated class with the payment system which would include the further
details of the payment class in the system.
Event partitioned system model for the use cases

13OBJECT ORIENTED MODELING
The main components of event partitioned diagram are users and administrative. These two
are the main components that are associated with the enrollment system of the national
university. The main event that takes place within the system are as follows:
 The users are responsible for providing credential data so that they can get enrollled
within the system. Once the data is entered within the system this are further verified by
the system and the process gets initiated.
 The user can choose their course and time of course as per their need.
 The system verifies each credential so that it can allow proper students with correct data
sets.
 The system also focuses on developing a list of courses and time that are available.
 Users are offered with different time slot as soon as the course gets filled with 40
students. It is important to maintain the class limit for every course.
 System asks the users to review the details so that they can proceed with further process
for making the fees transactions.
 User verifies each details and proceed with the fees payment procedures.
 Different payment methods are offered to the users so that they can choose appropriate
way of making the payments.
 User needs to provide input for the card so that they can process the transaction.
 Once the system completes all transaction than the system displays all necessary details
regarding the course to the users.
 Administrative are responsible for reviewing the user details.
 Administrative can review each course details and number of people enrolled for a
particular course.

14OBJECT ORIENTED MODELING
Conclusion
Thus from the above report it can be stated that with the implementation of enrollment
system it will become easy to manage the activities that takes place within the national
university. The national university will be able to manage the activities effectively without any
problem. The report has described all the major components in details with the important actors.
The main actors that are important for this system are the students and the administrative. The
report has derived the use case diagram for the enrollment system so that it becomes easy to
understand the working of the system. In addition to this the report has also addressed all the
important use cases along with the description. This will ensure proper understanding of the
activities that are expected to be performed within the system. The report has also developed a
UML diagram that will describe the activities. The last part of the report has included the event
partitioned diagram for the enrollment system. Thus it can be stated that enrollment system will
provide better benefits towards the national university of Melbourne.

15OBJECT ORIENTED MODELING
Bibliography
Dabbagh, M., Lee, S. P., &Parizi, R. M. (2016). Functional and non-functional requirements
prioritization: empirical evaluation of IPA, AHP-based, and HAM-based approaches. Soft
Computing, 20(11), 4497-4520.
David, O., Markstrom, S. L., Rojas, K. W., Ahuja, L. R., & Schneider, I. W. (2016). The object
modeling system. In Agricultural system models in field research and technology
transfer (pp. 322-335). CRC Press.
Dennis, A., Wixom, B. H., &Tegarden, D. (2015). Systems analysis and design: An object-
oriented approach with UML. John wiley & sons.
Eckhardt, J., Vogelsang, A., & Fernández, D. M. (2016, May). Are" non-functional"
requirements really non-functional? an investigation of non-functional requirements in
practice. In 2016 IEEE/ACM 38th International Conference on Software Engineering
(ICSE) (pp. 832-842). IEEE.
Gómez, F. J., Chaves, M. A., Vanfretti, L., & Olsen, S. H. (2018). Multi-Domain Semantic
Information and Physical Behavior Modeling of Power Systems and Gas Turbines
Expanding the Common Information Model. IEEE Access, 6, 72663-72674.
Halpin, T. (2015). Object-Role Modeling Fundamentals: A practical guide to data modeling with
ORM. Technics Publications.

16OBJECT ORIENTED MODELING
Kang, K., Merwade, V., Chun, J. A., & Timlin, D. (2016). Flexibility on storage-release based
distributed hydrologic modeling with object-oriented approach. Journal of
hydrology, 540, 17-25.
Khan, F., Jan, S. R., Tahir, M., Khan, S., & Ullah, F. (2016). Survey: dealing non-functional
requirements at architecture level. VFAST Transactions on Software Engineering, 9(2), 7-
13.
Khan, S., Babar, M., Khan, F., Arif, F., & Tahir, M. (2016). Collaboration Methodology for
Integrating Non-Functional Requirements in Architecture. the Journal of Applied
Environmental and Biological Sciences (JAEBS), 6(4S), 63-67.
Kurtanović, Z., & Maalej, W. (2017, September). Automatically classifying functional and non-
functional requirements using supervised machine learning. In 2017 IEEE 25th
International Requirements Engineering Conference (RE) (pp. 490-495). IEEE.
Mall, R. (2018). Fundamentals of software engineering. PHI Learning Pvt. Ltd..
Pauker, F., Wolny, S., Fallah, S. M., & Wimmer, M. (2018). UML2OPC-UATransforming UML
Class Diagrams to OPC UA Information Models. Procedia CIRP, 67, 128-133.
Solomencevs, A., & Osis, J. (2015, April). The algorithm for getting a uml class diagram from
topological functioning model. In 2015 International Conference on Evaluation of Novel
Approaches to Software Engineering (ENASE) (pp. 341-351). IEEE.
Spangenberg, N., Augenstein, C., Franczyk, B., Wagner, M., Apitz, M., &Kenngott, H. (2017,
June). Method for intra-surgical phase detection by using real-time medical device data.

17OBJECT ORIENTED MODELING
In 2017 IEEE 30th International Symposium on Computer-Based Medical Systems
(CBMS) (pp. 254-259). IEEE.