e leave

27
e-Leave: Online Leave Application System

Upload: htetthuzar

Post on 15-Jul-2015

85 views

Category:

Software


0 download

TRANSCRIPT

Page 1: E leave

e-Leave: Online Leave Application System

Page 2: E leave

Agenda

2

Introduction

Project Philosophy

System Architecture

Functional and System Capabilities

System Demo

Discussion

Conclusion

Q & A

Page 3: E leave

Introduction

Why automating leave

application process important?

Manual (paper-based) leave

application process is time-

consuming and less efficient

Effective leave management

lead to significant reduction in

costs and improvement in

productivity

Automating leave application

makes every application

paperless, convenient, fast and

efficient

Page 4: E leave

Introduction

Automated Leave Application would help in

Track status of all leave records

Convenience of time and location for applicant as well approver

Reduced workload of Administration staff

Reduce costs

Page 5: E leave

Project Philosophy – con’t

Pre-requisites

Java Platform : Jdk 1.7

Web Container : Tomcat 7.0

Web Server : Apache

Database :Mysql 5.5

IDE for Java : Esclipe 3.6

IDE for Mysql Database : Mysql WorkBench 5.2

Tools / Technology

J2EE, Servlet and JSP

JavaScript

JQuery

CSS (Cascading style sheet)

Page 6: E leave

Project Philosophy 2 Major Features

Leave Application System

User Management System

e-Leave Online Leave Application System

Leave Application System User Management System

Page 7: E leave

Project Philosophy – con’t

Roles and Responsibilities

Four team members

Four development phases

1. Modeling (10%)

2. System Development Design (20%)

3. Coding and Unit Testing (50%)

4. Integrated Testing and Bug Fixing (20%)

Page 8: E leave

System Architecture

Servlet : processes HTTP request s and responses, serve as controller

JSP : display dynamic content

Java Classes : implement backend ‘business’ codes

Page 9: E leave

System Architecture – con’t

High level model

– build with Use Case diagram

– define interaction between stakeholders and system

Page 10: E leave

Use Case Diagram

Page 11: E leave

System Architecture – con’t

Database design

- use ER diagram

- specifies relationship between entities

in database

Page 12: E leave

ER Diagram

Page 13: E leave

Functional and System Capabilities

Mainly, there are four modules

1. Login

2. Leave application module

3. Approval module

4. Admin module

Page 14: E leave

Functional and System Capabilities

1. Login module

- Every user needs to login to access to the system

Page 15: E leave

Functional and System Capabilities

2. Leave Application Module

a) Leave Application Listing

- employee uses for viewing leave information

Page 16: E leave

Functional and System Capabilities

b) Leave Form

- employee uses for applying leave

- Enforces form completion through required

field validation

Page 17: E leave

Functional and System Capabilities

3. Leave Approval Module

a) Leave Approval Listing

- manager uses for pending leave information

Page 18: E leave

Functional and System Capabilities

b) Approval Form

- manager uses for approving or rejecting leave

- Leave records are updated automatically once approved

Page 19: E leave

Functional and System Capabilities

4. Admin Module

a) User Account Listing

- system admin uses for managing application

Page 20: E leave

Functional and System Capabilities

b) User Form

- system admin uses for managing user information.

- immediate creation and update of records

Page 21: E leave

Functional and System Capabilities

Page 22: E leave

Discussion

The knowledge on Java technologies is fundamental skill required.

There was a challenge in the data manipulation in database system.

It is recommended to do deeper feasibility study as organizational standard, culture and leave policies vary one another.

Non-functional requirements such as security, performance etc. need to consider.

Page 23: E leave

Discussion – con’t

Future enhancements

- Task List : display tasks need to be done by logon user

- Email/SMS Notification : notify approver as well as applicant

- Audit Trail : tracing error and exception handling

- Reporting : provide facility to generate report

Page 24: E leave

Conclusion

Fulfilled the main goal – reduces physical movement and paper work.

Implemented e-leave system by providing essential and basic functional requirement within certain time limit.

Designed to make sure that the user can comfortably and efficiently utilize it.

Follow look-and-feel standards – consistent layouts and design throughout application.

Page 25: E leave

DEMO

Page 26: E leave

Question

26

Page 27: E leave

Thank you!

27