Object and Data Modelling: Enrollment System Analysis Report

This report provides a detailed analysis of object and data modelling applied to a university enrollment system. It begins by outlining the functional and non-functional requirements, including major selection, course selection, login, registration, report generation, payment methods, and security considerations. The report then presents use cases that describe the student enrollment process, followed by a UML domain model class diagram illustrating the system's structure and a detailed event partitioned system model. The content includes diagrams and models to visually represent the system's components and interactions, providing a comprehensive overview of the enrollment process from a software engineering perspective. The report draws upon various academic sources to support its findings.

Running head: OBJECT AND DATA MODELLING
Object and Data Modelling
Name of the Student
Name of the University
Author’s note:

1OBJECT AND DATA MODELLING
Table of Contents
1. Functional and Non-Functional Requirements:...........................................................................2
2. Use Cases:....................................................................................................................................5
3. UML Domain Model Class Diagram:.........................................................................................7
4. Event Partitioned System Model:................................................................................................8
Bibliography:...................................................................................................................................9

2OBJECT AND DATA MODELLING
1. Functional and Non-Functional Requirements:
Functional Requirements:
Functional Requirements
Major selection process The student is able to select the major that is offered by the National
University. There are several steps that can be adapted by the user for
ensuring the major for their course. An interactive surface is available to
the user from where they can select their major subjects. These is a very
important step to ensure the enrollment of the student with the university.
The screen of the interactive surface contains the limited courses that are
offered by the university. The student can select from the available list
that is offered by the University.
Selection of the course When the student is done with selecting the major they can select the
courses that are offered. To complete the process of the enrollment the
student have to ensure that they have selected the list of the courses. These
is a very important step for the process of the course selection. These is
also limited to the selection of the available courses that is is offered by
the university. The courses comes under the major that is being selected
by the student.
Login process The system have an essential function that is the process of the
registration. These process ensures the user is valid. This also ensures that
the user can access their account from anywhere. They can also make the
required changes within their account that will be updated within their
account. But it is tough to identify the user who is using the system.
Registration process The press of the registration is very important. These ensures that the

3OBJECT AND DATA MODELLING
entered within the database of the system. These also help to easily make
the changes within the database that will ensure that the database will
always be updated. The credentials for the process registration need to fill
the information like login id and the password. The system have a very
strong base regarding the privacy issues. The information of the student
are kept in a very secure way. The students are also asked to retype their
password so that they can ensure that they do not put a wrong password.
Generation of report The system also dealt with the process of the generation of the report.
These have the information about the students who are employed with the
university. An analyzed information about the student is also available in
the system.
Course and major The major and the courses that are available under that particular major
are arranged in a particular way within the database. These make it easy
for the student to select a particular major and getting the knowledge of
the courses that falls under that criteria.
Mode of payment The user also get a variety of options for selecting the payment mode for
the system. The interface mainly promote the use of card payment as it an
environment-friendly option. If a cash payment is done the student have to
go to the management physically to ensure that the payment is made. The
IT people are responsible to ensure that the options are available to the
users to make the payment.

4OBJECT AND DATA MODELLING
Non-functional Requirements:
Non-functionality requirements
Security Security is a very important for an interactive systems. The payment information that is
done by the user is very important as it contains the information about the personal
account details of the user. The information about the student that is passed should not
be open. The encrypted information need to be passed that will only decoded by the
management. The threats from different type of attack user can experience a safe
environment while accessing the system need to be minimized so that they can enhance
their experience of using the system. The details of the user that are stored within the
system need to be safe and secure and should not be leaked by any means.
Real-time The flow of the data from the user to the management need to be real time. The data
that is typed by the user need to be visible. The task input need to be visible to the user
so that they can avoid the errors while assessing the system. Real-time data integrity is
important to the interactive system. The information or the flow of the data within the
system need to be such that it will not frustrate the users of the interactive system.
Accessibility The system need to be easily assessable to the users the terms that are used by the
system to give instructions to the users need to be simple. Complex term cannot be
understand by the use. These can create difficulties to the users while they use the
system. The use of the system should simple.
Usability The usability requirements refers to how the system is effective and efficient to the
users. It also allow the users o understand the complex activities that are included in
using the system. These will also allow the user to prevent the errors that occur while
using the system. The users also get the messages that are in simple language to redo or
undo any actions that are taken by them. The alert messages and the hints for using the

5OBJECT AND DATA MODELLING
interactive system is available to the users in easy terminologies.
User
interface
These is a where the interaction between the user and the system took place. The
process that are performed in the server is not available to the users as these
information will confuse the user of the system. The resolution of the devices from
where the system is used should not determine the responsiveness of the system. The
system need to be effective enough for undertaking and performing the tasks.
Reliability There is a need that the student can trust the system. The student to get satisfaction of
using the system need to have trust while using the system. If the user cannot rely on
the system that they are using they will never achieve the satisfaction level.
2. Use Cases:
Figure 1: Use Case of Enrollment System

6OBJECT AND DATA MODELLING
(Source: Created by Author)
Use Case ID UC EXTERNAL USER 08
Use Case Name Pay for Enrolment
Description The student can make payment using debit card, master card or
account number.
Precondition The user have to confirm that every details in review page is
correct
Trigger The system tries to close enrolment process
Actors Student
Stakeholder Student, National University. Teacher
Associated Use Case None
Action Student select payment option
If student selects the card then cardholder name, card number,
card type, expiry number and three digit code are entered into
the system
The user will confirm payment
Post-condition The system verify the entered details and create a receipt against
the payment
Exception The student card is blocked

7OBJECT AND DATA MODELLING
3. UML Domain Model Class Diagram:
Figure 2: UML Domain Model Class Diagram of Enrollment System
(Source: Created by Author)

8OBJECT AND DATA MODELLING
4. Event Partitioned System Model:
Figure 3: Event Partitioned System Model of Enrollment System
(Source: Created by Author)

9OBJECT AND DATA MODELLING
Bibliography:
Afreen, N., Khatoon, A., & Sadiq, M. (2016). A taxonomy of software’s non-functional
requirements. In Proceedings of the second international conference on computer and
communication technologies (pp. 47-53). Springer, New Delhi.
Arora, P. K., & Bhatia, R. (2018). Agent-Based Regression Test Case Generation using Class
Diagram, Use cases and Activity Diagram. Procedia Computer Science, 125, 747-753.
Azzeh, M., & Nassif, A. B. (2016). A hybrid model for estimating software project effort from
Use Case Points. Applied Soft Computing, 49, 981-989.
Bhatti, S. N., Usman, M., & Jadi, A. A. (2015). Validation to the requirement elicitation
framework via metrics. ACM SIGSOFT Software Engineering Notes, 40(5), 1-7.
Condori-Fernandez, N., & Lago, P. (2018). Characterizing the contribution of quality
requirements to software sustainability. Journal of Systems and Software, 137, 289-305.
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.
Horcas, J. M., Pinto, M., & Fuentes, L. (2016). An automatic process for weaving functional
quality attributes using a software product line approach. Journal of Systems and
Software, 112, 78-95.

10OBJECT AND DATA MODELLING
Jakobs, E. M., Digmayer, C., Vogelsang, S., & Servos, M. (2017, July). Not ready for industry
4.0: Usability of CAx systems. In International Conference on Applied Human Factors
and Ergonomics (pp. 51-62). Springer, Cham.
Kamimori, S., Ogata, S., & Kaijiri, K. (2015, July). Automatic method of generating a web
prototype employing live interactive widget to validate functional usability requirements.
In 2015 3rd International Conference on Applied Computing and Information
Technology/2nd International Conference on Computational Science and
Intelligence (pp. 8-13). IEEE.
Karim, S., Liawatimena, S., Trisetyarso, A., Abbas, B. S., & Suparta, W. (2017, November).
Automating functional and structural software size measurement based on XML structure
of UML sequence diagram. In 2017 IEEE International Conference on Cybernetics and
Computational Intelligence (CyberneticsCom) (pp. 24-28). IEEE.
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.
Mai, P. X., Goknil, A., Shar, L. K., Pastore, F., Briand, L. C., & Shaame, S. (2018). Modeling
security and privacy requirements: a use case-driven approach. Information and Software
Technology, 100, 165-182.
Murali, R., Ireland, A., & Grov, G. (2016, May). UC-B: Use case modelling with event-b.
In International Conference on Abstract State Machines, Alloy, B, TLA, VDM, and Z (pp.
297-302). Springer, Cham.

11OBJECT AND DATA MODELLING
Rodríguez, F. D., Acuña, S. T., & Juristo, N. (2015). Design and programming patterns for
implementing usability functionalities in web applications. Journal of Systems and
Software, 105, 107-124.
Smoots, G. C., Garstenauer, A., & Blackburn, T. (2016, April). Measuring system usability
during requirement engineering: requirements engineering. In 2016 International
Conference on Information Systems Engineering (ICISE) (pp. 68-72). IEEE.
Wautelet, Y., Heng, S., Hintea, D., Kolp, M., & Poelmans, S. (2016, November). Bridging user
story sets with the use case model. In International Conference on Conceptual
Modeling(pp. 127-138). Springer, Cham.