MIS501: UML Designing Concept Report on University Enrolment System

This report delves into the application of the Unified Modeling Language (UML) in designing a timetabling and enrolment system for Torrens University Australia. The report begins with an introduction to UML, its purpose, and its role in software system design. It then describes the project background, outlining the need for a web-enabled system accessible to students, teachers, and staff across various platforms. The objectives of the system, including clear abstraction, system context specification, and visualization of the information structure, are clearly stated. The core of the report focuses on the use-case diagram, detailing the actors involved (students, teachers, organizational staff, and the director) and their interactions within the system. Use-case descriptions, associations, generalization, dependencies (including include and extend relationships), are explained to illustrate system functionalities. The report concludes by emphasizing the significance of UML diagrams in representing complex system protocols in a clear and understandable manner, facilitating better outcomes for all stakeholders. References to relevant literature are also included.

Running head: UML designing concept
UML designing concept
Name of the Student:
Name of the University:
Author name:

1UML designing concept
Table of Contents
Introduction................................................................................................................................2
Project background description..................................................................................................2
Objectives...................................................................................................................................3
Use-Case Diagram.....................................................................................................................3
Use Case Description.............................................................................................................5
Association.............................................................................................................................6
Generalization........................................................................................................................6
Dependencies: Include...........................................................................................................6
Dependencies: Extend............................................................................................................7
Conclusion..................................................................................................................................8
References..................................................................................................................................9

2UML designing concept
Introduction
UML refers to a standard language named Unified Modeling Language, which is
typically used for specifying, visualizing, documenting and constructing the abstracts of the
software system. It also can be defined as the blueprint of the software system, which is
generally model a software system as well as non-software system. UML can be considered
as a mid-level language that is associated with the object-oriented designing and analysis to
structure code in several languages by UML diagrams (Stikkolorum & Chaudron, 2016). In
this report, we will discuss the goal, objective of this tool, the functionality of this tool and
the use of UML in the context of designing timetabling and enrolment system for Torrens
University Australia.
Project background description
The Torrens University Australia has a strong information system suite, and they
show their interest in developing a timetabling and enrolment system for their students and
organizational staffs. The interface of this system is web-enabled, and therefore the students,
teachers and others staffs in the university can easily access the system from their phones,
tablets or computers on a variety of platforms and operating system (Samuel & Shukla,
2018). Since different users access this real-time system, and the user may be a student, a
teacher, staffs, or any other people. The system model all the branches, courses, subjects,
manage the classes and schedule time for the organization associated with the system.
University enrolment system provides facilities for entering students, review their progress,
schedule their classes at several campuses such as Sydney, Brisbane, Adelaide and
Melbourne to provide the future and current students with core subject and an elective

3UML designing concept
subject. The Program Director manages all the classes and allocates each class to the
particular teaching faculties. The system also allows the timetabling manager to allocate
classes in the specific classrooms for their student. Therefore effective visualization of the
system from various perspectives is the most important part, and the UML diagram helps to
achieve this.
Objectives
 To make a clear abstraction without implementation details of the system and makes
it simple to understand by the students and organizational staffs easily.
 Specify the context of the system, validate the system architecture and capture the
requirement of the system.
 To visualize the strong information structure of the enrolment and timetabling system
 To ssimplifies the interaction between every entity, concepts and the relation among
various entities within the system using this UML modelling (Mukherjee, 2016).
 From the board director, teachers, students, staffs to common people, anybody can use
this tool to understand the use of the system.
Use-Case Diagram
Use case modelling scheme is used to analyse and design the system, to classify,
organize and clarify the requirements of the student enrolment system. It can be defined as
the combination of all possible sequences and the interaction between the users and system
within a particular environment to achieve their objective (Solomencevs & Osis, 2015). An
ellipse represents the possible sequences, and an actor can be any external entity which is
used to model the system.

4UML designing concept
Figure: 1. Use Case Diagram for University Enrolment System
(Image Source: Created by author)
The actors involved in the university enrolment system are Student, Teacher, Director or any
other Organizational staffs. The uses cases represent the activities that performed by various
actors are described below:

5UML designing concept
Use Case Description
Actors/Users Use cases User goal
Student:  System Registration
 Login to the system
 Browse campuses
 Select courses to
enrolment
 Select core and
elective subjects
 Generate feedback
a. Student register into the system from the Student
Enrolment Process.
b. Student can browse the system to see the campuses
in the Torrens University.
c. Student can select courses in which they want to
enrol their name.
d. Select core subject and elective subject.
e. Student can share their feedback if any changes
required.
Teacher:  Login to the system
 Browse campuses
 Maintain class
record
a. The teacher can directly login to the system and
browse the system.
b. They can browse the campuses to check the class
allocations.
c. Check status updated by the program director of the
university.
d. Also, check for the allocated time and classes for
them.
Organizationa
l Staff:
 Login to the system a. Organizational staffs can directly login to the

6UML designing concept
 Browse campuses
 Maintain class
record
system and browse the system.
b. They can browse the campuses to check all the
courses.
c. Check status updated by the program director if
any.
d. Also, check for the allocated time or classes for
them.
Director:  Schedule time
 Schedule classes
 Allocate room
 Allocate teacher for
classes
a. Director can directly login to the system and
browse the system.
b. Allocate classroom and time for the classes for the
student to enrol into the system.
c. Allocate classes to all teaching staffs.
 Association
An association relation between actors and use cases indicates that the actors interacts
with the university enrolment system for a specified use-cases. The relationship is
represented by a solid line (Manzini, 2017). In the above diagram the Student (an actor) is in
association with multiple use cases.

7UML designing concept
 Generalization
The generalized relationship in use case is that, an actor can replace by another actor.
In the above diagram, an Organizational staff can be replaced by a Teacher. This implies that
there exists actions that an Organizational Staff can perform but a teacher canno & et al.,
2016t (Decker).
 Dependencies: Include
Use cases depends on each other to achieve the goal. An include dependency invoked
while one use case uses the functionality of another one. This relationship allows to include
the steps between more than one Use Cases in the University enrolment system. For example,
a use case ‘browse campuses’ will first run the use case ‘signin to the system’ to check the
access permission of the user to run the process. Suppose we want to capture the Student
enrolment details which include the elective and core subjects details of the individual
students, the include relationship occurs in this situation as a recognizable sequence in a
different context (Salehi & et al., 2016). Another example, we may require to capture them as
the new student or recall them as the existing student. The direction of flow goes from
primary use-case to included use-case.
 Dependencies: Extend
A use-case can call other use cases under certain circumstances for example as
alternatives. In the above diagram, the dependency must read use the ‘use case maintain class
record for courses extend the use case schedule classes and schedule time’. This relationship
modify the behaviour of the extended Use Cases. There are many functionalities used to open

8UML designing concept
up the whole possibilities and dangers in the sub-flows in the system (Nassif, Capretz & Ho,
2016). The extend relationship is used to pull all the sub-flows, and the alternative flows
related to new use cases. This relationship helps to execute the base use-cases when we want
to get a specific point within the flow when the right conditions met.

9UML designing concept
Conclusion
From the above discussion, it can be concluded that UML diagrams are one of the
most standard used modelling language to represent the strong information program protocol
of the TUA organization in a simple and better way. Even though all the diagrams help to
represent the different perspectives of the enrolment system since there are differences while
designing, collaborating, processing, and implanting the complex structure of any system. It
will help to make a clear vision of both the software and non-software system. Moreover, it
will also help the program director, teaching faculties, students, and other organizational
staffs to understand the purpose of every module of the system to produce a better outcome.

10UML designing concept
References
Decker, M. J., Swartz, K., Collard, M. L., & Maletic, J. I. (2016, October). A tool for
efficiently reverse engineering accurate UML class diagrams. In 2016 IEEE
International Conference on Software Maintenance and Evolution (ICSME) (pp. 607-
609). IEEE.
Manzini, C. V. E. (2017). Design for sustainable consumption and production systems.
System Innovation for Sustainability 1: Perspectives on Radical Changes to
Sustainable Consumption and Production, 138.
Mukherjee, M. (2016). Object-Oriented Analysis and Design. International Journal of
Advanced Engineering and Management, 1(1), 1-11.
Nassif, A.B., Capretz, L.F. & Ho, D., 2016. Enhancing use case points estimation method
using soft computing techniques. arXiv preprint arXiv:1612.01078.
Salehi, P., Hamou-Lhadj, A., Toeroe, M., & Khendek, F. (2016). A UML-based domain
specific modeling language for service availability management: Design and
experience. Computer Standards & Interfaces, 44, 63-83.
Samuel, K. M., & Shukla, R. S. (2018). CHALLENGES TO DESIGN A DISTRIBUTED
DATABASE USING UML AND MERISE. International Journal of Advanced
Computer Technology, 7(6), 01-14.

11UML designing concept
Solomencevs, A., & Osis, J. (2015, April). The algorithm for getting a uml class diagram
from topological functioning model. In 2015 International Conference on Evaluation
of Novel Approaches to Software Engineering (ENASE) (pp. 341-351). IEEE.
Stikkolorum, D. R., & Chaudron, M. R. (2016, July). A Workshop for Integrating UML
Modelling and Agile Development in the Classroom. In Proceedings of the Computer
Science Education Research Conference 2016 (pp. 4-11). ACM.