4.

SYSTEM DESIGN

4.1. PROJECT DESCRIPTION

The Employee management and Payrollsystem project has been divided into Six
modules. They are,

1. Company Master

2. Employee

3. Leave

4. Loan

5. Salary

6. Report

4.2.MODULE DESCRIPTION

This section attempts to describe each module of the project in brief and the detailed description
of each of these modules is spread throughout this document

COMPANY MASTER
This Company master used to store the details of the Company,Branch,Department,Destination and Grade
Details the Company could been track the Company Information.

The details for the company master like

 Company Details

 Branch Details

 Department Details
  Destination Details

 Grade Details have been stored.

EMPLOYEE

The employee is used to record the details contain in the main form, This has the entry for the employee
personal details like dept code,desg code,grade code,emp code,employename,fathersname,date of
birth,sex,married status,qualification,address,pincode,mobile number,blood group,salary these details are
been recorded, deleted, searched. This details stored in the employee module

LEAVE

This module is used to store and review the Leave details of employee. It
contains two sub modules. The operations perform this module are as

 Leave Master

 Leave Avalid

Leave master module can contain employe code,year,casual leave,sick leave,

previlege leave,maternity leave,other leave details can stored it.

Leave availed module can used to manage or availability of the leave to store and
view add,delete or update the availability of leave.

LOAN

loan module is used to provide store and review the loan details of employee. It
contains two sub modules. The operations perform this module are as

 Loan Master

 Loan Avalid

Leave master can include the loan type and rate of interest .
 Loan availed module can provide employeeloan using empcode,loantype
including rate of interest,date of availing,amount availed,total amount to
repay,total instalments,balance instalments,amount/instalments,amount repaid to
manage the loan availabilty to store ,view and add,delete or update.

SALARY

payrollgeneration module is used to provide and generate the salaryclip store and
review the salary details of employee.payrollgeneration include the fields
employeecode,date of issue,department,destination,grade, and two sections
allowences and deductions The operations perform this module as follows

 Allowences

 Deductions

Allowences includes Basic amount and calculate percentage of

H.R.A,CA,Medical,Washing,Special allowences,other1,toher2 and finally generate the
Totalamount and Gross salary

Deductuons can includes PF,GPF,Med Deduction,P.Tax,Incometax,Insurance,Loan,special

deductions using to generate the Totalamount of deductions and finally got Net salary.

REPORTS

The reports are used to generate the hardcopy for information, this report has the details
like Employee information,Companydetails report, Leavedetails report,Branchdetails report,
Loandetails report,Departmentdetails report, and EmployeeSalary reports. It contains

 Employee report

 Salary report

 Company report

 Department report

 Branch reports
Leave reports

4.4 USER INTERFACE DESIGN

INPUT DESIGN
Input design is a part of overall system design, requires the very careful analysis of the
input data items. The goal of the input design is to make the data entry easier, logical and free
from errors. The user controls input data.

The commonly used input, output devices are mouse, keyboard and the visual display
unit. Well designed, well organized screen formats are used to acquire the inputs. The data
accepted is stored on database file.

OUTPUT DESIGN

Output is the most important and direct source of information the user. Efficient and
intelligent output design improves the system relationships with the users and helps in decision-
making. The output is collected in order to help the user to make a wise decision.

5. SYSTEM IMPLEMENTATION

Implementation is the phase where the system goes for actual functioning. Hence inthis phase
one has to be cautious because all the efforts undertaken during the project willbe fruitful only if
the software is properly implemented according to the plans made.The implementation phase is
less creative than system design. It is primarilyconcerned with user training, site preparation and
file conversion. Depending on the natureof the system, extensive user training may be required.
The initial parameters of the should be modified as the result of programming efforts;
programming provides a realitytest for the assumptions made by the analyst.The system testing
checks the readiness and accuracy of the system to access,update and retrieve data from new
files. Once the programs become available, the test dataare read into the computer and process.

6. SYSTEM TESTING

Unit Testing

Unit testing has the goal of discovering errors in the individual module of the system unit testing
should be as exhaustive as possible to ensure that each representative case handled by each
module has been tested. Unit testing is eased by a system structure that is composed of small,
loosely coupled modules. All modules were thoroughly unit tested and bugs were corrected.

System testing involves two kinds of activities:

 Integration testing
 Acceptance testing

Integration testing

The integration testing strategy dictates the order in which modules must be available, and
thus exerts a strong influence on the order in which modules are written, debugged, and unit
tested. The subsystem consists of several modules that communicate with each other through
well-defined interfaces. Normally, a subsystem implements a major segment of the total system.
The primary purpose of subsystem testing is to test both control and data interfaces. Bottom-up
integration is the traditional strategy used to integrate the components of the system into a
functioning whole. Bottom-up integration consists of unit testing followed by subsystem testing,
followed by testing of the entire system.

Bottom-up testing include the necessity to write and debug test harness for the module and
subsystem.

Top-down integration starts with the main routine and or two immediately subordinate
routines in the system structure

Top-down integration offers several advantages:

1. System integration is distributed through the implementation phase modules are integrated
as they are developed.
2. Top-level interfaces are tested first and most often.
3. The top-level routines provide a natural tests harness for lower-level routines.
4. Errors are localized to the new modules and interfaces that are being added.

Sandwich integration is predominately top-down but bottom-up techniques are used on some
modules and subsystems.

The modules were integrated using sandwich approach.

System testing

System testing is concerned with subtleties in the interfaces, decision logical control
flow, recovery procedures, and throughput, capacity and timing characteristics of the entire
system.

Acceptance testing involves planning and execution of functional tests, performance tests and
stress tests to verify that the implemented system satisfies its requirements. Acceptance tests are
typically performed by the quality assurance and/or customer organization.

Acceptance testing

Acceptance testing involves planning and execution of functional tests, performance tests,
and stress tests in order to demonstrate that the implemented system satisfies its requirements.
In addition to functional and performance tests, stress tests are performed to determine the
limitation of system.

Acceptance tests will incorporate test cases developed during unit testing and integration
testing. Additional test cases are added to achieve the desired level of functional, performance,
and stress testing of the entire system.

7.SYSTEM MAINTENANCE

We may define Software Maintenance by describing four activities that are undertaken after a
program is released for use.

Corrective Maintenance

The first maintenance activity occurs since it is unreasonable to assume that software testing will
uncover all errors in a large software system. The process of includingthe diagnosis and
correction of one or more errors is called corrective maintenance.

Adaptive Maintenance

This activity that contributes to the definition of maintenance occurs since rapidchange is
encountered in every aspect of computing. Therefore, adaptive maintenancemodifies software to
properly interface with the changing environment.

Perfective Maintenance

This activity involves recommendations for new capabilities, modifications to theexisting

functions and general enhancements whenthe software is used. To satisfy theserequests,
perfective maintenance is performed.

Preventive Maintenance
This activity occurs when software is changed to improve further maintainability or reliability. If
the only available element of a Software Configuration is the source code,maintenance activity
begins with the evaluation of the code, often complicated by poor internal documentation. The
subtle characteristics such as program structure, global datastructure, system interfaces and
performance & design constraints are difficult to hand lead are often misinterpreted. The
amounts of changes that are made to the code aredifficult to access.

8.CONCLUSION

The Employee Management Payroll System didn’t automate 100% of their work, but it is really
a good start to computerize everything and entire Detail can be 100% computerized.As far as the
work done so far much care was given about the user friendliness and a verygood interaction
with the end users. The interface are so designed and channeled the userscan never make any
mistake while using the application, for an example while adding new record, user can’t go out
without either saving or canceling the operation, till the timeeither they save or cancel the current
operation all other operations are blocked. There is nochance of making any mistake in the
application.

9.LIMITATIONS AND FURTHER ENHANCEMENTS

Limitations:

 Employee Management and Payroll System is limited to our control. Any change or
modification can be done by us only.
 It is not an online application or system.
  We have not provided any backup system for this.
 The system need to run ms-access on background.

Further Enhancements:

 Search details can be enhanced by detailed identification of searching problems and

rectification steps by company.
 This system is entirely designed for STAND ALONE usage, according to the need of the
customer if needed the same system can be designed with Network facility to handle the
branch activities also.
 To make this system Online and creating data backups.
 Integrated Password management facility can be created.