PROJECT REPORT

Submitted By:

Zaman Arif (2018-GCUF-07844)

Usama Zafar (2018-GCUF-07797)

Project Submitted (Employee leave management

system)

in partial fulfillment of

The requirements of the degree of

ASSOCIATE DEGREE
IN
COMPUTER SCIENCE

UNIVERSITY COMMUNITY COLLEGE

GOVERNMENT COLLEGE UNIVERSITY, FAISALABAD

SYSTEM MODULES OF LEAVE APPLICATION MANAGEMENT
SYSTEM:

Our system is comprised of few important interfaces or we can say

modules behind it so here we will discuss the modules related to all
those interfaces and workflow further.

Register:
One user has to register on this interface with it actual data to be filled
and applied in the same interface, then pressed enter to be saved in the
database. Further, move to log in.

Login:
The user inputs its secure user id and password and enters the system.
User can login multiple times as many times he wants

Leave apply:
Here is the module for applying for leave to the interface. One has to
enter his details about the leave like reason of the leave.

Choose the dates of the leave. Depending upon the user’s account and
policy of the company or premise the cost of the leave is calculated and
shown to the interface.

Live review:
After successful application of the leave application is will come under
scrutiny done by an admin. According to his need, he will review it and
take necessary action in next module.

Leave approval:
Here admin approves the leave or not is reflected by admin to the users.
Here all the real-time update will be shown to the users. Users can see
only their own leave request there.
Log out:
In the end, the user can log out the system to release the resources held
for the purpose of anything else.

SYSTEM REQUIREMENTS OF LEAVE APPLICATION

MANAGEMENT SYSTEM:

we can access this system through a computer or portable device.

Every system needs ups for removing the cause of electricity loss and
data loss with it as one can save their answers or end in time. For proper
evaluation of the test.

The system needs to be of 1.3 g h z minimum cp u clock speed.

it should have minimum 2 g b ram for proper working with speed. To

avoid delays in actions.

mouse and keyboard also required for typing as it is purely a data feed
which and subjective combined so for fast and comfortable execution
we have to use mouse and keyboard.

other we can take an admin system reserved for staff account

maintaining it along.

SYSTEM DESIGN OF LEAVE APPLICATION MANAGEMENT SYSTEM:

Now we have to design our system before implementing it in such a

way that it can execute all the work we want without any loss of data
and without using any kind of functionality.

For this purpose, we have two kind diagram we use here to represent
the system interaction and flow the data storage which is er diagram
here. These are as follows:-

E-R DIAGRAM OF LEAVE APPLICATION MANAGEMENT

SYSTEM:
Entity Registered User:
The user or the staff of the company is the user of this portal and we
have to register himself on this network with his actual credentials. As
the need for scrutiny.

Primary key registered user Id:

This is system generated id which unique in its own. need for the every
entity to recognize easily and reference in any other interface with other
entities easily and usefully.

Name :
Name of the staff as in the joining letter should be same he is
recognized by that name and another name than that will not go to be
recognized.
Designation:
What is a job he assigned for and what is the designation for which he
is posted at the moment is given here in this entity?

Number:
A number of the staff is taken to give the indication of the response of
his cell about the leave approval or not.

Email:
email is also taken to carve the insecurity of unreachable phones and
other problems too. for official approval, this can use.

Entity leave request:

Here in this entity, all the data regarding the leave request is fed in this.

Primary key leave request id:

This is system generated id which unique in its own. need for the every
entity to recognize easily and reference in any other interface with other
entities easily and usefully.

Duration:
The number of days that much he needs leave should be mentioned
over here.

Start date:
From which date he needs those leave should be mentioned over here.

End date:
till which date he needs those leave should be mentioned over here.

Type of leave:
the type of leave should be given as the priority of the resolution will be
given through this attribute. Few of the options like paid or unpaid . is
chosen from the drop-down box.
Description:
Here one needs to fill it very carefully and very precisely as it will get
under scrutiny if found may be punished too or penalty levied.

Here it should be written very creatively that reader gets influence

through the first shot. And approve as soon as possible.

Leave cost:
Depending upon the leave type in the above entity the cost of the leave
will be calculated it depends upon the policy of the system of the
company of providing the leaves.

Primary key leave cost id:

This is system generated id which unique in its own. need for the every
entity to recognize easily and reference in any other interface with other
entities easily and usefully.

Foreign key user_id:

The key for reference is given here for the important data to be fetched
from there needed data is put into expressions and formulations then
calculated the left cost.

Foreign key Leave id:

The key for reference is given here for the important data to be fetched
from there needed data is put into expressions and formulations then
calculated the left cost.

Leaves status:
Now, this is the task of the admin to review the leave request and
response to the leave in the form of yes or no.

Primary key leave status-id:

This is system generated id which unique in its own. need for the every
entity to recognize easily and reference in any other interface with other
entities easily and usefully.
Leave_id;
The key for reference is given here for the important data to be fetched
from there needed data is put into expressions and formulations then
calculated the left cost.

User_id:
The key for reference is given here for the important data to be fetched
from there needed data is put into expressions and formulations then
calculated the left cost.

Admin:
Admin has the main power and the main purpose of the system is
approved by this entity. It has few important entities needed to review
and update the user’s requests.

Id:
This is system generated id which unique in its own. need for the every
entity to recognize easily and reference in any other interface with other
entities easily and usefully.

Password:
The most secure password is taken into consideration so as the misuse
of the system can be cured. here mostly used pass are avoided. The
complex password which is not easily pronounceable is taken into
consideration.

Logs:
Logs are taken regularly as to analyze the system on our parameters and
get some useful results for the future improvements as well as security
concern is also taken in mind. These logs are studied and the results are
analyzed.
USE CASE DIAGRAM OF LEAVE APPLICATION MANAGEMENT
SYSTEM:

The use case diagram is made to show the external users and system
use cases interaction at any time. So here we have actors and use case
and link with them we have them here as below. : –

Here is only a two type of users which are present here in this system.
This user has all the privileges but it cannot register itself on this
system as the admin needs to verify the registering user.

After the admin verifies the user only when he is eligible to use the the-
the system and after that, it has all the privileges. Attributes given to the
user are:

We have actors as Users which was firstly unregistered to the system

and now after filling the registration form where we have many
attributes which are available and need to be filled for future reference
and correct working system for him is required.

then he can log in by putting in credentials and then move to the home
page

he will have an interface of the home page where at one part he has the
option of apply for leave and another part as see the request status.

he can apply for the leave by entering in that and picking the date from
date pickers and giving the other important attributes in that.

now he can confirm the leave request then it goes to the admin panel

Admin:
Here admin have the option shown to him as see the request and other
approved requests.

he will see the requests here and do the necessary action as needed.

as the response given it is recorded and updated to other interfaces in

real time.

next is to show this user panel he can see and get a notification for the
same with details of the leave given to him.

FUNCTIONAL AND NON-FUNCTIONAL REQUIREMENTS OF

LEAVE APPLICATION MANAGEMENT SYSTEM:

Non Functional Requirements of leave application management

system:
The user needed to be able to register in the portal with his own set of
attributes as required in the entity attributes.

The user can login with his credentials

user should be able to enter the detail of the leave

he can apply for the leave by entering in that and picking the date from
date pickers and giving the other important attributes in that.
now he can confirm the leave request then it goes to the admin panel

Here admin have the option shown to him as see the request and other
approved requests.

The same changes are reflected in the other interfaces too.

Execution qualities, like security and usefulness, that square measure

evident at the run time.

Evolution qualities, like liabilities, maintainability, flexibility and

quantifiable, that square measure embodied within the static structure of
the code.

Non-functional of leave application management system necessities

place restrictions on the merchandise being developed, the event
method, and specify external constraints that the merchandise should
meet

Keep things simple and consistent:-

Simple and Harmonic way making UI is very intuitive and needs to
followed

Make good use of typography:-

The typography is taken care very strictly as the need of the system.

Use colour and contrast properly:-

Color combo of lite and dark is good way emphasis and done well in
this system

Consider feedback messages:-

The feedback form is a very good way taking feedback of forms and
improving the system.

Simplified forms:-
The form is made simple to fill with the clean user interface.
Our project qualifies all the criteria of functional and non-functional
accordingly and the system is up to mark performance vice. Here we
need to take care of few more things before heading towards the
system.

The the most important feature of application world is that application’s

ease of usage .application will easy to use if made while keeping in
mind that user need not think twice about searching any feature.

Everything should be made distinctive by using the colour combination

such that everything needed most frequently highlighted with focus
colours. We can use simple layouts like the card and grid layout etc.

By varying colour and other UI combination, many good intuitive

interfaces can be made. Which ultimately makes the interface easy to
use for a long time.

Unlike ancient style wherever the goal is to form the thing or

application physically enticing, the goal of interface style is to form the
user’s interaction expertise as straightforward and intuitive as attainable
– what’s typically known as user-centred style.

Where smart graphic/industrial style is daring and eye-catching, smart

interface style is commonly delicate and invisible.

SPARK ONLINE LEAVE MANAGEMENT SYSTEM

CONCLUSION OF LEAVE APPLICATION MANAGEMENT
SYSTEM:

So here we finally are with a leave application management system

which can take request of the staff for leave to be applied according to
its own set of attributes filled by the user and requested.

One requested shown to the admin, admin reads that approve or

disapprove according to his requirement then it is up to admin. Admin
reviews all the actions and other activities beyond that and takes
necessary actions.

Leave request screen is an internal part of Employee Self Service.

Leave request operate empowers worker to request for varied leaves as
per their demand & company time unit policy starting from short leaves
to long leave, leave of absence to come off.

Employees will read their past leave request & current leave application
standing. Leave request will be saved within the draft mode by the
worker & then will be submitted to the reportage manager & the
hierarchy for applicable action.

The choice to regularize leave or cancel the applied leave at any time
makes the leave request operate “employees delight“.
Leaves applied via request action area unit checked by the leave rules
engine & consequently, generates the desired message & warnings, that
additional helps workers to require correct call.
It is a good grasp reality, any work finished utmost transparency ends
up in future engagement.

Leave ledger helps employers to showcase with utmost transparency

workers their actual monthly leave credit as per rules & leave kind,
additional it even shows the consumption of leaves on monthly basis by
the staff.

It drills down until the top to point out the dates on that leave is utilised.
simple to use Opportune leave management modules is well integrated
with Manager Self-Service feature, permitting managers to access
worker leave requests justifiably for leave, at the side of current leave
balance & historical information of the worker.

Any violation of leave rules throughout the applying by the worker is

highlighted in a very separate colour & with the explanation, helping
the manager to take the right decision before accepting or rejecting of
application

The managers before approving or rejecting leave requests can also

check other pending leaves in the department ensuring adequate
headcount for optimal productivity planning.
Hence we are complete with a system which is ready to give the facility
to the staff to track all the requests.
Algorithm: