pyrol system

7/30/2019 pyrol system

1/67

CRYPTOGRAPHY 2013

BANSAL INSTITUTE OF SCIENCE & TECHNOLOGY

BHOPAL (M.P.)

CERTIFICATE

This is to certify that the work embodied in this project work entitled

CRYPTOGRAPHY has been satisfactorily completed by ABHAY

KUMAR (0112CS091004), YOGESH PANDAGRE (0112CS081120),

YOGESH KHARE (0112CS081119) ,PANKAJ GUPTA (0112CS091068) . It

is a bonafide piece of work, carried out under the guidance of Department of

Computer science & Engineering, Bansal Institute of Science &

Technology, Bhopal for the partial fulfillment of the Bachelor of Engineering

during the academic year 2012-13.

Prof. Niket Bhargava Prof. Vijay Lokhande Prof. A. M.

Jain

(Project Guide) (H.O.D) (Principal)

1


2/67

CRYPTOGRAPHY 2013

C.S.E. Dept. C.S.E. Dept. BIST BHOPAL

CRYPTOGRAPHY

A Minor Project ReportSubmitted in Partial fulfillment for the award of

Bachelor of Engineering (B.E.) DegreeIn Computer Science & Engineering

RAJIV GANDHI PROUDYOGIKI VISHWAVIDYALAYA

BHOPAL (M.P.)

MINOR PROJECT REPORT

S ubmitted by

1) ABHAY KUMAR

2) PANKAJ GUPTA

3) YOGESH KHARE

3) YOGESH PANDAGRE

Under the Guidance of

2


3/67

CRYPTOGRAPHY 2013

Prof. Niket Bhargava

DEPARTMENT OF COMPUTER SCIENCE & ENGINEERING

BANSAL INSTITUTE OF SCIENCE & TECHNOLOGY

BHOPAL (M.P.)

MAY- 2013

3


4/67

CRYPTOGRAPHY 2013

ACKNOWLEDGEMENT

Words shall never be able to pierce through the Gamuts of emotions that

are suddenly exposed during the routine of our life. They shall never be able

neither to describe the spirit with which we worked together nor shall they ever

be able to express the feelings we felt towards our guides.

This project was a struggle that was made much more difficult due to

numerous reasons; some of error correction was beyond our control.

Sometimes we were like rudderless boat without knowing what to do next. It

was then the timely guidance that has seen us through all these odds. We would

be very grateful to them for their inspiration, encouragement and guidance in

all phases of the discretion.

It is our pleasure to have the guidance of Prof. Niket Bhargava, and

co guidance ofProf. Ashish Goswami. We thank them and our HOD Prof.

Vijay Lokhande sir and principal Prof. A.M Jain sir for their constant

encouragement and valuable advice during the course of our project.

Submitted by:-

ABHAY KUMAR (0112CS091004)

4


5/67

CRYPTOGRAPHY 2013

ABSTRACT

The bank management system is an application for

maintaining a persons account in a bank. The system provides

the access to the customer to create an account,

deposit/withdraw the cash from his account, also to view

reports of all accounts present. The following presentation

provides the specification for the system.. Traditional methodsinclude doing this by maintaining registers .

PAYROLL MANAGEMENT basically allows an organization to be

able to keep every detail about its employees . This is great

because company can be comfortable and have peace of mind

knowing that it can keep track of all its employees in just few

minutes and without any maintainance of papers.It can also

be used calculate the net salary after the reductions involving

p.f, hra, loan and provide the salary slip easily .

The aim of this project is to develop a easier detailed system

with the objectives as to create the employee database in

lesser time span and also allows modification of data in justone click.

The scope of this project is limited to the activities of the

operations unit of the Employee Details system which include

opening of Employee details and viewing all the details related

to the employee like seeing their salary,loan details.

5


6/67

CRYPTOGRAPHY 2013

This project employs the object oriented approach of software

engineering using appropriate (UML TOOLS) an object oriented

approach. Some of the steps taken are Feasibility study under

which understanding and identifying of existing system and

associated study is conducted, proper analysis and suggested

solution to tackle such problem, designing the new system

through an object oriented software tools (UML) and Coding

which is implemented C++ i.e Object Oriented Technology

INDEX

CHAPTER-1 INTRODUCTION:

1.1 SOFTWARE PROCESS MODEL

8

1.2 FEASIBILITY9

1.3 HARDWARE AND SOFTWARE REQUIREMENT15

1.4 FRONTEND16

CHAPTER-2 ANALYSIS:

2.1 STRUCTURE ANALYSIS

2.1.1 SRS

6


7/67

CRYPTOGRAPHY 2013

23

2.1.2 DATA DICTIONARY29

2.1.3 E-R DAIGRAM31

2.1.4 DATA FLOW DIAGRAM33

2.1.5 STATE TRANSITION DIAGRAM36

2.2 OBJECTORIENTED ANALYSIS

2.2.1 USE CASE DIAGRAM

37

2.2.2 CRCINDEX CARD 38

2.2.3STATE MACHINE DIAGRAM 38

2.2.4 FUNCTIONAL DIAGRAM38

CHAPTER-3 DESIGN:

3.1 STRUCTURE DESIGN

3.1.1 DATA STRUCTURE DESIGN39

3.2 OBJECT ORIENTED DESIGN

3.2.1 CLASS OBJECT DIAGRAM41

7


8/67

CRYPTOGRAPHY 2013

CHAPTER-4 TESTING:

4.1 TEST PLAN42

4.2 TEST STRATEGY

43

4.3 TEST HARNESS

44

4.4 TEST FIXER 45

4.5 TEST CASE

47

CHAPTER-5 DEPLOYMENT:

5.1 USER MANUAL

48

5.2 SCREEN LAYOUTS

50

CHAPTER-6 FUTURE ENHANMENT AND CONCLUSION62

CHAPTER-7 REFERENCES & BIBLIOGRAPY63

8


9/67

CRYPTOGRAPHY 2013

CHAPTER -1

INTRODUCTION:We are engineering the software product PAYROLL MANAGEMENT.

It works as an application to store employees details.

This project is made with a view to give all the details of an employee. It

helps the firm to maintain these records in a proper way.

This project is made with a view to give all the details of an employee.

1.It tells about the joining date of an employee.

2.It tells about the basic salary of an employee

3. It keeps the record of the address, name and telephone number of the

employee.

4. It keeps the track of the designation of an employee such as, whether

an employee is a manager or a superintendent.

5. It records whether an employee taken any kind of loan from the

company.

9


10/67

CRYPTOGRAPHY 2013

SOFTWARE PROCESS MODEL:

This application is based on the WATERFALL Software Model. It is developed and implemented

according to the requirement. This is the rigorous sequential process which is provided by the

WATERFALL Software Model.

WATERFALL MODEL

The waterfall model is a sequentialdesign process, often used in software development

processes, in which progress is seen as flowing steadily downwards (like a waterfall)

through the phases of Conception, Initiation, Analysis, Design,

Construction, Testing and Maintenance.This project is to be developed step by step using modelAGILE the time division for various stages is as follows.

a) REQUIREMENT

b) DESIGN

c) IMPLEMENTATION

d) VERIFICATION

E)MAINTAINENCE

Requirement Analysis : This phase is focused on possible requirements of the system for

the development are captured. Requirements are gathered subsequent to the end user

consultation.

System Software Design: Prior to beginning the actual coding, it is inevitable to understand

what actions are to be taken and what they should like. The requirement specifications are

studied in detail in this phase and the design of the system is prepared. The design

specifications are the base for the implementation and unit testing model phase.

Implementation : Subsequent to receiving the system design documents, the work is shared

into various modules and the real coding is commenced. The system is developed into small

coding units. These units are later integrated in the subsequent phase. Every unit is tested for

its functionality.

System Testing: The modules that are divided into units are integrated into a completesystem and tested for proper coordination among modules and system behaves as per the

10
http://www.wikipedia.org/wiki/Sequencehttp://www.wikipedia.org/wiki/Designhttp://www.wikipedia.org/wiki/Software_development_processhttp://www.wikipedia.org/wiki/Software_development_processhttp://www.wikipedia.org/wiki/Waterfallhttp://www.wikipedia.org/wiki/Analysishttp://www.wikipedia.org/wiki/Software_designhttp://www.wikipedia.org/wiki/Software_testinghttp://www.wikipedia.org/wiki/Software_maintenancehttp://www.wikipedia.org/wiki/Sequencehttp://www.wikipedia.org/wiki/Designhttp://www.wikipedia.org/wiki/Software_development_processhttp://www.wikipedia.org/wiki/Software_development_processhttp://www.wikipedia.org/wiki/Waterfallhttp://www.wikipedia.org/wiki/Analysishttp://www.wikipedia.org/wiki/Software_designhttp://www.wikipedia.org/wiki/Software_testinghttp://www.wikipedia.org/wiki/Software_maintenance


11/67

CRYPTOGRAPHY 2013

specifications. Once the testing is completed, the software product is delivered to the

customer.

Maintenance: It is a never ending phase. Once the system is running in productionenvironment, problems come up. The issues that are related to the system are solved only

after deployment of the system. The problems arise from time to time and need to be solved;

hence this phase is referred as maintenance.

In Royce's original waterfall model, the following phases are followed in order:

The waterfall modelproceeds from one phase to the next in a sequential manner. For

example, one first completes requirements specification, which after sign-off are considered

"set in stone." When requirements are completed, one proceeds to design. The software in

question is designed and a blueprint is drawn for implementers (coders) to followthis

design should be a plan for implementing the requirements given. When the design is

complete, an implementation of that design is made by coders. Towards the later stages of

this implementation phase, separate software components produced are combined to

introduce new functionality and reduced risk through the removal of errors.

Thus the waterfall model maintains that one should move to a phase only when its preceding

phase is completed and perfected. However, there are various modified waterfallmodels

(including Royce's final model) that may include slight or major variations upon this

process.

The process of WATERFALL Model can be understood by following diagram:

11
http://www.wikipedia.org/wiki/Waterfall_model#Modified_modelshttp://www.wikipedia.org/wiki/Waterfall_model#Modified_modelshttp://www.wikipedia.org/wiki/Waterfall_model#Modified_modelshttp://www.wikipedia.org/wiki/Waterfall_model#Modified_models


12/67

CRYPTOGRAPHY 2013

FIG. 1.1 WATERFALL

MODEL

1.2 FEASIBILITY STUDY:

After request clarification, analyst proposes some solutions. After that for

each solution it is checked whether it is practical to implement that solution.

This is done through feasibility study. In this various aspects like whether it istechnically or economically feasible or not. So depending upon the aspect on

which feasibility is being done it can be categorized into four classes:

Technical

Economical

Legal

Operational

12


13/67

CRYPTOGRAPHY 2013

The outcome of feasibility study should be very clear. It should answer the

following issue:

Is there an alternate way to do the job in a better way?

What is recommended?

It consists of following:

This includes the user demonstrable needs and how does a candidate

system meet them?

The result of feasibility customer is a formal proposal. This is simply a

report a formal document detailing the nature and scope of the proposalsolution. The proposal summarizes what is known and what is going to be

done.

1.2.1 Technical Feasibility:

In technical feasibility following issues are taken into consideration:

The required technology C++ is available. Also the resources are available to

work on this technology.

We also have to study about the investment required to develop the software.

The technical issues are raised during the feasibility stage of investigation are:

13


14/67


15/67

CRYPTOGRAPHY 2013

It involves estimating benefits and costs. These benefits and costs may be

tangible or intangible. We are not doing the brief analysis of cost benefit. But

when we go through the rough study we found that manual work in existing

system is very high than proposed system. Proposed system requires lessinvestment, time and manpower as compare to existing manual system. It

concludes that proposed system is technical as well as economically feasible.

The proposed System will save lots of paper work and Facilitate

magnetic record keeping thereby reducing the costs incurred on above heads.

This reduction in cost prompts the company to go for such computer-based

system.

The proposed System will save cost while create new page for the next

organization. It reduce man hour while made the change in the organizations

software. The suggested proposed system will suit the existing software and

hardware . Almost, it reduces cost for implementation. The system is developed

for long consideration so cost will be less when compares to develop the

application for each and every organization.

One time cost:- The system requires one time investment as follows:

Computer Intel 300 MHz: Rs. 23000/-

Inkjet Printer : Rs.

3200/-

UPS & Stabilizer : Rs. 4000/-

Soft wares (Turbo c++, Windows-XP, ): Rs.

45000/-

15


16/67

CRYPTOGRAPHY 2013

Total : (approx.) Rs. 75200/-

Recurring cost ( per month )

Printer cartridge : Rs. 1000/-

Electricity Consumption : Rs. 200/-

Stationary Cost : Rs. 500/-

Total : (approx.) Rs. 1700/-

1.2.3 Operational Feasibility:

Any developed system is operational feasible if

The user is not happy with current system and able to adopt the proposed

system.

In my case the user is really frustrated with the existing system because itcontains lots of manual work & requires more efforts.

16


17/67

CRYPTOGRAPHY 2013

In proposed system time required for overall operation becomes low.

1.2.3 BEHAVIORAL FEASIBILITY

This system helps the user to find in the best usage of resources keeping in

track of all the information about employees thereby reducing the time while

searching the desired details. The available resource can be handling with the

data relation method in order to avoid the redundancy data and give the bettersolution for particular result or data. The proposed system gives the better

performance in the sense of both time and resource.

1.3 HARDWARE AND SOFTWARE REQUIREMENT FOR

RUNNING THE PROJECT:

Hardware Requirement

17


18/67

CRYPTOGRAPHY 2013

The selection of hardware is very important in the existence and

proper working of any software. When selecting hardware, the size and

requirement are also important.

PROCESSOR: P3or Higher

RAM: 512MB

DISK SPACE: 20GB (For Data Storage)

MONITER: (For Displaying Data)

KEYBOARD (For Entering Data)

Software Requirement

The selection of software is very important in the existence and proper working

of

any system.

-Turbo C++ Version 3.0

-Windows XP or higher versions.

1.4 FRONT END :

18


19/67

CRYPTOGRAPHY 2013

FRONT END: C++

Object oriented programming is an approach that provides a way of

modularizing programs by creating partitioned memory area for both

data and functions that can be used for as templates for creating copies

of such modules on demand.

The main reason for inventing OOP was to remove the flaws encountered

in procedural programming.

Object oriented programming treats the data as a critical element in the

program development and does not allow it to flow freely around thesystem. It ties the data more closely to the functions that operate on it

and protects it from accidental modifications from outside functions.

OOP allows decomposition of problem into a number of entities called

objects and builds the data and functions around these objects. How ever

functions of one object can handle other objects.

Some features of object-oriented programming are:

Emphasis is on data rather than the procedure.

For time and higher productivity, programs are divided into objects.

Data structures are designed to characterize the objects.

19


20/67

CRYPTOGRAPHY 2013

* Functions that operate on the data of an object are tied together in

the data structure.

Data is hidden and cannot be accessed by external functions.

Objects may communicate with each other through functions.

New data and functions can be easily added as and when required.

It follows bottom -up approach in program design.

Benefits of OOPS

Oops offers several benefits to both the program designer and the user.

Object orientation contributes to the solution of many problems

associated with the development and quality of software products. The

new technology promises greater programmer productivity, better quality

of software and lesser maintenance costs. The principle advantages are:

Through inheritance, we can eliminate redundant code andextend the use of existing classes.

We can build programs from the standard working modules thatcommunicate with each other. This leads to saving ofdevelopment time and higher productivity.

The principle of data hiding helps the programmer to buildsecure programs that cannot be invaded by code from otherparts of the program.

Its possible to have multiple instances of an object to co-existwithout any interference

Its possible to map objects in the problem domain to those inthe program.

Its easy to partition the work in a project based on objects.

20


21/67

CRYPTOGRAPHY 2013

The data centered design approach enables us to capture moredetails of a model in implement able form.

Object oriented systems can be easily upgraded from small tolarge systems.

Message passing techniques for communication between objectsmakes the interface description with external systems muchsimpler.

Software complexity can be easily managed.

OOP can be regarded as the ultimate paradigm for the modeling of

information. The Object oriented programming approach is based on

certain concepts that include:

1. Objects

2. Classes

3. Data abstraction

4. Data encapsulation

5. Modularity

6. Inheritance

7. Polymorphism

Objects

Objects are the basic run time entities in an object-oriented system. They

may represent a system, a place, and a table of data or any item that a

program has to handle. Programming problem is analyzed in terms of

21


22/67

CRYPTOGRAPHY 2013

objects and the terms of communication between them. Program objects

must be chosen in such a way that they match closely with the real world

objects take up space in the memory and have an address. When a

program is executed objects interact by sending messages to each other.

Classes

As said earlier objects contain data and code to manipulate data. The

entire set of data of and code of an object can be made user defined data

type with the help of a class.

In fact, objects are variables of the type class. Once a class has been

defined we can create any number of objects belonging to that class.

Each object is associated with the data of type class with which they are

created. A class is thus a collection of objects of similar type.

Data abstraction

Abstraction is the concept of simplifying the real world problems into its

essential elements.Data abstraction refers to the act of representing

essential features without including the background details or

explanations. Classes use the concept of data these attributes. They

encapsulate all the essential properties on the objects that are to be

created. The attributes are some times called data members because

22


23/67

CRYPTOGRAPHY 2013

they hold information. The functions that operate on these attributes are

called member functions.

Since these functions use the concept of data abstraction they are known asabstract data types.

Data encapsulation

The wrapping up of data and the functions into a single unit is known as

encapsulation.

Encapsulation is the most fundamental concept of OOP and an important

feature of class. The data is not accessible to the outside world and only

to those functions that are wrapped inside the class. These functions

provide the interface and the objects data and the program. This

insulation of data from the direct access of the program is called data

hiding.

Modularity

The act of partitioning a program into individual components is calledmodularity. The justification for partitioning a program is that:

23


24/67

CRYPTOGRAPHY 2013

1. It reduces its complexity to some degree

2. It creates a number of well-defined documented boundaries within

the program

A module is a separate unit in it self. Many modules work hand in hand to

achieve programs goal.

Inheritance

Inheritance is the process by which one class inherits the properties of

objects another class. In object oriented programming the concept of

inheritance provides the idea of reusability. We can use additional

features to an existing class without modifying the original class. This is

possible by deriving a new class from the existing one.

Role of inheritance in Object oriented programming can be given as

follows:

24


25/67

CRYPTOGRAPHY 2013

1. The capability of inheritance to express the inheritance

relationship that ensures the closeness with the real world

models.

2. The second one is the idea of reusability, which allows the

addition of new features to an existing class without modifying

it.

3. The third is the transitive nature.

If a class A inherits the properties of another class B, then all the subclasses

of a will automatically inherit all the properties of B.

This is called the transitive nature of inheritance.

Polymorphism

25


26/67

CRYPTOGRAPHY 2013

Polymorphism is the ability of a message to be processed in more than

one form. Its the concept that supports the capability of an object of a

class to behave differently in response to a message or an action.

Polymorphism is thus the property by which the same message can be

sent to objects of several different classes.

Polymorphism plays an important role in allowing objects having different

internal structures to share the same external internal interface. This

means that a general class of operations may be accessed in the same

manner even though specific actions associated with each operation may

differ. Polymorphism is extensively used to implement inheritance.

Applications of C++

C++ is a versatile language for handling very large programs. It issuitable for virtually any programming task including development of

editors, compilers, databases, communication systems and any real life

application systems.

Since C++ allows us to create hierarchy related objects, we can build

special object oriented libraries, which can be used later by many

programmers.

While C++ is able to map the real world problem properly, the c part of

C++ gives the language the ability to get close to machine level details.

26


27/67

CRYPTOGRAPHY 2013

C++ programs are easily maintainable and expandable.

CHAPTER -2

ANALYSIS:

27


28/67

CRYPTOGRAPHY 2013

2.1 STRUCTURAL ANALYSIS:

2.1.1 SOFTWARE REQUIREMENT SPECIFICATION:

Objective:

Considering the stress and time taken to maintain employee details on papersand to view their details . The development of a well structure Payroll

Management system will allow organization to perform objectives like, creating

a management system that is easily accessible by the company easily, and will

easily provide all information regarding their employees without wasting paper

and time. Promote efficient and effective management for the companies by

focusing on those services that still require physical presence in organization.

Keep a detailed log of employees salary with the reductions . Generate the

salary slip of employees .

1.Introduction:

28


29/67

CRYPTOGRAPHY 2013

Purpose: - Payroll Management system is an service provided for the employees and their

company. It is an interactive service for information seekers of company. It is easy to access.

1.1) Goals and Objective:

It is easy for adding new employees new users .

It maintains a central base of information.

It allows easy modification of details.

List of employees will be displayed.

1.2) System statement of scope:

Major inputs include all the particulars like customers name,Address,contact no.,userid etc.for all the employees of the company. Inputs include details of customer . Outputs include

information about net salary, basic salary, loan and employees profile .

1.3) System Context:

Creating software for payroll and implementing it on computer is really a

great idea both for the information seekers as well as for employees. It

greatly helps the company as information about employees is available

at any time . It increases the ease both for managers.

1.4) Administrator:

Administrator is the central user of the payroll system. He is the only

person who can add, delete and update the whole database present on

the system. He can control various operations to be used by employee .

All the moves could be viewed by administrator at any instance.

29


30/67

CRYPTOGRAPHY 2013

1.5)Module functioning:

1.5.1) New employee

Administrator can add the new employees; .

He can also add the employees details such as name,address ,phone no.

This module contains the profile details of an employee.

1.5.2) Display employee

It can be used to view the employee details saved already.

It can viewed using his/her employee id.

1.5.3) List of employees

This module consist list of all the employees whose data has been saved

already.

30


31/67

CRYPTOGRAPHY 2013

1.5.4) Salary slip:

This module provides the salary details of an employee.

Given the basic salary it calculates hra,p.f,d.a .

It also calculates the net salary using above parameters.

1.5.5) Edit:

This module is used to modify the existing user details.

It is use to delete a data entry of employee already saved.

1.5.6)Exit:

This module gets the user to the main menu.

Informal Document:

SYSTEM-Payroll management

R1:EMPLOYEE

enter details of Employee:

R1.1: name

R1.2: address

R1.3: phone no

R1.4: day of joining

31


32/67

CRYPTOGRAPHY 2013

R1.5: loan

R2: Edit services

R2.1: delete information

R2.1.1: delete employee

R2.2: update information

R2.2.1: delete employees record.

32


33/67

CRYPTOGRAPHY 2013

2.1.2 DATA DICTIONARY:

EMPLOYEE BASIC DETAILS - SCHEMA

SNO NAME DATA TYPE

1 EMP ID INT

2 DESIGNATION CHAR[16]

3 ADDRESS CHAR[31]

4 PHONE NO INT

5 NAME CHAR[26]

LOAN DETAILS

33


34/67

CRYPTOGRAPHY 2013

SNO NAME DATA TYPE

1 EMP ID INT

2 LOAN INT

GRADATION DETAILS SCHEMA

SNO NAME DATATYPE

1 EMP ID INT

2 DESIGNATION CHAR[20]

34


35/67

CRYPTOGRAPHY 2013

ER DIAGRAM FOR PAYROLL MANAGEMENT

35

EMPLOYEE

empna

designatio

n

phone

empid

adrress

take

s

loan

empid amount

Work

in

company

empid

tn_durati

on


36/67

CRYPTOGRAPHY 2013

36

giv

en

Prom

ot-ed

salary

basichra

gradation

empid

giv

en

Promot-ed

salary

basichra

Ca,da

empid

pf

gradation

empid designation


37/67

CRYPTOGRAPHY 2013

2.1.4. DATA FLOW DIAGRAMS:

A data flow diagram (DFD) is a graphical representation of the "flow" of data

through an information system, modeling its process aspects. Often they are a

preliminary step used to create an overview of the system which can later be

elaborated. DFDs can also be used for the visualization ofdata

processing (structured design).

A DFD shows what kinds of information will be input to and output from the

system, where the data will come from and go to, and where the data will be

stored. It does not show information about the timing of processes, or

information about whether processes will operate in sequence or in parallel.

37

Profile

Details of

employee

Admin of

company
http://en.wikipedia.org/wiki/Information_systemhttp://en.wikipedia.org/wiki/Data_visualizationhttp://en.wikipedia.org/wiki/Data_processinghttp://en.wikipedia.org/wiki/Data_processinghttp://en.wikipedia.org/wiki/Information_systemhttp://en.wikipedia.org/wiki/Data_visualizationhttp://en.wikipedia.org/wiki/Data_processinghttp://en.wikipedia.org/wiki/Data_processing


38/67

CRYPTOGRAPHY 2013

Fig. 2.2 0th Level DFD of payroll management

38


39/67

CRYPTOGRAPHY 2013

Fig. 2.3 1st Level DFD of My Account

39


40/67

CRYPTOGRAPHY 2013

PAYROLL MANAGEMENT

Fig. 2.4 2nd Level DFD of My Account

2.1.5 STATE TRANSITION DIAGRAM:

40

ADMI

N

SYSTE

M

EMP.D

New

emp.

List of

employees

MODIFICATI

ON

DELETE

RECORD


41/67

CRYPTOGRAPHY 2013

2.2 OBJECT ORIENTED ANALYSIS:

2.2.1 USECASE DIAGRAMS:

A use case diagram at its simplest is a representation of a user's

interaction with the system and depicting the specifications of a use case.

A use case diagram can portray the different types of users of a system

and the various ways that they interact with the system. This type of

diagram is typically used in conjunction with the textual use case and will

often be accompanied by other types of diagrams as well.

Due to their simplistic nature, use case diagrams can be a good

communication tool for stakeholders. The drawings attempt to mimic the

real world and provide a view for the stakeholder to understand how the

system is going to be designed. Siau and Lee conducted research to

determine if there was a valid situation for use case diagrams at all or if

they were unnecessary. What was found was that the use case diagrams

conveyed the intent of the system in a more simplified manner

to stakeholders and that they were "interpreted more completely thanclass diagrams". The purpose of the use case diagrams is simply to

41

VIEWSALARY

SLIP

SLIP


42/67

CRYPTOGRAPHY 2013

provide the high level view of the system and convey the requirements in

layman's terms for the stakeholders. Additional diagrams and

documentation can be used to provide a complete functional and

technical view of the system.

admin

42

PAYROLL

SYSTEM

Maintains emp

details

Calculates emp

salary


43/67

CRYPTOGRAPHY 2013

Admin

Fig 2.7: Use Case level

CHAPTER -3

DESIGN:

3.1 STRUCTURE DESIGN:

3.1.1 DATA STRUCTURE DESIGN:

43

Modifies emp

details

View emp

details


44/67

CRYPTOGRAPHY 2013

Database design is the process of producing a detailed data model of a database. This

logical data model contains all the needed logical and physical design choices and physical

storage parameters needed to generate a design in a Data Definition Language, which can

then be used to create a database. A fully attributed data model contains detailed attributes

for each entity.

The term database design can be used to describe many different parts of the design of an

overall database system. Principally, and most correctly, it can be thought of as the logical

design of the base data structures used to store the data. In the relational model these are the

tables and views. In an object database the entities and relationships map directly to object

classes and named relationships. However, the term database design could also be used to

apply to the overall process of designing, not just the base data structures, but also the forms

and queries used as part of the overall database application within the database managementsystem (DBMS).

The process of doing database design generally consists of a number of steps which will be

carried out by the database designer. Usually, the designer must:

Determine the relationships between the different data elements.

Superimpose a logical structure upon the data on the basis of these

relationships

3.1 TABLE FOR NEW EMPLOYEE:

ATTRIBUTE DOMAIN

EMP ID Integer

44


45/67

CRYPTOGRAPHY 2013

ADDRESS Char

JOIN _date DATE

BASIC SALARY FLOAT

LOAN FLOAT

NAME CHAR

GRADE CHAR

3.2 TABLE FOR SALARY SLIP :

ATTRIBUTE DOMAIN

NET SALARY FLOAT

HRA FLOAT

P.F FLOAT

D.A FLOAT

3.1.4. CLASS OBJECT DESIGN:

45

EMPLOYEE DETAILS

*EMP DETAILS

*EMP DATE OF JOIN

*EMP ADDRESS

*EMP PHONE NO

*DESIGNATION

*EMP ID


46/67

CRYPTOGRAPHY 2013

Service provider

CHAPTER 4

TESTING:

Software testing is an investigation conducted to provide stakeholders with information

about the quality of the product or service under test. Software testing can also provide an

objective, independent view of the software to allow the business to appreciate and

understand the risks of software implementation. Test techniques include, but are not limited

to, the process of executing a program or application with the intent of finding software bugs

(errors or other defects).

46

ADMINISTRATOR

*CALCULATE EMPS NET PAY()

*RETRIEVE EMP DETAILS()


47/67

CRYPTOGRAPHY 2013

Software testing can be stated as the process of validating and verifying that a computer

program/application/product:

meets the requirements that guided its design and development,

works as expected,

can be implemented with the same characteristics,

and satisfies the needs of stakeholders.

Software testing, depending on the testing method employed, can be implemented at any

time in the development process. Traditionally most of the test effort occurs after the

requirements have been defined and the coding process has been completed, but in the Agile

approaches most of the test effort is on-going. As such, the methodology of the test isgoverned by the chosen software development methodology.

Different software development models will focus the test effort at different points in the

development process. Newer development models, such as Agile, often employ test-driven

development and place an increased portion of the testing in the hands of the developer,

before it reaches a formal team of testers. In a more traditional model, most of the test

execution occurs after the requirements have been defined and the coding process has been

complete

4.1 TEST PLAN:-

The Software Test Plan (STP) is designed to prescribe the scope,approach, resources, and schedule of all testing activities. The plan mustidentify the items to be tested, the features to be tested, the types of

testing to be performed, the personnel responsible for testing, the

47


48/67

CRYPTOGRAPHY 2013

resources and schedule required to complete testing, and the risksassociated with the plan.

Scope of the test plan

Approach of the test plan

Schedule of the test plan

Items to be tested

Features to be tested

Type of testing to be perform.

1.Scope of the test plan:-Scope of the test plan is to cover allmodules and our software to be tested completely. So that we will knowhow much our project is efficient.

2.Approach of the test plan:-We will apply different types

of testing to test our project such as high level testing ,low leveltesting,alphatesting,beta testing etc.

3.Schedule of the test plan:- Schedule of all testingactivities will be in that manner so that the testing will be easy n in flowand it will start from a small level to higher level.

4.Items to be tested:-All items which will be shown to user haveto be tested.

48


49/67

CRYPTOGRAPHY 2013

4.2 TEST STRATEGY:

Development

Process

Type of

Testing

Description White

box/Black

box

Client Needs Acceptance

Testing

Testing conducted

by a customer to

verify the system

meets the

acceptancecriteria of the

requested

application.

Black Box

Requirements System Testing Verify that the

entire software

system satisfies

the requirements.

Black Box

Design Integration

Testing

Tests the

interaction of

small modules of a

software

application.

White or

Black Box

Code Unit Testing Tests a small unit

(i.e. class) of a

software

application,

separate from

other units of the

application.

White Box

49


50/67

CRYPTOGRAPHY 2013

4.2.1. System Test:

The System tests will focus on the behavior of the management system.

User scenarios will be executed against the system as well as screen

mapping and error message testing. Overall, the system tests will test

the integrated system and verify that it meets the requirements defined

in the requirements document.

4.2.2. Performance Test

Performance test will be conducted to ensure that the salary calculation

expectations and does not exceed the specified performance criteria.

During these tests, calculated result will be measured under heavy stress

and/or volume.

4.2.3. Documentation Test:

Tests will be conducted to check the accuracy of the user documentation.

These tests will ensure that no features are missing, and the contents can

be easily understood.

4.2.4. Beta Test:

College will beta tests the new salary calculation system and will report

any defects they find. This will subject the system to tests that could not

be performed in our test environment.

4.2.6. User Acceptance Test:

Once the system is ready for implementation, the company will perform

User Acceptance Testing. The purpose of these tests is to confirm that

50


51/67

CRYPTOGRAPHY 2013

the system is developed according to the specified user requirements and

is ready for operational use.

4.3TEST HARNESS:

A test harness or automated test framework is a collection ofsoftware and test data

configured to test a program unit by running it under varying conditions and monitoring its

behavior and outputs. It has two main parts: the test execution engine and the test script

repository.

Test harnesses allow for the automation of tests. They can call functions withsupplied parameters and print out and compare the results to the desired value. The test

harness is a hook to the developed code, which can be tested using an automation

framework.

A test harness should allow specific tests to run (this helps in optimizing), orchestrate

a runtime environment, and provide a capability to analyses results.

The typical objectives of a test harness are to:

Automate the testing process.

Execute test suites of test cases.

Generate associated test reports.

A test harness may provide some of the following benefits:

Increased productivity due to automation of the testing process.

Increased probability that regression testing will occur.

Increased quality of software components and application.

Ensure that subsequent test runs are exact duplicates of previous ones.

Testing can occur at times that the office is not staffed (e.g. at night)

A test script may include conditions and/or uses that are otherwise difficult tosimulate (load, for example)

An alternative definition of a test harness is software constructed to facilitate integration

testing. Where test stubs are typically components of the application under development and

are replaced by working component as the application is developed (top-down design), test

harnesses are external to the application being tested and simulate services or functionality

not available in a test environment.

For example, if you're building an application that needs to interface with an application

on a mainframe computer but none is available during development, a test harness maybe

built to use as a substitute. A test harness may be part of a project deliverable. Its kept

51
http://wiki/Softwarehttp://wiki/Test_execution_enginehttp://w/index.php%3Ftitle=Test_script_repository&action=edit&redlink=1http://w/index.php%3Ftitle=Test_script_repository&action=edit&redlink=1http://wiki/Test_automationhttp://wiki/Test_Automation_Frameworkhttp://wiki/Test_Automation_Frameworkhttp://wiki/Regression_testinghttp://wiki/Softwarehttp://wiki/Test_execution_enginehttp://w/index.php%3Ftitle=Test_script_repository&action=edit&redlink=1http://w/index.php%3Ftitle=Test_script_repository&action=edit&redlink=1http://wiki/Test_automationhttp://wiki/Test_Automation_Frameworkhttp://wiki/Test_Automation_Frameworkhttp://wiki/Regression_testing


52/67

CRYPTOGRAPHY 2013

outside of the application source code and may be reused on multiple projects. Because a test

harness simulates application functionality - it has no knowledge of test suites, test cases or

test reports. Those things are provided by a testing framework and associated automated

testing tools.

4.4TEST FIXTURE:

Test fixture refers to the fixed state used as a baseline for running tests in software testing.

The purpose of a test fixture is to ensure that there is a well known and fixed environment inwhich tests are run so that results are repeatable. Some people call this the test context.

Examples of fixtures:

Loading a database with a specific, known set of data

Erasing a hard disk and installing a known clean operating system installation

Copying a specific known set of files

Four phases of a test:

Set up -- Setting up the test fixture.

Exercise -- Interact with the system under test.

Verify -- Determine whether the expected outcome has been obtained.

Tear down -- Tear down the test fixture to return to the original state.

Use of fixtures

Some advantages of fixtures include separation of the test initialization (and

destruction) from the testing, reusing a known state for more than one test, and specialassumption by the testing framework that the fixture set up works.

52
http://wiki/Software_testinghttp://wiki/Software_testing


53/67

CRYPTOGRAPHY 2013

CHAPTER 5

DEPLOYMENT:

5.1 USER MANUAL:

User manual define the work of each menu in our system.

At main menu, you have 6 choices namely:

1.New employee. - helps to add new record.

2.Display employee.- helps to view record which already exist.

3.List of employee. gives the list of all employees which already exist.

4.Salary of employee. calculates the net salary.

5.Edit.

53


54/67

CRYPTOGRAPHY 2013

0.Quit

Enter your choice:

*If you choose option 1,It is To write the Record of an Employee.

*If you choose option 2, It displays all the information of an employee.

*If you choose option 3, It shows the list of an employee.

*If you choose option 4,It gives us the basic salary of an employee.

*If you choose option 5, It takes the user to edit menu . It gives us twooptions

a)Modify-Choose 1 to modify the employee record.

b)Delete-Choose 2 to delete the employee record.

*If you choose option 0,It exits.and leaves the current menu.

54


55/67

CRYPTOGRAPHY 2013

5.2 SCREEN LAYOUT:

55


56/67

CRYPTOGRAPHY 2013

Registration Form:

56


57/67

CRYPTOGRAPHY 2013

Home Page:

57


58/67

CRYPTOGRAPHY 2013

Expenses Category:

58


59/67

CRYPTOGRAPHY 2013

Income Category:

59


60/67

CRYPTOGRAPHY 2013

Expenses:

60


61/67

CRYPTOGRAPHY 2013

Income:

61


62/67

CRYPTOGRAPHY 2013

Cash Book:

62


63/67

CRYPTOGRAPHY 2013

Bank Book:

63


64/67

CRYPTOGRAPHY 2013

Profile:

64


65/67

CRYPTOGRAPHY 2013

CHAPTER 6

FUTURE ENHANCEMENT AND

CONCLUSION:

Every project whether big or small always has some or the

other aspect in which it could be expanded, some more feature

can be joined to make that project even more valuable . Our

project also has such aspects.This is now working on

elementary level, it could also be made to work at higher levelWith little enhancements.

* IVRS can be implemented in this project.

65


66/67

CRYPTOGRAPHY 2013

* Enhancement related to management activities can be

made.

CHAPTER 7

REFERENCES AND BIBLIOGRAPHY:

1. Software Engineering: A practitioners approach

Roger.S.Pressman.

2. An object oriented approach

E.Balagurusuamy

66


67/67

CRYPTOGRAPHY 2013

Documents

pyrol system