Object Modelling

This report discusses the concept of object modelling in the context of developing a University Enrolment system. It covers functional and non-functional requirements, use case diagram, domain model class diagram, and event-partitioned system models.

Running head: OBJECT MODELLING
Object Modelling
Name of the Student
Name of the University
Author’s Note

1
OBJECT MODELLING
Table of Contents
Introduction................................................................................................................................2
Functional and Non-Functional Requirement............................................................................2
Use Case diagram.......................................................................................................................5
Domain Model Class Diagram...................................................................................................6
Event-Partitioned System models..............................................................................................7
Conclusion..................................................................................................................................7
Bibliography...............................................................................................................................9

2
OBJECT MODELLING
Introduction
The report is prepared for national university that has the requirement of developing
an University Enrolment system for facilitating the University administration department and
the students. The system is developed for the management of the university enrolment
throughout the academic year and help the administrator to gather student details from the
information system. The details of the students is needed to be inputted in the information
system like name, address, mobile number, personal details, email address, student id for
opening new account and they need to select their major subject. A verification is needed to
be done for the correct selection made by the student and show the available course in the
term for allowing the student to select the course and the class timing. The information
system helps in reducing the complexity of management and can close the enrolment request
once it reaches the limit. It also helps in automating the payment allows necessary changes to
be made in the information system for increasing the flexibility of operation.
Functional and Non-Functional Requirement
The functional requirement identified for the development of university enrolment system are
listed below:
Registration Component – It is needed for recording the student details and creating a
login account for the student with recording the details of the student such as name, address,
mobile number, personal email address and student id. The details of the student are validated
for the management of authentication and allowing the student to enrol for new courses and
classes.
Student component – It is key requirement where the student can select subjects
available in the course module and they can also preview the selection, semester and other
functionality of the profile.

3
OBJECT MODELLING
Management and Authentication – It is responsible for improving the security of the
University Enrolment System by authenticating the user and manages the activity of the user
such as creation of new account, removal of the account, modification of the account
information, etc. Moreover the component is also used for implementation of control access
matrix privilege.
Subject component – It is used for the implementation of functionality that are related
with different subject operation for the administrator. This functionality helps the
administrator to add new subject /courses in the information system, edit the credit points on
the existing subject or removing subject /course, etc. It is also used for showing the subjects
available to the user per semester.
Publish component – It is used for publishing reports, time table or notice that are
generated by administrator. The component is developed such that multiple time tables and
notices can be published at the same time.
Public component – It can be used by the guest viewer for accessing the information
system and find the subject and course offering for enrolling with the University course.
Payment component – It is used for receiving payment form the student for enrolling
with the course using different types of online payment options. The details of the payment
are recorded in the system such that the details are verified and a receipt is generated for the
user.
The following are the non-functional requirement that are essential for the
development of the university enrolment system of National University:
Security – The information residing in the enrolment system is needed to be protected
from the illegal access because it contains sensitive information such as the card details of the

4
OBJECT MODELLING
user that can be misused for gaining monetary benefits. Application of encryption and
asymmetric key authentication mechanism can eliminate the risk of different attacks.
Availability – The modules developed for the information system is needed to be
tested for checking the interaction between them and a direct connection should be used with
the database. The database is needed to be available 24*7 and the registration time should be
allowed during the office hours only such that the users not having internet connection at
home faces problem with enrolment. It is also needed to be connected via a high speed
internet such that the internet speed does not cause a bottleneck for degrading the
performance.
Usability – The information system is needed to be connected with a simple front end
interface such that the users face no problem while using the system. The student ID is
needed to be used as the username and customization is needed to be available such that the
user can customize the view according to their needs. Options editing the personal data
should also be provided such that the user can upgrade their profile and keep it updated.
Scalability – The information system is needed to be developed for handling the
future needs of the university. The modules developed for the information system is needed
to independent from each other and provide the desired result on integrating with each other
such that new modules can be added for increasing the functionality of the information
system.

5
OBJECT MODELLING
Use Case diagram

6
OBJECT MODELLING
Domain Model Class Diagram

7
OBJECT MODELLING
Event-Partitioned System models
Conclusion
For the development of the University enrolment system the requirement of the
University is evaluated and models are created. The functional and the non-functional
requirement identified for the development of University enrolment system is evaluated for
reviewing the complexity of the information system. For starting the development of the
system a software development methodology is needed to be selected and starting with the
development of the modules. The requirement is analysed for the development of the use case
and finding the actors associated with the system. The development is needed to be done in
phases consisting of the phases including planning concept for identification of the

8
OBJECT MODELLING
opportunity of the project by comparing successful examples and exploring the new features
that can eb added in the system. The inception phase is used for allocation of budget and
initial support is identified with involving the stakeholders. The iteration construction phase
is used for analysis of the design and identifying the complex issues for sorting the issues and
check the quality of codes. In the transition phase raw codes are tested and the development
of modules in phases.

9
OBJECT MODELLING
Bibliography
Nassif, A. B., Capretz, L. F., & Ho, D. (2016). Enhancing use case points estimation method
using soft computing techniques. arXiv preprint arXiv:1612.01078.
Suh, N. P. (2016). Challenges in Designing and Implementing Large Systems (Overcoming
Cost Overruns and Missed Project Schedules). In Axiomatic Design in Large
Systems(pp. 273-309). Springer, Cham.