Object and Data Modelling

This document provides an overview of object and data modelling, including functional and non-functional requirements, use cases, and system models. It discusses the importance of security, real-time data flow, availability, usability, user interface, reliability, and performance. The document also includes a bibliography for further reading.

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
1.1 Functional Requirement:.......................................................................................................2
1.2 Non-Functionality:.................................................................................................................4
2. Use Cases:....................................................................................................................................6
UML Domain Model Class Diagram:.............................................................................................9
Event Partitioned System Model:..................................................................................................10
Bibliography:.................................................................................................................................11

2OBJECT AND DATA MODELLING
1. Functional and Non-Functional Requirements:
The functional requirement describes about the processes that must be executed by the
system. On the other hand, the non-functional requirements measures the quality of execution of
the processes mentioned in functional requirements.
1.1 Functional Requirement:
Selecting Major: The system should have information regarding all the majors that are
offered by the National University. The first step toward getting enrollment into the National
University is selecting the Major. The student will receive a user interface that will list all the
majors available in the National University. Among all those majors the student can select only
one major. The number of majors visible on the screen will be limited to the number of majors
offered by the National University. That is why the student will select one of the available
majors.
Course Selection: After the student has selected the major, the system will redirect the
user to another page. In order to complete the enrollment process, it is essential that student
selects the course. These courses are categorized into the majors. Each major has different course
among which the student have to select one. The course selection is also like the major as the
number of courses available on the system is limited by the courses actually offered by the
National University. The student should be able to select different course if mistakenly selected
one.
Login: Login is an essential function that the system must have. The login is for the
system to recognize the validity of the user. The users of the system will be accessing the system
from their home. That is why it will be impossible to track which user is accessing the system

3OBJECT AND DATA MODELLING
from which device. The online systems uses the login id or email address of the user to recognize
the user. The login process allows the system to store the activities of the user in an organization
way. This is possible because, only one user can access to the system through one browser.
Registration: Registration is the way of collecting user data. The system needs to register
all the users for maintaining a security in the system. In order to register, the users have to
provide their personal details. The amount of details will vary based on the user category. The
management will provide different data than a student at the time of registration. During the
registration, the user selects the login credentials such as login id and password. The system
follows strong and complex password policy. The system also asks the user to verify the
password they have provided by re-typing the password into conform password field.
Report Generation: The system will be responsible for generating reports for the
management of the National University. The reports are generated using the data available in the
database along with the information generated by analyzing those data. The report is generally
meant for the management. However, the normal staff and teaching faculty can see the reports.
The management has the right to access every data and include those data into the report. The
teaching staff can only access the data to create reports that is related his role.
Major and Course Creation: The system requires to store the information of the majors
and courses to display those as options to the student. The administrator and teaching staff are
the responsible person to create the major and courses into the system database. In order to
complete this task, they get an interface which has all the necessary fields for creating a major or
course. At the time of creating a course, the teaching staff or administrator will select the major
in which it will reside.

4OBJECT AND DATA MODELLING
Payment: Payment is another crucial functional requirement for the proposed system.
The payment is made by the students. After the system gets the trigger that course has been
confirmed, the system prepares the payment page. The student will select one of the many
options for making payment. The payment can be done in one of three ways, such as cash, card
or PayPal account. The system will promoted payment through card. If the payment is to be done
by cash, then after the student physically pays the amount, the enrolment is confirmed. IT is
essential to remember that every required data and only necessary options are available to
student to make payment.
1.2 Non-Functionality:
Security: The security of the system can be put in the top major non-functional
requirement concern of proposed system. Proposed application allows the customer to make
payment through the system. During this process, the card details are stored into the system.
Because the payment transaction related data are transmitted through insecure open internet
connection. For this reason, the system needs a strong encryption/decryption methodology. This
technique will encrypt the message in such way that it can only be decrypted in the other end.
The security will be installed in the server also so that most of the major attacks can be
prevented.
Real Time: The real-time information flow states data in the system will flow in real
time. This means that the data inputted into the system will be visible to other users before it is
entered into the database. The real time data will be extremely helpful to data integrity. The
information flow in the system will be extremely fast and the user will not need to refresh the
page repeatedly to see updated information.

5OBJECT AND DATA MODELLING
Availability: The system should be available to the user 24*7. The users can access the
system anytime they want. As the system will provide remote access, there should not be any
restriction on access time. However, to update the system, down time will occur. If must then the
system can be at mid night. The system should inform the users about the unavailability of server
including the time and duration.
Usability: The usability refers to the situation how easily the users can access the
formation. The system should follow the usability principles to allow the users to understand
how to complete a task. The system will integrate three click policy so that a user do not have to
click more than thrice to get desired data. The system must have an efficient navigation. A main
menu will be put in every page of the system so that users can easily navigate. The system will
include error prevention technique. The users will get alert messages when they make a mistake.
The system will integrate easy roll back option. Hints will be provided for complex processes.
User Interface: The user interface will be the communication intermediate between the
users and the application. The user interface will provide only the information enough for
understanding and completing tasks. The processes done in the server will not be visible by the
user. The user interface will be created using three or four technologies. The interface will be
responsive so that user can open the system in various devices of different resolutions.
Reliability: The user must have complete trust in the system. They must be sure about the
information that system shares with them. The reliability ensures user satisfaction while using
the system. The system must show authentic data. Taken as an example, if a course is not
available then system should show that to student. Otherwise, the student will get admission
through the system and will find out that in reality his admission is cancelled. If the system is not
reliable then existence of it will have no meaning.

6OBJECT AND DATA MODELLING
Performance: The system should perform every task properly within desired time. The
system must respond to user request or action within three sends maximum. In case the internet
connection is low then an alert should be prompted to the screen. The system must complete a
task by maintaining the usability and security conventions. The system will be computing all the
processes up in the server where the processing power is very high so that user system resources
are used as less as possible. This is because, few processes requires huge amount of resources
that low end PC or mobile devices cannot support and the system will crash. In order to reduce
the response time, few low processing tasks will be executed at the user device.
2. Use Cases:
Registration: Registration is a basic use case of the system which allow user to register
into the system. This use case is accessed by student, teaching staff and administrator. This use
case is related to login use case. This use case has precondition that user should not have any
existing account within the application. The post condition of this use case is user is given login
credentials for signing in. The use case exception that user may be banned from the system.
Login: This use case is for allowing the users to access the system authorized way. This
use case is accessed by student, teaching staff and administrator. This use case is related to
registration use case. This use case has precondition that user should have existing account in the
system. The post condition of this use case is user is given access into the system. The use case
exception that system is blocking the user from accessing it.
Select Major: This use case is for allowing the students to select the major of their
choice. This use case is accessed by student only as they are allowed to enroll into course. This
use case is related to select course use case. This use case has precondition that student must be

7OBJECT AND DATA MODELLING
logged into the system. The post condition of this use case is system shows whether the major is
available or not. The use case exception that desired major is not available in the system.
Select Course: This use case is for allowing the students to select the course of their
choice which available within the selected major. This use case is accessed by student only as
they are allowed to enroll into course. This use case is related to select major use case. This use
case has precondition that student must select an available major. The post condition of this use
case is system asks the student to review all the selections that he/she has made. The use case
exception that system is not going forward to review page.
Make Payment: This use case is for allowing the students to pay for the course they have
selected. This use case is accessed by student only as they are allowed to enroll into course. This
use case is related to select major use case. This use case has precondition that student must
select an available major and course under that major. The post condition of this use case is
system will shows the outcome of the payment such as successful or unsuccessful. The use case
exception that payment gateway server is not working.
Add Course: This use case is for allowing the teaching staff to add new courses into the
system. This use case is accessed by teaching staff only. This use case is related to no other use
case. This use case has precondition that teaching staff must login to the system. The post
condition of this use case is system ask the major under which it will be mapped. The use case
exception that course is in the blacklist.
See Student Details: This use case is for allowing the management staff to see all the
student details such as their personal details and to which course they have enrolled. This use
case is accessed by management staff only. This use case is related to no other use case. This use

8OBJECT AND DATA MODELLING
case has precondition that management authorized devices should be used to access the system.
The post condition of this use case is a report is generated which can be exported in excel format.
The use case exception that no student has registered this season yet.
Figure 1: Use Case of Enrollment System
(Source: Created by Author)
Use Case ID UC_Student_04
Use Case Name Select Course
Precondition The student must be logged in
Actors Student
Associated Use Case Select major
Post-condition Student reviews all the selections that he/she has made

9OBJECT AND DATA MODELLING
Action Student select the major
The system shows the available courses under that major
The student select one of the course
The student conform the course
The system redirect the user to new page
Exception System is not going forward to review page

10OBJECT AND DATA MODELLING
UML Domain Model Class Diagram:

11OBJECT AND DATA MODELLING
Event Partitioned System Model:

12OBJECT AND DATA MODELLING
Bibliography:
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.
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.
Cowen, J. M., & Creed, B. (2017). Public School Choice and Student Achievement: Evidence
From Michigan’s Interdistrict Open Enrollment System. AERA Open, 3(3),
2332858417731555.
Aithal, P. S., Shailashree, V., & Kumar, P. M. (2016). Analysis of NAAC Accreditation System
using ABCD framework. International Journal of Management, IT and
Engineering, 6(1), 30-44.
El-Katary, H. M., Hamed, E. M. R., & Mahmoud, S. S. (2016). A Model for Classification
Secondary School Student Enrollment Approval Based on E-Learning Management
System and E-Games. INTERNATIONAL JOURNAL OF ADVANCED COMPUTER
SCIENCE AND APPLICATIONS, 7(2), 68-73.
Jagtap, S., Gawde, V., Pawar, R., Shendge, S., & Avhad, P. (2016). Generate Test Cases From
UML Use Case and State Chart Diagrams. International Research Journal of
Engineering and Technology (IRJET), 3, 873-881.

13OBJECT AND DATA MODELLING
Nassif, A. B., Capretz, L. F., & Ho, D. (2016). Enhancing use case points estimation method
using soft computing techniques. arXiv preprint arXiv:1612.01078.
de Sousa, T. C., Kelvin, L., Neto, C. D., & de Carvalho, C. G. N. (2017). A Formal Semantics
for Use Case Diagram Via Event-B. JSW, 12(3), 189-200.
Wolters, D., Gerth, C., & Engels, G. (2016). Modeling Cross-Device Systems with Use Case
Diagrams. In CAiSE Forum(pp. 89-96).
Kumar, B., & Singh, K. (2015). Testing uml designs using class, sequence and activity
diagrams. International Journal for Innovative Research in Science and
Technology, 2(3), 71-81.
Torchiano, M., Scanniello, G., Ricca, F., Reggio, G., & Leotta, M. (2017). Do UML object
diagrams affect design comprehensibility? Results from a family of four controlled
experiments. Journal of Visual Languages & Computing, 41, 10-21.
Torre, D., Labiche, Y., Genero, M., Baldassarre, M. T., & Elaasar, M. (2018, May). UML
diagram synthesis techniques: a systematic mapping study. In 2018 IEEE/ACM 10th
International Workshop on Modelling in Software Engineering (MiSE) (pp. 33-40).
IEEE.
Harrison, S., Villano, R., Lynch, G., & Chen, G. (2015, March). Likelihood analysis of student
enrollment outcomes using learning environment variables: A case study approach.
In Proceedings of the Fifth International Conference on Learning Analytics And
Knowledge (pp. 141-145). ACM.

14OBJECT AND DATA MODELLING
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.
Faitelson, D., & Tyszberowicz, S. (2017, May). UML diagram refinement (focusing on class-and
use case diagrams). In Proceedings of the 39th International Conference on Software
Engineering (pp. 735-745). IEEE Press.
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.