Online Voting System

A

PRO1ECT REPORT
ON
“ONLINE VOTING SYSTEM”
OF
BACHELOR OF TECHNOLOGY BACHELOR OF TECHNOLOGY
IN
Computer Engineering

ABSTRACT
“ONLINE VOTING SYSTEM” is an online voting technique. It is based on the othe online
sevices li!e “ONLINE "ESE"V#TION SYSTEM” .In this s$ste% &eo&le 'ho have citi(enshi&
o) IN*I# and 'hose age is above +, $eas o) an$ se- can give his.he vote online 'ithout going
to an$ &olling booth. Thee is a *#T#/#SE 'hich is %aintained b$ the ELE0TION
0OMMISION O1 IN*I# in 'hich all the na%es o) vote 'ith co%&lete in)o%ation is stoed.
In “ONLINE VOTING SYSTEM” a vote can use his.he voting ight online 'ithout an$
di))icult$. 2e.She has to )ill a egistation )o% to egiste hi%sel).hesel). #ll the enties is
chec!ed b$ the *#T#/#SE 'hich has alead$ all in)o%ation about the vote. I) all the enties
ae coect then a 3SE" I* and 4#SS5O"* is given to the vote6 b$ using that I* and
4#SS5O"* he.she can use his.he vote. I) conditions ae 'ong then that ent$ 'ill be
discaded.
CHAPTER-1
INTRODUCTION
1.1 Purpose
In “ONLINE VOTING SYSTEM” a vote can use his.he voting ight online 'ithout an$
di))icult$. 2e.She has to )ill a egistation )o% to egiste hi%sel).hesel). #ll the enties is
chec!ed b$ the *#T#/#SE 'hich has alead$ all in)o%ation about the vote. I) all the enties
ae coect then a 3SE" I* and 4#SS5O"* is given to the vote6 b$ using that I* and
4#SS5O"* he.she can use his.he vote. I) conditions ae 'ong then that ent$ 'ill be
discaded.
1.2 Scope
The sco&e o) the &o7ect that is hosted on the seve. Thee is a *#T#/#SE 'hich is
%aintained b$ the ELE0TION 0OMMISION O1 IN*I# in 'hich all the na%es o) vote 'ith
co%&lete in)o%ation is stoed.
1.4 Overview
 4o7ect is elated to Online Voting S$ste%.
 The &o7ect %aintains t'o levels o) uses89
• #d%inistato Level
• Vote Level
 Main )acilities available in this &o7ect ae89
• Maintaining vote:s Identi)ication.
• 4oviding online voting %anage%ent.
• 4oviding 3&dation o) vote:s in)o%ation.
• 4ovide vote in)o%ation to ELE0TION 0OMMISION O1 IN*I#.
• ELE0TION 0OMMISION O1 IN*I# %aintains the co%&lete in)o%ation
o) vote.
• Vote can give his.he vote )o% an$ &at o) India.
CHAPTER-2
OVERALL DESCRIPTION
2.1 Goals of proposed system
+. Planned approach towards working: - The 'o!ing in the ogani(ation 'ill be 'ell &lanned
and ogani(ed. The data 'ill be stoed &o&el$ in data stoes6 'hich 'ill hel& in etieval o)
in)o%ation as 'ell as its stoage.
;. Accuracy: - The level o) accuac$ in the &o&osed s$ste% 'ill be highe. #ll o&eation 'ould
be done coectl$ and it ensues that 'hateve in)o%ation is co%ing )o% the cente is accuate.
<. Reliability: 9 The eliabilit$ o) the &o&osed s$ste% 'ill be high due to the above stated easons.
The eason )o the inceased eliabilit$ o) the s$ste% is that no' thee 'ould be &o&e stoage o)
in)o%ation.
=. No Redundancy: - In the &o&osed s$ste% ut%ost cae 'ould be that no in)o%ation is e&eated
an$'hee6 in stoage o othe'ise. This 'ould assue econo%ic use o) stoage s&ace and
consistenc$ in the data stoed.
>. Immediate retrieval of information: - The %ain ob7ective o) &o&osed s$ste% is to &ovide )o
a quic! and e))icient etieval o) in)o%ation.
?. Immediate storage of information: - In %anual s$ste% thee ae %an$ &oble%s to stoe the
lagest a%ount o) in)o%ation.
@. Easy to Operate: - The s$ste% should be eas$ to o&eate and should be such that it can be
develo&ed 'ithin a shot &eiod o) ti%e and )it in the li%ited budget o) the use.
2.2 Background
ONLINE VOTING SYSTEM is a voting s$ste% b$ 'hich an$ Vote can use his.he voting ights
)o% an$ 'hee in India. ONLINE VOTING SYSTEM contains98
• Vote:s in)o%ation in database.
• Vote:s Na%es 'ith I*.
• Vote:s vote in a database.
• 0alculation o) total nu%be o) votes.
Vaious o&eational 'o!s that ae done in the s$ste% ae89
• "ecoding in)o%ation o) the Vote in Vote database.
• 0hec!ing o) in)o%ation )illed b$ vote.
• *iscad the )alse in)o%ation.
• Each in)o%ation is sent to ELE0TION 0OMMISSION O1 IN*I#.
2.3 Project Requirements
Hardware Requirements
- Computer/Processor : Intel Pentium class, 133 megahertz (MHz) or
higher
- Minimum RAM Requirements : 128 megabytes (MB) (256 MB or
higher recommended)
- Hard Disk :
o Hard disk space required to install: 600 MB
o Hard disk space required: 370 MB
- Display : Video: 800x600, 256 colors
- Input Device : Microsoft mouse or compatible pointing device
SOFTWARE SPECIFICATION :
Operating System 8 5indo's A,.
Front end Tool 8 V/.NET
Data Bases 8 Ms access
2.4 User Characteristics
Eve$ use should be8
 0o%)otable 'ith Intenet /o'se.
 2e %ust have bie) !no'ledge o) voting s$ste%.
 2e %ust also have basic !no'ledge o) English too.
2.5 Constraints
 G3I is onl$ in English.
 Login and &ass'od is used )o identi)ication o) Vote.
2.6 Definitions of problems
B Not User Friendly: The e-isting s$ste% is not use )iendl$ because the etieval o) data is
ve$ slo' and data is not %aintained e))icientl$.
B Difficulty in report generating: 5e equie %oe calculations to geneate the )inal esult so
it is geneated at the end o) the session. #nd the vote not get a single chance to change his.he
vote.
B Time consuming8 Eve$ 'o! is done %anuall$ so 'e cannot geneate e&ot in the %iddle o)
the session o as &e the equie%ent because it is ve$ ti%e consu%ing.
CHAPTER-3
FEASIBILITY STUDY
*e&ending on the esults o) the initial investigation the suve$ is no' e-&anded to a %oe detailed
)easibilit$ stud$. “FEASIBILITY STUDY” is a test o) s$ste% &o&osal accoding to its
'o!abilit$6 i%&act o) the ogani(ation6 abilit$ to %eet needs and e))ective use o) the esouces. It
)ocuses on these %a7o questions8
+. 5hat ae the use:s de%onstable needs and ho' does a candidate s$ste% %eet the%C
;. 5hat esouces ae available )o given candidate s$ste%C
<. 5hat ae the li!el$ i%&acts o) the candidate s$ste% on the ogani(ationC
=. 5hethe it is 'oth to solve the &oble%C
*uing )easibilit$ anal$sis )o this &o7ect6 )ollo'ing &i%a$ aeas o) inteest ae to be consideed.
Investigation and geneating ideas about a ne' s$ste% does this.
Ste&s in )easibilit$ anal$sis
Eight ste&s involved in the )easibilit$ anal$sis ae8
• 1o% a &o7ect tea% and a&&oint a &o7ect leade.
• 4e&ae s$ste% )lo'chats.
• Enu%eate &otential &o&osed s$ste%.
• *e)ine and identi)$ chaacteistics o) &o&osed s$ste%.
• *ete%ine and evaluate &e)o%ance and cost e))ective o) each &o&osed s$ste%.
• 5eight s$ste% &e)o%ance and cost data.
• Select the best9&o&osed s$ste%.
• 4e&ae and e&ot )inal &o7ect diective to %anage%ent.
3.1 Technical feasibility
# stud$ o) esouce availabilit$ that %a$ a))ect the abilit$ to achieve an acce&table s$ste%. This
evaluation dete%ines 'hethe the technolog$ needed )o the &o&osed s$ste% is available o not.
• 0an the 'o! )o the &o7ect be done 'ith cuent equi&%ent e-isting so)t'ae technolog$
D available &esonalC
• 0an the s$ste% be u&gaded i) develo&edC
• I) ne' technolog$ is needed then 'hat can be develo&edC
• This is concened 'ith s&eci)$ing equi&%ent and so)t'ae that 'ill success)ull$ satis)$ the
use equie%ent. The technical needs o) the s$ste% %a$ include8
Front-end and back-end selection
#n i%&otant issue )o the develo&%ent o) a &o7ect is the selection o) suitable )ont9end and bac!9
end. 5hen 'e decided to develo& the &o7ect 'e 'ent though an e-tensive stud$ to dete%ine the
%ost suitable &lat)o% that suits the needs o) the ogani(ation as 'ell as hel&s in develo&%ent o)
the &o7ect.
The as&ects o) ou stud$ included the )ollo'ing )actos.
Front-end selection:
+. It %ust have a G3I that assists e%&lo$ees that ae not )o% IT bac!gound.
;. Scalabilit$ and e-tensibilit$.
<. 1le-ibilit$.
=. "obustness.
>. #ccoding to the ogani(ation equie%ent and the cultue.
?. Must &ovide e-cellent e&oting )eatues 'ith good &inting su&&ot.
@. 4lat)o% inde&endent.
,. Eas$ to debug and %aintain.
A. Event diven &oga%%ing )acilit$.
+E. 1ont end %ust su&&ot so%e &o&ula bac! end li!e Ms #ccess.
#ccoding to the above stated )eatues 'e selected 424 as the )ont9end )o
develo&ing ou &o7ect.
Back-end Selection:
+. Multi&le use su&&ot.
;. E))icient data handling.
<. 4ovide inheent )eatues )o secuit$.
=. E))icient data etieval and %aintenance.
>. Stoed &ocedues.
?. 4o&ulait$.
@. O&eating S$ste% co%&atible.
,. Eas$ to install.
A. Vaious dives %ust be available.
+E. Eas$ to i%&lant 'ith the 1ont9end.
#ccoding to above stated )eatues 'e selected MY SFL as the bac!end.
The technical )easibilit$ is )equentl$ the %ost di))icult aea encounteed at this stage. It is
essential that the &ocess o) anal$sis and de)inition be conducted in &aallel 'ith an assess%ent to
technical )easibilit$. It centes on the e-isting co%&ute s$ste% and to 'hat e-tent it can su&&ot
the &o&osed s$ste%.
3.2 Economical feasibility
Econo%ic 7usti)ication is geneall$ the “/otto% Line” consideation )o %ost s$ste%s. Econo%ic
7usti)ication includes a boad ange o) concens that includes cost bene)it anal$sis. In this 'e
'eight the cost and the bene)its associated 'ith the candidate s$ste% and i) it suits the basic
&u&ose o) the ogani(ation i.e. &o)it %a!ing6 the &o7ect is %a!ing to the anal$sis and design
&hase.
The )inancial and the econo%ic questions duing the &eli%ina$ investigation ae
vei)ied to esti%ate the )ollo'ing8
• The cost to conduct a )ull s$ste% investigation.
• The cost o) had'ae and so)t'ae )o the class o) a&&lication being consideed.
. The bene)its in the )o% o) educed cost.
• The &o&osed s$ste% 'ill give the %inute in)o%ation6 as a esult the
&e)o%ance is i%&oved
• This )easibilit$ chec!s 'hethe the s$ste% can be develo&ed 'ith the available )unds. The
Online voting system does not equie eno%ous a%ount o) %one$ to be develo&ed. This
can be done econo%icall$ i) &lanned 7udiciall$6 so it is econo%icall$ )easible. The cost o)
&o7ect de&ends u&on the nu%be o) %an9hous equied.
3.3 Operational Feasibility
It is %ainl$ elated to hu%an ogani(ations and &olitical as&ects. The &oints to be
consideed ae8
• 5hat changes 'ill be bought 'ith the s$ste%C
• 5hat ogani(ation stuctues ae distubedC
• 5hat ne' s!ills 'ill be equiedC *o the e-isting sta)) %e%bes have these
s!illsC I) not6 can the$ be tained in due couse o) ti%eC
The s$ste% is o&eationall$ )easible as it ve$ eas$ )o the End uses to o&eate it. It onl$ needs
basic in)o%ation about 5indo's &lat)o%.
3.4 Schedule feasibility
Ti%e evaluation is the %ost i%&otant consideation in the develo&%ent o) &o7ect. The ti%e
schedule equied )o the develo&ed o) this &o7ect is ve$ i%&otant since %oe develo&%ent ti%e
e))ect %achine ti%e6 cost and cause dela$ in the develo&%ent o) othe s$ste%s.
# eliable Online voting system can be develo&ed in the consideable a%ount o) ti%e
CHAPTER-4
DESIGN
4.1 Software Requirement Specification
4.1.1 Objective:
The %ain ob7ectives o) s$ste% )o Online voting system ae8
• The ob7ective o) Online voting system is to hel& the ogani(ation in
auto%ating the 'hole %anual &ocessing o) the e-isting s$ste%.
• The %ain ob7ective to develo& the s$ste% is to %a!e the accuate D e))icient decisions in
di))eent tas!s at di))eent ti%e at di))eent situations. The e-isting s$ste% is %anual so
%e%bes o) the unit geneall$ )ace a lot o) e%baassing situations %an$ ti%es. No' the$
need to auto%ate the 'hole &ocess so as to %a!e it %oe eas$ and accuate.
• S$ste% should su&&ot %ulti9use envion%ent.
• S$ste% should be )ull$ auto%ated.
• S$ste% should &ovide concete secuit$ )eatues li!e ceating uses and assigning
&ivileges to uses o) the s$ste%.
• S$ste% should be ca&able to !ee& tac! o) all the detailed desci&tions o) the client and
the 'hole details o) sevices o))eed b$ the client ogani(ation.
• Vaious out&uts Ge&otsH should be available online an$ ti%e.
• S$ste% should be able to handle e-te%el$ lage volu%es o) data Gi.e. Lage database
su&&otH
4.1.2 Scope:-
Advanced technology9 It is an advanced technolog$ used no' a da$s. It inceases the E
!no'ledge o) the uses 'hich is ve$ necessa$ )o cuent geneation.
4.1.3 Advantages:
• 1ast and eas$ sevice.
• The online voting s$ste% &ovides a less ti%e consu%ing .
• It educes the &a&e 'o! and %a!es the 'o! less tedious )o ELESTION
0OMMISION.
• It is a bette 'a$ )o voting.
• /$ this voting &ecentage 'ill incease dasticall$.
Vote has no need to go to an$ &olling booth 6so it is eas$ to use.
4.1.4 Technologies to be used:-
This &o7ect 'ill be having
• *atabase *esign GMs #ccessH
• 1o% *esign GV/.NETH
• 0oding GV/.NETH
• Testing GI#M4 SE"VE"H
About vb.net:
.NET Framework SDK
You can develop such varied types of applications. That`s fine. But how? As with
most of the programming languages, .NET has a complete Software Development
Kit (SDK) - more commonly referred to as .NET Framework SDK - that
provides classes, interfaces and language compilers necessary to program for
NET. Additionally it contains excellent documentation and Quick Start tutorials.
that help you learn .NET technologies with ease. Good news is that - .NET
Framework SDK is available FREE of cost. You can download it from the MSDN
web site. This means that if you have machine with .NET Framework installed
and a text editor such as Notepad then you can start developing for .NET right
now!
Rich Functionality out of the box
NET framework provides a rich set of functionality out of the box. It contains.
hundreds of classes that provide variety of functionality ready to use in your
applications. This means that as a developer you need not go into low level details
of many operations such as file IO, network communication and so on.
· Easy development of web applications
ASP.NET is a technology available on .NET platform for developing dynamic
and data driven web applications. ASP.NET provides an event driven
programming model (similar to Visual Basic 6 that simplify development of web
pages (now called as web forms) with complex user interface. ASP.NET server
controls provide advanced user interface elements (like calendar and grids) that
save lot of coding from programmer`s side.
· OOPs Support
The advantages of Object Oriented programming are well known. .NET provides
a fully object oriented environment. The philosophy of .NET is - “Object is
mother of all.” Languages like Visual Basic.NET now support many of the OO
features that were lacking traditionally. Even primitive types like integer and
characters can be treated as objects - something not available even in OO
languages like C++.
· Security
Windows platform was always criticized for poor security mechanisms. Microsoft
has taken great efforts to make .NET platform safe and secure for enterprise
applications. Features such as type safety, code access security and role based
authentication make overall application more robust and secure.
1ust-In-Time Compilation (1IT)
The MSIL is the language that all of the .NET languages compile down to. After they
are in this intermediate language, a process called 1ust-In-Time (1IT) compilation
occurs when resources are used from your application at runtime. 1IT allows “parts”
of your application to execute when they are needed, which means that if something
is never needed, it will never compile down to the native code. By using the 1IT, the
CLR can cache code that is used more than once and reuse it for subsequent calls,
without going through the compilation process again.
Assembly
Assemblies are the building blocks of .NET Framework applications; they form the
fundamental unit of deployment, version control, reuse, activation scoping, and
security permissions. An assembly is a collection of types and resources that are
built to work together and form a logical unit of functionality. An assembly provides
the common language runtime with the information it needs to be aware of type
implementations. To the runtime, a type does not exist outside the context of an
assembly
The .NET runtime/Common Language Runtime (CLR) ships three different classes of
1ITters. The Main 1IT compiler converts the MSIL code it to native code with out any
optimizations. The 1IT compiler takes the MSIL code and optimizes it. So this compiler
requires lot of resources like, time to compile, larger memory footprint, etc. The Pre1IT
is based on the Main 1IT and it works like the traditional compilers (compiles MSIL to
native code during compilation time rather than runtime). This compiler is usually used at
the time of installation.
No matter whatever language we used to develop the HelloWorld program, it`s a known
fact that compiler`s are going to generate a MSIL format, once our code has been
converted in to MSIL format, from MSIL format all the code that we write will be
converted to native code in the same way whether if it is a VB.NET source or C# source.
.
Debugging is the most important feature of any programming language and Visual Studio
NET IDE provides this feature in an effective manner (but you can still do pretty good.
job with the .NET SDK alone). Application source code goes through two distinct steps
before a user can run it. First, the source code is compiled to Microsoft Intermediate
Language (MSIL) code using a .NET compiler. Then, at runtime, the MSIL code is
compiled to native code. When we debug a .NET application, this process works in
reverse. The debugger first maps the native code to the MSIL code. The MSIL code is
then mapped back to the source code using the programmer's database (PDB) file. In
order to debug an application, these two mappings must be available to the .NET runtime
environment.
To accomplish the mapping between the source code and the MSIL, use
the/debug:pdbonly compiler switch to create the PDB file (Note: When building
ASP.NET applications, specify the compilation setting debug÷"true" in the application`s
Web.config file). The second mapping between the MSIL code and native code is
accomplished by setting the 1ITTracking attribute in our assembly. By specifying the
/debug compiler switch, the PDB file is created and the 1ITTracking attribute is enabled.
When using this compiler switch, a debugger can be attached to an application loaded
outside of the debugger.
Once the required mappings exist, there are several means by which to debug our
applications. We can use the integrated debugger within Visual Studio .NET, or, if we
prefer, we can use DbgClr, a GUI-based debugger. There is also a command line
debugger, CorDBG that is included in the .NET Framework SDK.
Constants &Variables
A variable is a named memory location. They are programming elements that can change
during program execution. Data that needs to be stored in memory & accessed at a later
time are stored in variables. Instead of referring to the memory location by the actual
memory address you refer to it with a variable name.
Variables are declared as follows
Dim a as Integer
They can also be initialized at the time of declaration as follows:
Dim a as Integer ÷ 10
Constants are very similar to variables. The main difference is that the value contained in
memory cannot be changed once the constant is declared. When you declare a constant
its value is also specified and this value cannot be changed during program execution.
Constants are used in situations where we need to keep the value in some memory
location constant. If you use hard-coded values, and the value is changed then it has to be
changed in all the locations in the code where it has been used. Instead if we are using
constants, all we will need to do is to change the value of the constant. This would
propagate the changes to our entire application.
Simple Types (Primitive Data types)
Simple or value type variables are those, which are assigned space in the stack instead of
the heap. All the primitive types such as int, double etc are value type variables. The
simple types basically consist of Boolean and Numeric types, where Numeric is further
divided into Integral and Floating Point.
The first rule of value types is that they cannot be null. Anytime you declare a variable of
value type, you have allocated the number of bytes associated with that type on the stack
and are working directly with that allocated array of bits. In addition, when you pass a
variable of value type, you are passing that variable`s value and not a reference to the
underlying object.

Object Type
Object type or reference type variables are those, which are allocated storage space in the
heap. Reference type objects can be null. When a reference type is allocated under the
covers a value is allocated on the heap and a reference to that value is returned. There are
basically four reference types: classes, interfaces, delegates and arrays.
Class Type
Custom data types are available in .NET framework in the form of classes or class type. It
is nothing but a set of data and related behavior that is defined by the developer.
1.1.5 OVERVIEW:
1. Requirements:
· FUNCTIONAL REQUIREMENTS:
• "egistation o) the vote is done b$ ELE0TION 0OMMISION O1 IN*I#.
• ELE0TION 0OMMISION O1 IN*I# can change the in)o%ation an$ ti%e i) equied.
• "egistation o) the Vote de&ends u&on the in)o%ation )illed b$ the use.
• Vote is given a unique I* and 4#SS5O"*.
• Voter can give vote after login and entering the ID and PASSWORD.
• In the *#T#/#SE in)o%ation o) eve$ vote is stoed.
• *atabase sho's the in)o%ation o) eve$ use.
· NON-FUNCTIONAL REQUIREMENTS:
+. Secue access o) con)idential data Guse:s detailsH. SSL can be used.
;. ;= I @ availabilit$.
<. /ette co%&onent design to get bette &e)o%ance at &ea! ti%e.
=. 1le-ible sevice based achitectue 'ill be highl$ desiable )o )utue e-tension
6. SYSTEM TESTING
The &u&ose o) testing is to discove eos. Testing is the &ocess o) t$ing
to discove eve$ conceivable )ault o 'ea!ness in a 'o! &oduct. It &ovides a
'a$ to chec! the )unctionalit$ o) co%&onents6 sub asse%blies6 asse%blies andJo a
)inished &oduct It is the &ocess o) e-ecising so)t'ae 'ith the intent o) ensuing
that the
So)t'ae s$ste% %eets its equie%ents and use e-&ectations and does not )ail in
an unacce&table %anne. Thee ae vaious t$&es o) test. Each test t$&e addesses a
s&eci)ic testing equie%ent.
TY4ES O1 TESTS
3nit testing
3nit testing involves the design o) test cases that validate that the intenal
&oga% logic is )unctioning &o&el$6 and that &oga% in&ut &oduces valid
out&uts. #ll decision banches and intenal code )lo' should be validated. It is the
testing o) individual so)t'ae units o) the a&&lication .it is done a)te the
co%&letion o) an individual unit be)oe integation. This is a stuctual testing6 that
elies on !no'ledge o) its constuction and is invasive. 3nit tests &e)o% basic
tests at co%&onent level and test a s&eci)ic business &ocess6 a&&lication6 andJo
s$ste% con)iguation. 3nit tests ensue that each unique &ath o) a business &ocess
&e)o%s accuatel$ to the docu%ented s&eci)ications and contains cleal$ de)ined
in&uts and e-&ected esults.
Integration teting
Integation tests ae designed to test integated so)t'ae co%&onents to
dete%ine i) the$ actuall$ un as one &oga%. Testing is event diven and is %oe
concened 'ith the basic outco%e o) sceens o )ields. Integation tests
de%onstate that although the co%&onents 'ee individuall$ satis)action6 as sho'n
b$ success)ull$ unit testing6 the co%bination o) co%&onents is coect and
consistent. Integation testing is s&eci)icall$ ai%ed at e-&osing the &oble%s that
aise )o% the co%bination o) co%&onents.
1unctional test
1unctional tests &ovide a s$ste%atic de%onstation that )unctions tested ae
available as s&eci)ied b$ the business and technical equie%ents6 s$ste%
docu%entation6 and use %anuals.
1unctional testing is centeed on the )ollo'ing ite%s8
Valid In&ut 8 identi)ied classes o) valid in&ut %ust be acce&ted.
Invalid In&ut 8 identi)ied classes o) invalid in&ut %ust be e7ected.
1unctions 8 identi)ied )unctions %ust be e-ecised.
Out&ut 8 identi)ied classes o) a&&lication out&uts %ust be
e-ecised.
S$ste%sJ4ocedues8 inte)acing s$ste%s o &ocedues %ust be invo!ed.
Ogani(ation and &e&aation o) )unctional tests is )ocused on equie%ents6 !e$
)unctions6 o s&ecial test cases. In addition6 s$ste%atic coveage &etaining to
identi)$
/usiness &ocess )lo'sK data )ields6 &ede)ined &ocesses6 and successive &ocesses
%ust be consideed )o testing. /e)oe )unctional testing is co%&lete6 additional
tests ae identi)ied and the e))ective value o) cuent tests is dete%ined.
S$ste% Test
S$ste% testing ensues that the entie integated so)t'ae s$ste% %eets
equie%ents. It tests a con)iguation to ensue !no'n and &edictable esults. #n
e-a%&le o) s$ste% testing is the con)iguation oiented s$ste% integation test.
S$ste% testing is based on &ocess desci&tions and )lo's6 e%&hasi(ing &e9diven
&ocess lin!s and integation &oints.
5hite /o- Testing
White Box Testing is a testing in which in which the software tester has
knowledge of the inner workings, structure and language of the software, or
at least its purpose. It is purpose. It is used to test areas that cannot be
reached from a black box level.
/lac! /o- Testing
Black Box Testing is testing the software without any knowledge of the
inner workings, structure or language of the module being tested. Black box
tests, as most other kinds of tests, must be written from a definitive source
document, such as specification or requirements document, such as
specification or requirements document. It is a testing in which the software
under test is treated, as a black box .you cannot “see” into it. The test provides
inputs and responds to outputs without considering how the software works.
6.1 Unit Testing:
Unit testing is usually conducted as part of a combined code and unit
test phase of the software lifecycle, although it is not uncommon for coding
and unit testing to be conducted as two distinct phases.
Test strategy and approach
Field testing will be performed manually and functional tests will be
written in detail.
Test ob7ectives
• All field entries must work properly.
• Pages must be activated from the identified link.
• The entry screen, messages and responses must not be delayed.
1eatues to be tested
• Verify that the entries are of the correct format
• No duplicate entries should be allowed
• All links should take the user to the correct page.
6.2 Integration Testing
So)t'ae integation testing is the ince%ental integation testing o) t'o o
%oe integated so)t'ae co%&onents on a single &lat)o% to &oduce )ailues
caused b$ inte)ace de)ects.
The tas! o) the integation test is to chec! that co%&onents o so)t'ae
a&&lications6 e.g. co%&onents in a so)t'ae s$ste% o L one ste& u& L so)t'ae
a&&lications at the co%&an$ level L inteact 'ithout eo.
Integration testing for Database Synchronization:
 Testing the lin!s that call the 0hange 3sena%e D &ass'od6 Migation and
S$nchoni(ation sceens etc.
 The usena%e should be etained thoughout the a&&lication in the )o% o)
hidden vaiables o b$ using coo!ies.
 I) the login use does not have enough &ivileges to invo!e a sceen6 the lin!
should be disabled.
 #n$ %odi)ication in the Maste seve should be e)lected in the Slave
seve.
 The IML )ile should etieve onl$ the ecods6 'hich have been %odi)ied.
Test Results: #ll the test cases %entioned above &assed success)ull$. No de)ects
encounteed.
!"3 A##e$tan#e Teting
3se #cce&tance Testing is a citical &hase o) an$ &o7ect and equies
signi)icant &atici&ation b$ the end use. It also ensues that the s$ste% %eets the
)unctional equie%ents.
Acceptance testing for Data Synchronization:
 3ses have se&aate oles to %odi)$ the database tables.
 The ti%esta%& )o all insetions and u&dating should be %aintained.
 3ses should have the abilit$ to %odi)$ the &ivilege )o a sceen.
 Once the S$nchoni(ation stats6 the Maste seve o Slave Seve should
not be sto&&ed 'ithout noti)$ing the othe.
 The IML )ile should be geneated in shot ti%e6 i.e.6 be)oe the ne-t
%odi)ication occus.
Test Results: #ll the test cases %entioned above &assed success)ull$. No de)ects
encounteed.
4.2 Data Flow Diagram
DFD: Level 0
DFD Level-0
The above diaga% is a E9level *1* that onl$ sho's the )lo' o) data bet'een the vaious and
the s$ste%. In online voting s$ste% the #d%inistato is the contolle o) the s$ste% and all the
decisions ae %ade b$ hi%. The #d%inistato can handle the entie vote and thei details6
voting details etc. and vie' details o) the% and he can u&date that detail also.
3se
o
#d%inistato
Out&ut
S$ste%
DFD: Level 1:-


DFD Level 1
The above sho'n diaga% is a +9level *ata 1lo' *iaga% )o the Online voting s$ste%.
#ccoding to this *1* vaious &ocess ae done a)te login &ocess. The #d%inistato can
egiste vote. The ELE0TION 0OMMISION can egiste the votes and vote can use thei
Login


4ocess

Voting
4ocess

Vote
in)o%ation
chec!ing
&ocess

Vote
"egistation
4ocess

1inal
"e&ot
voting ights. The vote can vie' the )inal e&ot a)te giving vote..
.
DFD: Level 2
2.1:-
Login
vote data stoed data voting data )inal esult
Login 4ocess
#d%inistato Vote

1inal
"esult
Voting
&ocess
Vote
"egistation

In)o%ation
chec!ing
ad%inistatos
DFD: Level 2.1
The above sho'n diaga% is a ;.+ level *ata 1lo' *iaga% )o the Online voting
s$ste%. #ccoding to this *1*. The #d%inistato can egiste the vote
in)o%ation. #d%inistato can allo' o denies the vote. # vote can give vote i) all
the in)o%ation )illed b$ hi%.he ae coect.

Election0o%%ission
CHAPTER-%
SYSTE& &'DLING
Entity Relationship Diagram
VOTE"
#d%in.
id
4as
s
"egistatio
n

Login
1ail
"e&ot
Vie'

VOTING
Voting "e&ot

Fig.- E-R Diagram
The entit$ elationshi& diaga% sho's the elationshi& bet'een the vaious uses and
thei attibutes.
Class diagram-:
Fig: Relationship between the interface Actor List and its inheriting classes
Fig: Association between Actor interface and other inheriting classes
Registration, login, and logoff modules act as mediator.
Fig: Association between Registration, Actor List, Login, Logoff
Fig: Association between Election and Ballot (Flyweight, ingleton!
CONCLUSION
This Online Voting s$ste% 'ill %anage the Vote:s in)o%ation b$ 'hich vote can login and
use his voting ights. The s$ste% 'ill inco&oate all )eatues o) Voting s$ste%. Its &ovide the
tools )o %aintaining vote:s vote to eve$ &at$ and it count total no. o) votes o) eve$ &at$.
Thee is a *#T#/#SE 'hich is %aintained b$ the ELE0TION 0OMMISION O1 IN*I# in
'hich all the na%es o) vote 'ith co%&lete in)o%ation is stoed.
In this use 'ho is above +, $ea:s egiste hisJhe in)o%ation on the database and 'hen heJshe
'ant to vote heJshe has to login b$ his id and &ass'od and can vote to an$ &at$ onl$ single
ti%e. Voting detail stoe in database and the esult is dis&la$ed b$ calculation. /$ voting s$ste%
&ecentage o) voting is inceases. It deceases the cost and ti%e o) voting &ocess. It is ve$ eas$
to use and It is va$ less ti%e consu%ing. It is ve$ eas$ to debug.