Leave Application Management System

1
 Leave Application Management
System
Design Document

Version 1.0

Group Id:F1902694F6 

Supervisor Name: Dr. Nida Anwar 

2
Revision History

Date (dd/mm/yyyy) Version Description Author

21/01/2020 1.0 Leave Application Management System Summer Malik, Bushra
Munir

3
 Acronyms & Description

Term Description

VU Virtual University of Pakistan

ERD Entity Relational Diagram

IEEE Institute of Electrical and Electronic Engineers

LAMS Leave Application Management System

4
 Contents at Glance

1. Introduction..................................................................................................................6
2. Overview......................................................................................................................8
3. Entity Relationship Diagram(ERD).............................................................................9
4. Sequence Diagram......................................................................................................10
4.1Sign in.......................................................................................................................10
4.2 Leave Request..........................................................................................................11
4.3 Log out.....................................................................................................................12
4.4 Registration..............................................................................................................13
4.5 Attendance...............................................................................................................14
4.6 View report..............................................................................................................15
5. Architecture Diagram.................................................................................................16
6. Class diagram.............................................................................................................17
7. Database Design.........................................................................................................18
8. Interface Design.........................................................................................................19
9. Test Cases...................................................................................................................23

5
1. Introduction
The design document shows the designing process of the system in a graphical

form. This document tells about front end and back end design of the system.

It briefly describes how a system works, how an activity perform, how the system

interact with the database, etc… It describes the features of the system. This document

helps to design the project easily.

The document has these diagrams:

 Entity Relationship Diagram

o In this diagram the relationship between entities of the system is

described. Three main things in this diagrams are as follows:

 Entities

 Attributes

 relation

 Sequence diagram

o This diagram describes the sequence in which an activity is

performed.

 Architecture diagram

o Define the architecture of the system

 2 tier or three tier

 Class diagram

o Describe classes and their relationship

 Database diagram

o It describe database tables and their relations

 Interface diagram

o About interfaces of the system.

 1. Overview
The LAMS provide the following functionalities:-

1. User must register himself on interface, and fill the complete form. Admin will
approve the registration of users.
2. User must be able to get login.
3. Applying leave module must contain tabs like
 Total number of Available Leaves
 Reason of Leave
 Apply Date
 Address
 Module to calculate the Leave Deductions
 Total Cost to be deducted of Leaves
 Leaves could be either Casual, Earned, Without Pay or Medical

4. After successful applying of leave application, it will be available for Admin for
approval.
5. Employee will be able to mark their attendance online.

6. Admin will review about the leave and will be authorized to ‘Accept’ or ‘Reject’
the leave.
7. After the “Approval” or “Rejection” of leaves, SMS Alert/ Email Notification
must be sent to the concerned employee.
8. A proper user friendly Graphical User Interface must be designed, to make all
tasks interactive.
9. In end all status of leave application, must be shown to the user, and all records
and history of leaves must be saved into the database by admin.
10. Admin must be able to keep record of employees.
11. Administrator will be able to maintain daily attendance of employee.
12. User must be able to logout to release the interface.
2. Entity Relationship Diagram (ERD)
 4. Sequence Diagram
The sequence diagrams tells the sequence of activities perform in a system. This diagram shows
the working of all actors involve in the task. In which order the actors or objects interact with
each other and how they complete the task or an activity.

It briefly describes the working of a system.

4.1 Sign in

Sign in
4.2 Leave Request

Leave Request
4.3 Logout

Logout
4.4 Registration

Registration
4.5 Attendance
Attendance
4.6 View Report

View report
 3. Architecture Diagram
It describes the interaction of the system. There are two ways in which the system interacts.

In one way the user have a direct access to the database server and on the other way the user
interact with the interface first and then if needed the system forwarded the request to the server.

In this system 3 tier architecture is used. It has three tiers

 Client tier
 Web tier
 Data tier
6. Class diagram
4. Database Design
 5. Interface Design

8.1 Sign Up Page

5.2 Login Page
5.3 Mark Attendance
5.4 Apply Leave
 6. Test Cases

Test Case #1

Test Case Title: registration

Preconditions User must be a legal person.

User must have an internet connection

Actions
1. User fill the form first.
2. Submit the form.
3. Click on register button.
4. Admin view the request and give response against the request.

Expected The user register successfully.

Results

Tested By: Summer Malik, Bushra Munir

Test Case #2

Test Case Title: User Login

Preconditions User must be registered on the system.

Actions 1. Press the sign in button.

2. Give user name.
3. Give password.
4. Press login button.

Expected Results Successfully logged in.

Tested By: Summer Malik, Bushra Munir

Test Case #3

Test Case Title: Apply for leave

Preconditions Employee must be registered and logged in.

Actions

1. Click apply leave button

2. Give the instructions.
3. Apply for leave.
4. Admin view the request and give response.

Expected Results User apply for leave successfully

Tested By: Summer Malik, Bushra Munir

Test Case #4

Test Case Title: Attendance

Preconditions Employee must be registered and logged in.

Actions

1. User access the system from personal computer

2. Mark attendance.
3. Admin view the request and generat the response.

Expected Results Attendance marked successfully

Tested By: Summer Malik , Bushra Munir

Test Case #5

Test Case Title: Available Leaves

Preconditions Employee must be registered and logged in.

Actions
1. User check the availability of leaves.
2. The page having all leave records of the employee will b appear.
Expected Employee check the available leaves successfully.
Results
Tested By: Summer Malik, Bushra Munir
Test Case #6

Test Case Title: user Logout

Preconditions Employee must be registered and logged in.

Actions
1. The logged in user click on logout.
2. The system expire the session of the person..
3. The employee logged out from the system.

Expected Results The employee should be successfully logged out from system.

Tested By: Summer Malik, Bushra Munir