Object Modelling

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

OBJECT MODELLING1
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

OBJECT MODELLING2
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).

OBJECT MODELLING3
 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