Ambo University Clearance Management System
Ambo University Clearance Management System
AMBO UNIVERSITY
INSTITUTE OF
Group 10
s/no Name Id/No
1 Shumi Tolesa BRT/0374/09
2 Siraj Teha BRT/0375/09
3 Chelkeba Negasa BRT/0288/09
4 Yohannes Kiflu BRT/0395/09
5 Gebisa Merga BRT/0313/09
6 Chaltu Gabayo BRT/0286/09
Advisor [Link] W.
Co_Advisor Mrs. Hawi M.
May 11, 2021
Ambo,Ethiopia
APPROVAL SHEET
This is to confirm that the project entitled as “Web based student’s clearance management
system for Ambo University” is a work carried out by final year students of Information
Technology Program in a group bearing the name and signature as:-
Table of Contents
1. CHAPTER ONE......................................................................................................................................1
INTRODUCTION...........................................................................................................................................1
1.1. Background about the organization.........................................................................................1
1.2. Background of Study.................................................................................................................2
1.3. Statement of the problem..........................................................................................................3
1.4. Objectives...................................................................................................................................4
1.4.1. General Objective..............................................................................................................4
1.4.2. Specific Object...................................................................................................................4
1.5. Methodology and tools...............................................................................................................5
1.5.1. Data collection techniques.................................................................................................5
1.5.2. Development tools..............................................................................................................7
1.6. Scope of the project...................................................................................................................8
1.7. Feasibility Analysis....................................................................................................................8
1.7.1. Operational Feasibility......................................................................................................8
1.7.2. Technical Feasibility..........................................................................................................9
1.7.3. Economic Feasibility..........................................................................................................9
1.8. Significance of the project.......................................................................................................10
1.9. Beneficiary of project..............................................................................................................10
1.10. Specification for hardware and software...........................................................................11
1.11. Overall cost estimation........................................................................................................12
1.12. Time scheduling of project..................................................................................................12
2. CHAPTER TWO...................................................................................................................................14
SYSTEM ANALYIS.......................................................................................................................................14
2.1. Introduction.............................................................................................................................14
2.2. Description of existing system.................................................................................................14
2.2.1. Activities performed under existing system...................................................................14
2.2.2. Problem identified with the existing system...................................................................15
2.2.3. Business rules...................................................................................................................15
2.3. Description of proposed system..............................................................................................15
2.3.1. Functional requirements of proposed system................................................................16
2.3.2. No-functional requirements............................................................................................16
2.3.3. System interfacing............................................................................................................17
List of Tables
Table 1.1. Software Development Tools...................................................................................................7
Table 1.2. Hardware Requirement Cost...................................................................................................12
Table 1.3. Software Requirement Cost....................................................................................................12
Table 1.4 Cost estimation of the project..................................................................................................13
Table 2.1. Scenarios Analysis..................................................................................................................20
Table 2.2. Use case description for Create Account................................................................................24
Table 2.3. Use case description for Login...............................................................................................25
Table 2.4. Use case description for Registration......................................................................................26
Table 2.5. Use case description for Delete..............................................................................................26
Table 2.6. Use case description for Delete...............................................................................................27
Table 2.7. Use case description for view profile.....................................................................................28
Table 2.8. Use case description for Search.............................................................................................28
Table 2.9. Use case description for Approve...........................................................................................29
Table 2.10. Use case description for Generate Report...........................................................................30
Table 2.11. Use case description for Request.........................................................................................30
Table 3.1. User interface documentation.................................................................................................56
List of figures
Figure 2.1 Essential use case diagram.....................................................................................................22
Figure 2.2 Use case diagram....................................................................................................................23
Figure 2.3 Sequence diagram for Create Account by Admin and Offices..............................................31
Figure 2.4 Sequence diagram for registration..........................................................................................32
Figure 2.5 Sequence diagram for login....................................................................................................32
Figure 2.6 Sequence diagram for Update.................................................................................................33
Figure 2.7 Sequence diagram for View...................................................................................................33
Figure 2.8 Sequence diagram for Search.................................................................................................34
Figure 2.9 Sequence diagram for Delete..................................................................................................34
Figure 2.10 Sequence diagram for Approve............................................................................................35
Figure 2.11 Sequence diagram for Generate Report................................................................................35
Figure 2.12 Sequence diagram for Request.............................................................................................36
Figure 2.13 Activity diagram for Registration.........................................................................................37
Figure 2.14 Activity diagram for Create Account....................................................................................38
Figure 2.15 Activity diagram for Login...................................................................................................39
Figure 2.16 Activity diagram for Delete..................................................................................................40
Figure 2.17 Activity diagram for Update profile.....................................................................................41
Figure 2.18 Activity diagram for View....................................................................................................42
Figure 2.19 Activity diagram for Search.................................................................................................43
Figure 2.20 Activity diagram for Approve..............................................................................................44
Figure 2.21 Activity diagram for Generate Report..................................................................................45
Figure 2.22 Activity diagram for Request................................................................................................46
Figure 3.1 Class type architecture............................................................................................................49
Figure 3.2 Class Diagram........................................................................................................................50
Figure 3.3 Component modelling diagram..............................................................................................52
Figure 3.4 Deployment modelling diagram..............................................................................................53
Figure 3.5 Relational Database modeling for the system.........................................................................54
Figure 3.6 User interface...........................................................................................................................55
Acknowledgment
First and foremost and above all our biggest thanks would be to Almighty God
because nothing could be possible without his free will and the completion of this
project is supported by him. Secondly we would like to thank our Advisor Mr.
Shumet W. who assists us in each and every aspect of our project documentation
by being beside us. Input to the quality of this document, heart full guidance,
valuable advice, and providing to execute this project and our co-Adviser Mrs.
Hawi M. For his support by giving idea for us .Finally, the last but not the least,
even if it is usual the group members would like to thank each other. The main
contributors to do this document project are teamwork, friendship and the belief
that we may achieve something we set out to do.
Abstract
Student clearance management system is a web based project work that will help
build an effective information management for university. It is aimed at developing
a computer software system that replaces the manual method of clearance during
withdrawal, summer vacation and graduating time for students. The designed
software will serve as a more reliable and effective means of undertaking students
clearance, remove all forms of time delay and stress as well as enable you to
understand the procedure involved, as well as how to do your clearance online.
This project work makes use of data collection from the university, materials and
journals from various authors and the software was developed to effectively
achieve the aim of the project. In this project the implementation is carried out with
PHP, MYSQL as the database. In conclusion it will meet all the objectives and it
will be recommended for all the departments in Ambo University and other tertiary
institution.
List of Abbreviations
AU………………………………..Ambo university
JS…………………………………...Java Script
UI…………………………………..User Interface
Presently the University runs nine graduate and twenty-eight undergraduate programs which are
divided into eight colleges/institutes and thirty academic departments. Besides its main campus
at Ambo, the University also has one faculty-Faculty of Business and Economics at Woliso.
In the years to come, the university has the vision of becoming one of the most prestigious
universities in the country excelling in academics, research and community service giving its at
most attention to quality education. Offering relevant, quality education and training, conducting
demand driven research and rendering accessible community services.
Ambo University Awaro Campus also a branch beside a main campus. The campus
begins in 2005 E.C, by Institute of Technology. The University show a great change in seven
years and the student numbers is increased.
Ambo University is dedicated to serve the Ethiopian society and the world in discovery,
development and application of knowledge in wide range of disciplines. The university is
committed to maintain and ensure the provision of quality, cost effective, timely and need- based
education at undergraduate and graduate levels; engage in research and knowledge transfer;
conduct short term trainings and consultancy; and offer community services in a professional and
innovative manner so as to address the need of stakeholders[ CITATION Amb18 \l 2057 ].
─ Excellence
─ Gender equity
─ Team spirit
The system gives its function to many user of the University. The numbers of students grow
from year to year in many numbers. Now a day, there are many users of the clearance processing
system. But the project gives a service only the students. The students get one copies of
clearance sheet from department and get signature and stamp from around eight offices. These
are: -
─ Advisor
─ Bookstore
─ Library
─ Accounting office
─ Student’s Proctor
─ College/Institute Registrar
After they finished all necessary requirements, finally the students take copies of sheet that has
all signature and stamp from all offices. This processing makes the students bulky because they
go to about eight offices.
─ Data recording system is not centralized or not in the modern system which is
difficult to search.
─ It creates wastages of material & time.
─ Data redundancy &loss of data.
─ Consumes more resources to complete the process which is of high cost such as:-
Stationary material.
Printers and computers etc.
─ Need more manpower to process the clearance in the respective offices.
─ Error is happened during process the clearance System.
─ The process is very offensive for students when there is a harsh atmosphere like
rain.
Hence, it became imperative for computer software based online clearance system to eliminate
the shortcoming of the manual system in place as above listed problem.
1.4. Objectives
1.4.1. General Objective
The main objective of this project is to change the manual clearance processing system to web
based system and solve the above stated problems.
return the materials then if he return the material we sign in to the clearance form otherwise until
he/she return the material or he pay the fee for that material we did not sign in to the clearance
form.
Question 2: - How do you handle student information during borrowing materials from this
office?
Answer:-in order to control our resource which lends to the student we use a form which used to
record student information that borrow property from the office and borrowed property
information.
Question 3:-Is there any problem during this clearance process?
Answer:
1. In the earlier time we put only the signature and name of sport Offices so that some students
was put its own sign in to the clearance. But at this time we uses titter.
2. It is difficult to handle students and borrowed material’s information.
Question 4: In which ways you like to be the system?
Answer: We would like if it is networked computerized system because it enable us to
communicate with related office without the student coming to our office and to easily manage
each resource.
Interviewer Students
Question1: What difficulties you faced during the clearance process?
Answer:
─ Absence of some staff officers who sign Clearance form that leads us to repeatedly visiting
particular offices.
─ To sign a clearance form we goes around various office of the university like:-
─ Chief of library circulation,
─ University book store keeper,
─ sport Offices,
─ student service
─ School head etc.
Because of these the clearance process is time consuming and stressful.
Question2: In which ways you like to be the clearance process?
Answer: It is better for us to get only from one office or using online.
Document analysis: we have used document analysis data gathering method to collect the
documented information.
Observation: we observe the process that going on when we make clearance within manual
system.
Questionnaires: those types of data’s are also collected by distributing question and answering
method by having the fall and success to the students.
4. Pen: - used to writing different information that we get from persons and different
websites.
5. White paper: - used to writing on and take data or notes on it.
─ The System contains all the recorded information that can be handled by the registrar
and other offices.
1. Students: - by providing fast access to the clearance system by reducing time like waiting
in the queue and going to different offices. The students access the system anywhere and
anytime when they need the clearance. It improves the tiredness of student by avoiding to
going to different offices to get the clearance system.
2. University: - in manual system there is loss of materials like time, paper, pen which is
cost and more manpower, the system reduces loss of costly materials and manpower.
3. Developers of the project: - it increase our knowledge and we get moral satisfaction from
the project we developed.
─ Notepad++
─ Opera browser, Baidu browser , Google Chrome browser
─ Diagram Designer
─ Microsoft office 2007
─ MYSQL
─ Adobe Photo Shop CS3
The minimum hardware requirement specifications for developing this project are as follows:
─ Hard Disk
─ CD-ROM 700MB
─ Flash Disk 8GB
─ Printer
─ Computer
─ Network Adapter
Jan
Feb
Mar
May
2020
Oct
Nov
Apr
S/ Project phase
Jun
no
2020
2019
2020
2020
2019
2020
2019
2020
1 Proposal
2 Requirement
gathering and
analysis
3 Designing the
system
4 Implementation
5 Testing
2. CHAPTER TWO
SYSTEM ANALYIS
2.1. Introduction
This chapter deals with analyzing the proposed system by using different UML analysis
modelling techniques such as use case diagrams, the use case descriptions (scenarios), sequence
diagrams, activity diagrams and analysis class diagram.
After identifying the actors and use cases, the use cases are developed and textual descriptions
(scenarios) are stated. The Sequence diagram is depicted based on the use cases which are
developed for the proposed system [4]. Activities will be represented by the activity diagrams
Input to the system is the form which is fulfilled by the proper users. These forms are filled by
student and submitted to the various offices for issuing of receipts.
Process Analysis
The form is filling by the students then collected and signed by the respected offices to certify
that the student has completed all the necessary things. Hence a certificate issued to show that
the student have completed all the clearance processing.
Output Analysis
The output from the system is the certificate or one form of clearance issued to the student
stating that the student fulfilled all university obligations and is now free to pass out from the
university.
This system will do the analyzing and storing of information either automatically or
interactively. It will make use of online access to Internet. The proposed system will also have
some other features like:-
─ Login system must be present and secured by password and logout after cover.
─ Accuracy in the handling of data.
─ Fast rate of operation and excellent response time.
─ The system is flexible i.e. it can be accessed at any time.
─ Easy way of back up or duplicating data in diskettes in case of data loss.
─ Better storage and faster retrieval system.
─ Accessibility from anywhere.
─ Unauthorized user cannot access the system for the reason of system security.
─ Users must be registered to access the system to be authorized user by filling the necessary
information in the registration form.
Process requirements: - The system performs the services for all inputs by functional
components of the system based on the given inputs.
Input related requirements: - After the system is implemented, to perform a process it needs
inputs like student username, student ID No and other information which are necessary to in
processing clearance are entered in clearing process.
Output related requirements: - The system takes in an input to perform or to process some
function in order to produce an output based on the given input.
Storage related requirements: - The system developed by using MySQL database server which
used to store all the students information like cleared students and the current available students
information to be cleared.
User Interface: - The developed system provides web application user interfaces that are
compatible browsers like Internet Explorer, Mozilla Firefox, Google chrome, etc.
Security and Access Permissions: - The system provides or contains user name and password for
each users based on their privilege. This performs the following activity: -
─ Authenticated user with predefined access right will only enter to the information
related to database.
─ Every users should use strong passwords especially admin.
─ User must enter valid user name and password to login to system. Without this, access
to the system is denied.
─ Data is encrypted for security.
─ System allows only registered users to access clearance system and also allows the
users’ to view their own profile not the other users’ profile.
Backup and Recovery: - When team member standard to develop a system they must have to put
use a backup mechanism by using removable flash disks, or CDs.
Usability:-The system shall be very easy to learn, needs basic computer knowledge to use and
have a help menu to guide the user.
Availability: - There is no delay in the availability of any information, whatever needed, can be
captured very quickly and easily. The server should be always on to be available.
User Interface
Application will be accessed through a Browser Interface. The interface would be viewed best
using 1024 x 768 and 800 x 600 pixels resolution setting. The software would be fully
compatible with Microsoft Internet Explorer for version 6 and above. No user would be able to
access any part of the application without logging on to the system.
Hardware Interface
Server Side:
Communication Interface
─ Broadband Internet
Actor name
System Represents boundary between physical system and
boundary the actor who interact with the physical system
The actors that interact with the system are the Proctors; Registrar, student service, sport science,
bookstore, library, and students are users of the system. They are described here in brief:-
Name: Proctor
Description: A Proctor is a person who is responsible for Approve, update, Generate Report and
search the student’s information.
Name: Bookstore
Description: A Bookstore is a person who is responsible for Approve, Update, Generate Report
and search the student’s information.
Description: A Sport science is a person who is responsible for Approve, Update, Generate
Report and search the student’s information.
Name: Library
Description: A Library is a person who is responsible for Approve, Update, generate report and
search the student’s information.
Description: A Student service is a person who is responsible for Approve, Update, generate
Report and search the student’s information.
Description: Registrar Admin is a person who is responsible for Approve, create account ,delete
record and Generate Report.
Name: Student
Description: Student is a person who is responsible for Update profile, Request, and views their
own information.
─ Proctor
─ Student service
─ Bookstore
─ Library
─ Sport science
─ Department
Create account
Report
Search
Offices
Registrar Delete
Approve Proctor
Sport Science
Student service
Library
Book Store
Department
Update
Student
View
Request
<<include>>
<<include>>
Update Profile
Registrar
<<include>>
<<include>>
CreateAccount Login Student
<<include>>
<<include>>
<<include>>
Approve
<<include>>
Office <<include>>
Search
Request
Sport Science
Student service ReporteGenerate
Library
Book Store View Profile
Department
wants to createaccount
<<Create>>
valid()
invalid()
re enter correct info verify()
Figure 2.3 Sequence diagram for Create Account by Admin and Offices
Wants to Register
invalid()
enter correct info verify()
want to login
invalid() verify()
Offices :home Page :Login Form :Update Page :Update Form :DB
wants to update
invalid verify()
Select Update()
enter update info
Actor1
invalid() verify()
re-enter us ername & pass
select view()
enter id
Offices :Home Page :Login Form :Search Page :Search Form :DB
Wants to Search
invalid()
verify()
re-enter usern & pass
enter id
searc h info
display info
wants to delete
invalid() verify()
re-enter usern & pass
select del()
enter id
display confirmation
Of fices :Home Page :Login Form :Approve Page :Approve Form :DB
wants to s ubmit
invalid()
re-enter us ern & pass verify()
select approve()
Admin :Home Page :Login Form :Ge nerate Page :Ge nerate Form :DB
wants to generate
invalid()
re-enter usern & pass
enter information
display confirmation
Student :Home Page :Login Form :Reque st Page :Request Form :DB
Wants to Request
Invalid()
re-enter un & pw verify()
Select request
Enter request info
Students
Registration Form
correct
Admin
CreateAccount Form
Incorrect
Is the info
System indicate wrong information
Correct?
correct
Actors
Login Form
re-enter correct
Fill username & password Username & pass
correct
display information
Admin
Delete Form
correct
Admin
correct
Student
View Form
correct
Admin, Offices
Search Form
correct
Admin, Offices
Approve Form
correct
Admin
Student
Request Form
correct
3. CHAPTER THREE
SYSTEM AND OBJECT DESIGN
3.1. Introduction
System design is the process and focuses on decomposing the system into manageable parts.
During requirements analysis, we concentrated on the purpose and the functionality of the
system [5]. During system design, we focus on the processes, data structures, and software and
hardware components necessary to implement it.
3.1.1. Purpose of the system and object design
The purpose of the Ambo University Student clearance system is as the following:
Define what methods or mechanisms we use to achieve requirements of the system.
Fill the gap between the system specification produced during requirements elicitation
and analysis.
Make the system easily manageable by individual team member
To develop very efficient and simple clearance environment
To decrease the tiredness by the student that they are rounding all over the clearance
offices (staffs).
To decrease work load of the clearance employers.
To decrease the wastage of resources and time taken.
─ Error Handling and Extreme conditions: The system should be robust enough to handle error
conditions and continue with normal operations. If an error occurs, the system should
identify the error and notify to the user.
─ Availability: AU Student clearance system should be accessible from any computer if the
computer is connected with a server computer by local area network and will be accessible
anytime a user would want to use the program.
─ Security: AU Student clearance system should be secured, i.e., not allow other users or
unauthorized users to access data that has no the right to access it.
─ Modifiability: AU Student clearance system should be modifiable for further modification and
enhancement of the application.
─ Compatibility: Should be developed between the system and its interfaces
─ Adaptability: ability of the system to meet a wide range of functional requirements without
requiring physical modification.
User
-IDNo : Char
-FName : String
-MName : String
-LName : String
-Age : Int
-Gender : Char
* request
*approved
─ The class diagram is the main building block in our project modelling.
─ It is used both for general conceptual modelling of the systematic of the application and for
detailed modelling translating the models into programming code.
These are:-
─ The middle section contains the attributes which store information about an item
─ The bottom section contains the methods/operation that show what are done on object or
class.
The class Diagram below shows the class of our system, their inter relationship (including
inheritance and association) and the operations and attributes of each classes.
Offices
Security
Clearance
Processing
System Clearance DB
Student
/Application
Perisitence
Registrar
Ambo University Web based clearance System is server client structure architecture, where
clients access services offered by server. The deployment diagram is shown as follows.
Client Machine
:Chrome TCP/IP
Web Server
Admin
:Opera :XAMPP
:Mozilla
:Torch
PHP
Central Data
Base
:MYSQL
Description of the architecture of the system is described as follows. Clients are responsible for:-
─ The system user interface should be consistent with all other program.
─ The caption and the test of user interface should be self-descriptive and clear to
understand.
─ The user interface should be easy to understand.
─ The user interface should be customized.
─ The user interface should be accompanied with help files that describe the usage of each
user interface.
─ The user interface should be designed in the way that they can be extended easily to
support localization.
Homepage
Sport
Admin Student Proctor Department Book Store Library
science
Create
Upadate Upadate Upadate Upadate
account Upadate Upadate
Upadate Search Search Search Search
View Search
Search Aprove Aprove Aprove Aprove
Request Aprove
Delete
Aprove
Reference
[1] [Link]/
[2][Link]
id=bLzOaXQJG8oC&printsec=frontcover&dq=software+project+development+references&hl=
en&sa=X&ei=JQjaUJqVGM3GswaO9IGYCg&ved=0CEQQ6AEwAg#v=onepage&q=softwar
e%20project%20development %20references&f=false
[3] Object Oriented Analysis& Design, Understanding System Development with UML 2.0 and
Mike O Docherty 2005
[4] Anigbogu G. (2000). Systematic planning for educational change. California:
[5] System Analysis and Design for Software Engineers NIIT 2005
4.1. Introduction
Implementation is one of parts of the project development phase where project inputs are
converted to project outputs. In implementation phase, main task is coding. In implementation;
we tried to put into practice what was proposed in the project document i.e. transforming
the project proposal into the actual project. Then the developed system is implemented or
hosted on the server for the users to get the purpose or benefit of the system
Unit testing is every module of the System is separately tested. It is often done by the
programmer to test that the unit he/she has implemented is producing expected output against
given input.
When administrator creates account for student, he needs to add to the system and when
they miss some information the system displays error message as follows.
Integrated testing
The process of bringing together all the modules that a program comprises for testing purpose
System testing
System test insures that the entire integrated software system meets requirements. It tests a
configuration to insure known and predictable results. System testing is based on process
description and flows, emphasizing pre-driven process links and integration points.
In essence system testing is not about checking the individual parts of design, but about checking
the system as a whole. In effect it is one huge component.
Volume Testing
The purpose of volume testing is to find weakness in the system with respect to its handling
of large amount of data during extended time periods.
Acceptance testing
The process by which users test completed information of system, the end result of which is the
user acceptance of the system. Acceptance testing checks the system delivers what was
requested.
are complete; it will test to ensure that they integrate well with each other, the operating
system, and other components. System testing:-After all of the above testing are checked
we will test our system by other peoples and we will conduct some comments how they get
our system
Generally, based on the existing system problems the team will find a proposed solution
which solves some problems of the existing system. Like it decreases time consumption,
energy consumption, resource loses during processing the clearance system in manual system.
7. 5.2. Recommendation
Based on shortage of time and some other condition like resources we do not include
some features to our project. The team wants to recommend those who wants further work on
our project like adding chat room, which facilitates communication between administrator
and the different offices listed in this project and student to ask the administrator why
he/she can’t approved their clearance request and if the students lost the university property
he/she cannot physical contact with the casher person in order to payment. The other features
we recommend to be added to in this project are clearance processing for administration
of students and other worker like cafeteria workers, and library workers and all employees of
the Ambo University.
8. I. Reference
Books
Object Oriented Software Engineering using UML, Patterns and Java Second Edition by
Bernd Burgge and Allen [Link]
Design and Implementation of Student Clearance System (A Case Study of Caritas
University)
STAN MAGEE, CCP and LEONARD L. TRIPP Guide to software engineering
standards and specifications PART II
Alain Abran, École de technologiesupérieureJames W. Moore, The MITRE Corp. (2004
Version) Guide to software engineering body of knowledge 2004 Version
The UnifiedModeling Language Reference Manual, James Rumbaugh, Ivar Jacobson and
Grady Booch, Addison Wesley, 1999.
Website
[Link]
[Link]
[Link]
[1] [Link]/
[2][Link]
id=bLzOaXQJG8oC&printsec=frontcover&dq=software+project+development+references&hl=
en&sa=X&ei=JQjaUJqVGM3GswaO9IGYCg&ved=0CEQQ6AEwAg#v=onepage&q=softwar
e%20project%20development %20references&f=false
[3] Object Oriented Analysis& Design, Understanding System Development with UML 2.0 and
Mike O Docherty 2005
[4] Anigbogu G. (2000). Systematic planning for educational change. California:
[5] System Analysis and Design for Software Engineers NIIT 2005
9. II. Appendix
The proposed system aims to replace the manual clearance process by allowing students to complete clearance online, reducing the need to visit various offices in person. This approach is designed to ease queuing, minimize stress, decrease time delays, and offer convenience as students can access the system from anywhere at any time. Additionally, it promises to improve the transparency, reliability, and efficiency of handling clearance tasks .
The online clearance system enhances information processing speed by utilizing a digital platform that allows for immediate access to and processing of data. Unlike the manual system, which requires physical transportation and handling of documents, the online system can quickly retrieve, process, and store information without physical delays. This efficiency reduces the time required for clearance processing and minimizes data entry errors .
The use case for 'Register' describes a process where students interact with the system by filling out a registration form. The system validates the submitted information, and if correct, allows the student to register. This interaction ensures data integrity and offers a systematic approach to adding new users, minimizing errors and incomplete submission issues .
The project is deemed economically feasible due to its potential to drastically reduce labor costs, decrease reliance on physical materials like paper and pens, and improve overall institutional efficiency. The automation of clearance processes means less human intervention is required, thus reducing associated costs. Additionally, the convenience and speed of the online system can improve university operational workflows, making it a cost-effective solution .
The online clearance system seeks to address inefficiencies in the manual system, such as time-consuming physical processes, high potential for human error, and the need for students to visit multiple offices to complete clearance tasks. By digitizing these processes and streamlining data handling, the system reduces stress and workload for both students and staff .
The system ensures security and authorization through a robust login system that requires users to be registered, possessing a username and password for access. This structure prevents unauthorized users from accessing the system and ensures that only authenticated and authorized users can interact with sensitive information. The system's design includes security measures such as secure passwords, user registration, and access logs to track activities .
Key functional requirements include recording user details, validating inputs, providing secure login functionality, and offering fast response times for data retrieval and processing. Non-functional requirements focus on system security, user-friendliness, and availability, ensuring the system is accessible, performs well under load, and safeguards user data .
The anticipated benefits for students include faster access to the clearance system, reducing the time spent in queues and traveling between offices, and the ability to perform tasks anytime and anywhere, reducing fatigue. For the university, the benefits include cost savings on materials and manpower, reduced processing times, and enhanced operational efficiency with less reliance on paper-based systems .









