Project: System Analysis and Design for Online Enrolment System

This project analyzes the online student enrolment system for ABC University, focusing on stakeholders, actors, functional and non-functional requirements, and use case diagrams. The analysis includes identifying key stakeholders like developers, testers, students, managers, and employees, as well as actors such as students, enrolment officers, administrators, and managers. It details functional requirements such as student registration, login, tuition fee submission, registration forms, confirmation, audit tracking, user accounts, system security, and database integration. Non-functional requirements, including usability, reliability, availability, and security, are also discussed and justified. The project culminates in the design and documentation of use cases for student registration, login for tuition fee submission, class schedule management, and course selection. This comprehensive approach aims to provide a robust and efficient online enrolment system, replacing the current manual process. The use case diagrams help to illustrate the interaction among elements in the online enrolment system.

System Analysis and Design
1

Contents
INTRODUCTION...........................................................................................................................3
Question-1........................................................................................................................................3
Question-2........................................................................................................................................4
Question-3........................................................................................................................................5
Question-4........................................................................................................................................5
CONCLUSION..............................................................................................................................10
REFERENCES..............................................................................................................................11
2

INTRODUCTION
System analysis and design can be defined as a process for identifying solution through an
effective plan. It helps for maintain overall functionality of system effectively and efficiently. IN
this report, it is based on the online enrolment system where how they will perform different
operation and function. It will identify the stakeholder and actors within system which mainly
perform significant task, afterwards it will determine the non-functional and functional
requirement of system.
Question-1
Determine the stakeholders in the project and at least 4 stakeholders
As per given case study, the online enrolment system can be handled by multiple
stakeholder whereas they can perform different activities through system. The number of
stakeholders will be identified in the project.
 Developer
 Tester
 Student
 Manager
 Employee
Identify the actors in the system and at least four actors.
According to online enrolment system, there are multiple actors participate in system to
perform functions. Sometimes, it can easily store and collect information of actor such as
student. It can be identified the different actors within system (Kharmoum, Retal and Omary,
2019).
 Student
 Student enrolment officer
 Administrator
 Employee
 Manager
3

Question-2
Identify the major functional requirements for system.
Functional requirement is defined as function within system and its components where it
will be identifying the specific behaviour between input and output. In student enrolment system,
Student have registered in system for selecting particular course (Bowers and et.al., 2020).
Therefore, it easily identifies the different records about the student where how they can fulfil
their requirements.
 Student registration: It is important step that performed by student where they can edit,
modify, update information through administrator. After registration, each student detail
must be recorded within system. in future, student can easily access data.
 Login account: student need to login the account into system so that they can easily check
details of course. The enrolment system provides facilities for submit fees through online
medium. Student has been successfully login that will search the updated information
such as course name, student number, class time, date.
 Tuition fees submission form: Student need to login their account for choosing
appropriate option for purpose tuition fees submission.
 Registration form: it should be collecting the information about available courses that
provided by university. Student use form to enter their personal information or data.
Afterwards, they also identifying the information from centralised database system.
 Confirmation: it is last process where enrolment system established the communication
through alert message. In this way, it can perform the different functionality for
completing the action within system.
 Audit tracking: Enrolment officer can use online system to track details of each student
on regular basis. It is the best way to keep record large number of data or information of
student in proper manner.
 User accounts: Admin will provide the username and password to protect their personal
information within system. it should keep reset or handled by system.
 System Security: authorised user can access the data through system. student can edit
their profit while protecting through password.
 Internal/ external Database: it has established the link between the student entity,
consideration that will be select the specific profile of student by admin.
4

 Administration panel: system provide the right for updating information of student. It will
create the new entities and approve profile of student.
Question-3
By using online student enrolment system identify the five different non-functional requirements
for system. justify each of non-functional requirement.
Non-functional requirement is defined the specific criteria that mainly used to judge the
overall operation of system rather than behaviour. Sometimes, it is contrasted with the functional
requirements that define overall functions as well as behaviour (Kopczyńska, Ochodek and
Nawrocki, 2020). Non-functional requirements are described about the behaviour constraint in
the system functionality.
 Usability: It is mainly referred that user operate student enrolment system because it is
become user-friendly for understanding overall functionality in proper manner.
 Reliability: it also identified that how entire system work in properly or not. Sometimes,
it has decreased reliability of system due to increase bugs, errors. Therefore, there are
different type of problem arise within system such as hardware failure.
 Availability: The Student enrolment system always maintains the availability of
information about courses, classes time and date. In this way, it directly impacts on the
overall maintenance schedule where team may define critical components within system.
 Security: It is the most common feature that require to implement within student
enrolment system so that they can easily protect or secure information of student.
Furthermore, it also ensured that system must be protected from unauthorised access.
It has been justified that these are considerations as important aspects for system management. It
should be handled by administrator to provide better facilities and services. By using system,
User can easily access information and also enter personal information within system. so as need
to maintain proper security aspects.
Question-4
Design and develop the use case of online student enrolment system, provide the comprehensive
description of requirements.
A use case diagram is a type of graphic depiction of interaction among elements in the
online enrolment system. It is based on the methodology that help for analysing overall system, it
may be organised, clarifying and identifying the specific requirements (Xiao, Su and Su, 2020).
5

Sometimes, it refers to something that being developed and operated such as service website.
The use car diagrams are employed in UML which are representing through standard notation for
modelling in real time objects.
By using use case diagram, system objectives can be including planning overall
requirements, validating hardware design, testing and debugging the software product under
development (Kelechi and et.al., 2020). sometimes, it is also creating the online help for
performing customer service-oriented task. A use case is a list of actions, events that are typical
defining interaction between role of action and system to achieve specific goals.
Use case of student registration
Figure: 1
Use case of student login for tuition fees submission
Figure 2
Use case of classes schedule
6

Figure 3
Use case of selecting the particular courses
Figure 4
7

Question-5
Develop and document that elaborated with use cases.
Use case description of maintain classes schedule
Use case Use case of Use case of Maintain Classes
Schedule
ID 2
Description The use case is mainly including different
information about the classes, location and
subject. Student login through system while
searching details about classes.
Actor  Admin
 Student enrolment officer
 Student
Flow of action  The student enrolment officer login the
maintain information of student.
 Admin give approval from request to
the student.
 Student choose classes for particular
subject.
 Admin is sending alert message to
student and successfully schedule time,
date for classes.
Trigger  Student enrolment officer has started to
login and also perform different
operation such as modify and update, of
classes.
Precondition  The course information that are
subjected registered in the system.
Post conditions  Student also registered in the particular
course.
Normal Course  Login Student officer
8

 It provides an approval through admin.
Alternative courses  Sometimes, it has generated the
message of incomplete process and
afterwards, it automatically rejected at
the time of processes.
Exception It has increased the issues when officer may
forget information of login whereas student
cannot easily receive the message from
confirmation of classes schedule
Table:1
9

Use case of selecting particular course
Use case Use case of selecting particular course
ID 3
Description The use case is mainly including different
information about the course whereas Student
login through system while searching details
about course and identifying availability.
Actor  Admin
 Student enrolment officer
 Student
Flow of action  The login the system through username
and password. Afterward, it will check
the course details.
 Admin edit, update and modify details
on the system.
Trigger  Student enrolment officer has started to
login and also perform different
operation such as modify and update, of
classes.
Precondition  The course information that are
subjected registered in the system.
Post conditions  Student also registered in the particular
course.
Normal Course  Login Student officer
 Admin give approval for student.
Alternative courses  Sometimes, it has generated the
incomplete process where admin is not
properly maintaining update course
information. In this way, it will show
the rejection processes.
Exception It has increased the issues when student may
10

select wrong course and it is not become easier
to change data and also not receive the
message from confirmation of course.
11

CONCLUSION
From above discussion, it concluded that System analysis and design is a type of procedures
that help for identifying solution through an effective plan. It can maintain overall functionality
of system effectively and efficiently. It has summarised that online enrolment system for storing
information about student such as login, classes scheduled, fees payment. These are different
operation performed within system. Furthermore, it can be determining stakeholder and actors
within system which mainly perform significant task, it also identifies the non-functional and
functional requirement of system.
12