Object Modelling

This document discusses object modelling, including functional and non-functional requirements, use case, UML class diagram, and event partitioning diagram. It provides an in-depth analysis of the enrolment information system of a national university. The document also includes a bibliography for further reference.

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......................................................................................................................................6
2.1 Use Case diagram..................................................................................................................6
2.2 Use case Description..............................................................................................................7
2.3 Fully developed use case Description for Sign Up process.................................................10
3. UML Class Diagram..................................................................................................................12
4. Event Partitioning Diagram of Payment Process.......................................................................13
Bibliography..................................................................................................................................14

2OBJECT MODELLING
1. Functional and Non-functional Requirements
The information system of the National University includes many functional as well as
non-functional requirements that are needed for implementing the system.
The functional requirements that are included with the information system of the National
University are stated below.
 The information system of the national University enrolment process will take the name
of the students as an input in the system (Linares-Flores et al., 2015).
 The interface will be user friendly and the students will be able to navigate through the
system website easily.
 The data related to the course and the data related to the terms related to the course are
stored in the information system.
 The system also counts the number of student in each class and if the number exceeds 40,
the system stops taking admission for that class (Beimel & Kedmi-Shahar 2018).
 The system shows the final details of the options selected by the students before making
the final payment (Chapman, 2018).
 The system asks for student id that was mentioned on their COE letter. The system
should store all details of the COE letters so that they can match the credentials at the
time of login.
 The list of courses that are available for the particular term is displayed by the system.
 The student are allowed to select 3 or 4 courses in a particular term and select their class
times available accordingly (Rahman & Zin, 2018).

3OBJECT MODELLING
 The system also verifies if the student has made correct selections from the list of
available courses and has not made arbitrary selection.
 The system allows the student to make correction if there is any mistake in course and
term selection by the student.
 The system allows payment procedure in three different process in the system; master
card, debit card, or to some designated account number.
 The paying through credit card and debit card, the system asks for the card details from
the student to proceed the payment (Laplante, 2017).
 The system stores the details of the account when the option for designated account
number is selected by the student.
 The system also stores the detailed information on the commencement dates of all the
academic terms in the organization.
 The system also stores the details of the orientation week in the database of the system so
that the student get to know the details of the orientation week.
 The library details and the details of the department is also shown in the system based on
the particular enrolment is shown by the system.
There are functional as well as non-functional requirements for a system that is too be
built for the National University. Some of the requirements might be technology independent and
other requirements might be technology specific in the information system that is to be
developed and designed (Pedrycz, 2016). The technique to validate the requirements of the
information system after meeting the client’s needs as well as necessities is using the FURPS+
technique. This particular technique helps to classify the requirements and helps to identify
different non-functional requirements that are included in the system. The acronym that stands

4OBJECT MODELLING
for the FURPS+ is functionality, usability, reliability, performance, and supportability. All the
points are explained below:
Functionality: The functionality of the information system mainly represents the
technical features that are associated with the information system (Ericson, 2015). The
functionality of the system are explained in the functionality of the information system. The
functional requirements are the architecturally functional requirement of the information system
that is being built for the National University.
Usability: The usability in the FURPS+ feature mainly includes to look at the
requirements, capturing of the requirements and the stating of the requirements that are
dependent on the issues of user interface (Vachharajani, Vasant & Pareek, 2016). The human
factors that are includes in the system are included in the usability of non-requirement functional
requirements of the system. The aesthetics as well as the consistency of the system are also
satisfied with the requirement of the system.
Reliability: Reliability in the non-functional requirements includes the availability of the
system, the accuracy of the system and the recoverability of the system (Alur, Henzinger &
Vardi, 2015). The national University enrolment system that is being proposed in this report will
be available for all 24x7 days and the system that is being built is very much accurate for
satisfying the user requirement in the system. The reliability of a system includes the system to
be secured and there system should not be prone to data breach. There are variety and wide range
of data related to the students and the university in the information system and thus the security
of the system is an important part of the National University enrolment system.

5OBJECT MODELLING
Performance: The performance related with the non-functional requirement includes the
throughput, the response time of the system, the recovery time of the system and the start-up
time for the information system (Montgomery, 2017). The throughput time indicates the time
that system responds to the user for completing a particular work. The performance also
indicates the total number of concurrent users that the system can support while carrying out
activities in the system. The university has many student logging the system at the time and the
system needs to support all the users at the same time. The information system includes the start-
up time and the recovery time of the application.
Supportability: The supportability includes the adaptability, internationalization,
maintainability, and the configurability (Dick, Hull & Jackson, 2017). The system should have
adaptability to work at all the time and the system should be maintained and should be kept
updated in the system. There should be relational database that are included in the system that
helps to design the coding and the system construction. There are many standards for developing
the information system of the National University and the system will be designed with visual
basic implementation.
The “+” sign in the FURPS+ states implementation, interface, operations, packaging, as
well as legal constraints that are to be carried for developing the system of National University of
enrolment system.

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

7OBJECT MODELLING
2.2 Use case Description
Use case Use case Description
Sign up The student needs to sign up with the student
ID given to the students in the COE letter.
Without the student id, the student will not be
able to sign up.
Login With the student id and the password, the
student needs to login in the system for
enrolling themselves in the information
system of the National University.
Course Details The details of the course is needed by the
student so that they can enrol themselves in
the system of National University.
Term Details The term details consists of all the terms that
are associated with each course. The system
explains all the details of the system.
Term Selection Term selection refers to the term that is being
selected by the student on behalf of their
requirement. The students select the term only
if all the constraints are satisfied in the
company.
Payment making For proceeding with the payment, the
students’ needs to select a particular payment

8OBJECT MODELLING
method for completing the payment process.
There are three types of payment methods that
are to be included in the system and one
option is to be selected by the student.
Approval of Registration The administrative staffs approves the
registration of the student and the enrolment
of the student in the system of National
University. The student needs to register
themselves to complete the approval.
Upload Course details The details of the course are uploaded by the
administrative staff associated with the
system. They have the access to add, delete or
modify the courses accordingly.
Upload Term details The details of the terms are uploaded by the
administrative staff associated with the
system. They have the access to add, delete or
modify the courses accordingly.
Need card details The staffs needs the details of the card for
processing the payment of the system. The
system also needs to store the details of the
card for future use.
Master Card The master card use case is selected when the
student selects the credit card option for

9OBJECT MODELLING
proceeding with the payment system.
Debit Card The debit card use case is selected when the
student selects the debit card option for
proceeding with the payment system.
Library Information All the information related with library is to
be uploaded by the administrator and the
student reads the details of the library from
this particular use case.
Reviewing Details Before the payment method, the student needs
to review the details of the selected options
that were selected by the student to enrol
themselves in the system.
Table 1: Use case Description
(Source: Created by Author)

10OBJECT MODELLING
2.3 Fully developed use case Description for Sign Up process
Use Case Name Payment Making
Scenario Enrolment Information System of National University
Triggering
Event
The students need to select all the courses that they want to include in
their academic year.
The student also need to select the term and the course time details in the
system.
Before going to payment, the student will have to review the options
selected by them.
Brief
Description
This use case includes the payment process of the system. The payment
process includes three types of payment that is supported by the system.
This particular use case will carry out the payment processes that includes
the card payment or the account payment. The student have to enter the
card details for paying for the course via debit card or credit card.
Actors The actors in this system are the student, the administrative staff and the
database administrator.
Related Use
Case
Term Details, Team Selection, Reviewing Details.
Stakeholders The stakeholders associated with this use case are the students, the trainer,
the administrative staffs and the owner of the National University.
Pre-conditions Precondition associated with the payment case study includes selecting
the courses, selecting the course details, selecting the term details and
reviewing the final details of the selection before proceeding with the

11OBJECT MODELLING
payment activity.
Post-Conditions After the payment activity is completed, the student will be able to see the
library details, the orientation details of the course and the location of the
department in the system.
Flow of
Activities
Actor System
The student as an actor needs to
know about the payment
procedure of the system.
The system should alert the user
about the payment procedure before
proceeding with the payment, this is
because once after proceeding with
the payment procedure, the user
cannot return back the page.
The student needs to know the
details of the card and know
details of all three payment
options that the information
system provides.
The system needs to provide a good
interface for the student at the time
of entering the card details in the
system.
Exception
Condition
There should be proper storage and proper security of the system so that
the students feel safe to proceed the payment process in the system.
Table 2: Fully Developed Use case Diagram for Payment Making
(Source: Created by Author)

12OBJECT MODELLING
3. UML Class Diagram
Figure 1: Class Diagram of Enrolment System of National University
(Source: Created by Author)

13OBJECT MODELLING
4. Event Partitioning Diagram of Payment Process
Figure 3: Event Partitioning Diagram for Payment Making Use case
(Source: Created by Author)

14OBJECT 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.

15OBJECT 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.