Beruflich Dokumente
Kultur Dokumente
The Leave Management system is an Intranet based application that can be accessed throughout
the organization or a specified group/Dept. This system can be used to automate the workflow of
leave applications and their approvals. The periodic crediting of leave is also automated. There are
features like notifications, cancellation of leave, automatic approval of leave, report generators etc
in this Tool.
This project is aimed at developing a web based Leave Management Tool, which is of importance to
either an organization or a college.
The Easy Leave is an Intranet based application that can be accessed throughout the organization or
a specified group/Dept. This system can be used to automate the workflow of leave applications and
their approvals. The periodic crediting of leave is also automated. There are features like
notifications, cancellation of leave, automatic approval of leave, report generators etc in this Tool.
There are registered people in the system. Some are approvers. An approver can also be a
requestor. In an organization, the hierarchy could be Engineers/Managers/Business
Managers/Managing Director etc. In a college, it could be Lecturer/Professor/Head of the
Department/Dean/Principal etc.
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
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.
EXISTING SYSTEM:
All Work are done Manually.
Cannot Upload and Download the latest updates.
No use of Web Services and Remoting.
Risk of mismanagement and of data when the project is under development.
Less Security.
No proper coordination between different Applications and Users. Fewer Users - Friendly.
PROPOSED SYSTEM:
The development of the new system contains the following activities, which try to automate the
entire process keeping in view of the database integration approach.
In this world of growing technologies everything has been computerized. With large number
of work opportunities the Human workforce has increased.
Thus there is a need of a system which can handle the data of such a large number
of Employees. This project simplifies the task of maintaining records because of its user
friendly nature.
The objective of this project is to provide a comprehensive approach towards
the management of employee information.
This will be done by designing and implementing an HR management system that will bring
up a major paradigm shift in the way that employee information is handled.
Well-designed database to store employee information.
A user friendly front-end for the user to interact with the system.
The leave management system is designed in such a way that makes it possible to access it through
any web browser program.
The leave management system was designed, developed and implemented taking the distinction of
the leave of absence policies and type of leave and the system is exclusively designed and developed
for HR department in general and the employees leave records section in particular. The employee
leave section is solely responsible for keeping the leave and related records of employee and
keeping track of their information.
MODULE DESCRIPTION
Administrator:-
In this module the Administrator has the privileges to add all the Employees and register them in the
organization and check the information of the Employee and check the status of the leave when they
have taken and what type of leave they have taken and search is done based on the employee and
report is generated based on employee.
Search:-
This module contain complete search like Leave search, Type of Leave, Employee based on the leave
and starting and ending day of leave.
Employee:-
In this module employee has the privileges to use his username and password for login and he can
see the request given by the customer and he can pass the process to the Business Manager and
maintain the record of the customers.
Reports:-
This module contains all the information about the reports generated by the Employees based on
the Performance and by the leave status.
Authentication:-
This module contains all the information about the authenticated user. User without his username
and password can’t enter into the login if he is only the authenticated user then he can enter to his
login.
OPERATING SYSTEM:64-bit
NETBEANS: Version 8.0.2
LANGUAGE: Java
BACKEND:MYSQL
• Java is platform independent language hence can be executed on architecture that support on
JVM.
• Java also reduces cost related to deployment & maintenance of hardware & software.
• Java base clients are think like that uses minimum hardware resources.
• There are big insentive to create java-based solution for corporate as shifting there
application across the architecture will not involve overhead or cost.
MySQL-Back end
Databases are the systems that contain many different objects used together to facilitate fast and
efficient access to the data.
MySQL is an application program interface form Microsoft that lets a programmer writing Windows
applications; get access to a relational as well as non-relational database from both Microsoft and
other database providers.
The ‘administrative user interface’ concentrates on the consistent information that is practically,
part of the organizational activities and which needs proper authentication for the data collection.
These interfaces help the administrators with all the transactional states like Data insertion, Data
deletion and Date updation along with the extensive data search capabilities.
The ‘operational or generic user interface’ helps the end users of the system in transactions through
the existing data and required services. The operational user interface also helps the ordinary users
in managing their own information in a customized manner as per the included flexibilities
INPUT STAGES:
Data recording
Data transcription
Data conversion
Data verification
Data control
Data transmission
Data validation
Data correction
INPUT MEDIA:
At this stage choice has to be made about the input media. To conclude about the input media
consideration has to be given to;
Type of input
Flexibility of format
Speed
Accuracy
Verification methods
Rejection rates
Ease of correction
Storage and handling requirements
Security
Easy to use
Portability Keeping in view the above description of the input types and input media, it can
be said that most of the inputs are of the form of internal and interactive. As Input data is to
be the directly keyed in by the user, the keyboard can be considered to be the most suitable
input device.
OUTPUT MEDIA:
In the next stage it is to be decided that which medium is the most appropriate for the output.
The main considerations when deciding about the output media are:
Keeping in view the above description the project is to have outputs mainly coming under the
category of internal outputs. The main outputs desired according to the requirement
specification are:
SYSTEM ARCHITECTURE
Architecture flow:-
Below architecture diagram represents mainly flow of requests from users to database through
servers. In this scenario overall system is designed in three tires separately using three layers called
presentation layer, business logic layer and data link layer. This project was developed using 3-tire
architecture.
Presentation Layer
Request Response
Data Link
Data Base
Technical Feasibility
Operation Feasibility
Economical Feasibility
TECHNICAL FEASIBILITY
The technical issue usually raised during the feasibility stage of the investigation includes the
following:
OPERATIONAL FEASIBILITY
User-friendly
transactions based on the constraints. Theses forms and reports are generated as userfriendly to the
Client.
Reliability
The package wills pick-up current transactions on line. Regarding the old transactions, User will enter
them in to the system.
Security
The web server and database server should be protected from hacking, virus etc
Portability
The application will be developed using standard open source software (Except Oracle) like Java,
tomcat web server, Internet Explorer Browser etc these software will work both on Windows and
Linux o/s. Hence portability problems will not arise.
Availability
This software will be available always.
Maintainability
The system called the ewheelz uses the 2-tier architecture. The 1st tier is the GUI, which is said to be
front-end and the 2nd tier is the database, which uses My-Sql, which is the back-end.
The front-end can be run on different systems (clients). The database will be running at the server.
Users access these forms by using the user-ids and the passwords.
ECONOMIC FEASILITY
The computerized system takes care of the present existing system’s data flow and procedures
completely and should generate all the reports of the manual system besides a host of other
management reports.
It should be built as a web based application with separate web server and database server. This is
required as the activities are spread through out the organization customer
wants a centralized database. Further some of the linked transactions take place in different
locations.
Open source software like TOMCAT, JAVA, Mysql and Linux is used to minimize the cost for the
Customer.
Notification
Accept\Reject Validate
HOD
DFD
:-
Level 0 Data Flow Diagram
Check
Type of leave
Employee Login For Leave Fills
Application. Fills the Form
Documents
Database Employee Fills
Check Request
HOD
Granting the
Permission. Accept\Reject
Database HOD
Accept\Reject
Request
Check Detail of
Admin
Employee. Update Records
Notification
Database Admin
Rejected\ Rejected\
Approval Approval
Head 0f Superintendent
Department
Home Page
Login page
Add\Delete Dept
Add\Delete Employee
Leave Checking
Leave Section
Search Employee
Search Dept
Home Page
Login Page
Change Password
Update Info
User_password
#Per-id
#user_id login Per_module
User_name
Per_desc
User_mobile
Permission
user_email User
Rep_name
Administration
user_address #Rep_id
Rep_desc
Rep_type
Report
Rep_date
Emp_add
manage
Emp_id
Lv_desc
Emp_mail Employee
Emp_password
Emp_name
Emp_mobile
leave
#lv_id Lv_type
Lv_emp_id
Lv_status
TESTING IN STRATEGIES
In order to make sure that the system does not have errors, the different levels of testing
strategies that are applied at differing phases of software development are:
Unit Testing:
Unit Testing is done on individual modules as they are completed and become executable. It is
confined only to the designer's requirements.
Incorrect or missing functions Interface errors Errors in data structure or external database access
Performance errors Initialization and termination errors.
In this testing only the output is checked for correctness. The logical flow of the data is not checked.
Integrating Testing :
System Testing :
Involves in-house testing of the entire system before delivery to the user. It's aim is to satisfy the
user the system meets all requirements of the client's specifications.
Acceptance Testing :
It is a pre-delivery testing in which entire system is tested at client's site on real world data to find
errors.
Test Approach :
Testing can be done in two ways:
Bottom up approach
Top down approach
Bottom up Approach:
Testing can be performed starting from smallest and lowest level modules and proceeding one at a
time. For each module in bottom up testing a short program executes the module and provides the
needed data so that the module is asked to perform the way it will when embedded with in the
larger system. When bottom level modules are tested attention turns to those on the next level that
use the lower level ones they are tested individually and then linked with the previously examined
lower level modules.
Validation:
The system has been tested and implemented successfully and thus ensured that all the
requirements as listed in the software requirements specification are completely fulfilled. In case of
erroneous input corresponding error messages are displayed