Object Modelling

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 functional requirement of the National University information system that is being
proposed are listed below:
 The system gets the details of the student from the student to register them on the
database of the system.
 The system also stores all the course details that are provided by the university.
 The system stores all the terms that the university provides for the students.
 The system also count the total number of students in a lecture class. The total number of
student should not exceed 40 for a particular class.
 The new updated database system of the National University stores the course details of
the student and shows them to the student at the time of final enrolment before paying
process.
 The information system of the university allows a particular student to choose three to
four courses for a semester and their corresponding class time.
 The system also allows the student to make the necessary changes, if required before
processing with the payment system.
 There are three payment procedures that the system allows. The system allows master
card payment, debit card payment, and designated direct account payment.
 In case of master card payment and debit card payment, the system asks the student to
provide with the card details for processing the payment.
 The system also stores the card details for future payment and only with the OTP or the
four digit pin of the card, the student can make the payment. There is no need to enter the
card details over and over again.

3OBJECT MODELLING
 The system also stores the information about the dates of the academic terms for each
course and each term, the orientation week, the library available and other such details
and displays the to the student.
The non-functional requirement that are required for the national university information
system are listed below. There are many constraints that the system should satisfy. The non-
functional constraints includes FURPS feature where “F” is the function requirement and
“URPS” are the non-functional requirements. The constraints that information system should
support are discussed below.
 Usability: The information system that is being built up will be accessible, aesthetics, as
well as consistency. So the system satisfies the usability feature of the non-functional
requirements. The information system includes all the standard of user interface and
provides documentation for the information system.
 Reliability: The information system that is being proposed for the National University
should be safe in order to keep all the data secure and safe from the intruders. The system
will be available to all the students and the staffs and the system will be robust. The
system will have the ability to handle the exception in the programming and there will be
no data loss tolerance in the system.
 Performance: The system of information system will support a wide quantity of
concurrent users that is many students and staffs will be able to access the online system
at a same time and the response time of all the functions are also less in the system.
 Supportability: The information system includes supportability that includes testability,
maintainability, compatibility, adaptability, configurability, scalability, and installability.
There will be relational database in the system, along with coding and construction.