Pay Roll Management_001

8/2/2019 Pay Roll Management_001

http://slidepdf.com/reader/full/pay-roll-management001 1/45

Software Engineering Project

ON

PAY ROLL MANAGEMENT

SYSTEM

Academic session: 2011-2014 Course Code: B.B.A (CAM)-154

Guide by: Submitted by: Ms. Sushma malik SURAJ REGMI

Roll no. 04890101911

B.B.A (CAM) 2nd Semester

Submitted to:

Fairfield Institute of Management & Technology

(Affiliated to GGS Inderprastha University, Delhi)

ISO 9001:2008 & 14001:2004 CERTIFIED

Kapashera, New Delhi-110037



TABLE OF CONTENT

ACKNOWLEDGMENTDECLARATION

CERTIFICATE

OBJECTIVE

SYNOPSYS

INTRODUCTION

ADVANTAGE OF THE PROPOSED SYSTEM

TOOLS & TECHNOLOGIES

WHY USE C++?

SOFTWARE PRINCIPLES

System Analysis

A. Interaction with user

B. Software DesigningC. Program designing

D. Programming

E. Documentation

a. User Manual

b. Technical Manual

SOFTWARELIFE CYCLE

A. Problem definition

B. AnalysisC. Design

D. Coding / Implementation

E. Testing

F. Maintenance



IMPORTANT FUNCTION& THEIR PURPOSES

DATA STRUCTURE (TABLES) OF MODULES

A. Customer information

B. Receipt & payment C. Loan rate of bank

DFD & ER DIAGRAMS

A. Data Flow Diagram:

B. ER-Diagram

FEASIBILITY

Economic Feasibility Technical Feasibility

SOFTWARE TESTING

A.Verification

B.Validation

C.Wrost-case testing

D.LEVEL OF TESTING

Unit testing

Integration testing System testing

Validation testing

Testing Tools

CONCLUSION

BIBLIOGRAPHY



Fairfield Institute of Management & Technology

(Affiliated to GGS Inderprastha University)ISO 9001:2008 & 14001:2004 CERTIFIED

Kapashera, New Delhi-110037

CERTIFICATE

This is to certify that this is a bonafide record of the project work done

satisfactory at Fairfield Institute of Management & Technology by

VIPUL enrollment no. 04690101911 under the supervision of Ms.

SUSHMA MALIK.

This project or a similar project on this topic has not been

submitted for any other examination & does not from part of other course

under gone by candidate.

_____________________ _____________________

Signature of Internal Guide Signature of Student

Ms.SUSHMA MALIK VIPUL

Roll no. 04690101911

B.B.A (CAM) 2

nd

Semester

Place: New-Delhi



ACKNOWLEDGEMENT

We thankfully acknowledge the encouragement and guidanceprovided by Ms. SUSHMA (Project Guide), without whose help this

project would not have achieved its present form. Her continual attention

and encouragement helped us get going.

I am highly indebted to Fairfield institute of

Management & Technology for providing excellent support for

the project.

VIPUL



DECLARATIONI hereby, declare that my project work entitled“PAY ROLL

MANAGEMENT SYSTEM ”submitted in Fairfield Institute of

Management & Technology,Kapashera, New Delhi-110037 has been

carried out by my own individual effort.

I also declare that, any or all of the contents incorporated in this

work, has not been submitted in any form for the award of any other

degree of any other institution or university.

(SIGNATURE)

SURAJ REGMI

Enrolment no. 04890101911

2nd Semester B.B.A (CAM)



0BJECTIVE

The objective of this project is to implement the concept of

software engineering & to co-relate the concept with real life

project . This project aims at development of software for PAY

ROLL MANAGEMENT system. Student system involves keeping

records of students.It would make work of theemployes easier. The

regular job of maintaining numerous records and maintaining them

on a daily basis for each student is not needed any more.



SYNOPSIS

Technical details The memory requirements include HDD (Free Space) 10GB, FDD

1.44MB. The other hardware required involves SVGA Color monitor,



Multimedia kit (CD drive, sound card, speaker, microphone),HCL

infinity 2000 mtx system, with 32-bit file system,Logitech mouse and

105 keys Keyboard.

The software platform involves windows xp operating system

Programming language C++ and documentation MS-WORD 2007

(office XP).

C++ language is chosen as it is object oriented and thus, offers

modeling the real-world problem as close as possible to the user’s

perspective Unlike, the traditional methodology (Function-Oriented

Programming), object-oriented programming emphasizes on the data

rather than the algorithm. C++ is a superset of c with features

designed to support oops. OOP is a new way of organizing code and

data that promises increased control over the complexity of the

software development process.

C++ has a well defined syntactic and semantic structure,

reliability, fast translation, efficient object code, orthogonal, machine

independence, provability, generality, and consistency with commonly

used notations, subsets, uniformity, and extensibility. With C++, it is



much easier to build and maintain a really big code .Object – Orientation

provides many other advantages in the production and maintenance of

software; shorter development time, high degree of code sharing and

malleability.

Benefits of the proposed system



Less Time Consuming.

Less Paper Work.

Easy Report Generation.

Easy Query Processing.

It Is Fully User Friendly.

Faster Access of Information.

INTRODUCTION



The Goal of the proposed system are:-

To allow only authorized user to access various function and

processed availablein the system.

Locate any account wanted by the user.



Reduced clerical work as most of the work done by computer.

Provide greater speed and reduce time consumption.

To increase the number of account and customer.

This will reduced the manual work and give informationinstantly. the softwarewill maintain the rest list of account and

customer record and balance status.

The software will be user friendly so that even a beginner can

operate the packageand thus maintain the status of account

and balanced status easily.

PAY ROLL MANAGEMENTProblem Statement:

To automate the existing Manual Management of the

Institutional system and how to manage ainstitutional System.



Why This Topic:

The philosophy behind the development of this solution ensures that

each module addSignificance value to the users by reducing cost

improving process and increase productivity.

My software deal into fast crisp service to the member of the

institute by providing them good facilities with in a less time.

It can also help to update any changes in customer details or in

transaction details.

It is capable of handling a large database.

User friendly, efficient and less time consuming for both the

users.

Base on these objective I designed my project. However more

valuable suggestions on the above are warmly welcomed.

Objective of this project is to implement , the concept of software

engineering and relate the concept with real life.

Advantages of the proposed system

Less Time Consuming.

Less Paper Work.



Easy Report Generation.

Easy Query Processing.

It Is Fully User Friendly.

Faster Access of Information.



TOOLS & TECHNOLOGIES

Minimum Hardware And Software Requirements

This software will require following Hardware and Softwarerequirements

A) Minimum Hardware Requirements:-

Pentium 4 Computer



Fax Machine

Printer

101 Key keyboard

1GB RAM

Mouse

160GB Hard Disk

B) Minimum Software Requirements:-

Window xpMS-Office

C) Other Requirements:-

Stationery

customers



WHY USEC++?

C++ isa superset of c with features designed to support oops. OOP is a

new way of organizing code and data that promises increased control

over the complexity of the software development process.



Yet, C being a structured programming language offered

the ease of software development but failed to support maintenance of

large code.

With C++, it is much easier to build and maintain a really big code.

Object Oriented Programming is centeredon new concepts such as

Objects, Classes, Polymorphism, Inheritance, etc.

It is well-suited paradigm for the following: -

Modeling the real-world problem as close as possible to the user’s

perspective

Interacting easily with computational environment using familiar

metaphors

Constructing reusable software components and easily extendable

libraries

Easily modifying and extending implementations of components

without having to recode everything from scratch

A language’s quality is judged by twelve important criteria. They

are a well defined syntactic and semantic structure, reliability, fast



translation, efficient object code, orthogonal, machine

independence, provability, generality, consistency with commonly

used notations, subsets, uniformity, and extensibility. The various

constructs of OOP languages (such as C++) are designed to

achieve these with ease.

Unlike, the traditional methodology (Function-Oriented

Programming), object-oriented programming emphasizes on the

data rather than the algorithm. In oops, data is

compartmentalized or encapsulated with the associated functions

and this compartment or capsule is called an object.

In the OOP approach, the problem is divided into objects ,

whereas in function-oriented programming the problem is divided into

functions. Although, both approaches adopt the same philosophy of

divide and conquer, OOP conquers a bigger region, while function-

oriented programming is content with conquering a smaller region.

Object-Oriented Programming contains function-oriented

programming and so OOP can be referred to as the superset of



function-oriented programming and hence, it can be concluded that

OOP has an edge over function-oriented programming.

Some of the most prominent features of C++ are classes, operator

and function overloading, free store management, constant types,

references, inline and friend function, inheritance, virtual functions,

streams for console and file manipulations, templates and exception

handling.



Advantage:

Information hiding and data abstraction increase reliability and

help decouple the procedural and representational specification

from its implementation.

Dynamic binding increases flexibility.

Inheritance coupled with dynamic binding enhances the

reusability of code, thus increasing the productivity of a

programmer. Code reuse is possible in conventional language as

well, but object-oriented language greatly enhances the

possibility of reuse.

Object – Orientation provides many other advantages in the

production and maintenance of software; shorter development

time, high degree of code sharing and malleability.



SOFTWAREPRINCIPLES



System Analysis

A. Interaction with user:

1) Get knowledge about existing system of the library

2) Assess the user's requirement and problems faced by them

3) Re-defining the Problem.

4) To assess basic data, transactions of the book.

5) To review the various formats, forms, registers

6) To collect information about member/book.

7) Get the sense of various constraints

B. Software Designing:

1) Preparing control flows.(DFD’s)

2) Data base designing (preparing structures).

Set relationships among attributes of various tables for effective

updating and to remove ambiguity in data.



C. Program designing:

1) Developing algorithm(pseudo code)

2) Designing different input screens

3) Designing Reports

D. Programming:

Writing source code for various modules

Main designing issues:Though it is the matter subjected to vary,

yet some of the major designing issues to be covered which are:-

1) User friendly software through Event-driven techniques,

Forms with control objects.

2) User of controls to provide easy navigation through

different Database and operation.

3) Back up.

4) Security

E. Documentation:



User Manual: For smooth exploitation of software facilities by

user

Technical Manual: For giving knowledge of technical

shortcomings and problems likely to occur and methods to overcome

that besides appraisal of technical features of this system.

A) Testing

B) Installation

C) Training to the users



SOFTWARE LIFECYCLE





Analysis:

Analysis phase delivers requirements specification. Specification

must be carefully checked for suitability, omission, inconsistencies and

ambiguities. In this project the analysis is done with the help of the

managerand staffs after considering the needs of the Student system i.e.

what is the basic need of the Student’sand why it is requiring for the

automation of the institution. After going through the entire

requirement we have come to the next phase of the Software Life Cycle.

Design:

Design is the process of mapping systems requirements

defined during analysis to an abstract representation of a specific-

system implementation, meeting the cost and performance constraints.

The purpose of design phase is to specify a particular software system

that will meet the stated requirements. This project is divided into

modules and their interactions. The modules may then be further

decomposed into sub-modules and procedures until each module can be

implemented easily.



Coding / Implementation:

Once the specification and the design of the software are

over, the choice of a programming language remains as one of the most

critical aspect in producing reliable software. Implementation involves

the actual production of code. Although it is one of the important

phases, it takes only 20% of the total development time. In this project

the generation of program is done with the use of appropriate

programming language i.e. C++.

Testing:

Testing is the process of exercising or evaluating a system

or system component by manual or automated means to verify that it

satisfies the specified requirements. Normally, most of the testing and

debugging is done after the system has been implemented. A large

percentage of errors are discovered during testing originates in the

requirement and design phase.



The techniques that have been proposed for unit testing include the

following: -

Path testing: Each possible path from input to output is traversed

once.

Branch testing: Each path must be traversed at least once.

Functional testing:Each functional decomposition is tested at

least once.

Special Value Testing: Testing for all values assumed to cause

problems.

All the modules that have been developed before and tested individually

are put together – integrated in this phase and tested as a whole

system. After doing this in the project the project will be almost ready

to be delivered.



Maintenance:

Once the system passes all the tests, it is delivered to the

customer and enters the maintenance phase. Any modification made to

the system after initial deliveries are usually attributed to this phase.

Basically in this phase the software will be maintained and this is done

prior to release of software and I have reviewed the software and

assured that all the documentation is available.



FEASIBILITY



FEASIBILITY STUDY

This process of evaluating the options, arriving at the best solution is

what doing a feasibility study is all about. Essentially it means that if it

is proposed to build a new system some preliminary investigation is

done at this stage to find out whether this is actually feasible and viable

to implement.

A Feasibility Study has to look at the following

Need analysis1) Background of the organization : As revealed by the present state

of the organization I realized that organization had no order and

was running without information.

2) Viewpoint oriented analysis: For any medium-sized or large

system, there are usually different types of end-user. Different

people in an organization all have some kind of interest in the

system requirements.

Current member of the institute- they will receive

information from the system.

Manager of the organization where the system is to be

installed-they will be interested in obtaining management

information from the system.

Counter staff in the institution where the system is to be

installed – they will be involved in day-to-day running of the

system



Database administrator-they will be responsible for

integrating system with the software database.

Economic Feasibility:

Once of the attempts to weight the cost of developing

andimplementing a new system, against thebenefits that

would accrue from having the new system in place. The partof feasibility study givesthe top management the economic

justification for a new system.

Technical Feasibility:

Currently the organization is working on manua

System. But the technologies that are going to be required forthe development of new system are MS-Excel as backend and

C++ as front end.

Even working on this technology for development teams will

boost up their working. The eventual user will be comfortable

using this technology. As a result it will lead to growth of the

organization.



Software Testing

Testing:

Testing is the process of exercising or evaluating a system

or system component by manual or automated means to verify that it

satisfies the specified requirements. Normally, most of the testing and

debugging is done after the system has been implemented. A large

percentage of errors are discovered during testing originates in the

requirement and design phase.

A more appropriate definition is:“Testing is the process of executing a program with

the intent of finding errors.”

• Who should Do the Testing ? Testing requires the developers to find errors from their software.It is difficult for software developer to point out errors from own

creations.



• What should We Test ?We should test the program’s responses to every possible input. Itmeans,we should test for all valid and invalid inputs. Suppose a program

requirestwo 8 bit integers as inputs. Total possible combinations are 28x28. If onlyone second it required to execute one set of inputs, it may take 18 hourstotest all combinations. Practically, inputs are more than two and size isalsomore than 8 bits. We have also not considered invalid inputs where somany combinations are possible.

Verificationis the process of evaluating a system or componentto

determine whether the products of a given development phase satisfytheconditions imposed at the start of that phase.

_ Verification and Validation

Validation is the process of evaluating a system or component

during or atthe end of development process to determine whether it satisfies thespecified requirements .

Testing= Verification+Validation

The boundary value analysis test cases for our program with twoinputs

variables (x and y) that may have any value from 100 to 300 are:

(200,100),(200,101), (200,200), (200,299), (200,300), (100,200), (101,200),(299,200) and(300,200). . Each dot represent a test caseand inner rectangle is the domain of legitimate inputs. Thus, for aprogram of nvariables, boundary value analysis yield 4n + 1 test cases



Example-Consider a program for the determination of the nature of roots of aquadratic equation. Its input is a triple of positive integers (say a,b,c)

andvalues may be from interval [0,100]. The program output may haveone of the following words.[Not a quadratic equation; Real roots; Imaginary roots; Equal roots]Design the boundary value test cases.

SolutionQuadratic equation will be of type:ax2+bx+c=0Roots are real if (b2-4ac)>0Roots are imaginary if (b2-4ac)<0Roots are equal if (b2-4ac)=0Equation is not quadratic if a=0

Worst-case testing

If we reject “single fault” assumption theory of reliability and may liketo seewhat happens when more than one variable has an extreme value. Inelectronic circuits analysis, this is called “worst case analysis”. It ismorethorough in the sense that boundary value test cases are a propersubsetof worst case test cases. It requires more effort. Worst case testing for afunction of n variables generate 5n test cases as opposed to 4n+1 testcases for boundary value analysis. Our two variables example will have52=25 test cases



Structural TestingA complementary approach to functional testing is called structural /white box

testing. It permits us to examine the internal structure of the program.

Levels of TestingThere are 3 levels of testing:i. Unit Testingii. Integration Testingiii. System Testing

There are number of reasons in support of unit testing than testing theentire product.

Unit Testing

1. The size of a single module is small enough that we can locate anerrorfairly easily.2. The module is small enough that we can attempt to test it in somedemonstrably exhaustive fashion.3. Confusing interactions of multiple errors in widely different parts of thesoftware are eliminated.





Integration TestingThe purpose of unit testing is to determine that each independentmodule is

correctly implemented. This gives little chance to determine that theinterfacebetween modules is also correct, and for this reason integration testingmust beperformed. One specific target of integration testing is the interface:whetherparameters match on both sides as to type, permissible ranges, meaningand

utilization.

System TestingOf the three levels of testing, the system level is closet to everydayexperiences.We test many things; a used car before we buy it, an on-line cablenetworkservice before we subscribe, and so on. A common pattern in thesefamiliar

forms is that we evaluate a product in terms of our expectations; notwithrespect to a specification or a standard. Consequently, goal is not tofind faults,but to demonstrate performance. Because of this we tend to approachsystemtesting from a functional standpoint rather than from a structural one.Since it isso intuitively familiar, system testing in practice tends to be less formalthan itmight be, and is compounded by the reduced testing interval thatusuallyremains before a delivery deadline.



Validation Testing

It refers to test the software as a complete product

This should be done after unit & integration testing.Alpha, beta & acceptance testing are nothing but the various ways of involving customer during testing.

Testing ToolsOne way to improve the quality & quantity of testing is to make theprocess as

pleasant as possible for the tester. This means that tools should be asconcise,powerful& natural as possible.The two broad categories of software testing tools are :

_ Static _ Dynamic

There are different types of tools available and some are listed below:1. Static analyzers, which examine programs systematically and

automatically.2. Code inspectors, who inspect programs automatically to make surethey adhereto minimum quality standards.3. standards enforcers, which impose simple rules on the developer.4. Coverage analysers, which measure the extent of coverage.5. Output comparators, used to determine whether the output in aprogram is

appropriate or not.6. Test file/ data generators, used to set up test inputs.7. Test harnesses, used to simplify test operations.8. Test archiving systems, used to provide documentation aboutprograms.



CONCLUSION

The entire project work has enlightened me in the following areas:

As present world is going closer & closer, the new emerging technologies &

systems are growing day-by-day, keeping the same in mind this system isdesigned in a very modular way..

This system has the ability to plug into any existing system & can be

considered for the future extensibility in a very flexible way.

Co-operative teamwork always produces effective results.

Constructive feedback improves project quality.

Scheduling a project & adhering to that schedule creates a strong sense of

time management.

Confidence of handling for real life projects has increased to a great extent.



WEB REFERENCE

http://en.wikipedia.org/wiki/Systems_Development_Life_Cycle

http://cab.org.in/Lists/Knowledge%20Bank/Attachments/83/SDLC

.pdf

http://en.allexperts.com/q/Peoplesoft-2100/Data-Flow-Diagram-

Entity-2.htm

https://wiki.ucar.edu/display/sea/Software+Requirements+Specific

ation+%28SRS%29.

http://www.cc.gatech.edu/classes/AY2000/cs3802_fall/

http://www.techwr-

l.com/techwhirl/magazine/writing/softwarerequirementspecs.html

http://www.umsl.edu/~sauterv/analysis/er/er_intro.html

http://www.learn.geekinterview.com/data-warehouse/dw-basics/what-is-data-flow-diagram.html



http://cab.org.in/Lists/Knowledge%20Bank/Attachments/83/SDLC.pdf





http://en.allexperts.com/q/Peoplesoft-2100/Data-Flow-Diagram-Entity-2.htm





https://wiki.ucar.edu/display/sea/Software+Requirements+Specification+%28SRS%29







http://www.techwr-l.com/techwhirl/magazine/writing/softwarerequirementspecs.html



























BIBLIOGRAPHY

Software engineering

A practitioner’s approach, 5th edition by

Roger S Pressman,

Mcgraw Hill ( Internationalediction)

Software Analysis & design

- Awad.

Software Analysis & design

-Lee

Software Engineering, concepts

- Fairley

Documents

Pay Roll Management_001