PAYROLL MANAGEMENT SYSTEM

InkProject Report Submitted to

SOURASHTRA COLLEGE
(Autonomous)
In the partial fulfilment of the requirement for the award of the degree of the
B.sc(computer science) JUNE 2015-APRIL 2018

SUBMITTED BY
K.R.KRISHNA KUMAR(15UCS138)
And
R.H.AMRISH KUMAR(15ucs115)

UNDER THE GUIDENCE OF

Prof.M.S.KRISHNAVENI MSc..Mphil.,

DEPARTMENT OF COMPUTER SCIENCE

SOURASHTRA COLLEGE
(Autonomous)
(AFFLIATED TO MADURAI KAMARAJ UNIVERSITY RE-ACCREDITED BY
NAAC WITH ‘B’ GRADE)
PASUMALAI,MADURAI-625004
2015-2018
 PAYROLL MANAGEMENT SYSTEM

InkProject Report Submitted to

SOURASHTRA COLLEGE
(Autonomous)
In the partial fulfilment of the requirement for the award of the degree of the
B.sc(computer science) JUNE 2015-APRIL 2018

SUBMITTED BY
K.R.KRISHNA KUMAR(15UCS138)
And
R.H.AMRISH KUMAR(15ucs115)

UNDER THE GUIDENCE OF

Prof.M.S.KRISHNAVENI MSc..Mphil.,

DEPARTMENT OF COMPUTER SCIENCE

SOURASHTRA COLLEGE
(Autonomous)
(AFFLIATED TO MADURAI KAMARAJ UNIVERSITY RE-ACCREDITED BY
NAAC WITH ‘B’ GRADE)
PASUMALAI,MADURAI-625004
2015-2018
 DEPARTMENT OF COMPUTER SCIENCE
SOURASHTRA COLLEGE
(Autonomous)
(AFFLIATED TO MADURAI KAMARAJ UNIVERSITY RE-ACCREDITED BY
NAAC WITH ‘B’ GRADE)
PASUMALAI,MADURAI-625004
2015-2018

BONAFIDE CERTIFICATE

Certified that the project entitle “PAYROLL MANAGEMENT SYSTEM”was done

by,K.R.KRISHNA KUMAR(15UCS138)R.H.AMRISH KUMAR(15UCS115) in the
Department of computer science, Sourashtra College under the guidance of
PROF.M.S.KRISHNAVENI.M.sc.,Mphil., Itis submitted in partial fulfillment of
requirement of sourashtra college under the Degree of Bachelor of Science in
Computer Science, during the year JUNE 2015-APRIL 2018.

Internal Guide Head of the Department

Submitted for the VIVA-VOICE examination held in the department of computer

science of Madurai Kamaraj University at Sourashtra College held on ___________.

Internal Examiner External Examiner

DECLARATION

I hereby declare that the project entitled “PAYROLL MANAGEMENT

SYSTEM ” Submitted by us for the award of degree has not formed the basis
for the award of Degree, Diploma, Association, Fellowship of similar titles
and this dissertion was done Independently by us under the guidance of
PROF.M.S.KRISHNAVENI.M.sc.,Mphil., and has not submitted for any
other purpose.

Place: MADURAI Yours sincerly

Date:

K.R.krishnakumar

R.H.Amrishkumar
 ACKNOWLEDGEMENT

We thank our principal Dr.L.P.RAMALINGAM M.COM,M.Phil.,Ph.D., PGDCA.,CGT., for

having given us the prestigious opportunity of being the number of institution.

We wish to express our sincere thanks to

prof.Mr.K.R.THANIKASALAM MCA.,MBA.,M.PhilHead of the department for
permitting us to undertake this project and for his valuable comments and
suggestions.

We convey our sincere thanks and in depth gratitude to our

internal guide Prof.M.S.KRISHNAVENI M.SC.,Mphil., and his motivation and
guidance played a vital role in early completion of the project.

Our wholehearted thanks to all the professor and non-

teaching staffs of our department for their kind co-operation during the project.

Our sincere thanks to guide for his valuable guidance which

lead to the completion of the project

We thank our parents for their constant encouragement and

motivation. We thank our friends for their moral support and informative co-
operation during the strenuous hours.
SI NO CONTENTS

01 Introduction
1. project description
02 System Analysis
a. Existing system
b. Proposed system
03 Feasiblity Study
a. Types of Feasiblity
b. Evalvating feasibility
04 Modules
a.Module description
05 System Requirements
06 Software Description
07 System design
08 Data Flow diagram
09 System Testing & implementation
1. Acceptance Testing
10 Conclusion
PAYROLL MANAGEMENT SYSTEM

ABSTRACT:

Payroll Management System document formally defines about the requirements of the new
proposed theory and it also briefly state about the non-functional and functional requirements. At
the same time it includes a description about the interface that is used by the users as well as the
requirements of the training and documentation. Payroll Management project helps to generate
the rate of salary each month and it is also equipped with a system that can take care of the
attendance of the employee’s in a firm. It keeps a track of the employee’s attendance and on that
basis it generates the monthly salary. It also helps to generate pay slip as well as the summary of
the payroll. The report of the ESI and provident fund is generating by this system. Printout is
also available so that it can be submitted to the department.
Project Description

Payroll Management System, in this proposed system is mainly developed for the purpose of
easy to calculate salary of each employee in the company based on attendance. In this attendance
also done in this application, using employee id or employee name. Employee details also stored
in the database of application any time we retrieve that details. In this application, the
administrator is only authenticated to handle whole company report. The administrator process in
this application is like he/she is authenticate to add, edit, delete and view employee profile, entry
details and attendance calculation, which is used to calculate the monthly salary. It is provided
more security to the company department records. This system is provided computerized
process. Payroll Management project helps to generate the rate of salary each month and it is
also equipped with a system that can take care of the attendance of the employee’s in a firm. It
keeps a track of the employee’s attendance and on that basis it generates the monthly salary. It
also helps to generate pay slip as well as the summary of the payroll. The report of the ESI and
provident fund is generating by this system. Printout is also available so that it can be submitted
to the department.
EXISTING SYSTEM

The existing system is a manual process. In existing system, the whole payroll information and
reports are maintained manually like note i.e. paper work. Sometimes any records are able to
miss. The records are stored in note; so, anyone can able to make any fraud action. It raises more
problems when particular record will be needed and that record is missed. Anyone can able to
stole and modify the records. If any employee is retired within few days or months and it is
comfortable to find the vacancies in company.

DISADVANTAGES:

1. Manual Process

2. The whole records are maintained in note like paper work

3. It raises more problem

4. It is a time consuming process

5. The records are not safe

6. Anyone can able to modify reports

7. Anyone can able to miss use report

PROPOSED SYSTEM

In this proposed system is mainly developed for the purpose of easy to calculate salary of
each employee in the company based on attendance. In this attendance also done in this
application, using employee id or employee name. Employee details also stored in the database
of application any time we retrieve that details. In this application, the administrator is only
authenticated to handle whole company report. The administrator process in this application is
like he/she is authenticate to add, edit, delete and view employee profile, entry details and
attendance calculation, which is used to calculate the monthly salary. It is provided more security
to the company department records. This system is provided computerized process.

ADVANTAGES:

1. Computerized process

2. Easy to maintained reports

3. Easy to handle whole reports

4. It is a trusted and secured process

5. No one can able to modify and miss use the details.

Feasibility Study

The Feasibility study is an analysis of possible alternative solutions to a problem and a

recommendation on the best alternative. It can decide whether a process be carried out by a new
system more efficiently than the existing one. The feasibility study should examine three main
areas; - market issues, - technical and organizational requirements, - financial overview. The
results of this study are used to make a decision whether to proceed with the project, or table it.
If it indeed leads to a project being approved, it will - before the real work of the proposed
project starts - be used to ascertain the likelihood of the project's success.

Content of a Feasibility Study:

Things to be studied in the feasibility study:

1. The present organizational system

2. Stakeholders, users, policies, functions, objectives...
3. Problems with the present system
4. Inconsistencies, inadequacies in functionality, performance...
5. Possible solution alternatives
Sticking with the current system” is always an alternative

1. Different business processes for solving the problems

2. Different levels/types of computerization for the solutions
3. Advantages and disadvantages of the alternatives
TYPES OF FEASIBILITY

The feasibility study includes complete initial analysis of all related system. Therefore the
study must be conducted in a manner that will reflect the operational, economic as well as
technical and scheduling feasibility of the system proposal. These are the four main types of
feasibility study.

Operational

This aspect defines the urgency of the problem and the acceptability of any solution. It shows
if the system is developed, will it be used. The operational study includes people-oriented and
social issues: internal issues, such as manpower problems, labor objections, manager resistance,
organizational conflicts and policies; also external issues, including social acceptability, legal
aspects and government regulations. It takes in consideration whether the current work practices
and procedures support a new system and social factors of how the organizational changes will
affect the working lives of those affected by the system.

Technical

The technical aspect explores—if the project feasibility is within the limits of current
technology and does the technology exist at all, or if it is available within given resource
constraints (i.e., budget, schedule,...). In the technical feasibility the system analyst look between
the requirements of the organization, such as, (I) input device which can enter a large amount of
data in the effective time (II) Output devices which can produce output in a bulk in an effective
time (III) The choice of processing unit depends upon the type of processing required in the
organization.

Schedule Feasibility

Given his technical expertise, the analyst should determine if the project deadlines are
reasonable whether constraints placed on the project schedule can be reasonably met. Some
projects are initiated with specific deadlines. You need to determine whether the deadlines are
mandatory or desirable. If the deadlines are desirable rather than mandatory, the analyst can
propose alternative schedules.

It is preferable (unless the deadline is absolutely mandatory) to deliver a properly functioning

information system two months late than to deliver an error-prone, useless information system on
time! Missed schedules are bad, but inadequate systems are worse! We may have the technology,
but that doesn't mean we have the skills required to properly apply that technology. True, all
information systems professionals can learn new technologies. However, that learning curve will
impact the technical feasibility of the project, specifically, it will impact the schedule.
Economic Feasibility

The bottom line in many projects is economic feasibility. During the early phases of the
project, economic feasibility analysis amounts to little more than judging whether the possible
benefits of solving the problem are worthwhile. As soon as specific requirements and solutions
have been identified, the analyst can weigh the costs and benefits of each alternative. This is
called a cost-benefit analysis.

EVALUATING THE FEASIBILITY STUDY

The feasibility study is germane to the determination of whether there should be any
further plans: The conclusion might be, “We’ve looked at the proposal thoroughly, and have
concluded that it does not profitably serve our needs in the foreseeable future.” But if the
conclusions of the study are positive, it should provide you with a clear understanding of what
the implementation plan entails in terms of change, cost, benefit, risk, and time. The feasibility
study them serves two functions:

1. The study makes the case for funding the implementation project
2. The outputs of the study provide the inputs for the implementation plan
MODULES:

1. Substantiate Practice Module

2. Employee Process Module

3. Salary Practice Module

4. Report Process Module

MODULE DESCRIPTION:

Substantiate Practice Module:

The Substantiate Practice Module is credentials provided are compared to those on file in a
database of authorized user’s information on a local operating system or within an authentication
server. If the admin credentials match, the process is completed; admin is granted authorization
for access. Using username and password admin login is checked if username and password will
be match to database record it will be allow accessing the application otherwise it will display
the alert message box on the screen

Employee Process Module:

This Employee Process Module (or) Particularization Module is indicating employee related
information. The administrator can update each employee’s details using employee id when
occurs modification in employee phase. This id is automatically generated when the employee
details will be entering in employee phase. The administrator is only authenticated to add,
update, delete and view employee’s details in and from this application. The employee’s details
are stored in database; so, the administrator is easily retrieved any details from database. The
added fields are in the employee details phase like employee name, qualification, contact details,
address, date of birth and gender.

Salary Practice Module:

Salary Practice Module is based on the company attendance in particular month, if any employee
took leave at office working day it will be a loss of pay in that month salary. Attendance is
calculated by this application. In this application salary increment process also done by admin
increment amount also mentioned at an employee registration process, employee salary
increment based on the employee date of join in the office and performance of work status.
Report Process Module:

In This Report Process Module is used to defines the process of manage and view reports.
This system is also providing the facility to the report view like attendance based report, Salary
based Report. The administrator is authenticating person to view mange and view report. The
reports are so secured. This system is provides graphical representation for each record. These
reports are used to manage and view details about particular employee and salary
SYSTEM REQUIREMENTS:

Software Requirements:

Front End           : PHP (JDK 1.8, NETBEANS 8.0)

Back End      : My SQL

O/ S                  : Windows 7 (Ultimate X-86[32 bit])

Database : Wampserver2.0

Hardware Requirements:

     Processor             : PIV MHz Or Above

      RAM                  : 1 GB

      Hard Disk            : 60 GB Minimum

SOFTWARE DESCRIPTION

PHP:

PHP is a general-purpose server-side scripting language originally designed for Web

development to produce dynamic Web pages. It is one of the first developed server-side scripting
languages to be embedded into an HTML source document rather than calling an external file to
process data. The code is interpreted by a Web server with a PHP processor module which
generates the resulting Web page. It also has evolved to include a command-line
interface capability and can be used in standalone graphical applications. PHP can be deployed
on most Web servers and also as a standalone shell on almost every operating
system and platform free of charge. 

A competitor to Microsoft's Active Server Pages (ASP) server-side script engine and

similar languages, PHP is installed on more than 20 million Web sites and 1 million Web
servers. Software that uses PHP includes Media Wiki, Joomla, Word press, Concrete5, My BB,
and Drupal. PHP was originally created by Rasmus Lerdorf in 1995. The main implementation
of PHP is now produced by The PHP Group and serves as the formal reference to the PHP
language. PHP is free software released under the PHP License, which is incompatible with
the GNU General Public License (GPL) due to restrictions on the usage of the term PHP. While
PHP originally stood for Personal Home Page, it is now said to stand for PHP: Hypertext
Preprocessor, a recursive acronym.

Usage:

PHP is a general-purpose scripting language that is especially suited to server-side web

development where PHP generally runs on a web server. Any PHP code in a requested file
is executed by the PHP runtime, usually to create dynamic web page content or dynamic images
used on Web sites or elsewhere. It can also be used for command-line scripting and client
side graphical user interface (GUI) applications. PHP can be deployed on most Web servers,
many operating systems and platforms, and can be used with many relational database
management systems (RDBMS). It is available free of charge, and the PHP Group provides the
complete source code for users to build, customize and extend for their own use.
 PHP acts primarily as a filter, taking input from a file or stream containing text and/or
PHP instructions and outputting another stream of data; most commonly the output will be
HTML. Since PHP 4, the PHP parser compiles input to produce byte code for processing by the
Zend Engine, giving improved performance over its interpreter predecessor.

Originally designed to create dynamic Web pages, PHP now focuses mainly on  server-
side scripting, and it is similar to other server-side scripting languages that provide dynamic
content from a Web server to a client, such as Microsoft's ASP.NET, Sun Microsystems' Java
Server Pages, and mod_perl. PHP has also attracted the development of many frameworks that
provide building blocks and a design structure to promote rapid application development (RAD).
Some of these include Cake PHP, Symfony, Code Igniter, Yii Framework, and Zend Framework,
offering features similar to other web application frameworks.

Security:

About 30% of all vulnerabilities listed on the  National Vulnerability Database are

linked to PHP.  These vulnerabilities are caused mostly by not following best practice
programming rules: technical security flaws of the language itself or of its core libraries are not
frequent (23 in 2008, about 1% of the total). Recognizing that programmers make mistakes,
some languages include taint checking to detect automatically the lack of input validation which
induces many issues. Such a feature is being developed for PHP, but its inclusion in a release has
been rejected several times in the past.

Syntax:

The PHP interpreter only executes PHP code within its delimiters. Anything outside its
delimiters is not processed by PHP (although non-PHP text is still subject to control
structures described in PHP code). The most common delimiters are <? Php to open and?> to
close PHP sections. <script language="php"> and </script> delimiters are also available, as are
the shortened forms <? or <?= (which is used to echo back a string or variable) and ?> as well
as ASP-style short forms <% or <%= and %>. While short delimiters are used, they make script
files less portable as support for them can be disabled in the PHP configuration, and so they are
discouraged. The purpose of all these delimiters is to separate PHP code from non-PHP code,
including HTML.
 The first form of delimiters, <?php and ?>, in XHTML and other XML documents,
creates correctly formed XML 'processing instructions'. This means that the resulting mixture of
PHP code and other markup in the server-side file is itself well-formed XML.

Variables are prefixed with a dollar symbol, and a type does not need to be specified in
advance. Unlike function and class names, variable names are case sensitive. Both double-quoted
("") and here doc strings provide the ability to interpolate a variable's value into the string. PHP
treats newlines as whitespace in the manner of a free-form language (except when inside string
quotes), and statements are terminated by a semicolon. 

PHP has three types of comment syntax: /* */ marks block and inline comments; // as
well as #are used for one-line comments. The echo statement is one of several facilities PHP
provides to output text, e.g., to a Web browser.

Speed Optimization:

PHP source code is compiled on-the-fly to an internal format that can be executed by

the PHP engine. In order to speed up execution time and not have to compile the PHP source
code every time the Web page is accessed, PHP scripts can also be deployed in executable
format using a PHP compiler.

Code optimizers aim to enhance the performance of the compiled code by reducing its
size, merging redundant instructions and making other changes that can reduce the execution
time. With PHP, there are often opportunities for code optimization. An example of a code
optimizer is the accelerator PHP extension.

Another approach for reducing compilation overhead for PHP servers is using an  op
code cache. Op code caches work by caching the compiled form of a PHP script (op codes)
in shared memory to avoid the overhead of parsing and compiling the code every time the script
runs. An op code cache, APC, is planned to be built into an upcoming release of PHP. Op code
caching and code optimization can be combined for best efficiency, as the modifications do not
depend on each other (they happen in distinct stages of the compilation).
Compiler:

The PHP language was originally implemented as an interpreter. Several compilers have been
developed which decouple the PHP language from the interpreter. Advantages of compilation
include better execution speed, static analysis, and improved interoperability with code written in
other languages. PHP compilers of note include Phalanger, which compiles PHP into Common
Intermediate Language (CIL) byte-code, and Hip-hop, developed at Face book and now available
as open source, which transforms the PHP Script into C++, then compiles it, reducing server load
up to 50%.

HTML:

Hyper Text Markup Language (HTML) is the main markup language for displaying

web pages and other information that can be displayed in a web browser. HTML is written in the
form of HTML elements consisting of tags enclosed in angle brackets (like <html>), within the
web page content. HTML tags most commonly come in pairs like<h1> and </h1>, although
some tags, known as empty elements, are unpaired, for example<img>. The first tag in a pair is
the start tag, the second tag is the end tag (they are also called opening tags and closing tags). In
between these tags web designers can add text, tags, comments and other types of text-based
content.

The purpose of a web browser is to read HTML documents and compose them into visible
or audible web pages. The browser does not display the HTML tags, but uses the tags to interpret
the content of the page.

HTML elements form the building blocks of all websites. HTML allows images and
objects to be embedded and can be used to create interactive forms. It provides a means to create
structured by denoting structural semantics for text such as headings, paragraphs, lists, links,
quotes and other items. It can embed scripts in languages such as JavaScript which affect the
behavior of HTML Webpages.

Web browsers can also refer to Cascading Style Sheets (CSS) to define the appearance
and layout of text and other material. The W3C, maintainer of both the HTML and the CSS
standards, encourages the use of CSS over explicit presentational HTML markup.
Data types:

HTML defines several data types for element content, such as script data and style sheet
data, and a plethora of types for attribute values, including IDs, names, URIs, numbers, units of
length, languages, media descriptors, colors, character encodings, dates and times, and so on. All
of these data types are specializations of character data.

Html Application:
An HTML Application (HTA; file extension ".hta") is a  Microsoft Windows application
that uses HTML and Dynamic HTML in a browser to provide the application's graphical
interface. A regular HTML file is confined to the security model of the web browser's security,
communicating only to web servers and manipulating only webpage objects and site cookies.
An HTA runs as a fully trusted application and therefore has more privileges, like
creation/editing/removal of files and Windows Registry entries. Because they operate outside the
browser's security model, HTAs cannot be executed via HTTP, but must be downloaded (just like
an EXE file) and executed from local file system.
MYSQL:

My SQL is the world's most used open source relational database management system

(RDBMS)as of 2008 that run as a server providing multi-user access to a number of databases. It
is named after co-founder Michael Widenius' daughter, my. The SQL phrase stands for
Structured Query Language.

The My SQL development project has made its source code available under the terms of
the GNU, as well as under a variety of proprietary agreements. My SQL was owned and
sponsored by a single for-profit firm, the Swedish company My SQL AB, now owned by Oracle
Corporation.

My SQL is a popular choice of database for use in web applications, and is a central
component of the widely used LAMP open source web application software stack—LAMP is an
acronym for "Linux, Apache, My SQL, Perl/PHP/Python." Free-software-open source projects
that require a full-featured database management system often use My SQL.

Programming:

My SQL works on many different system platforms, including AIX, BSDi, FreeBSD, HP-

UX, eComStation, i5/OS, IRIX, Linux, Mac OS X,Microsoft Windows, NetBSD, Novell
NetWare, OpenBSD, OpenSolaris, OS/2 Warp, QNX, Solaris, Symbian, SunOS, SCO Open
Server, SCO UnixWare, Sanos and Tru64. A port of My SQL to OpenVMS also exists. My SQL
is written in C and C++. Its SQL parser is written in yacc, and a home-brewed lexical analyzer. 

Many programming languages with language specific APIs include libraries for accessing

My SQL databases. These include My SQL Connector/Net for integration with
Microsoft's Visual Studio (languages such as C# and VB are most commonly used) and the
JDBC driver for Java. In addition, an ODBC interface called My ODBC allows additional
programming languages that support the ODBC interface to communicate with a My SQL
database, such as ASP or ColdFusion. The HTSQL - URL-based query method also ships with a
My SQL adapter, allowing direct interaction between a My SQL database and any web client via
structured URLs.
Features:

1. A broad subset of ANSI SQL 99, as well as extensions

2. Cross-platform support
3. Stored procedures
4. Triggers
5. Cursors
6. Updatable Views
7. Information schema
8. Strict mode (ensures My SQL does not truncate or otherwise modify data to conform to
an underlying data type, when an incompatible value is inserted into that type)
9. X/Open XA distributed transaction processing (DTP) support; two phase commit as part
of this, using Oracle's Inno DB engine
10. Independent storage engines (My ISAM for read speed, Inno DB for transactions
and referential integrity, My SQL Archive for storing historical data in little space)
11. Transactions with the Inno DB, and Cluster storage engines; save points with Inno DB
12. SSL support
13. Query caching
14. Sub-SELECTs (i.e. nested SELECTs)
15. Replication support (i.e. Master-Master Replication & Master-Slave Replication) with
one master per slave, many slaves per master, no automatic support for multiple masters
per slave.
16. Full-text indexing and searching using My ISAM engine
17. Embedded database library
18. Unicode support (however prior to 5.5.3 UTF-8 and UCS-2 encoded strings are limited to
the BMP, in 5.5.3 and later use utf8mb4 for full Unicode support)
19. ACID compliance when using transaction capable storage engines (Inno DB and Cluster)
20. Partitioned tables with pruning of partitions in optimizer
21. Shared-nothing clustering through My SQL Cluster
22. Hot backup (via My SQL hot copy) under certain conditions
23. Multiple storage engines, allowing one to choose the one that is most effective for each
table in the application (in My SQL 5.0, storage engines must be compiled in; in My SQL
5.1, storage engines can be dynamically loaded at run time).
SYSTEM DESIGN
The most creative and challenging phase of the system design. It is a “how to” approach to
the creation of the proposed system. It refers to the technical specification that will apply. It
provides the understanding and procedural details necessary for implementing the system
recommended in the feasibility study.

INPUT DESIGN:
Input design is the process of covering user oriented inputs to computer based format.
It also includes determining the record media, method of input, speed of capture and entry into
the system.

TYPES OF INPUT:

1. Flexibility of format

2. Speed

3. Accuracy

4. Verifications of methods

5. Rejection rates

6. Ease of correction

7. Offline facilities

8. Need for specialized documentation

9. Storage and handling requirements

10. Automatic features

11. Security

12. Easy to use

13. Environment of data captures portability

 14. Compatibility with other system

15. Cost etc.,

Keyboard & mouse may be used as the input media. Inaccurate input data are the most
common cause of the errors in data processing. Errors entered by user can control by the input
design. With the reference to my project port no, is given as input.

OUTPUT DESIGN:

The normal procedure is to design the output in detail first and then to work back to the inputs.
The outputs can be in the form of operational documents, lengthy reports, and the input records
have to be validated, edited, organized and accepted by the system before being processed to
produce the output may have been define.

TYPES OF OUTPUT:
1. Content

2. Format

3. Location

4. Frequency

5. Response

6. Volume

7. Sequence

8. Action

9. Action required

The next stage is to determine the most appropriate medium for output consideration will be:

Suitability of the device to particular application

1. The need for hard copy

2. The response time required

3. The location of the user

4. The software/hardware available cost

With reference to my project, outputs are taken in the form of report.

DATA FLOW DIAGRAM

1. The DFD is also called as bubble chart. It is a simple graphical formalism that can be
used to represent a system in terms of input data to the system, various processing carried
out on this data, and the output data is generated by this system.
2. The data flow diagram (DFD) is one of the most important modeling tools. It is used to
model the system components. These components are the system process, the data used
by the process, an external entity that interacts with the system and the information flows
in the system.
3. DFD shows how the information moves through the system and how it is modified by a
series of transformations. It is a graphical technique that depicts information flow and the
transformations that are applied as data moves from input to output.
4. DFD is also known as bubble chart. A DFD may be used to represent a system at any
level of abstraction. DFD may be partitioned into levels that represent increasing
information flow and functional detail.
DFD SYMBOLS:

In the DFD, there are four symbols

1. A square defines a source(originator) or destination of system data

2. An arrow identifies data flow. It is the pipeline through which the information flows
3. A circle or a bubble represents a process that transforms incoming data flow into
outgoing data flows.
4. An open rectangle is a data store, data at rest or a temporary repository of data

Process that transforms data flow.

 Source or Destination of data

Data flow

DFD

Level 1: Administration Process

Start

Home – Admin Process

If Incorrect
Login Process

If Correct

Admin Home
j
Add, Edit, View, and Delete

Attendance Info

Register Emp Info

 Employee List

Salary Info

Employee Reports

Logout

End

SYSTEM IMPLEMENTATION

Implementation is an activity that brings the developed system into operational use and
turning it over to the user. The changeover from the old to the new system can be arranged once
the computer system is tested and approved. The most important phase in software life cycle is
project implementation. The major work involved in the implementation phase is coding. After
conducting feasibility, analysis design, and the information collected from detailed study will
way but for the implementation part. As when the system is operated manually, the system is not
operated in efficient manner, the system finds lot of drawbacks, in order to overcome these
difficulties, In order to function the system efficiently, the system is subjected to
computerization. Lot of man power was spend, when the system is operated manually, the
system this involves more money in maintaining the system.

Difficulty in maintaining records, each very time a separate ledger should be maintained
for the transaction purposes and its more time consuming where the efficiency of the system is
lost and also there is no proper security in order to maintain the data and which involves Data
Redundancy leads to data inconsistency, all these problems can be solved while going for
computerized system, the computerized system will discard all human errors as said above and
which maintains accuracy and which increases the efficiency of the system for faster
transactions. Implementation is that stage in the project where the theoretical design ids turned
into a network system.

The first task in implementation is deciding on the method and time scale to be adopted.
The major effort is to ensure that the programs in the system are working properly. The most
important phase in software lifecycle is project implementation. The major work involved in the
implementation phase is coding. After conducting a feasibility study, analysis, design, the
information collected from detailed study will way out for the implementation part. As when the
system is operated manually, the system is not operated in efficient manner, the system finds lot
of drawbacks, in order to overcome these difficulties, in order to function the system efficiently,
the system is operated manually, the system requires lot of man power, and consumes lot time to
handle the transactions, this involves more in maintaining the system.

System implementation is the practice of creating or modifying a system to create a new

business process or replace an existing business process. Technology integration is the practice
of integrating multiple system activities to interact and generate information efficiently. In both
cases, the system development lifecycle (SDLC) is heavily integrated in these practices. A CPA
professional may be involved in designing a system, performing end-user testing, or training
others how to utilize the financial system.

The purpose of System Implementation can be summarized as follows: making the new
system available to a prepared set of users (the deployment), and positioning on-going support
and maintenance of the system within the Performing Organization (the transition). At a finer
level of detail, deploying the system consists of executing all steps necessary to educate the
Consumers on the use of the new system, placing the newly developed system into production,
confirming that all data required at the start of operations is available and accurate, and
validating that business functions that interact with the system are functioning properly.
Transitioning the system support responsibilities involves changing from a system development
to a system support and maintenance mode of operation, with ownership of the new system
moving from the Project Team to the Performing Organization. A key difference between
System Implementation and all other phases of the lifecycle is that all project activities up to this
point have been performed in safe, protected, and secure environments, where project issues that
arise have little or no impact on day-to-day business operations. Once the system goes live,
however, this is no longer the case. Any miscues at this point will almost certainly translate into
direct operational and/or financial impacts on the Performing Organization. It is through the
careful planning, execution, and management of System Implementation activities that the
Project Team can minimize the likelihood of these occurrences, and determine appropriate
contingency plans in the event of a problem.

LIST OF PROCESSES:

This phase consists of the following processes:

_ Prepare for System Implementation, where all steps needed in advance of actually deploying
the application are performed, including preparation of both the production environment and the
Consumer communities.
_ Deploy System, where the full deployment plan, initially developed during System Design and
evolved throughout subsequent lifecycle phases, is executed and validated.
_ Transition to Performing Organization, where responsibility for and ownership of the
application are transitioned from the Project Team to the unit in the Performing Organization that
will provide system support and maintenance.
SYSTEM TESTING

Testing is a process of executing a program with the intent of finding an error.

Testing is a crucial element of software quality assurance and presents ultimate review of
specification, design and coding.

System Testing is an important phase. Testing represents an interesting anomaly for

the software. Thus a series of testing are performed for the proposed system before the system is
ready for user acceptance testing.

A good test case is one that has a high probability of finding an as undiscovered
error. A successful test is one that uncovers an as undiscovered error.

Testing Objectives:
1. Testing is a process of executing a program with the intent of finding an error
2. A good test case is one that has a probability of finding an as yet undiscovered error
3. A successful test is one that uncovers an undiscovered error

Testing Principles:

1. All tests should be traceable to end user requirements

2. Tests should be planned long before testing begins
3. Testing should begin on a small scale and progress towards testing in large
4. Exhaustive testing is not possible
5. To be most effective testing should be conducted by a independent third party

The primary objective for test case design is to derive a set of tests that has the highest
livelihood for uncovering defects in software. To accomplish this objective two different
categories of test case design techniques are used. They are

1. White box testing.

2. Black box testing.

WHITE-BOX TESTING:

White box testing is focus on the program control structure. Test cases are derived to ensure
that all statements in the program have been executed at least once during testing and that all logical
conditions have been executed.

BLOCK-BOX TESTING:

Black box testing is designed to validate functional requirements without regard to the
internal workings of a program. Black box testing mainly focuses on the information domain of
the software, deriving test cases by partitioning input and output in a manner that provides
through test coverage. Incorrect and missing functions, interface errors, errors in data structures,
error in functional logic are the errors falling in this category.
TESTING STRATEGIES:

A strategy for software testing must accommodate low-level tests that are necessary to verify
that all small source code segments has been correctly implemented as well as high-level tests that
validate major system functions against customer requirements.

TESTING FUNDAMENTALS:

Testing is a process of executing program with the intent of finding error. A good test
case is one that has high probability of finding an undiscovered error. If testing is conducted
successfully it uncovers the errors in the software. Testing cannot show the absence of defects, it
can only show that software defects present.

TESTING INFORMATION FLOW:

Information flow for testing flows the pattern. Two class of input provided to test the
process. The software configuration includes a software requirements specification, a design
specification and source code.

Test configuration includes test plan and test cases and test tools. Tests are conducted and
all the results are evaluated. That is test results are compared with expected results. When
erroneous data are uncovered, an error is implied and debugging commences.

UNIT TESTING:

Unit testing is essential for the verification of the code produced during the coding phase
and hence the goal is to test the internal logic of the modules. Using the detailed design
description as a guide, important paths are tested to uncover errors with in the boundary of the
modules. These tests were carried out during the programming stage itself. All units of Vienna
SQL were successfully tested.

INTEGRATION TESTING:
 Integration testing focuses on unit tested modules and build the program structure that is
dictated by the design phase.

System testing:

System testing tests the integration of each module in the system. It also tests to find
discrepancies between the system and it’s original objective, current specification and system
documentation. The primary concern is the compatibility of individual modules. Entire system is
working properly or not will be tested here, and specified path ODBC connection will correct or
not, and giving output or not are tested here these verifications and validations are done by
giving input values to the system and by comparing with expected output. Top-down testing
implementing here.

ACCEPTANCE TESTING:

This testing is done to verify the readiness of the system for the implementation. Acceptance
testing begins when the system is complete. Its purpose is to provide the end user with the
confidence that the system is ready for use. It involves planning and execution of functional
tests, performance tests and stress tests in order to demonstrate that the implemented system
satisfies its requirements.

Tools to special importance during acceptance testing include:

Test coverage Analyzer – records the control paths followed for each test case.

Timing Analyzer – also called a profiler, reports the time spent in various regions of the code are
areas to concentrate on to improve system performance.

Coding standards – static analyzers and standard checkers are used to inspect code for deviations
from standards and guidelines.

TEST CASES:

Test cases are derived to ensure that all statements in the program have been executed at least
once during testing and that all logical conditions have been executed.

Using White-Box testing methods, the software engineer can drive test cases that
1. Guarantee that logical decisions on their true and false sides.
2. Exercise all logical decisions on their true and false sides.
3. Execute all loops at their boundaries and within their operational bounds.
4. Exercise internal data structure to assure their validity.
The test case specification for system testing has to be submitted for review before system
testing commences.

CONCLUSION:

In this proposed system is mainly developed for the purpose of easy to calculate salary of each
employee in the company based on attendance. In this application, the administrator is only
authenticated to handle whole company report. The administrator process in this application is
like he/she is authenticate to add, edit, delete and view employee profile, entry details and
attendance calculation, which is used to calculate the monthly salary. It is provided more security
to the company department records. This system is provided computerized process.
REFERENCE:

[1] Jannyl Darren A. Villarama; John Paul Raphael O. Gernale; Don Airon N. Ocampo; Jocelyn
Flores Villaverde,"Wireless biometrie attendance management and payroll system",2017IEEE
9th International Conference on Humanoid, Information Technology, Year: 2017,Pages: 1 - 5

[2] Benfano Soewito; Fergyanto E. Gunawan; Manik Hapsara."Smartphone for next generation
attendance system and human resources payroll system",2017 4th International Conference on
Electrical Engineering, Computer Science and Informatics (EECSI),Year: 2017,Pages: 1 - 6

[3] Evelio Hernández Pascual,"Continuous auditing to manage risks in payroll",2016 11th

Iberian Conference on Information Systems and Technologies (CISTI),Year: 2016,Pages: 1 - 6

[4] Monika Arora; Deepankar Chakrabarti,"Application of Business Intelligence: A Case on

Payroll Management",2013 International Symposium on Computational and Business
Intelligence,Year: 2013,Pages: 73 – 76

[5] Y. C. Lee and A. Y. Zomaya, “Energy efficient utilization of resources in cloud computing
systems,” J. Supercomput., vol. 60, no. 2, pp. 268–280, 2012.

[6] A. Beloglazov, R. Buyya, Y. C. Lee, and A. Zomaya, “A taxonomy and survey of energy-
efficient data centers and cloud computing systems,” Adv. Comput., vol. 82, pp. 47–111, 2011.
[7] R. Buyya, C. S. Yeo, S. Venugopal, J. Broberg, and I. Brandic, “Cloud computing and
emerging IT platforms: Vision, hype, and reality for delivering computing as the 5th utility,”
Future Generation Comput. Syst., vol. 25, no. 6, pp. 599–616, 2009.

[8] L. Wang, G. Von Laszewski, A. Younge, X. He, M. Kunze, J. Tao, and C. Fu, “Cloud
computing: A perspective study,” New Generation Comput., vol. 28, no. 2, pp. 137–146, 2010.

[9] R. Ranjan, R. Buyya, and M. Parashar, “Special section on autonomic cloud computing:
Technologies, services, and applications,” Concurrency Comput.: Practice Exp., vol. 24, no. 9,
pp. 935–937, 2012.

[10] M. Yadin and P. Naor, “Queueing systems with a removable service station,” Operations
Res., vol . 14, pp. 393–405, 1963.

Table Structure

Attendance_system(database)

attendance(table)

SERIAL NO FIELD NAME DATATYPE DESCRIPTION

1 AttIDIprimary key) int(20) Attendance id details

2 EmpID int(10) Employee id details

3 Prensent int(1) Employee present details

4 AttDate date Attendance date details

Employee_detail(table)

SERIAL NO FIELD NAME DATATYPE DESCRIPTION

1 EmpID(primary key) int(10) Employee id details

2 EmpName varchar(255) Employee name details

3 EmpAddress text Employee address details

4 EmpMobile varchar(15) Employee mobile details

5 EmpEmail varchar(50) Employee email details

6 EmpBirthdate date Employee birth date details

7 EmpBloodGroup varchar(5) Employee blood group details

8 EmpTechnology varchar(20) Employee technoology details

Incremental_detail(table name)

SERIAL NO FIELD NAME DATATYPE DESCRIPTION

1 IncID(primary key) int(20) Increment Id details

2 EmpID int(20) Employee id details

3 Salary int(20) Salary details

4 IncrementDate date Increment details

salary_detail(table name)

SERIAL NO FIELD NAME DATATYPE DESCRIPTION

1 SalaryID(primary key) int(20) Salary id details

2 EmpID int(20) Employee id details

3 JoinDate date Join date details

4 EmpType varchar(20) Employee type details

5 CurrentSalary int(10) Current salary details

6 IncrementAmount int(10) Increment amount details

7 IncrementAfter int(5) Increment after details

8 IncrementDate date Increment date details

9 LastSalary int(10) Last salary details

10 LastIncrement date Last increment details

users(Table name)

SERIAL NO FIELD NAME DATATYPE DESCRIPTION

1 UserID(primary key) int(10) User id details

2 UserName varchar(50) User name details

3 Password varchar(50) User password details

Screen Shot

Run the project->payroll

Admin login username=admin and password =admin

Continue…..

Click add_attendance
Continue…..

Click employee register

Continue…..

Continue…..
Emp_list

Click salary detail

Edit employee details

Continue…..
Delete employee module

Continue…..
Emp reports module

Continue…..
Continue…..

Continue…..
Sample Coding:
index.php

<?php

require_once '../../library/config.php';

require_once '../library/functions.php';

$_SESSION['login_return_url'] = $_SERVER['REQUEST_URI'];

checkAdmin();

$view = (isset($_GET['view']) && $_GET['view'] != '') ? $_GET['view'] : '';

switch ($view) {

case 'detail' :

$content = 'detail.php';

$pageTitle = 'View Account Detail';

break;

case 'statement' :

$content = 'statement.php';

$pageTitle = 'View Account statement';

break;

default :

$content = 'list.php';

$pageTitle = 'View Account details';

}
$script = array('user.js','jquery.min.js');

require_once '../include/template.php';

?>

Detail.php

<?php

if (isset($_GET['accId']) && $_GET['accId'] > 0) {

$accId = $_GET['accId'];

} else {

header('Location: index.php');

$sql = "SELECT u.id, u.fname, u.lname, u.bdate, u.is_active, u.email, u.phone, u.pics,

a.acc_no, a.type, a.balance,

ad.address, ad.city, ad.state, ad.zipcode

FROM tbl_users u, tbl_accounts a, tbl_address ad

WHERE u.id = a.user_id AND ad.user_id = u.id

AND a.id = $accId";

$result = mysql_query($sql) or die('Cannot get product. ' . mysql_error());

$row = mysql_fetch_assoc($result);

extract($row);

$atype = "";

if($type == "CA"){$atype = "Checking Account";}

else if($type == "SA") {$atype = "Saving Account";}

else if($type == "FDA") {$atype = "Fixed deposit Account";}

?>

<p align="center" id="mainHead">User Details</p>

<form action="process.php?action=transaction" method="post" id="frmTransaction">

<table width="100%" border="0" align="center" cellpadding="5" cellspacing="1"

class="entryTable">

<tr>

<td width="150" class="label">Account Holder Name</td>

<td class="content"><?php echo strtoupper( $fname. ' '. $lname); ?>&nbsp;<br/><br/>

Email:&nbsp;<a href="mailto:<?php echo $email; ?>"><?php echo $email; ?></a>

&nbsp;[&nbsp;<a href="admin/user/?view=email&userId=<?php echo $id; ?>">Edit

Email</a>&nbsp;]<br/><br/>

Phone:&nbsp;<?php echo $phone; ?></td>

<td rowspan="3" class="content">

<?php

$upics = (isset($pics) && $pics != "") ? "thumbnails/".$pics : "anonymous-user.jpg";

?>

<img src="images/<?php echo $upics; ?>" style="float:right;" width="180" height="180" />

</td>

</tr>

<tr>
<td width="150" class="label">Address</td>

<td class="content"><?php echo $address; ?><br/>

<?php echo $city; ?><br/>

<?php echo $zipcode; ?>&nbsp;<?php echo $state; ?></td>

</tr>

<tr>

<td width="150" class="label">Account Number</td>

<td class="content"><strong><?php echo $acc_no; ?></strong>&nbsp;&nbsp;(<?php echo

$atype; ?>)

<input type="hidden" name="user_id" value="<?php echo $id; ?>" />

<input type="hidden" name="acc_no" value="<?php echo $acc_no; ?>" />

</td>

</tr>

<tr>

<td width="150" class="label">Current Balance</td>

<td colspan="2" class="content">Balance:&nbsp;$&nbsp;<?php echo $balance; ?></td>

</tr>

<tr>

<td width="150" class="label">Transaction History</td>

<td colspan="2" class="content">

<a href="admin/account/?view=statement&accNo=<?php echo $acc_no; ?>">View Transaction

History</a>
</td>

</tr>

<tr>

<td width="150" class="label">Transaction Type</td>

<td colspan="2" class="content">

<select name="type" id="type">

<option value="#"> -- select transaction type --</option>

<option value="credit">Credit Fund</option>

<option value="debit">Debit Fund</option>

</select>

</td>

</tr>

<tr>

<td width="150" class="label">Amount</td>

<td colspan="2" class="content"><input type="text" name="amt" id="amt" size="10" /></td>

</tr>

<tr>

<td width="150" class="label">Date of Transfer</td>

<td colspan="2" class="content"><input type="text" name="dot" id="dot" size="20" />&nbsp;

(Format: mm/dd/yyyy)</td>

</tr>
<tr>

<td width="150" class="label">Transfer Description</td>

<td colspan="2" class="content"><textarea name="desc" id="desc" cols="35"

rows="2"></textarea></td>

</tr>

</table>

<p align="center">

&nbsp;&nbsp;

<input name="btnBack" type="button" id="btnBack" value=" Back "

onClick="window.history.back();">

&nbsp;&nbsp;

<input name="btnTxType" type="button" id="btnTxType" value=" Proceed Transaction ">

</p>

</form>

<script language="javascript">

$(document).ready(function(){

var format = function(num){

var str = num.toString().replace("$", ""), parts = false, output = [], i = 1, formatted = null;

if(str.indexOf(".") > 0) {

parts = str.split(".");

str = parts[0];

}
str = str.split("").reverse();

for(var j = 0, len = str.length; j < len; j++) {

if(str[j] != ",") {

output.push(str[j]);

if(i%3 == 0 && j < (len - 1)) {

output.push(",");

i++;

formatted = output.reverse().join("");

return("$" + formatted + ((parts) ? "." + parts[1].substr(0, 2) : ""));

};

var isDate = function(txtDate) {

var currVal = txtDate;

if(currVal == '') return false;

var rxDatePattern = /^(\d{1,2})(\/|-)(\d{1,2})(\/|-)(\d{4})$/; //Declare Regex

var dtArray = currVal.match(rxDatePattern); // is format OK?

if (dtArray == null) return false;

//Checks for mm/dd/yyyy format.

dtMonth = dtArray[1];
dtDay= dtArray[3];

dtYear = dtArray[5];

if (dtMonth < 1 || dtMonth > 12) return false;

else if (dtDay < 1 || dtDay> 31) return false;

else if ((dtMonth==4 || dtMonth==6 || dtMonth==9 || dtMonth==11) && dtDay ==31)

return false;

else if (dtMonth == 2)

var isleap = (dtYear % 4 == 0 && (dtYear % 100 != 0 || dtYear % 400 == 0));

if (dtDay> 29 || (dtDay ==29 && !isleap)) return false;

return true;

};

$('#amt').keyup(function(e){

$(this).val(format($(this).val()));

});

$('#btnTxType').click(function() {

var ttype = $("#type").val();

if(ttype == '#') {

alert('Select Transaction Type');

$("#type").focus();
return false;

var amt = $("#amt").val();

if(amt == '') {

alert('Please insert transaction amount.');

$("#amt").focus();

return;

/*

if($.isNaN(amt)) {

alert('Invalid amount. Please insert amount as integer.');

$("#amt").focus();

return;

*/

var dot = $("#dot").val();

if(dot == '') {

alert('Please insert Date of Transaction.');

$("#dot").focus();

return;

}
if(!isDate(dot)) {

alert('Invalid Date.');

$("#dot").focus();

return;

var desc = $("#desc").val();

if(desc == '') {

alert('Please insert transaction description.');

$("#desc").focus();

return;

$('#frmTransaction').submit();

});

});//ready

</script>