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

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

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