Object Modelling

This document provides an overview of object modelling and its functional and non-functional requirements. It includes use case diagrams, UML class diagrams, and event partitioning diagrams. The document focuses on the National University information system.

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.

4OBJECT MODELLING
Implementation requires standards, implementation language and platform for
implementing. The application will support two to three human languages and the system
will be available all 7 x 24 days. All the presentation logic will be designed using visual
basic.

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

6OBJECT MODELLING
2.2 Use case Description
Use case Use case Description
Sign up for the system The student needs to sign up for the process
of National University information system.
Login the system For accessing the course details the student
needs to login in the system.
Request Course Details After the login process, the student needs to
request for the details of the course from the
system.
Request Term Details After getting the course details, the student
needs to request for the details of the term for
a particular course.
Selects Term After getting the course details and term
details the student selects their preferred
course and term and they can select up to 3 to
4 courses per year.
Makes Payment After selecting, the student makes the
payment.
Approves Registration The database system checks the credential of
the student and approves the registration
process.
Provide course details When the student request for course details,
the system provides them with the details of

7OBJECT MODELLING
course. If there are 40 student already
registered for a particular course, system does
not give the details of those courses
Provide Term Details When the student request for term details, the
system provides them with the details of
terms available.
Asks Card Details For the payment option, the system asks the
user to provide the card details foe processing
the payment successfully.
Display Necessary Details of Course After all the processes completion, the system
reviews the selected option to the students in
case of any change before the payment
process.
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 Process
Scenario National University Information system
Triggering
Event
Got CEO letter
Decided to take admission in National University
Checked the course details
Brief
Description
If the students want to take admission in the university, they have to
register themselves in the information system of National University. For
registering themselves, they needs to provide their personal details to get
the student ID and the username and password with which they can login
the system for future follow up.
Actors The actors involved are students and the staffs handling the information
system database.
Related Use
Case
Login the system, View course details, and selects course details.
Stakeholders The stakeholders involved are students, administrative staffs, and the
database handling members.
Pre-conditions The student needs to get the CEO letter and then only they can register
themselves in the information system of the National University.
Post-Conditions After the sign up process is completed, the student needs to login to
continue to complete the admission process.
Flow of
Activities
Actor System
Reads the sign up Before sign up, the system instructs the user

9OBJECT MODELLING
process about how to go through the registration
process.
Enter the personal
details
The system asks for the personal details of the
student to store them in database when
registration is complete
Exception
Condition
The database admin should have a proper storage system to store the data
provided by the student in the database.
Table 2: Fully Developed Use case Diagram
(Source: Created by Author)

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

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

12OBJECT MODELLING
Bibliography
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.
de Sousa, T. C., Kelvin, L., Neto, C. D., & de Carvalho, C. G. N. (2017). A Formal Semantics
for Use Case Diagram Via Event-B. JSW, 12(3), 189-200.
Khan, F., Jan, S. R., Tahir, M., Khan, S., & Ullah, F. (2016). Survey: dealing non-functional
requirements at architecture level. VFAST Transactions on Software Engineering, 9(2), 7-
13.
Laplante, P. A. (2017). Requirements engineering for software and systems. Auerbach
Publications.
Mahmoud, A., & Williams, G. (2016). Detecting, classifying, and tracing non-functional
software requirements. Requirements Engineering, 21(3), 357-381.
Nassif, A. B., Capretz, L. F., & Ho, D. (2016). Enhancing use case points estimation method
using soft computing techniques. arXiv preprint arXiv:1612.01078.
Shiue, Y. C., Lo, S. H., & Liu, K. F. (2017, July). The Research of the Seven Steps of
Normalized Object Oriented Design Class Diagram. In International Conference on
Frontier Computing (pp. 315-325). Springer, Singapore.
Wang, C., Pastore, F., Goknil, A., Briand, L., & Iqbal, Z. (2015, July). Automatic generation of
system test cases from use case specifications. In Proceedings of the 2015 International
Symposium on Software Testing and Analysis (pp. 385-396). ACM.