Project Report Neerav

7/31/2019 Project Report Neerav

1/107

ELECTION VOTINGSYSTEM

SUBMITTED BY:

NAME- KUMAR NEERAVREGISTRATION NO. - 581270

DATE OF SUBMISSION:

UNDER THE GUIDANCE OF: Mrs. Arpana Chaturvedi

Submitted in partial fulfillment of the requirementsfor qualifying DOEACC A Level.

Name & Address of the accredited institute:

JAGANNATH INSTITUTE OF MANAGEMENT & SCIENCESMATHURA ROAD

NEW DELHI
http://www.go2pdf.com/


2/107

- - 2 - -

Table of Contents: -

S. No. Topics Page No.

1 Acknowledgement

Certificate

34

2 Objective of the Project

Scope Of the Project

56

3 Theoretical Background 7

4Definition of Problem

10

5 System Analysis and Design

Feasibility Study

Project Life Cycle

Design

12

6 System Planning (PERT CHART) 24

7 Methodology 27

8Hardware & Software Requirement

31

9 Cost & Benefit Analysis 33

10 Life Cycle of The Project 35

11 System Testing & Implementation 44

12 Screenshots 48

13 Documentation 53

14 Conclusion 101

15 Future Scope of the Project 103

16 List of Table

List of Figures

Data Dictionary

105105106

REFRENCES 107


3/107

- - 3 - -

ACKNOWLEDGEMENT

I would like to thanks to all my guides who really acted as pillars to help my way

throughout this project that has led to successful and satisfactory completion of this study

of this project.

Firstly I would like to thanks my project incharge M rs. Arpana Chaturvedi under

whose able guidance and motivation this work has been performed.

The inspiration of the faculty members of the Computer Science Department of JIMS

MATHURA ROAD enabled me to make a thorough study of this subject.

Last but not the least, no acknowledgement will be complete without mentioning my

family and friends. They have also supported me throughout the development projects.

NAME: KUMAR NEERAV

REG. NO.: 581270


4/107

- - 4 - -

CERTIFICATE

This is to certify that the Project entitled, ELECTI ON VOTI NG SYSTEM

is a bona-fide work done by Mr. KUMAR NEERAV

(DOEACC Registration No: 581270) in partial fulfillment of A Level

examination and has been carried out under my direct supervision and

guidance. This report or a similar report on the topic has not been submitted for

any other examination and does not forma part of any other course undergone

by the candidate.

Signature of Guide / Supervisor

Name: Arpana chaturvedi

Place: New Delhi

Designation: Sr. lecturer

Date: 28-08-2010

Address: Jagannath I nstitute of M anagement Sciences.


5/107

- - 5 - -

Objective of the Project

Today IT field is emerging day by day. The process is going very fast everyday.

Everything is being done on a single click. In ancient days there were a register or a diary

to maintain a record. But today every work is done by the computer and with a great

security. And this process is always developing day by day.

In this fast growing world of IT I just want to help out the industry with making of a

small software naming ELECTION VOTING SYSTEM. This software will keep up the

updated data of the all the voters and candidates in the voting system, etc. This will keep

up the data till then you want to keep it and always allow you to update the changes.

So, thats all from the introduction of the software. Hope you like my software.


6/107

- - 6 - -

SCOPE OF THE PROJECT

Today, IT industry is known as word of magic. No doubt it brings a universal change in

society. The existing manual system is very tedious; therefore this system is used to get

the existing system more efficient and fast.

The proposed system aims to develop a system that helps to manage all

drawbacks of the existing system. The system has a user friendly environment where the

end user can perform all the activity. Even if the user has little knowledge of computers

he/she can easily operate.

The proposed system has the following objectives to be achieved.

User Friendly Environment.

Less Space.

Fast Retrieval.

Easy to Operate.

Accuracy.

Cost Reduction.


7/107

- - 7 - -

THEORETICAL

BACKGROUND


8/107

- - 8 - -

The main objective of the ELECTI ON VOTI NG SYSTEM is to perform all the

functions or operations accurately. It overcomes all the problems that we have in our

existing system. Our existing system is as follows:

I. Redundancy of data: - when the data values are stored repeatedly in multiple

copies in the database it is known as redundancy of data. Multiple copies of the same data

serve no useful purpose. On contrary it wastes expansive storage space besides

introducing other types of problem. Due to this, our database becomes lengthy and

difficult to maintain. If there is duplication of data, then there is a possibility of

inconsistency of data. Due to the above problem, it is very difficult to handle thedatabase. For example, if a passenger generates a query and there is duplication of data, it

is impossible to processing the passengers query.

II. Update Problem:- The updation problem is further categorized into three

category:-

a. I nsertion Problem: - In manual record keeping system the user may enter

the irrelevant values or data, manual system not force any constraints. Therefore Insertion

problem implies writing of wrong, irrelevant data into the table. This leads to inaccuracy

or inconsistency of data into the tables. Thus the new computerized system checks that

the right data is entered into the table or not, or gives the error when the user input the

wrong data.

b. Updation Problem: - In the manual record keeping system there is a

problem arise when the user update the data, due to duplicacy of the record the user faces

many difficulties because if the user want to update one record the user is forced update

all the duplicate records of that, but practically it is not possible to change all the

duplicate records this leads to in accuracy in the result.

Deletion Problem: - In the existing system, there may be a possibility of duplication of

records. If the user wants to cancel his/her record, then he/she want to delete all the

duplicate records. Practically it is not possible to delete all existing duplicate record.


9/107

- - 9 - -

Apart of duplication problem and updation problem, there is another problem that is, our

existing system is very slow. The process of inserting, updating or deleting of records is

limited to speed of operator. And maintaining registers or papers is very difficult there is

need of extra storage space and person who maintain the registers of records. There are

more chances of loses of records during handling of records


10/107

- - 10 - -

DEFINATION OF PROBLEM


11/107

- - 11 - -

The current system is not organized. It is a system based on more of manual work.

The main idea behind this system is to save ELECTION VOTING SYSTEM records

with their request related to the voters and the candidates. The speed of the system

depends on the human speed.

The conventional system in the ELECTION VOTING SYSTEM is manual where all

the work is done manually by entering the records in the various files and folders.

It is quite cumbersome to proceed through the manual system because, allotments of

various aspects of addition, modification, searching, deletion and also the

maintenance of it take ample time. Maintaining these files requires a lot of space as

well.

Since it is totally depending on human, efficiency is low. There is less security as all

the information is basically kept as hard copy in a register. The computer back up is

also in the file system.


12/107

- - 12 - -

SYSTEM ANALYSIS & DESIGN


13/107

- - 13 - -

Feasibility Study

Feasibility is the measure of how beneficial or practical the development of an

information system will be to an organization. Feasibility analysis is the process of

measuring Feasibility.

Feasibility analysis is a cross life cycle activity, which has to be continuously performed

throughout the system development. By using the creeping commitment approach,

feasibility is measured at different times in the system development. This evaluation

ensures that the project is beneficial and practical to an organization.

Feasibility Test:-

There are four types of Feasibility Test:-

Operational Feasibility

Technical Feasibility

Schedule Feasibility

Economic Feasibility

Operational Feasibility:-

This application is very easy to operate as it is made user friendly. Main consideration is

users easy access to all the functionality of the application.The PIECE formula is used as the basis for analyzing the urgency of the problem.

PIECE stands for:

P- Performance

- Throughput


14/107

- - 14 - -

- Response Time

I- Information

- Input

- Output

- Stored Data

E- Economics

- Cost of Processing Order is high

- Too many employee involve in one operation

C- Control

- Too little control or security

- Effort required for job is excessive

E- Efficiency

- System not co-ordinate with another system

- How end user and manager feel about the system

Technical Feasibility:-

Measure of practically of a specific technical solution and availability of technical

resources. Technology is infeasible and not practical if the organization cant afford the

technology, so make sure that the chosen technology is known and easy to solve. In this

there is no need of any special hardware.

Schedule Feasibility:-

It is measured that how reasonable the project timetable is.


15/107

- - 15 - -

Economic Feasibility:-

Measure of the cost-effectiveness of a project solution.

- Cost Benefit Analysis

As soon as the specific requirements and solutions have been identified, the analysts can

way the cost and benefits of each alternative.

Project Life Cycle:-

The basic objective of software engineering is to: develop methods and procedures for

software development that can scale up for large systems and that can be used to

consistently produce high quality software at low cost and with a small cycle time. That

is, the key objectives are consistency, low cost, high quality, small cycle time, and

scalability.

The basic approach that software engineering takes is to separate the development

process from the software. The premise is that the development process controls the

quality, scalability, consistency, and productivity. Hence to satisfy the objectives, one

must focus on the development process. Design of proper development process and their

control is the primary goal of the software engineering. It is this focus on the process that

distinguishes it from most other computing disciplines. Most other computing disciplines

focus on some type of the product-algorithms, operating systems, databases etc. while

software engineering focuses on the process for producing products.

To better manage the development process and to achieve consistency, it is essential that

the software development be done in phases.

Different Phases of the Development Process:


16/107

- - 16 - -

1) Requirement Analysis:

Requirement analysis is done in order to understand the problem the software system is to

solve. The problem could be automating an existing manual process, developing a new

automated system, or a combination of the two. The emphasis in requirements analysis is

on identifying what is needed from the system, not how the system will achieve its goals.

There are at least two parties involved in the software development-a client and a

developer. The developer has to develop the system to satisfy the clients needs. The

developer does not understand the clients problem domain, and the client does not

understand the issues involved in the software systems. This causes a communicationgap, which has to be adequately bridged during requirements analysis.

2) Software Design:

The purpose of the design phase is to plan a solution of the problem specified by the

requirements documents. This phase is the first step in moving from the problem domain

to the solution domain. Starting with what is needed; design takes us toward how to

satisfy the needs. The design of a system is perhaps the most critical factor affecting the

quality of the software. It has a major impact on the later phases, particularly testing and

maintenance.

The design activity is divided into two phases: System Design and Detailed Design. In

system design the focus is on identifying the modules, whereas during detailed design the

focus is on designing the logic for each of the modules

3) Coding:

The goal of the coding phase is to translate the design of the system into code in a given

programming language. Hence during coding, the focus should be on developing

programs that are easy to read and understand, and not simply on developing programs

that are easy to write.


17/107

- - 17 - -

4) Testing:

Testing is the major quality control measure used during software development. Its basic

function is to detect errors in the software. Testing not only uncover errors introduced

during coding, but also errors introduced during the previous phases. Thus, the goal of

the testing is to uncover requirement, design and coding errors in the programs.

Therefore, different levels of testing are used. Testing is an extremely critical and time

consuming activity. It requires proper planning of the overall testing process. The output

of the testing phase is the test report and the error report. Test report contains the set of

test cases and the result of executing the code with these test cases. The error reportdescribes the errors encountered and the action taken to remove the errors.

One such l ife cycle model is the Waterfall Model. In the tradit ional l i fe

cycle model, called the waterfall model, each phase has well-defined

s t ar t in g a n d e n di n g p o in t s , w i t h c l ea r ly i d en ti f i ab l e d e li v er a bl e s t o t h e

next phase. In practice, it is rarely so simple.

A w a t e r f a l l life cycle model comprises the following phases:

Requirements analysis and specification

Design and specification

Coding and module testing

Integration and system testing

Delivery and maintenance


18/107

- - 18 - -

TheWaterfall M odel

FIG 5.1

Analysis

DESIGN

CODING

IMPLEMENTATION

TESTING


19/107

- - 19 - -

This application used the above described SDLC model for the successful

completion and implementation along with testing of the project.

The Development Lifecycle of a project includes the following 3 stages:

Project Initiation

Project Execution

Project Completion

In Project Init iat ion stage, a team prepares the project plan and f inalizes

the outcome of each stage. Here, the team also prepares a comprehensive

list of tasks, and the project manager assigns responsibil i t ies to the team

members, depending on their skills and abilities.

In the Project Execution stage, the team develops the product. Here, in the

c a se o f o u r p r oj e ct , w e d e ve l op e d t h e E LE C TI O N V O TI N G S Y ST EM .

This stage is further classified as:

Requirements Analysis

High Level Design

Low Level Design

Construction

During this phase, we analyzed the requirements to be fulf il led by the job

s ea rc h u ti l it y & i d en ti fi ed t he p ro ba bl e a pp ro ac h f or m ee ti ng t he se

r e qu i re me n ts . T o i d en t if y t h e r e qu i re m en t s w e s t ud i ed t h e v ar i ou s j o b

s ea rc h u ti li ti e s a t t he v ar io us w eb si t es . a nd f in al l y w e i de nt if ie d t he

following requirements:


20/107

- - 20 - -

Enable a registered user to logon, af ter his/her login details are

validated.

Ena bl e th e us er t o can ac cess t he f in ali ti es p ro vi de d as

authorized by administrator.

Allow the users to quickly search for details.

In the Project Completion stage, we completed the documentation of our

project and giving final touches to our project.

DESIGN:-

In the system design process, the primary objective is to identify user requirements and to

build a system that satisfies these requirements. Design OS system is largely the logical

design. The logical design can be sketched on a paper or on a computer terminal. The

design, also include the physical design elements, describes the data to be inputted, the

process involved in the manipulation of data and the output.

(a) The analyst should specify the file structures, storage devices etc.

(b) The database is also designed in this phase.

(c) Hardware cost, capability, speed, error rates, and other performance

characteristics are specified.

(d) Changes to be made in the organization structure of the firm are outlined.

(e) Input, output, files, forms and procedures are planned.

(f) Finally, standards for testing, documentation and system control are formulated.

E-R Diagram:-

Entity-Relationship (E-R) analysis involves capturing and analyzing of maximum

possible details on data record for building an information system for an orgn. Entity


21/107

- - 21 - -

relationship (E-R) modeling is concerned with the structure of data rather than with the

business rules. Some amount of business rules may also be implied in the E-R model.

Structure of data involves details on entities, attributes & relationships. Business rules

define such characteristics as the domain value of attributes, unique characteristics of

entities, relationships among different entities and validating operations to be performed

during data entry.

E-R analysis involves the following:-

Determining what types of people, places, things and materials interacts with the

business and about which objects the data must be maintained. These objects form

the entities. Determining different characteristics (attributes) of each entity. This involves

identifying only those characteristics which are of interest to the orgn. And for

which the system is being built.

Determining what unique feature such as the primary key can be used to identify

an entity in an entity set.

Determining the associations (relationships) among identified objects.

Entity Relationship M odeling:-

The entity relationship model for data uses three features to describe data. These are the

followings:-

Entities

An entity is a person, place, thing or event of interest to the organization and about which

data are captured, stored or processed. For eg. an Employee is an entity.

Attributes

Various types of data items that describe an entity are known as attributes. For eg. Name,

address, DOB etc are attributes of the entity employee.

Relationship

An association of several entities in a entity relation model is called relationship.


22/107

- - 22 - -

E-R Diagram Symbols:-

Name Symbol M eaning

Rectangle Representedentity set

OvalRepresented

Attributes

Diamond

Representsrelationshipsamong entity sets

Line

Links attributesto entity setsand entity setsto relationships


23/107

- - 23 - -

E-R Diagram:-

Fig 5.2

VoterVotingSystem

Candidates

Uses

Determi-nes

Effects

Name CodeName

Age

Gender

Name Code

Name

PartyName

PartySign

Summary

Vote Show

Edit


24/107

- - 24 - -

SYSTEM PLANNING


25/107

- - 25 - -

PERT CHART: - I t is stands for Project Evaluation and review Technique

Pert chart is a graphical network model that depicts a projects tasks and the relationship

between those tasks. A PERT chart presents a graphic illustration of a project as a

network diagram consisting of numbered nodes(either circles or rectangles) representing

events, or milestones in the project linked by labeled vectors (directional lines)

representing tasks in the project.

The direction of the arrows on the lines indicates the sequence of tasks.

Arrow is used to represents task.

Circle represents the beginning or completion of task.

The PERT chart process includes following steps: -

Identifies the specific activities and milestone.

Determine the proper sequence of the activities.

Construct a network diagram.

Estimate the time required for each activity.

Determine the critical path.

Update the PERT chart as the process progresses.


26/107

- - 26 - -

PERT CHART

Problem FeasibilityDefinition 3 study

5

System analyze &Design

5

Flow chart DF 53

4Data Dictionary

10

Coding

34

ImplementationTesting 9

1 2

3

45

6

7

8 9


27/107

- - 27 - -

METHODOLOGY


28/107

- - 28 - -

C++ is a general-purpose, high-level programming language with low-level facilities.

It is a statically typed free-form multi-paradigm language supporting procedural

programming, data abstraction, object-oriented programming, generic programming

and Runtime Type Identification (RTTI). Since the 1990s, C++ has been one of the

most popular commercial programming languages.

Bjarne Stroustrup developed C++ (originally named "C with Classes") in 1983 at Bell

Labs as an enhancement to the C programming language. Enhancements started with

the addition of classes, followed by, among other features, virtual functions, operator

overloading, multiple inheritance, templates, and exception handling. The C++

programming language standard was ratified in 1998 as ISO/IEC 14882:1998, the

current version of which is the 2003 version, ISO/IEC 14882:2003.

In past years the standards for C++ have been in a state of evolution. This meant that

each compiler vendor handled certain details differently. However, in November

1997, the ANSI/ISO C++ standards committee approved the final draft of what is

now known as Standard C++. (ANSI stands for American National Standards

Institute, and ISO stands for International Standards Institute). Standard C++ adds

many new features to the language, such as the Standard Template Library (STL).

The most popular development environments for C++ are manufactured by Microsoft

and Borland and run on the various flavors of Microsoft Windows.

OOP involves concepts that are new to programmers of traditional languages such asPascal, Basic, and C. These ideas, such as classes, inheritance, and polymorphism, lie

at the heart of object-oriented programming.

History

Stroustrup began work on C with Classes in 1979. The idea of creating a new

language originated from Stroustrup's experience in programming for his Ph.D.

thesis. Stroustrup found that Simula had features that were very helpful for large


29/107

- - 29 - -

software development, but the language was too slow for practical use, while BCPL

was fast but too low-level and unsuitable for large software development. When

Stroustrup started working in Bell Labs, he had the problem of analyzing the UNIX

kernel with respect to distributed computing. Remembering his Ph.D. experience,

Stroustrup set out to enhance the C language with Simula-like features. C was chosen

because it is general-purpose, fast, and portable. Besides C and Simula, some other

languages which inspired him were ALGOL 68, Ada, CLU and ML. At first, the

class, derived class,

strong type checking, inlining, and default argument features were added to C viaCfront. The first commercial release occurred in October 1985.

In 1983, the name of the language was changed from C with Classes to C++. New

features were added including virtual functions, function name and operator

overloading, references, constants, user-controlled free-store memory control,

improved type checking, and a new single-line comment style with two forward

slashes (//). In 1985, the first edition of The C+ + Programming Language was

released, providing an important reference to the language, as there was not yet an

official standard. In 1989, Release 2.0 of C++ was released. New features included

multiple inheritance, abstract classes, static member functions, const member

functions, and protected members. In 1990, The Annotated C+ + Refer ence Manual

was published. This work became the basis for the future standard. Late addition of

features included templates, exceptions, namespaces, new casts, and a Boolean type.

As the C++ language evolved, a standard library also evolved with it. The first

addition to the C++ standard library was the stream I/O library which provided

facilities to replace the traditional C functions such as printf and scanf. Later, among

the most significant additions to the standard library, was the Standard Template

Library.

After years of work, a joint ANSI-ISO committee standardized C++ in 1998

(ISO/IEC 14882:1998). For some years after the official release of


30/107

- - 30 - -

the standard in 1998, the committee processed defect reports, and published a

corrected version of the C++ standard in 2003. In 2005, a

technical report, called the "Library Technical Report 1" (often known as TR1 for

short) was released. While not an official part of the standard, it gives a number of

extensions to the standard library which are expected to be included in the next

version of C++. Support for TR1 is growing in almost all currently maintained C++

compilers.

While the C++ language is royalty-free, the standard document itself is not freely

available

Featuresintroduced in C++

Compared to the C language, C++ introduced extra features, including declarations as

statement, function-like casts, new/ delete, reference type, inline functions, default

arguments, function overloading, namespaces, classes

Features are:-

Identity

Classification

Encapsulation

Data abstraction

Polymorphism

Inheritance

Including all class-related features such as i member function, virtual function,

abstract classes, and constructors, operator overloading, templates, the :: operator,

exception handling, and runtime type identification.


31/107

- - 31 - -

HARDWARE & SOFTWAREREQUIREMENT


32/107

- - 32 - -

Hardware requirements: -

Intel Pentium III processor

Minimum 128 MB RAMRecommended 256 MB RAMMinimum hard disk 20GB

Software requirements: -Windows operating systemC++ complier compatible with the Windows OS

Networking requirements: -Internet connection

The estimated cost of these entire requirements is around 10000 to 12000

There are sufficient cost benefits because computerized system has better efficiency thanmanual system and it also reduces the hiring cost of peons or clerks for maintaining thefiles. In the new system the accessing is much faster than the old manual system so italso beneficial in terms of time.


33/107

- - 33 - -

COST AND BENEFITANALYSIS


34/107

- - 34 - -

COST-BENEFITSANALYSIS

Cost Categories

Equipment cost It includes various items of computing equipment associated withthe work.

Operating cost It includes the expense to run the system. Operating cost dependson the amount of time taken for a process i.e., it includes the costassociated with the day to day operation of the system.

Personnel cost It includes the salaries and wages of analyst, programmers,operators, consultants etc. Salary may be on hourly basis or theentire salary for the duration of the project.

Material cost It includes cost of stationary, paper, ribbons, floppies, CDs etc.

Conversion cost It includes that of designing new forms and procedures,expenditure to prepare the project for using the new system.

Benefit Categories

Performance The criteria emphasize whether the new system has resulted in amarked improvement in the accuracy in access to information.Does the new system provide easier and secure access to theauthorized user

Minimizing cost If the new system is efficient with minimum error, reduction ofstaff is a benefit that should be measured and included in costbenefit analysis


35/107

- - 35 - -

LIFE CYCLE OF THE PROJECT


36/107

- - 36 - -

Data Flow Diagram (DFD):-

Data Flow Diagrams provide a logical model of the system and show the flow of data and

the flow of the logic involved.

Data Flow Diagram have the following characteristics:

They show the passage of data through the system

They focus on the processes that transform incoming data flows (input) into

outgoing data flows (outputs).

The processes that perform this transformation normally create as well as use

data. External entities send and receive data flows from the system.

Data Flow Diagram is also known as Bubble Chart.

Data Flow Diagram supports a top-down approach for analysis.

Symbols used in DFD:-

DFD consist of symbols joined together by a line. There may be a single DFD for entire

system or it may be exploded into various levels, namely level 1, level 2, level 3 etc. Thetop-level diagram is often called a Context Diagram. Context Diagram contains a single

process and it shows an overall review of the system under development.

Four Symbols are used in drawing dataflow diagram. These are:-

External Entities (Source or sink)

Data Flow

Processes

Data Store

External Entities:-

An external entity is a source or a destination of data. External entities are represented by

rectangles. These may be people, program, organization or other entities that enteract

with system.


37/107


38/107

- - 38 - -

CONTEXT LEVEL DFD

Fig 5.3

VOTINGSYSTEMCANDIDATE

VOTER


39/107

- - 39 - -

0 LEVEL DFD

Fig 5.4

VOTER

SYSTEM

VOTERCANDIDATE

EnterDetails

UpdateDetails

MaintainDetails

CheckDetails


40/107

- - 40 - -

1st LEVEL DFD

Fig- 5.5

Voter

1.0

Prepare VoterDetail

2.0

PrepareCandidate

System

3.0

VotingInformation

Detail

Current RecordTable

Candidate

CandidateRegister

VoterRegister

Request Update

Verify

Update


41/107

- - 41 - -

2ND LEVEL DFD

Fig 5.6

1.1

Add VoterName

1.1

Modify VoterName

1.1

Delete VoterName

VoterRequest

VoterRegister

Updated

Data


42/107

- - 42 - -

2.1

Add Candidate

Name

2.2

Modify

CandidateName

2.3

DeleteCandidate

Name

CandidateRequest

CandidateRegister

Updated

Data


43/107

- - 43 - -

3.1

Add Voter

Name

3.2

Add Candidate

Name

3.3

Voting System

VoterRequest

Current RecordRegister

Updated

Data


44/107

- - 44 - -

SYSTEM TESTINGAND IMPLEMENTATION


45/107

- - 45 - -

Testing

The most crucial stage of software development, testing validates the application.

During testing we will be concerned about the inputs and their expected outputs. We

emphasize on the testing where we will input the data and compare the output with

the expected results. At this stage we are not concerned about the process; we are

only looking for correct outputs. Various software testing techniques exists which

take different approaches to test and validate a software.

Tests done on the designed software was to verify the following properties of the

software:

Correctness(satisfaction of the specifications)

Reliability(how well it meets the requirements)

Portability (running in different environments)

Usability (ease with which user can use the software)

Maintainability (modifications after initial release), etc.

Some of them, which we used to test the software, are:

Unit Testing

Unit testing focuses verification effort on the smallest unit of software design The

software component or module. Using component level design description as a guide,

important control paths are tested to uncover errors within the boundary of the


46/107

- - 46 - -

module. Tests of data flow across a module interface were carried out for each

module of the software. Errors in certain modules were detected and later rectified,

thus correcting the dataflow path.

I ntegration Testing

Once all the modules have been unit tested, they are interfaced together and passed

through integration testing using top down integration approach.

Black Box Testing

This approach enables the software engineer to derive sets of input conditions that

will fully exercise all functional requirements for a program. This approach is applied

during the later stages of testing and attention is focused on matching the outputs with

the expected result.

Debugging

Debugging is removing the undesirable errors or bugs from the program. We

implemented debugging using the C++ compiler compatible with the Windows

system in which the application was developed.

During testing the program to tested is executed with the set of test cases and have the

output of the program for the test cases is evaluated to determine if the program is

performing as expected. Due to its approach dynamic if the program is performing as

expected. Due to its approach dynamic testing can only presence of errors in the

program, the exact nature of errors is not usually decided by testing. Testing forms isthe process to determine errors in the program.

Once a program are tested individually then the system as a whole needs to be tested.

During testing the system is used experimentally to ensure that the software does not

fail i.e. it will run according to its specification. The programs executed to check for


47/107

- - 47 - -

any syntax and logical errors. The errors are corrected and test is made to determine

whether the program is doing what supposed to do.

The cautions kept in mind while choosing the tests are:

1. The testing should be based on sound and systematic techniques.

2. Testing should help locate errors, not just detect their presence.

3. Testing should be repeatable, i.e., repeating the same experiment, supplying the

same input data to the same piece of code, produces the same results.

IMPLEMENTATION

System implementation is made up of many activities. The six major activities we are

concerned with in this chapter are coding, testing, installation, documentation,

training and support. The purpose of these steps is to convert the physical system

specification into working and reliable software and hardware, document the work

that has been done, and provide help for current and future users and caretakers of the

system. These steps are often done by other project team members besides analysts,

although analysts may do some programming. In any case, analyst is responsible for

ensuring that all the various activities are properly planned and executed.

In the implementation phase, user actually starts using the system. This phase

therefore involves training the users for using the system and also providing theem

driendly documentation to refer to.

In system implementation, user training is crucial for minimizing resistance to change

and giving the mew system a chance to prove its worth. Training aid such as user

manuals, a data dictionary, job performance aids that communicate information about

the new system and help screens, provide the user with a good start on the new

system.


48/107

- - 48 - -

SCREENSHOTS


49/107

- - 49 - -

Description:-

M enu:-


50/107

- - 50 - -

1: Voting report

2: See M enu


51/107

- - 51 - -

3: Edit


52/107

- - 52 - -


53/107

- - 53 - -

DOCUMENTATION


54/107

- - 54 - -

WHAT IS DOCUMENTATION?

Documentation is a description of the system used to communicate, instruct and

record information for historical, operational or reference purposes. Documents

are very important because they represent the formal information flow of the

present system. Documentation establishes and declares the performance criteria

of system and provides and explanation of how the system can be used.

USES OF DOCUMENTATION

Documentation is used in many ways for different purpose. These are as follows:

Documents facilitate communication about an application between the

technical development personnel and the on technical users.

Documents are necessary during abnormal maintenance, i.e. when a new

programmer has to maintain old software system after the original

programmer of analyst has left the organization.

It is also very helpful to train the users. Good documentation will provide a

self-instructional approach that will allow employees to learn at their own

place.

Documents are also very helpful for trouble shooting when the application-

system breaks down. Documents help corporate management to understand the system sufficiently

to make decisions and to appreciate its financial and resource implications.\

Documentation can provide controls not only internal to the firm, but also

external to the business application such as audit trails.

Documentation also helps in the evaluation process.


55/107

- - 55 - -

//**********************************************************// PROJECT ELECTION-VOTING SOFTWARE

//**********************************************************

#include#include#include#include#include#include#include#include#include

char description(){ delay(2000);cout


56/107

- - 56 - -

ch=getch();if(ch==13)break;

elseif(ch==27)exit(-1);elsecout


57/107

- - 57 - -

int voter_namecode;int voting_status;};

class candidate_status{public:int candidate_namecode;int numVotes;};

class vote{

public :void add_candidate_name(void) ;void delete_candidate_name(void) ;void modify_candidate_name(void) ;void list_of_candidate_names(void) ;void voting(void) ;

void add_voter_name(void) ;void delete_voter_name(void) ;void modify_voter_name(void) ;void list_of_voters_names(void) ;

private :int last_candidate_code(int &num_candidates) ;void delete_candidate_record(int) ;void modify_candidate_record(int) ;void display_candidate_record(int) ;int name_candidate_found(int) ;int candidate_recordno(int, candidate_record&) ;void candidate_sort(void) ;

int last_voter_code(int &num_voters) ;

void delete_voter_record(int) ;void modify_voter_record(int) ;void display_voter_record(int) ;int name_voter_found(int) ;int voter_recordno(int, voter_record &vr) ;void voter_sort(void) ;voter_status* init_voter_status(int &num);candidate_status* init_candidate_status(int &num);} ;


58/107

- - 58 - -

class menu{

public :void main_menu(void) ;private :void edit_menu(void) ;vote v;} ;

void menu :: main_menu(void){

clrscr() ;char ch ;while (1){clrscr();gotoxy(27,4) ;cout


59/107

- - 59 - -

if (ch == '2'){vote v ;

v.list_of_candidate_names() ;gotoxy(1,20) ;cout


60/107

- - 60 - -

gotoxy(28,18) ;cout


61/107

- - 61 - -

gotoxy(28,22) ;cout


62/107

- - 62 - -

void vote :: list_of_voters_names(void){clrscr() ;

voter_record vr;fstream file ;file.open("VOTER.DAT", ios::in|ios::binary) ;file.seekg(0) ;int row = 6 , found = 0 , pageno = 1 ;gotoxy(30,2) ;cout


63/107

- - 63 - -

}elserow++ ;

}if ( !found ){gotoxy(5,10) ;cout


64/107

- - 64 - -

valid = 1 ;gotoxy(1,8) ; clreol() ;gotoxy(1,24) ; clreol() ;

gotoxy(1,25) ; clreol() ;gotoxy(3,25) ;cout


65/107

- - 65 - -

getch();}

} while (!valid) ;do{valid = 1 ;gotoxy(1,12) ; clreol() ;gotoxy(1,24) ; clreol() ;gotoxy(1,25) ; clreol() ;gotoxy(3,25) ;cout


66/107

- - 66 - -

vcode++ ;}do

{gotoxy(1,17) ; clreol() ;gotoxy(1,24) ; clreol() ;gotoxy(1,25) ; clreol() ;gotoxy(5,17) ;cout


67/107

- - 67 - -

fstream file ;file.open("VOTER.DAT", ios::in|ios::binary) ;file.seekg(0,ios::beg) ;

int found=0 ;while (file.read((char *)&vr, sizeof(voter_record))){if (vr.voter_namecode == tcode){found++ ;break ;}}file.close() ;return found ;

}

int vote :: voter_recordno(int tcode, voter_record &vr){voter_record temp;fstream file ;file.open("VOTER.DAT", ios::in|ios::binary) ;file.seekg(0,ios::beg) ;int found=0 ;

while (file.read((char *)&temp, sizeof(voter_record))){found++ ;if (temp.voter_namecode == tcode){vr = temp;break ;}}file.close() ;return found ;

}

void vote :: delete_voter_record(int tcode){voter_record vr;fstream file ;file.open("VOTER.DAT", ios::in|ios::binary) ;fstream temp ;temp.open("temp.dat", ios::out|ios::binary) ;


68/107

- - 68 - -

file.seekg(0,ios::beg) ;while ( !file.eof() ){

file.read((char *)&vr, sizeof(voter_record)) ;if ( file.eof() )break ;if ( vr.voter_namecode != tcode )temp.write((char *)&vr, sizeof(voter_record)) ;}file.close() ;temp.close() ;file.open("VOTER.DAT", ios::out|ios::binary) ;temp.open("temp.dat", ios::in|ios::binary) ;temp.seekg(0,ios::beg) ;

while ( !temp.eof() ){temp.read((char *)&vr, sizeof(voter_record)) ;if ( temp.eof() )break ;file.write((char *)&vr, sizeof(voter_record)) ;}file.close() ;temp.close() ;}

void vote :: delete_voter_name(void){clrscr() ;char t_code[5], ch ;int tcode ;gotoxy(3,25) ;cout


69/107

- - 69 - -

gets(t_code) ;tcode = atoi(t_code) ;if (tcode == 0)

return ;}clrscr() ;if (!name_voter_found(tcode)){gotoxy(5,5) ;cout


70/107

- - 70 - -

cout


71/107

- - 71 - -

valid = 0 ;while (ch == 'Y' && !valid){

valid = 1 ;gotoxy(1,14) ; clreol() ;gotoxy(1,24) ; clreol() ;gotoxy(1,25) ; clreol() ;gotoxy(3,25) ;cout


72/107

- - 72 - -

return ;if ((strlen(vr.age) < 1) || (strlen(vr.age) > 10) || !string_is_number(vr.age)){

valid = 0 ;gotoxy(3,24) ;cout


73/107

- - 73 - -

gotoxy(5,21) ;cout


74/107

- - 74 - -

gets(t_code) ;tcode = atoi(t_code) ;if (tcode == 0)

return ;}clrscr() ;if (!name_voter_found(tcode)){gotoxy(5,5) ;cout


75/107

- - 75 - -

file.seekg(0,ios::beg) ;

for( i = 0; i < size; i++)file.read((char*)&(arr[i]),sizeof(voter_record));file.close() ;

for (i=1; i


76/107

- - 76 - -

void vote :: candidate_sort(void){int i=0,j ;candidate_record *arr, temp ;fstream file ;file.open("CANDIDATE.DAT", ios::in|ios::binary) ;

while (file.read((char *) &temp, sizeof(candidate_record)))i++ ;

file.clear();

arr = (candidate_record*) new candidate_record[i];

int size ;size = i ;

file.seekg(0,ios::beg) ;

for( i = 0; i < size; i++)file.read((char*)&arr[i],sizeof(candidate_record));

file.close() ;

for (i=1; i


77/107

- - 77 - -

file.close() ;}

void vote :: modify_candidate_name(void){clrscr() ;char t_code[5], ch ;int tcode ;gotoxy(3,25) ;cout


78/107

- - 78 - -

if (ch == 'N')return ;modify_candidate_record(tcode) ;

}

void vote :: modify_candidate_record(int tcode){candidate_record cr;int recno ;int revenue;recno = candidate_recordno(tcode,cr) ;int valid, t_code ;

char ch,t_namecode[5] ;gotoxy(71,2) ;cout


79/107

- - 79 - -

cout


80/107

- - 80 - -

{gotoxy(20,16) ; clreol() ;cout


81/107

- - 81 - -



82/107

- - 82 - -

{valid = 0 ;gotoxy(3,24) ;

cout


83/107

- - 83 - -

if (cr.candidate_namecode == tcode){found++ ;

break ;}}file.close() ;return found ;}

void vote :: display_candidate_record(int tcode){ candidate_record cr;fstream file ;

file.open("CANDIDATE.DAT", ios::in|ios::binary) ;file.seekg(0,ios::beg) ;while (file.read((char *)&cr, sizeof(candidate_record))){if (cr.candidate_namecode == tcode){gotoxy(5,3) ;cout


84/107

- - 84 - -

char ch;int num_candidates;tcode = last_candidate_code(num_candidates) ;

tcode++ ;do{clrscr() ;gotoxy(71,2) ;cout


85/107

- - 85 - -

{valid = 1 ;gotoxy(1,10) ; clreol() ;

gotoxy(1,24) ; clreol() ;gotoxy(1,25) ; clreol() ;gotoxy(5,25) ;cout


86/107

- - 86 - -

valid = 1;gotoxy(1,14) ; clreol() ;gotoxy(1,24) ; clreol() ;

gotoxy(1,25) ; clreol() ;

gotoxy(5,25) ;cout


87/107

- - 87 - -

{valid = 1;gotoxy(1,18) ; clreol() ;

gotoxy(1,24) ; clreol() ;gotoxy(1,25) ; clreol() ;

gotoxy(5,25) ;cout


88/107

- - 88 - -

{gotoxy(1,15) ; clreol() ;gotoxy(1,24) ; clreol() ;



89/107

- - 89 - -

gotoxy(3,4) ;cout


90/107

- - 90 - -

row++ ;}if ( !found )

{gotoxy(5,10) ;cout


91/107

- - 91 - -

while (file.read((char *) &temp, sizeof(candidate_record))){found++ ;

if (temp.candidate_namecode == tcode){cr = temp;break ;}}file.close() ;return found ;}

void vote :: delete_candidate_record(int tcode){candidate_record cr;fstream file ;file.open("CANDIDATE.DAT", ios::in|ios::binary) ;fstream temp ;temp.open("temp.dat", ios::out|ios::binary) ;file.seekg(0,ios::beg) ;while ( !file.eof() ){

file.read((char *)&cr, sizeof(candidate_record)) ;if ( file.eof() )break ;if ( cr.candidate_namecode != tcode )temp.write((char *)&cr, sizeof(candidate_record)) ;}file.close() ;temp.close() ;file.open("CANDIDATE.DAT", ios::out|ios::binary) ;temp.open("temp.dat", ios::in|ios::binary) ;temp.seekg(0,ios::beg) ;

while ( !temp.eof() ){temp.read((char *)&cr, sizeof(candidate_record)) ;if ( temp.eof() )break ;file.write((char *) &cr, sizeof(candidate_record)) ;}file.close() ;temp.close() ;}


92/107

- - 92 - -

void vote :: delete_candidate_name(void){clrscr() ;char t_code[5], ch ;int tcode ;gotoxy(3,25) ;cout


93/107

- - 93 - -

return ;delete_candidate_record(tcode) ;gotoxy(5,15) ;

cout


94/107

- - 94 - -

}return cs;

}

void vote::voting(){clrscr() ;

char ch,name[50];int n ,num_voters = 0, num_candidates = 0;int vtr_rec;

voter_status* vs = init_voter_status(num_voters);candidate_status* cs = init_candidate_status(num_candidates);int valid=0;if (num_voters == 0){gotoxy(3,6);cout


95/107

- - 95 - -

for(i = 0; i < num_voters; i++){if (vs[i].voting_status == 0) break;

}if (i == num_voters){gotoxy(3,4);cout


96/107

- - 96 - -

else break;}

n = string_is_number(name);gotoxy(6,5);clreol();

if (n == 0){cout


97/107

- - 97 - -

while(1){

clrscr();

gotoxy(3,24) ;clreol();cout


98/107

- - 98 - -

continue;}int can_rec;

for(can_rec=0; can_rec


99/107


100/107

- - 100 - -

}ch = getche();

delete[] vs;delete[] cs;}


101/107

- - 101 - -

CONCLUSION


102/107

- - 102 - -

This software is a database project with all the basic capabilities a database should have.

This application software is about Voting Management System. It records the list of

candidates, voters etc. The entered records will be saved and can be shown further.

In doing so, an appreciation of project management, communication and consultancy

skills should be acquired, along with a thorough understanding of the development of

windows based applications using C++. I feel that all of these aims were achieved, some

to greater extent than others. I will break down these objectives in the following sections,

and discuss what was achieved from them.


103/107

- - 103 - -

FUTURE SCOPE OF THEPROJECT


104/107

- - 104 - -

Including module to enable the softwares user to keep tracks of

number of Voters & Candidates.

Including a module that adds number of Voters & Candidates.

Including a module to enter the data.

A module in which number of voters polling can be viewed

Including a module to view the available candidates and voters.

Help

Exit.


105/107

- - 105 - -

List of tables

S. No Table No. Disc. Of Table

01 1 Vote

02 2 See Menu

03 3 Edit

List of Figures

S. No. Fig. No. Disc. of Fig. Page No.

01 5.1 WaterfallModel

22

02 5.2 E-R Diagram 28

03 5.3 Context LevelDFD

31

04 5.4 Zero Level

DFD

32

05 5.5 First LevelDFD

33

06 5.6 Second LevelDFD

34


106/107

- - 106 - -

Data Dictionary

Attributes Data type

chpass[20]Candidate_namecode[10]Candidate_name[50]

partyname[50]partysign[50]summary[1]Revenue[100]Age[100]

Area[50]Voter_namecodeVoter_nameAge[10]Gender[10]

Voting_statusnumvotes

charcharintchar

charcharcharcharCharCharIntCharCharChar

Intint


107/107

REFRENCES

1. E-Balaguruswami- Object Oriented Programming With C++

2. DOEACC A level

3. Wikipedia

4. www.cforum.com

5. www.yahoogroups.com

6. System Analysis And Design- Jain & Jain
http://www.cforum.com/http://www.yahoogroups.com/http://www.yahoogroups.com/http://www.cforum.com/

Project Report Neerav

Documents

Transcript of Project Report Neerav