employee management

A

ON

Submitted in partial fulfillment of the requirement for the award of Degree of

BACHELOR OF COMPUTER APPLICATION (BCA)

SUBMITTED TO

Department of Computer Science

SUBMITTED TO

SUBMITTED BY Mr.Parmod Kumar

Sachin Kumar (8551214)

Vikas Kumar (8551281)

Alam Rana (8551296)SUBMITTED ATSHRI RAM COLLEGE MUZAFFARNAGAR

I would like to take this opportunity to express my gratitude towards all the people who have in various ways, helped in the successful completion of my project.

I must convey my gratitude to Mr. PARMOD KUMAR for giving us the constant source of inspiration and help in preparing the project, personally correcting my work and providing encouragement throughout the project.

I also thank all my faculty members for steering me through the tough as well as easy phases of the project in a result oriented manner with concern attention. Sachin Kumar (8551214)

Vikas Kumar (8551281) Alam Rana (8551296)

I am the student of BCA 6TH SHRI RAM COLLEGE MUZAFFARNAGAR (AFFILATED TO C.C.S UNIVERSITY MEERUT). Here by declare that the project report on EMPLOYEE MANAGEMENT SYSTEM is our original work.I also declare that have done our work self accurately even then if over mistake or error had kept in. We request to our faculties to points out these error and guide our to remove these error for our future. We are also thankful for our faculties.

Sachin Kumar (8551214)

Vikas Kumar (8551281) Alam Rana (8551296)

This is to certify that the Project Report titled EMPLOYEE MANAGEMENT SYSTEM is the bona fide project work carried out by Mr. Dinesh Kumar students of BCA, SHRI RAM COLLEGE MUZAFFARNAGAR during the year 2010, in partial fulfillment of the requirements for the award of the Degree of Bachelor of Computer Application and that the project report has not formed the basic for the award previously of any degree, diploma or any other similar title.

Place: MUZAFFARNAGAR

Signature of the Guide

Title (cover page) Acknowledgement

Declaration Institute certificate

Contents

Introduction System Objectives Problem Definition Project Analysis

Feasibility study Block diagram

Cost & benefit analysis Project Design

System Analysis

Design Hints & Guidelines

Front end and back end used System evaluation and testing System implementation System Development

System maintenance System documentation

Screen shots Coding

CONCLUSION GLOSSARY BIBLOGRAPHY

ThisProjectisbuilttomodelthe EMPLOYEE MANAGEMENT SYSTEM ascloselyaspossible.Somefeaturesare:

Separateprofilesforusers,containingalltheirpersonaldata.

Possibilityofmultiple entriesperprofile.

Findingthe salary and hours according to the according the employye name and as well as the status.A such a management system by which you can search employee and his data and available of total number of hours. Separateprofiletypeforofficials.

Appropriateerrorchecking.Alltheseandothertransactionsandfeatureshavebeendescribedindetailinthefollowingsection.

1.1 The EMPLOYEE MANAGEMENT SYSTEM (EMS) is a software application to assist an employee salary with transactions related to making book entry.1.2From the viewpoint of the employee management system -

1.2.1Minimize repetitive work done by the system administrator and booking clerks.1.2.2Employee system that would keep a record of employee data including their

Pension plan.

1.2.3Union membership status, and taxes and also to be able to calculate the pay of the

Employees taking into consideration employee data.

1.2.4 Maximize the revenue of the company by various means:

1.2.4.1 Increase awareness among many company about various special offers by which they can save more much time. 1.2.4.2 The software we developed calculates the employee net pay from the deductions.1.2.4.3 The payslip can be printed out as a receipt.1.3Most of the bugs that we found and those that the clients and beta users found have been corrected. Any new bugs found will also be corrected and the software will be

Updated and released.1.4Because we used object-oriented principles, modifying the software to fix bugs

Or add a new feature has been relatively easy.

1.1 Definition of ProblemXP, the user story serves the purpose of the problem statement and the specifications. The user

Story provided by the client was as follows:

You are to design and implement a payroll system that should accept employee hours worked, compute net pay and record all the payroll data for subsequent processing. The system should prepare pay cheques and a payroll ledger, and maintain data on a sequential payroll file. Non-statutory deductions such as union dues and pension plans to be made.

The payroll data are employee number, employee name, pay rate, and union member flag. The year-to-date total should contain earnings, federal tax, pension plan, and union dues To accomplish these tasks, we had to meet with the client to find out exactly what the program is meant to do. Here are the sub stories that we were able to get from the client:

The program accepts employee hours worked

The program computes net pay

The program record all the payroll data for subsequent processing

The program should prepare pay cheques

The program should prepare a payroll ledger

The program should maintain data on a sequential payroll file

Non-statutory deductions such as union dues and pension plans to be made

Year-to-date total should contain earnings, federal tax, pension plan, and union dues

Payroll data are employee number, employee name, pay rate, and union member flag

1.2 Terminology Definition

This section gives a definition and explanation of some of the terms used in the project:

Employee Data: This is the employee's information in the company. It consists of the employee

identification number, employee name, pay rate, pension plan flag, and union member flag.

Payroll Records: The payroll records are used to store each months hours worked, and the rates for

That month.

Rates: Rates consists of the percentage that would be deducted from the gross pay depending on

union membership status, pension plan, state and federal tax. Each employee can have a uniquehourly rate.Payroll Ledger: This is a table that shows the calculated pay of employees and the month in which

they earned the pay. The ledger can be filtered by name, identification number, year and month.

Hours Worked: This is the number of times that an employee work in a month. The hours worked is

used to calculate the pay that an employee will receive for that month.

Net Pay: The net pay is the final salary amount that would be given to the employee after all the

deductions are subtracted from the gross pay. The deductions include among others taxes, union

member dues and pension plan.

Gross Pay: The gross pay is the amount that the employee earns before the deductions are

subtracted.

Deductions: Deductions are made up of taxes, union membership dues, pension plan. They are

subtracted from the gross pay to give the net pay which is the employee's final pay for the month.

Taxes: The taxes consists of the state dues and federal dues. A percentage of the employee's salary

goes to state and country.

Union Membership Dues: This is meant for employee's that are union workers in the company.

They get to pay a percentage for union dues. An employee can be a union member and later change

status to be a non-union member.

Pension Plan: Employees that opted to use the pension plan of the company get to pay a particular

percentage of their pay in preparation for their retirement.

Payslip: These are similar to pay cheques. They allow the employee to have his or her pay printed

out on paper so that they can cash it.

Year-To-Date Total: The year-to-date total is the summation of all the previous earnings till the

month before the current month.

1.3 Definition of Project Objectives

The purpose of this project is to put into practice what we have learnt so far in our software

engineering class. We spent most of the semester studying extreme programming. With extreme

programming, the client knows how far he or her software is coming and knows what to except at

one particular time or the other. The software is built exactly the way the client wants it to be built.

1.4 Project Deliverables

We met with our client on a few occasions to show our progress so far. In the long run, showing the

client part of the finished product in stages helped. There were a few things he brought to our

understanding and we were able to change those things. If we had waited till we finished the coding,

we would have found it really difficult to correct the errors we found in such a short time.

The graphical user interface was acceptable to the client at this stage even though he thought we

could improve on it with a little more time. From our project deliverables, the client was able to

bring to our understanding that the employees should have different pay rates and that it would be

safe (for record purposes) to calculate the employee's year-to-data total salary earnings. These

observations were later incorporated into the final deliverable.1.5 Project Plan

At the beginning of the project, we scheduled meeting time for the group to discuss on the design

and implementation of the software and what language to use in writing the software. We had several

meetings to this effect. When then developed a time-line for the projectwhen we would be releasing

the first version for scrutiny and the estimated time we thought we would use for refactoring. We also

pondered on a suitable name to give the project. We came up with the name Piccolo but it was later

changed to Payroll System after our meeting with our client.

The group was then divided into two pairs that would work on parts of the code. We kept in touch

with each other and whenever we had difficulties, we asked each other questions. On some

occasions, we had to pretend we were the customer so as to try to figure out some of the things that

user would desire, such as the friendliness of the user interface and ease of navigation through the

software. We also created a blog so that we could communicate with each other, and also so that our

client could track our progress.When we discovered that we were behind schedule, we met to create a new time-line. We were

behind schedule mostly because of our different engagements in school work and other personal

issues. Fortunately for the team, we were able to stick to the new time-line and the project was

completed in due time.

After the major part of the code was completed, we went ahead to lace the code, that is, adding

exception handlers which will make the software more robust. We avoided this at the beginning

because we did not want to get confused with too many lines of code.

The version of the software that has been released can still be improved depending on user response.

So far, we have succeeded in completing the desired goal of from the user stories given to us. The

beta software has been released about three times and we have been able to get good ideas from the

various users on how to improve the functionality, reliability and robustness of the software.

DESIGN

2.1 An Introduction to the methods and techniques adopted

Within the design

The software was built using Visual Basic and it can run on computers that have the .NET

Framework installed. We divided the whole project into five main modules: employee data, payroll

records, rates, ledger and help.

When a data is saved, the data gets written into an XML file. Keeping in line with making the

software platform-independent, XML is also a highly platform-independent format for storing data.

This is where all the data of the employee is stored, along with each months payroll data for the

employee. There is also a separate XML file for storing current rates. For an employee data or

payroll data to be saved to the file, it has to be serialized. Getting any data from the file will require

the data to first be deserialized before it can be used. Serialization and deserialization helped make

the data storage very simple.

We also used the object-oriented paradigm to code and organize our program. This ensured code

reuse, and efficient updating of the code later on.

2.2 High-Level Architecture Diagram of the main components

2.3 More detailed description of the most important modules

of the design

The most important modules of the design are the employee data, payroll records and rates. For the

employee data module, we had to keep track of the identification number, name, union membership

status, pension plan agreement and payroll of an employee. We also had to link these to a general

module that will hold all the other employees. There had to be a means of storing all these data,

retrieving them, adding data and deleting data without giving any errors. From the employee data

module, we had to create a link to the employee's pay records.

The payroll records had to contain the number of hours that the employee had worked and in what

month and year that the employee worked. We also had to keep in mind the rate with which we

would be able to calculate the employee's pay. The payroll records also had to contain the employee's

deductions, that is, the deductions from the pension plan, union membership fee and taxes.

Obviously, the payroll records also had to contain the gross and net pay of the employee.

The picture below shows a brief look at the modules of the original design.

We refactored the modules. This had to be done after one first deliverable was given to out client.

2.4 Indication of how the design fulfills the requirements

From the design picture above, it is clear that the software is meant to accept employee data, i.e., the

identification number, name, union membership status and pension plan. It should stores these data

in a XML file. The software computes the employee payroll depending on the rate and deductions

that has been specified for the employee. New employees can always be added to the list of existing

employees. There is no limit to the number of employees that the list holds. An employee's data can

be modified as well as deleted from the list.

Each employee has a link to a pay data in the payroll records module. From the design diagram, we

can see that a new payroll data can be added to the employee's list of existing pay data. The payroll

calculates the employee's pay depending on the hours worked, the employee's rates and deductions

that include pension dues, union membership dues and taxes. Each pay data is stored according to the

month and year is was calculated.

IMPLEMETATION

Some of the difficulty we faced was in trying to make the desired functions work. At first the coding

seemed a little complex, so we went back to the client for clarification and we were able to get a

more detailed description of the functions. After studying the IDE we wanted to use, the coding

became less complex and we were able to figure out how to go about it.

3.1 Technical issues encountered

Some of the technical issues and questions we encountered were with the following:

How the program saves data

How errors are detected and the error messages that should appear

What happens when we try overwriting data that already exists on the list

Is the software user friendly?

Is the Graphic User Interface elegant ?

The platform the software should run on

We were able to answer and resolve these issues after meetings and discussions with the entire

group.

3.2 Software development practices adopted

We used Extreme Programming to build the software.

We adopted the whole team approach in which the client was involved through out the software

development.

We used simple designs which were as simple as the current functionality allowed by the system.

We first began with very simple design which is incrementally improved.

Continuous integration was also used where each code was compiled run and tested before

adding to the system after which the system must meet all the criteria

The most important practice adopted was pair programming. We paired up with members of the

team and each team met at various times to code. After each pair coded, they made sure they

tested and compiled it, then added it to the main system which they sent to the other group

members.

We also made sure that we coded according to coding standards, the development codes were

consistent and had the same style through out.

FEASIBILITY STUDY:-Feasibility study before development or customization of software we think following of the major points, which includes following: -

a) Economical

b) Technical

c) DurationEconomical:-This study about the software basically give the suggestion like if we develop software for our organization than how much it will forfeitable, workable as well as economical. If we developing a software which very economical but not profitable there it is also wrong decision. Still we have economical study about the system table following of the point.

How much costing of the software?

What is the output of the customization?

What are the advantages in compression manual we check

Whether it is time or not?

Whether it is use friendly or not?

It is mountable for long term.

Understanding about the software

Corrective of software.

Technical:-We also consider some technical points about development of software.

We see whether the software is reliable or not.

Whether it is work time for long time or not.

What are the languages as well as OS is used for development of software.

It provides security or not.

Software is reusable or not.

Software is updated or not.

Software is flexible or not whether software can maintain.

Duration:-It is also a major point when we develop software. We also consider about time, how much time software place to complete because for a big organization time factor is money for full successful of the software also Tax some times so we have consider from starting to last that means beginning to software.

Data Storage Data Access

In developing cost estimates for a system, we need to consider servable cost elements. Among them hardware, personnel, facility, operating, & supply costs.

Hardware Cost:-Hardware cost relate to the actual purchase or lease of the computer & peripherals Ex. Printer, disk, floppy drive, the best way to control for this cost is to treat it as an operating cost.

Personnel Cost:-This includes staff salaries & benefits (health insurance, vocation time, sick pay etc.) as well as pay for those involved in developing system. Costs incurred during the development of a system are one time costs & are labeled developmental costs. Once the system is installed the costs of operating &maintaining the system become recurring costs.

Facility Costs:-Facility costs are expenses incurred in the preparation of the physical site where the application or the computer will be i operation. This includes wiring, flooring, acoustics, lighting & air conditioning. These costs are treated as one time costs.

Operating Cost:-Operating costs include all costs associated with the day to day operating system. The amount depends on the number of sifts the nature of the application & the caliber of the operating staff. There are various ways of covering operating costs to overhead. Another approach is to change each authorized user for the amount of processing they request from the system. The amount charged is based on the computer time, staff time & the volume of output produced.

Supply Cost:-These costs are variable costs that increase with increased use of paper, ribbon, disks & the like they should be estimated & include in the overall cost of the system.

Equipment Cost:-Equipment costs include rental & annual deprecation of any equipment such as typewriter, copies, computer terminals & microcomputers used in connection with the system. Other costs associated with the equipment, such as insurance & maintenance should also be included.

SYSTEM:-A system can be defined as A set of arrangement of elements that are organized to accomplish some method, procedure or control by processing information.

System Analysis stages down the broad frame work of strategy stage into its minute details. This is the stage where intensive user interaction assumes a lot of importance.

System DEVELOPMENT:-Development Phase, translates a set of requirements into an operational system that we call Software. At early stages of hardware development a hardware engineer does not reach for a soldering iron, similarly the Software engineer should not reach the compiler. Design is accomplished first.

The first phase of development concentrates on design. The design phase for software with a description of architecture and data design. That is a modular structure is developed first, interfaces are defined and data structure is established. Design criteria are used for the assessment of quality. This preliminary design step is reviewed for completeness and tractability to software requirements.

Procedural aspects of each modular component of the software design are considered next, and is following by the CODING the generation of program using an appropriate programming language or CASE tool occurs after the design is complete. Software engineering methodology views coding as a consequence of good design. Code is then reviewed for style and clarity, but should otherwise be directly traceable to a detailed design description.

DETAILED ENTITY RELATIONSHIP DIAGRAM :-

Identification of all the Entities of importance for which data need to be stored and defined their relationship with each other was a major task at this level. All the identified entities were mapped on a E-R-diagram. It is of utmost importance to cover all the necessary entities and defined their relationship with each other correctly because any errors at this stage would result in the reworking in the further stages.

Unique Identification, UID:-A unique identification is required to be identified and associated with each other at this stage.

Function Hierarchy:-Function hierarchy is used for grouping related functions under a parent function. The hierarchy is balanced so that all elementary functions come in the same level of hierarchy. A good hierarchy drawn at this stage helped in menu generation at a later stage.

The Basic Objective:-The basic objective of the system design was the system being developed should be able to fit into the existing system, that is it become a part of the system and it should not lead to any changes which can adversely affect the existing system. The airways having many activities which affect one another so the approach of airways reservation is generated for the simplification of data handling.

The approach would bring in the following benefits:- Standardization of the methods and procedures.

Availability of information centrally.

Minimizing future maintenance requirements.

Reduction in the learning process for new personal.

Packaged systems:-The systems would have the following features:- Completely menu drive interface with the provision of initiating even the batch jobs by the user himself.

On Line help

Strong documentation

Validation checks done by the system itself

Minimization of input to the system to produce maximum output.

Designing is the most important part of the software development. It requires a careful planning and logical thinking on the system designer. Designing a software means to plan how the various parts of the software are going to achieve the desired goal. It should done with the utmost care because if this phase contains any errors then that will be going to affect the performance of the system, as a result it may take more processing time, more coding, extra work load etc.

As the software is to be designed in ORACLE RDBMS, the concept of the database is must for quality designing. It will be designing of the database, designing of forms, designing of reports.

Separate tables have been created for each entity of the system. In order to make the response time negligible, all the tables have been created in the Memory File System. Moreover indexes have been created on the tables in the number of records have been made random.

The design stages takes the final specification of the system from the analysis stages and finds the best way of fulfilling them, given the technical environment and previous decision on required level of automationThe system design is carried out in two phases:- Architectural Design Detailed Design

ARCHITECTURAL DESIGN:-The high level design maps the business system described in the program requirement specification to logical data structure, it involves:Identification of the entities that constitutes the system:-All the entities related to the module were identified, checked and consolidated

Identifying the Relationships:-The relationships between the entities, within and outside the system were identified.

Attribute definition:-The pertaining of the entities was identified and their field characteristics were specified.

Normalization:-

The entities were normalization, after first and the second normalization was achieved for all the entities.

Interface:-Interface with the other systems were done and attributes related to external entities identified.

DETAILED DESIGN:-The low level design maps the logical model of the system to a physical database design.

Table Mapping:-The Table was created for the system using the design view, which is the part of the ORACLE. This has provision to create the entities and attributes into the Tables. The name of the entity is taken as the table name.

Default Database Design:-In ORACLE we can create tables through the queries and some command. The tables divide into two parts. These names are as follow: -

ROWS

COLUMNSThe steps involved here were:-1. Generation of table

2. Check Validation Rule

3. Check Validation Text

4. Primary Keys

5. Unique Keys

6. Foreign Keys

Relationship:-ORACLE allows many types of relationship between the tables. These relationship names are as follow: -

One to One Relationship

Many to One Relationship

Many to Many Relationship

Program specifications:-The program specifications were written for the master, transactions, reports and queries. The logic for each field, block and form were written so that anyone who does not know the system will be able to code the logic. Field validations and user-friendly error messages were written as part of the program specification.

WINDOW 98 used as PLATFORM

Windows XP is latest version of windows and also GUI. This is best then another Operating system and easy.Windows XP has come up with another bonanza, that is, Network Communication with other users. The users can connect with other users to share data files and peripheral devices, like Printers.

The Communication tools of Windows XP include E-Mail and connection to Internet.

VISUAL BASIC used as FRONT ENDVisual Basic uses front-end programming because VB use Back end as like oracle and any other Database.

In VB we can use easy database connectivity and design the Form, Report, and others MDI applications with the help of Database.

VB facility the database controls which helps the changing, modifying, deleting and adding facility in database with the help of command buttons and controls.

VB is used for see the Data in many modes such as with the help of MSFlexGrid Controls, Textbox, Combo box, List box, Image, Picture control and other.

Visual Basic gives the different types of accessing the Database (RDO, ADO and DAO)

Visual Basic is complete programming language that supports programming constructs for looping, decision making and efficient processing. These constructs include

For.next

Do.loop

Selectcase

Withend with

If.then.else

Visual Basic helps of creation Menus, Master-Details Form.

MS ACCESS used as BACK END

MS ACCESS is a database and partially RDBMS. In Access we can create Database design and give the validations. Access allows the many types of relations between the tables.

Access used as Backend with the Visual Basic. Access allows creating the Primary Key, Foreign Key and Unique Key. In Access we can store the data in to the table for using the wizard options.

During system testing, the system is used experimentally to ensure that the software does not fall, i.e. it will run according to specification and in the way users expect. Special test data input for processing and the result examination. A limited number of users may be allowed to use the system so that analysis can see whether they use it in unforeseen ways. It is preferable to discover any surprises the organization implements the system and encounters them later on. This type of testing which allows only a few, selected users to work on the system is known as BETA TESTING. On the other hand the testing done by the developer (s), themselves is known as ALPHA TESTING.

Testing is generally performed by persons other than those who the original programs to ensure complete and unbiased testing and more reliable software.

The norms followed during the testing phase were thoroughly tested by me, the developer; I was required to release the programs source code. The source code was copied into the area. If some changes were desired in the program, I was suitably informed and was required to make the necessary modifications.

Following testing procedures were used

UNIT TESTING

Unit testing is the testing of a single program module in an isolated environment. The testing of the processing procedure is the main focus. In this regard, all the modules were separately tested first as isolated and complete entities. This helped a lot in discovering problems related to a single module and rectifying them in the contest of the module itself, rather than considering module-related problem in a global context.

INTEGRATION TESTING

Integration testing is the process of testing the interfaces among system modules. Some testing ensures that data moves between systems as intended. In the regard of a particular module was obtained in correct format, so that the next module could accept it appropriately. This could be done either after the entire system was developed, or in stages than one module was developed.

SYSTEM TESTING

System testing is the testing of the system against its initial objectives. Such testing is done either in a simulated environment or in a live environment.

In the case of the system which I developed, the testing was done in a pseudo-real environment. The organization has an area called the Development , where all development work is carried out, whereas the Client is the area where all on-line work is undertaken. Since the kind of work which I was involved dealt with insertion, updating and in tables, all the work was developed in the Development area. I call the environment pseudo-real since all data which is being used for on-line transaction can be copied into the tables of the Development and live data can be worked on. Thus whatever would be the output on the Client is reflected exactly on the Development also? Thus, discovery of error became simpler in that the errors which would occur in the real-time environment were exactly duplicated in the Development environment.All the above types of testing were carried out and various extreme cases were also introduced to check for whether the system responded as expected. The various Forms, database packages, procedures, function; visual basic programs and functions were tested to discover they behaved in the manner expected of them and gave accurate results. However, the factor, which helped most in the modification and rectification of the system, was the user response. The user after using the system would invariably come up with some idea to improve the system. Such ideas, if feasible, were incorporated into the system, thus leading to an improvement in the overall efficiency of the system.

Implementation, literally, means to put into effect or to carry out. The system implementation phase of software engineering deals with all activities that take place to convert from the old system to the new. Proper implementation is essential to provide system to meet organizations requirements.

During the implementation phase debugging, documentation of the system was created out, module in the project for

Accuracy of Results,

Minimization of response Time,

Clarity and Simplicity of the code,

Minimization of Hard Coding i.e. (a generic approach was followed )

Minimization of amount of memory used.

Various types of errors were discovered while debugging the modules. These ranged from errors to failure to account for various processing cases. Proper documentation of each module was done by embedding comments in the executable portion of the code. To enhance the readability, comments, indentation, parenthesis, black spaces, blank lines and borders were around the blocks of comments. Care was taken to use descriptive names for table, field, modules, forms etc., The proper use of indentation, parenthesis and blank lines was also ensured during coding.

Testing of the Report Generation module was carried out to find out the response time of the system for the generating reports. To make the response time negligible

Maintenance is a fact of life in the development of information systems. However the making of changes & adjustments dont necessarily signal correction of error or the occurrence of problems.

Among the most frequent changes requested by end users is the addition of information to a report format. Information requirements may be revised as the result of system usage or changing operational needs. Perhaps oversights that occurred during the development process need to be corrected.

Often, the need arises to capture additional data for storage in a database or perhaps when it is necessary to add error detection features to prevent system users from inadvertently taking an unwanted action.

These are the realities of application maintenance, when they occur, however they are an indication that the system is being used & that it is serving a useful function rather than being shelved by the intended, such as :

More accurately defining the users requirements during system development.

Assembling better systems documentation.

Making better use of existing tools & techniques.

Including proper comments.

Documentation is the process of collecting, organizing, storing and maintaining on paper (or some relatively permanently medium) a complete record of why application were developed, for whom, what function they perform, and how these functions are carried out. Thus it provides an explanation of how a system operates & what feature characterize models & algorithms. Producing documentation is an important but often neglected activity of programmers.

Documentation of the system always reduces maintenance costs and makes maintenance much easier. Documentation can be broadly classified as:1. INTERNAL DOCUMENTATION

2. EXTERNAL DOCUMENTATION

INTERNAL DOCUMENTATION

Internal documentation in the code can be extremely useful in enhancing the understandability of programs. Internal documentation of programs is done by the use of comments. All the languages provide means of writing comments in the programs. Comments are textual statements that are meant for the reader and are not executed. Comments, if properly written, and if kept consistent with the code, can be invaluable during maintenance.

The purpose of comments is not to explain the internal logic of the program the program itself is the best documentation for the details of logic. The comments should explain what the code is done is doing, and not how it is done it.

Comments should be provided for the block of code, particularly those parts of code which are hard to follow.

Providing comments for module is most useful as module form the unit testing, compiling, verification and modification. Comments for a module are often called prologue for the module. It is best to standardize the structure of the prologue of the module. It is desirable that prologue contains the following information:a) Module functionality or what the module is doing

b) Parameters are their purpose

c) Assumptions about the input, if any

d) Global variable accessed and or modified in the module

As explanation of parameters (whether they are input only, output only or both input and output , why they are needed by the module and how the parameters are modified ) can be quite useful during maintenance.

In addition to that given above, often information can be included, depending on the local coding standards. Example includes: Name of the author,

Date of compilation

Last date of modification.

Note that if the module is modified, then the prologue should also be modified, if necessary. A prologue that is inconsistent with the internal logic of the module is prologue worse than having no prologue at all.

While coding programs for the Station Coding System special attention has been paid to the internal documentation of the system, in addition to the external documentation. Each program/module has: Program/module name on top

Date of creation of the program

Last modification date

The S/W tool used to developed the program

Description of input to the program/module

Description of the output produced

How the module is related to other modules

Purpose of variables/constants used

Apart from this comment lines have been inserted wherever it was felt that they were necessary. Moreover meaningful variable names/constants have been assigned to different variable/constants used in the programs.

Main window

Company information window

Employee information window

Leave window

Payroll information

Graphical repersantation

Query form

Company informationPrivate Sub cmdadd_Click()

If Adodc1.Recordset.RecordCount = 1 Then

MsgBox "u have already added the details of your company..u can update them by pressing update button"

Exit Sub

End If

Adodc1.Refresh

Adodc1.Recordset.AddNew

End Sub

Private Sub cmdclose_Click()

Me.Visible = False

End Sub

Private Sub cmddelete_Click()

On Error Resume Next

Adodc1.Refresh


MsgBox "db is empty"

End If


Adodc1.Recordset.MoveFirst

Adodc1.Recordset.Delete

Adodc1.Recordset.Update

txtadd1 = ""

txtadd2 = ""

txtcity = ""

txtcname = ""

txtcontry = ""

txtemail = ""

txtfax = ""

txtnote = ""

txtphone = ""

txtstate = ""

txtwebsite = ""

End If

End Sub

Private Sub cmdmodify_Click()



End Sub

Private Sub cmdupdate_Click()



End Sub

Private Sub Form_Load()

Form1.Width = 6855

Form1.Height = 5970

End SubGraphical RepersantationDim ii As Double

Dim e As Double

Dim r As Double

Dim iii As Double

Private Sub cmdage_Click()

'chartman.DataSource = Adodc1

'chartman.Legend = True

Adodc1.RecordSource = "select empno,firstname, salary from employee"

Adodc1.Refresh

End Sub

Private Sub cmdages_Click()

Adodc1.RecordSource = "select empno,firstname, (Date()-dob)/365 from employee"

Adodc1.Refresh

End Sub

Private Sub cmdautorotate_Click()

e = chartman.Plot.View3d.Elevation

r = chartman.Plot.View3d.Rotation

Timer1.Enabled = True

End Sub

Private Sub cmdborder_Click(Index As Integer)

With chartman.Plot.Backdrop

Select Case Index

Case 0

.Frame.Style = VtFrameStyleThickOuter

' Set style to show a shadow.

Case 1

.Frame.Style = VtFrameStyleNull

' .Shadow.Style = VtShadowStyleDrop

End Select

End With

End Sub

Private Sub cmdch_Click(Index As Integer)

'optdef.Value = False

'chartman.ShowLegend = True

Select Case Index

Case 0

chartman.chartType = VtChChartType2dBar

Case 1

chartman.chartType = VtChChartType3dBar

Case 2

chartman.chartType = VtChChartType2dPie

Case 3

chartman.chartType = VtChChartType2dLine

Case 4

chartman.chartType = VtChChartType3dLine

Case 5

chartman.chartType = VtChChartType3dStep

End Select

End Sub

Private Sub cmdexperience_Click()

Adodc1.RecordSource = "select empno,firstname, (Date()-doj)/365 from employee"

Adodc1.Refresh

End Sub

Private Sub cmdshadow_Click(Index As Integer)

With chartman.Plot.Backdrop

Select Case Index

Case 0

.Shadow.Style = VtShadowStyleDrop

' Set style to show a shadow.

Case 1

.Shadow.Style = VtShadowStyleNull

End Select

End With

End Sub

Private Sub cmdsolid_Click(Index As Integer)

With chartman.Plot

Select Case Index

Case 0

' Set the style to solid.

.Wall.Brush.Style = VtBrushStyleHatched

Case 1

.Wall.Brush.Style = VtBrushStyleSolid

End Select

' Set the color to white.

.Wall.Brush.FillColor.Set 255, 255, 255

End With

End Sub

Private Sub cmdstop_Click()

Timer1.Enabled = False

Timer2.Enabled = False

e = chartman.Plot.View3d.Elevation

r = chartman.Plot.View3d.Rotation

ii = 1

iii = 1

End Sub

Private Sub Timer1_Timer()

chartman.Plot.View3d.Set r + ii, e

ii = ii + 1

End Sub

Private Sub Timer2_Timer()

chartman.Plot.View3d.Set r, e + iii

iii = iii + 1

End Sub

Employee payrollPrivate Sub cmdadd_Click()

On Error GoTo x


x:

End Sub

Private Sub cmdclose_Click()

Me.Visible = False

End Sub

Private Sub cmddelete_Click()

On Error GoTo x

Adodc1.Recordset.Delete


txtaddress = ""

txtcasual = ""

txtcasualid = ""

txtcity = ""

txtcountry = ""

txtdept = ""

txtdesignation = ""

txtdob = ""

txtdot = ""

txteducation = ""

txtemail = ""

txtemergency = ""

txtempno = ""

txtexperience = ""

txtfname = ""

txthiredate = ""

txtlname = ""

txtmname = ""

txtnormal = ""

txtnormalid = ""

txtnote = ""

txtsalary = ""

txtsick = ""

txtsickid = ""

txtspouse = ""

txtstate = ""

txtstatus = ""

txttelephone = ""

txtterminate = ""

lstactive.Clear

lstinactive.Clear

Adodc1.Refresh

Form_Load

x:

End Sub

Private Sub cmdfirst_Click()



End Sub

Private Sub cmdlast_Click()


Adodc1.Recordset.MoveLast

End Sub

Private Sub cmdnext_Click()


Adodc1.Recordset.MoveNext

If Adodc1.Recordset.EOF = True Then


End If

End Sub

Private Sub cmdprevious_Click()


Adodc1.Recordset.MovePrevious

If Adodc1.Recordset.BOF = True Then


End If

End Sub

Private Sub cmdupdate_Click()

On Error GoTo cancelupdate


lstactive.Clear

lstinactive.Clear

Adodc1.Refresh

Form_Load

Exit Sub

cancelupdate:

MsgBox Err.Description

End Sub


Form2.Width = 10845

Form2.Height = 6480

On Error GoTo x

Dim i As Integer

Adodc1.Refresh



For i = 1 To Adodc1.Recordset.RecordCount

lstactive.AddItem Adodc1.Recordset.Fields(2)


Next


x:

End Sub

Private Sub lstactive_Click()

Adodc1.Refresh

Dim l As String

Dim no As Integer

Dim count As Integer

count = 0

no = lstactive.ListIndex

'l = lstactive.Text

'Adodc1.Recordset.Find "firstname='" & l & "' "


While Adodc1.Recordset.EOF True

If count = no Then

Exit Sub

End If

count = count + 1


Wend

End SubLeave infoPrivate Sub cmdclose_Click()

Me.Visible = False

End Sub

Private Sub cmdenterleave_Click()

Form4.Visible = True

End Sub

Private Sub cmdupdateleave_Click()

cmdenterleave_Click

End Sub


Form3.Width = 6075

Form3.Height = 5700

On Error GoTo x

Dim i As Integer

Adodc1.Refresh



For i = 1 To Adodc1.Recordset.RecordCount

lstemp.AddItem Adodc1.Recordset.Fields(2)


Next


x:

End Sub

Private Sub lstemp_Click()

leavename = lstemp.Text

Adodc1.Refresh

Dim l As String

Dim no As Integer

Dim count As Integer

count = 0

no = lstemp.ListIndex

'l = lstactive.Text

'Adodc1.Recordset.Find "firstname='" & l & "' "



If count = no Then

normalleaveid1 = Adodc1.Recordset.Fields(20)

sickleaveid1 = Adodc1.Recordset.Fields(21)

casualleaveid1 = Adodc1.Recordset.Fields(22)

Exit Sub

End If

count = count + 1


Wend

End Sub

Leave entry

Private Sub cmdcasualleavedetails_Click()


Form6.tab1.Tab = 1

End Sub

Private Sub cmdcasualupdate_Click()


Adodc2.Recordset.Fields(0) = casualleaveid1

Adodc2.Recordset.Fields(1) = casualfrom.Value

Adodc2.Recordset.Fields(2) = casualto.Value


MsgBox "-database updated successfully-"

End Sub

Private Sub cmdnormalleavedetails_Click()


Form6.tab1.Tab = 2

End Sub

Private Sub cmdnormalupdate_Click()


Adodc3.Recordset.Fields(0) = normalleaveid1

Adodc3.Recordset.Fields(1) = normalfrom.Value

Adodc3.Recordset.Fields(2) = normalto.Value



End Sub

Private Sub cmdsickleavedetails_Click()


Form6.tab1.Tab = 0

End Sub

Private Sub cmdsickupdate_Click()


Adodc1.Recordset.Fields(0) = sickleaveid1

Adodc1.Recordset.Fields(1) = sickfrom.Value

Adodc1.Recordset.Fields(2) = sickto.Value



End Sub


lblleavename.Caption = leavename

Me.Width = 8010

Me.Height = 5580

End Sub

Payroll informationPrivate Sub cmdleaveaddition_Click()

Dim total As Long

total = Val(txtsalary.Text) * 12

If total > 50000 And total 60000 And total 150000 Then

total = total - 150000

total = (total / 100) * 30

total = total / 12

txttax.Text = total

Else

txttax.Text = "0"

End If

End Sub

Private Sub cmdpay_Click()


If txtempno = "" Or txtsalary = "" Or txtnet = "" Or txtdop = "" Or txtpaymode = "" Then

MsgBox "one or more fields r left blank..so try again"

Exit Sub

End If


Adodc2.Recordset.Fields(0) = Val(txtempno.Text)

Adodc2.Recordset.Fields(1) = Val(txtsalary.Text)

Adodc2.Recordset.Fields(2) = txtdop.Text

Adodc2.Recordset.Fields(3) = txtpaymode.Text

Adodc2.Recordset.Fields(4) = txtchequeno.Text

Adodc2.Recordset.Fields(5) = Val(txttax.Text)

Adodc2.Recordset.Fields(6) = Val(txtothertax.Text)

Adodc2.Recordset.Fields(7) = Val(txtnet.Text)

Adodc2.Recordset.Fields(8) = Val(txtleave.Text)


MsgBox "records r updated"

lstpaid.Clear

lstunpaid.Clear

Form_Load

End Sub

Private Sub cmdrebateothertax_Click()

txtothertax.Text = "0"

End Sub

Private Sub cmdrebatetax_Click()

txttax.Text = "0"

End Sub

Private Sub cmdtotal_Click()

txtnet.Text = Val(txtsalary.Text) + Val(txttax.Text) + Val(txtothertax.Text) + Val(txtleave.Text)

End Sub

Private Sub Command1_Click()

txtleave.Text = "0"

End Sub



End Sub


Form5.Width = 6105

Form5.Height = 6090

On Error GoTo x

Dim i As Integer

Dim j As Integer

Dim k As Long


Adodc1.Refresh




k = Adodc1.Recordset.Fields(0)




If k = Adodc2.Recordset.Fields(0) And Left(Adodc2.Recordset.Fields(2), 2) = Left(Date, 2) Then

lstpaid.AddItem Adodc1.Recordset.Fields(2) & " " & Adodc1.Recordset.Fields(0)

GoTo m

End If


Wend

lstunpaid.AddItem Adodc1.Recordset.Fields(2) & " " & Adodc1.Recordset.Fields(0)

m:


k = ""

Wend



x:

End Sub

Private Sub lstpaid_Click()

Adodc2.Refresh

'Adodc2.Recordset.Find "empno=" & Val(Mid(lstpaid.Text, InStr(lstpaid.Text, " ")))



If Adodc2.Recordset.Fields(0) = Val(Mid(lstpaid.Text, InStr(lstpaid.Text, " "))) Then

txtempno = Adodc2.Recordset.Fields(0)

txtsalary = Adodc2.Recordset.Fields(1)

txtdop = Adodc2.Recordset.Fields(2)

txtpaymode = Adodc2.Recordset.Fields(3)

txtchequeno = Adodc2.Recordset.Fields(4)

txttax = Adodc2.Recordset.Fields(5)

txtothertax = Adodc2.Recordset.Fields(6)

txtleave = Adodc2.Recordset.Fields(8)

txtnet = Adodc2.Recordset.Fields(7)

Exit Sub

End If


Wend

End Sub

Private Sub lstunpaid_Click()

Dim m As Long

Dim n As Long

txtempno.Text = ""

txtchequeno = ""

txtdop = ""

txtpaymode = ""

txtsalary = ""

txtnet = ""

txtothertax = ""

txttax = ""

txtleave = ""

m = Val(Mid(lstunpaid.Text, InStr(lstunpaid.Text, " ")))

txtempno.Text = m



If m = Adodc1.Recordset.Fields(0) Then

n = Adodc1.Recordset.Fields(18)

txtsalary = n

txtdop = Date

Exit Sub

End If


Wend

End Sub

Leave detailsPrivate Sub cmdgetsickleaverecord_Click()

On Error GoTo x

DataGrid1.Visible = True

Dim strsql As String

strsql = "Select * From sickleavetable where sickleaveid=" & sickleaveid1

Adodc1.RecordSource = strsql

Adodc1.Refresh

Exit Sub

x:

DataGrid1.Visible = False

MsgBox "no records currently available"

End Sub


Me.Height = 4755

Me.Width = 6735

cmdgetsickleaverecord_Click

pressme_Click

pressmeplzz_Click

End Sub

Private Sub pressme_Click()

On Error GoTo x



strsql = "Select * From casualleavetable where casualleaveid=" & casualleaveid1


Adodc2.Refresh

Exit Sub

x:



End Sub

Private Sub pressmeplzz_Click()

On Error GoTo x



strsql = "Select * From normalleavetable where normalleaveid=" & normalleaveid1


Adodc3.Refresh

Exit Sub

x:



End Sub

Query form

Private Sub Check10_Click()

If Check10.Value = 1 Then

Check10.Tag = "," & Check10.Caption

Else

Check10.Tag = ""

End If

End Sub




Else

Check11.Tag = ""

End If

End Sub




Else

Check12.Tag = ""

End If

End Sub




Else

Check13.Tag = ""

End If

End Sub




Else

Check14.Tag = ""

End If

End Sub



Check15.Tag = "," & Check15.Caption & "phone"

Else

Check15.Tag = ""

End If

End Sub




Else

Check16.Tag = ""

End If

End Sub




Else

Check17.Tag = ""

End If

End Sub




Else

Check18.Tag = ""

End If

End Sub




Else

Check19.Tag = ""

End If

End Sub




Else

Check20.Tag = ""

End If

End Sub




Else

Check21.Tag = ""

End If

End Sub




Else

Check22.Tag = ""

End If

End Sub




Else

Check23.Tag = ""

End If

End Sub




Else

Check24.Tag = ""

End If

End Sub




Else

Check25.Tag = ""

End If

End Sub




Else

Check26.Tag = ""

End If

End Sub




Else

Check27.Tag = ""

End If

End Sub




Else

Check28.Tag = ""

End If

End Sub




Else

Check29.Tag = ""

End If

End Sub




Else

Check30.Tag = ""

End If

End Sub




Else

Check31.Tag = ""

End If

End Sub




Else

Check32.Tag = ""

End If

End Sub




Else

Check33.Tag = ""

End If

End Sub




Else

Check7.Tag = ""

End If

End Sub




Else

Check8.Tag = ""

End If

End Sub




Else

Check9.Tag = ""

End If

End Sub

Private Sub chkall_Click()

If chkall.Value = 1 Then

chkall.Tag = " * "

Else

chkall.Tag = ""

End If

End Sub

Private Sub cmdquery_Click()

On Error GoTo x

If chkall.Value = 1 Then

sqlbaby = " select * "

Else

sqlbaby = sqlbaby & Check7.Tag & Check8.Tag & Check9.Tag & Check10.Tag & Check11.Tag & Check12.Tag & Check13.Tag & Check14.Tag & Check15.Tag & Check16.Tag & Check17.Tag & Check18.Tag & Check19.Tag & Check20.Tag & Check21.Tag & Check22.Tag & Check23.Tag & Check24.Tag & Check25.Tag & Check26.Tag & Check27.Tag & Check28.Tag & Check29.Tag & Check30.Tag & Check31.Tag & Check32.Tag & Check33.Tag

End If

sqlbaby = sqlbaby & " from employee"

If chkwhere.Value = 1 Then

sqlbaby = sqlbaby & " where "

sqlbaby = sqlbaby & "lastname='" & txtlname.Text & "'"

sqlbaby = sqlbaby & " or firstname='" & txtfname.Text & "'"

sqlbaby = sqlbaby & " or city='" & txtcity.Text & "'"

sqlbaby = sqlbaby & " or state='" & txtstate.Text & "'"

sqlbaby = sqlbaby & " or department='" & txtdept.Text & "'"

If txtsalary.Text "" Then

sqlbaby = sqlbaby & " or salary" & txtsalary.Text

End If

If txtdob.Text "" Then

sqlbaby = sqlbaby & " or dob" & txtdob.Text

End If

If txtdoj.Text "" Then

sqlbaby = sqlbaby & " or doj" & txtdoj.Text

End If

End If

Adodc1.RecordSource = sqlbaby

Adodc1.Refresh

Form_Load

Exit Sub

x:


End Sub



Form7.Width = 12000

Form7.Height = 9000

sqlbaby = "Select empno "

chkwhere.Value = 0

End Sub

Direct queries Private Sub cmdquery_Click()

On Error GoTo x

Dim sql1 As String

sql1 = txtdirectquery.Text

Adodc1.RecordSource = sql1

Adodc1.Refresh

Form_Load

Exit Sub

x:


End Sub


Me.Width = 11985

Me.Height = 7710

End Sub

Direct queries check

Private Sub cmdquery_Click()

On Error GoTo x

Dim sql2 As String

sql2 = textdirectcheck.Text

Adodc1.RecordSource = sql2

Adodc1.Refresh

Form_Load

Exit Sub

x:


End Sub


Me.Width = 8655

Me.Height = 6810

End Sub

Mdi formPrivate Sub cmdcharts_Click()


End Sub

Private Sub cmdcompanyinforma_Click()


End Sub

Private Sub cmddetails_Click()

PopupMenu popmeup

End Sub

Private Sub cmdexit_Click()

Unload Me

End

End Sub

Private Sub cmdleaveinfo_Click()


End Sub

Private Sub cmdpayroll_Click()


End Sub



End Sub

Private Sub MDIForm_Load()


End Sub

Private Sub query_Click(Index As Integer)

If Index = 0 Then


End If

If Index = 1 Then


End If

If Index = 2 Then


End If

End Sub

The project made me realize the significance of developing software for client, where all the eventualities have to be taken care of, unlike at educational institution, where the sole aim is to learn. What may be seen to the developed to be software complete in all respects, I was required to meet the stringent demands of the in-house client in the materials department. Through this seemed tough at first, I realized that pressure goaded us on to develop better and better applications.

During the project, the real importance for following all the principle of System Analysis and Design drawled on me. I felt the necessity of going through the several stages, because only such a process could make one understand the problems at hand, more so due to the enormous size of data stores involved and their manipulation

In retrospect, I would like to say that the institute provided us with sample opportunities to learn Oracle 8 and its tools. I specifically was able to learn ORACLE and its Tools. I specially was able to learn VISUAL BASIC 6.0. I also succeeded in understanding a number of tricky concept in database, which were earlier only hazy blobs in the realm of our comprehension.However my project library management is an asset to the organization, even then FURTHER ENHANCEMENT is possible in this project such as new forms & reports can be included as and when required.Unfortunately due to lack of time we can developed any report in this system but this is not the end of this system software, it is beginning. We can change and modify this software due to more requirements of needs and also removed some errors which is finding in this system software.

We also developed some complex reports which is required and makes this software more powerful and friendly for user by which user can handle library data more easily and can calculate all the calculation without any other software i.e., users all the requirements will be fulfill by this software and user can manage all the numeric data calculations.

S.No.TermsDescription

1BACK UPA copy of something preserved to insure against the damage of primary copy.

2DATA BASEA repository of stored data.

3DBMSData Base Management System is a layer if Software between the physical database itself & the users of the system.

4DDData Dictionary, which is a data base that Contains data about data i.e. description of other in the system

5FLOW CHARTFLOW CHART which depicts relation between different entities in the system.

6HARDWAREThe physical equipment in a system comprising of computers, terminals, Keyboards & Other ancillary items.

7ITDInformation Technology Division.

8MENUA group of options from which Selection is to be made.

9MODULEA small components of a larger system

10ON-LINEA term describing people, equipment or Devices that are in direct communication with the computer

11PIPreliminary Investigation

12PROGRAMA sequence of instruction given to the Computer to solve a particular problem.

13PROTOTYPEA development model of the system for test Purpose

14RDBMSA data Base/ Management System in which Relationships are defined by tables.

15RSDRequirement Specification Document.

16SCALABILITYThe ability to increase the performance With the growth in Hardware.

17SOFTWAREComputer program, procedure & Associated documentation concerned with the operator of a system.

BOOK NAME

AUTHOR1. Complete Reference of MS-Office

Techmedia

2. An Introduction to Database Systems

C. J. Date

3. System Analyses and Design

E M. Awad

4. The Complete VISUAL BASIC

Tulec

5. Programming in VB

Black Book6. Visual Basic from the Ground Up

Gary Cornell

7. Mastering in VB

Steve 8. VB with MS-Access

Rita Sahoo

9. Visual Basic 6.0

Smith

RATES

EMPLOYEE DATA

PAYROLL RECORDS

PAYROLL SYSTEM

ENTRY EMPLOYEE

REPORTS

EMPLOYEE

PAYROLL SYSTEM

SLIP

PAYSLIP

LEDGER

76

employee management

Documents

employee system

system evaluation

system administrator

employee management

project work

project report

vikas kumar

parmod kumar sachin