1.

System Analysis & Design

1.1.User characteristics

Primary user’s of the system

Each user has their own account.

• Employees

Employees
All the employees should be register here. Employee can request leave,
view the status of leave, eligibility of leave, and cancel the leave
request.

Secondary user’s of the system

• Administrator
• Supervisor
• Manager
• HRM

Administrator

Administrator is responsible for the entire system. He Keeps

track of every activity of the system.

Supervisor

Supervisor checks the employee leave request and he validate or cancel

the leave. He also can eligibility of leave and send it to the manager
Manager

Manager validate the leave, and send it to the HRM

1.2. Inputs and outputs

INPUT:-

Input1:- Login name and password

User uses login name and password to enter into their accounts.

Input2:-employee details

This detail includes employee’s name, address, and e-mail

address position of employee in the organization.

Input3:-Leave request

Through this employee can request leave

Input 4:-cancel leave

Through this employee can cancel the request leave

OUTPUT

Output1:Approval of leave.

Output2: View the status of employee, which display

employee in or out to the organization.

Output 3:- Cancel the leave request

All the input is in text format.

1.3.Interface Requirements

1.4.Functional requirements

There are registered people in the system. Some are approvers. An approver
can also be a requestor.

1. A person should be able to

• login to the system through the first page of the application

• change the password after logging into the system

• see his/her eligibility details (like how many days of leave

he/she is eligible for etc)

• query the leave balance

• see his/her leave history since the time he/she joined the
company/college

• apply for leave, specifying the from and to dates, reason for
taking leave, address for communication while on leave and
his/her superior’s email id

• see his/her current leave applications and the leave applications

that are submitted to him/her for approval or cancellation

• approve/reject the leave applications that are submitted to

him/her

• withdraw his/her leave application (which has not been

approved yet)

• cancel his/her leave (which has been already approved). This

will need to be approved by his/her Superior
 • get help about the leave system on how to use the different
features of the system

2. As soon as a leave application /cancellation request /withdrawal

/approval /rejection /password-change is made by the person, an
automatic email should be sent to the person and his superior giving
details about the action

3. The number of days of leave (as per the assumed leave policy) should
be automatically credited to everybody and a notification regarding
the same be sent to them automatically

4. An automatic leave-approval facility for leave applications which are

older than 2 weeks should be there. Notification about the automatic
leave approval should be sent to the person as well as his superior

5. A summary report of the leave details of his/her sub-ordinates should

be sent to every manager periodically

6. A calendar giving the public holidays of the organization/college

should be available on the system

1.5.Non functional requirements

Only the authorized persons can access the details stored in

the database. For this, password security is provided. The authorized user
is allowed to modify the details. Unauthorized persons are not allowed to
access the details. Only authorized

• Secure access of confidential data (user’s details).

• Better component design to get better performance at
peak time
• Flexible service based architecture will be highly
desirable for future extension
1.6.Operational requirements

SOFTWARE SPECIFICATIONS

PLATFORM : WINDOWS XP
FRONT END TOOL : ASP.NET with C#
BACK END TOOL : Oracle database system

HARDWARE SPECIFICATION
PROCESSOR : PENTIUM DUAL CORE

RAM :1 GB

HARD DISK : 5 GB OR ABOVE.

KEYBOARD : iball

CD DRIVE : 52 X

Optical Mouse : iball

USE CASE DIAGRAM FOR ONLINE LEAVE MANAGEMENT SYSTEM
Class diagram for online leave management system
employee
LOGIN
#Eid: String
#Ename: String
#Did: String
#Dname:string -User_Name: string
#email id: String 1 1
#phone no: Number -Password : string

+ Login ()
+Request leave () LOGIN VALIDATOR
+cancel leave()
+view status() + login_data()
+ view leave eligibility +Invok_validator()

USER ID + Validate_user()

Superviser HRM
ADMINISTRATOR
+
+H_ID
+SID :STRING

+Validate leave()
+View status() +Validate leave()
+enter_emp_details ()
+ View eligibility +View status()
+ View details()
+ View eligibility
1.7.Sequence diagrams

Login:-

User User Interface Server Database

Enter
username and
password Validate user
Successful
validation

Server sends HTML

Login page Verify user

Unsuccessful
Server sends validation
HTML

Error login page

Enter employee details

USER User Interface Server Database

Enter the details of Data send to

the emp database

Successfully saved
the data
View leave eligibility/leave status/emp status

USER User Interface Server Database

Login

Acknowledgement

Request view

Sends query Query passed

Result
Result sends to Returned
interface
Displays details
Request for leave/cancel leave

USER Database
User Interface Server

Login

Acknowledgement

Request /cancel leave

Sends query Query passed

Result
Result sends to Returned
interface
Displays details
 2. Design
2.1. Theoretical Background

The technology used is ASP .net with C# as front end

and SQL 2000 as back end.

2.2. Architecture

Data input (web Online leave Other system

client) management (Interface)
system (Interface)

Web server Validate leave

Database server
 E-R Diagram
e-mail
Ename EID Phone no S_id

phone

Request
employee supervisor
Leave

e-mail Location
C_name
Website
C_nam address
e

Location

HRM

e-mail

S_id
Website
address

Database Design:-
 1: Login

FIELD DATA TYPE SIZE DESCRIPTION

Username Varchar 20 Primary key

password Varchar 20 Not null

2: employee details
FIELD DATA TYPE SIZE DESCRIPTION

E_id number 20 Primary key

E_name number 20 Not null

D_id varchar 20 Not null

D_name varchar 20 Not null

category char 1 Not null

Address varchar 25 Not null

Ph_no number 15 Not null

Mobile number 12 Not null

Job_des varchar 15 Not null

salary Number 15 Not null

 3: Request leave

FIELD DATA TYPE SIZE DESSCRIPTION

E_id Varchar 20 Foreign key

E_name Varchar 20 Not null

Reason varchar 200 Not null

Type_leave varchar 10 Not null

Date_to date

Date_from date

4: cancel leave

FIELD DATA TYPE SIZE DESCRIPTION

E_id number 20 Foreign key

E_name Varchar 20 Not null

Type_leave varchar 10 Not null

Date_to date

Date_from date
 5: leave table
FIELD DATA TYPE SIZE DESCRIPTION

Leave_id number 20 Primary key

E_id number 20 Foreign key

E_name varchar 20 Not null

D_id varchar 20 Not null

D_name varchar 20 Not null

Not null
Type_leave Varchar 10
Date_from date

Date_to date
 6: Valid_request
FIELD DATA TYPE SIZE DESCRIPTION

Leave_id number 20 Primary key

E_id number 20 Foreign key

E_name varchar 20 Not null

D_id varchar 20 Not null

D_name varchar 20 Not null

Not null
Type_leave Varchar 10
Date_from date

Date_to date
 7: manager_valid

FIELD DATA TYPE SIZE DESCRIPTION

Leave_id number 20 Primary key

E_id number 20 Foreign key

E_name varchar 20 Not null

D_id varchar 20 Not null

D_name varchar 20 Not null

Not null
Type_leave Varchar 10
Date_from date

Date_to date

8: HRM_valid
 FIELD DATA TYPE SIZE DESCRIPTION

Leave_id number 20 Primary key

E_id number 20 Foreign key

E_name varchar 20 Not null

D_id varchar 20 Not null

D_name varchar 20 Not null

Not null
Type_leave Varchar 10
Date_from date

Date_to date

9:leave eligibility

7: manager_valid

FIELD DATA TYPE SIZE DESCRIPTION

E_id number 20 Foreign key

E_name varchar 20 Not null

D_id varchar 20 Not null

D_name varchar 20 Not null

Not null
Type_leave Varchar 10
Date_from date

Date_to date