Object Modelling

This document provides an overview of object modelling, including its functional and non-functional requirements. It covers topics such as use case, UML class diagram, and event partitioning diagram. The document also discusses usability, reliability, performance, and supportability in the context of the enrolment information system. It is a valuable resource for students studying system design and verification.

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

1OBJECT MODELLING
Table of Contents
1. Functional and Non-functional Requirements.............................................................................2
2. Use Case....................................................................................................................................5
2.1 Use Case diagram..................................................................................................................5
2.2 Use case Description..............................................................................................................6
2.3 Fully developed use case Description for Sign Up process...................................................8
3. UML Class Diagram..................................................................................................................10
4. Event Partitioning Diagram of Sign Up process........................................................................11
Bibliography..................................................................................................................................12

2OBJECT MODELLING
1. Functional and Non-functional Requirements
The national university enrolment system that is being proposed includes functional
requirements that are included in the system. Some of the functional requirements are listed
below:
 The system has the capability to take the input of the students so that they can be
registered on the database system of the enrolment system.
 All the details of the student is stored in the system along with the course details that the
students selects.
 The course details are also stored in the system database from which the students selects
their choice of course.
 Each course has different terms and all the terms details are also shown by the system
while taking the details of the course.
 Each class should have maximum total number of students as 40 and when the count is
finished, the system will exclude that particular course from the list.
 The final details of the students showing the course details and term details are shown by
the system before making the payment for the system.
 The enrolment system will allow a particular student to select a maximum of three or four
subjects from all the available courses.
 Necessary changes are allowed by the system if required before proceeding with the
payment of the course.
 The system allows three types of payment procedure, one is debit card payment, direct
account payment and master card payment.

3OBJECT MODELLING
 When there is debit card payment and master card payment, the system asks for the card
details from the user to proceed the payment method.
 The system has also the ability to store the details of the card for paying in future. For
that the student only needs to enter the one time password of the card from the registered
mobile number and complete the payment. The details of the card is not needed to enter
over and over again for paying in future. This saves a lot of time.
 The system shows the dates, the academic details of each terms, details of the library,
details of orientation week on the screen so that the registered students may get the
details from the system.
Along with the functional requirements, there are also non-functional requirements that
are enrolment system of the National University includes. Non-functional requirements includes
a feature known as FURPS+. The F in the FURPS+ feature includes the functional requirements
that is explained above. The “URPS+” stands for usability, reliability, performance and
supportability. All the features of the non-functional requirements are explained below:
Usability: Usability includes accessibility of the system, aesthetics of the system and
consistency related with the system. The enrolment information system that is included in the
system support the usability constraint of the non-functional requirement. All system that is
being proposed will have a good user interface so that students can enrol themselves easily. The
information system also has a documentation so that it becomes easier for the stakeholders to get
to known about the usability of the system that is being built for the enrolment system. All the
standards of the user interface will be satisfied using the enrolment system.
Reliability: Reliability refers to the system being secured and safe so that the users can
use it safely. Reliability occurs when the system is secured and there is no fear of data breach in

4OBJECT MODELLING
the system. The enrolment information system that is being proposed for the national university
will satisfy the reliability constraint of the non-functional requirement. The enrolment system
will be safe as well as secure so that the data of the system will be secured from the attackers and
there will be proper security measure taken to prevent the system from being attacked.
Availability of the system will also be robust to the students as well as the staffs associated with
the National University.
Performance: The performance constraint of an information system states that the
system can be used by many concurrent users at the same time. The information system that will
be designed for the National University will satisfy the performance constraint as the system and
will support many concurrent users at the same time. Many users can use the system information
system for conducting the operations of the information system. The system will be accessible
online and the response time of the system will only be some fraction of seconds for navigating
through the pages.
Supportability: The last constraint of the enrolment information system that is proposed
for the system includes other constraints such as configurability, installability, maintainability,
testability, adaptability, scalability and compatibility. The system will be designed with the help
of relational database that will include coding as well as construction of the system. The
implementation of the system requires the standards, the platform that is needed for system
implementation, and the language of implementation that is being used by the system. The
enrolment system will also support different human languages and will be available for almost
all the time. The system will also include visual basic for the implementing the presentation logic
of the information system.

5OBJECT MODELLING
2. Use Case
2.1 Use Case diagram
Figure 1: Use Case Diagram of Enrolment Information System
(Source: Created by Author)

6OBJECT MODELLING
2.2 Use case Description
Use case Use case Description
Sign up The sign up process of the information system
will include the sign up process where the
customer will sign up for completing the
registration.
Login The system will have to complete the login
process for selecting the course details and the
term details. They also have to login for
getting the other details related to the
university and the course.
Course Details The student needs to get the course details of
the university so that they can enrol
themselves for the course.
Term Details The student also get to know about the term
details of the course. The student needs to
request for getting the course details.
Term Selection The student selects the term of the session for
which they want to attend the course.
Payment making The student needs to make the payment for
the selected course in this use case.
Approval of Registration The administrator approves the registration of
the student.

7OBJECT MODELLING
Selecting course details The selecting process of the course details are
to be selected in this use case.
Selects Term Details The selecting process of the term are to be
selected by the student in this use case.
Upload Course details The course details of the academic year is to
be uploaded by the administrator in this use
case.
Upload Term details The term details of the academic year is to be
uploaded by the administrator in this use case.
Need card details For approving the course of the student, the
administrator needs to get the card details of
the student.
Other Information All the other information related to the course
details are to be uploaded in this use case so
that the student can get the information of the
course.
Reviewing Details Before the payment process, the student needs
to review their form finally to confirm all the
selected credentials.
Table 1: Use case Description
(Source: Created by Author)

8OBJECT MODELLING
2.3 Fully developed use case Description for Sign Up process
Use Case Name Sign Up
Scenario Enrolment Information System
Triggering
Event
Getting the registration letter from the CEO consisting of the CIN
number.
Decides to take admission in the university.
Checking the course details
Brief
Description
This use case includes the signing up process of the student. Before
registering themselves in the system of enrolment system. The student
needs to sign up in the process with the CIN number given from the
university with their private password. Only after the sign up process the
student can login to the system for completing their registration.
Actors Actors associated with the system are the students and the administrator
of the system.
Related Use
Case
Login, Course details, Course details, and Term Details.
Stakeholders The stakeholders associated with the system are administrative staffs,
database handling members, and students.
Pre-conditions The precondition associated with this particular case study is getting the
CIN number in the admission letter from the CEO. Without the CIN
number, the student cannot login in the system.
Post-Conditions After sign up process being complete, the student needs to select their
course details and term details for completing the registration.

9OBJECT MODELLING
Flow of
Activities
Actor System
The student needs to
know the procedure of
the registration process
before signing up in
the system.
The system lists the procedure and the
documents required for signing up for the
system of enrolment of the national University.
The student needs to
provide their personal
details such as name,
their phone number
and other credentials
for signing up the
process.
The system stores all the data in the database
given by the student for storing them in the
database securely.
Exception
Condition
The storage system of the university should have preventive measures and
security system for storing them in the database of the system.
Table 2: Fully Developed Use case Diagram
(Source: Created by Author)

10OBJECT MODELLING
3. UML Class Diagram
Figure 1: Class Diagram of Enrolment Information System
(Source: Created by Author)

11OBJECT MODELLING
4. Event Partitioning Diagram of Sign Up process
Figure 3: Event Partitioning Diagram for the Sign Up Use case
(Source: Created by Author)

12OBJECT MODELLING
Bibliography
Alur, R., Henzinger, T. A., & Vardi, M. Y. (2015). Theory in practice for system design and
verification. ACM Siglog News, 2(1), 46-51.
Beimel, D., & Kedmi-Shahar, E. (2018). Improving the identification of functional system
requirements when novice analysts create use case diagrams: the benefits of applying
conceptual mental models. Requirements Engineering, 1-20.
Chapman, W. (2018). Engineering modeling and design. Routledge.
Dennis, A., & Wixom, B. H. (2018). Systems analysis and design. Wiley.
Dick, J., Hull, E., & Jackson, K. (2017). Requirements engineering. Springer.
Ericson, C. A. (2015). Hazard analysis techniques for system safety. John Wiley & Sons.
Laplante, P. A. (2017). Requirements engineering for software and systems. Auerbach
Publications.
Linares-Flores, J., García-Rodríguez, C., Sira-Ramírez, H., & Ramírez-Cárdenas, O. D. (2015).
Robust backstepping tracking controller for low-speed PMSM positioning system:
design, analysis, and implementation. IEEE Transactions on industrial
informatics, 11(5), 1130-1141.
Montgomery, D. C. (2017). Design and analysis of experiments. John wiley & sons.
Mutambara, A. G. (2017). Design and analysis of control systems. CRC press.

13OBJECT MODELLING
Oinas-Kukkonen, H., & Harjumaa, M. (2018). Persuasive systems design: key issues, process
model and system features. In Routledge Handbook of Policy Design (pp. 105-123).
Routledge.
Pedrycz, W. (2016). Granular computing: analysis and design of intelligent systems. CRC press.
Rahman, N. A., & Zin, N. A. M. (2018). Visualizing Requirements using Use Case Diagram and
Diagram 0 for Compound Information System. Journal of Mathematics & Computing
Science, 1(1), 34-34.
Vachharajani, V., Vasant, S., & Pareek, J. (2016). Feasibility Study of Proposed Architecture for
Automatic Assessment of Use-Case Diagram. In Proceedings of International
Conference on ICT for Sustainable Development (pp. 97-104). Springer, Singapore.