Final Report Voting System
Final Report Voting System
Final Report Voting System
CHAPTER 1
INTRODUCTION
Elections allow the populace to choose their representatives and express their
preferences for how they will be governed. Naturally, the integrity of the election
process is fundamental to the integrity of democracy itself. The election system must
be sufficiently robust to withstand a variety of fraudulent behaviors and must be
sufficiently transparent and comprehensible that voters and candidates can accept the
results of an election. Unsurprisingly, history is littered with examples of elections
being manipulated in order to influence their outcome.
1.1 Purpose of project:
E-Voting
CHAPTER 2
PROJECT ANALYSIS
2.1 Existing system:
The voter has to visit the booths to vote a candidate so there is wastage of time.
The voter has to manually register into the voter List. Also vote counting has to be
done manually.
All the information of the voter or candidate is to be filling in manually.
Voter must be present in his/her constituency to give his/her vote.
The existing system of Election is running manually.
There are electronic voting machines used which increases the cost of carrying out
the election.
Software Requirements
E-Voting
E-Voting
E-Voting
E-Voting
E-Voting
Under the study of Implementation feasibility, weve got to draw the finger to
the certain issues, like
Is it possible to install the software within the given environment?
Will organization management and user support for the installation of the
software?
Will proposed system cause any harm to the operations of the organization
CHAPTER 3
SYSTEM DEVELOPMENT ENVIRONMENT
3.1 Front end:
Java language:
Java is an innovative programming language that has become the language of
choice for programs that need to run on a variety of different computer systems. First
of all, Java enables you to write small programs called applets. These are programs
that you can embed in web pages to provide some intelligence. Being able to embed
executable code in a web page introduces a vast range of exciting possibilities. Instead
of being a passive presentation of text and graphics, a web page can be interactive in
any way that we want.
Javas support for the Internet and network-based applications generally
doesnt end with applets. For example, Java Server Pages (JSP) provides a powerful
means of building a server application that can dynamically create and download
HTML pages to a client that are precisely customized for the specific request that is
received. Of course, the pages that are generated by JSP can themselves contain Java
applets. Java also allows us to write large-scale application programs that we can run
unchanged on any computer with an operating system environment in which Java is
supported. This applies to the majority of computers in use today. We can even write
programs that will work both as ordinary applications and as applets.
E-Voting
The most important characteristic of Java is that it was designed from the
outset to be machine independent. We can run Java programs unchanged on any
machine and operating system combination that supports Java. The next most
important characteristic of Java is that it is object-oriented.
History:
Java is a general purpose programming language. Object oriented
programming language develops by Sun Micro system of USA in 1991 originally
called OAK and team lead by James Gosling. The main aim had to make Java
simple, portable and reliable.
In 1995 OAK was renamed to java as it did not survive legal registration
.Many companies such as, Netscape and Microsoft announcement their support for
E-Voting
java. In 1996 java language is famous for Internet programming as well as general
purpose object oriented programming.
Applets:
E-Voting
10
E-Voting
because capacity can be easily added or reallocated from the resource pools as
needed.
The database has logical structures and physical structures. Because the
physical and logical structures are separate, the physical storage of data can be
managed without affecting the access to logical storage structures.
CHAPTER 4
PROJECT DESIGNING
4.1. Dataflow diagram:
Context level DFD:
11
E-Voting
LEVEL 1 DFD:
12
E-Voting
13
E-Voting
LEVEL 2 DFD:
DFD FOR VOTING:
14
E-Voting
LEVEL 2 DFD:
DFD FOR ADMINISTRATOR
15
E-Voting
Actor
Use Case
An actor represents a user or another system that will interact with the system
your modeling. A use case is an external view of the system that represents some
action the user might perform in order to complete a task. The use case diagrams in
our project are drawn for:
1. Administrator
2. Vote
16
E-Voting
1 Administrator
Party Description
Parliament Participants
Administrator
Assembly Participants
Fig. 4.2.1.2 Administrator
Description:
This is the use case for the administrator in which he can perform various
operations like enter party description, parliament participants details and assembly
participant details.
Actor:
Administrator
Preconditions:
The administrator should enter a valid Username and password in login screen
to perform the operations. Addition of record is done if the record does not exist in the
database. Modification of a record is done for an existing record.
Post conditions:
The administrator can perform various operations like enter party description,
parliament participants details and assembly participants details
Main flow:
17
E-Voting
2. Voter
Registration
Parliament vote
Assembly vote
18
E-Voting
The voter can register and he vote for parliament as well as assembly. He can
view the participants details.
4.3Class Diagram
Class Diagrams are widely used to describe the types of objects in a system
and their relationships. Class Diagrams model class structure, and contents using
design elements such as classes, packages and objects. Classes are composed of three
things:
They are as follows:
Name
19
E-Voting
Attributes
Operations
Conceptual Model
20
E-Voting
Administrator
- UserName: Char
get Password ( )
getMPParticipantDetail ( )
getMLADetails ( )
getPoliceRecords ( )
setPoliceRecords( )
getEducationRecord ( )
setEducationRecord ()
getPropertyValue( )
setPropertyValue( )
- Password: Char
getUserName ( )
Partys Desc
-Party Name: char
-MP Name: char
-MLA Name: char
. getPartyDetails ( )
getPartyMP ( )
getPartyMLA ( )
setPartyMessage ( )
getLeaderMessage (
setParticipantDesc (
Enter Data
Registration
-NSSN: varchar
-First Name: char
-Last Name: char
-Date of birth: int
-Division: char
-Village: char
voter
-Enter Vote
getPartyDetails ( )
getPartyMP ( )
getPartyMLA ( )
getNssn ( )
setNssn ( )
getVoterId( )
setVoterId( )
getDateofBirth( )
setDateofBirth( )
getDivision( )
setDivision( )
getVellage( )
set
getPartyDetails
21
E-Voting
Conceptual Model
During analysis of the problem domain, a conceptual model should be
developed based on the real-life entities within the problem space. The entities in a
conceptual model have less to do with the software components of the system and
more to do with the physical entities that are fundamental to the business. The
conceptual model usually illustrates the concepts, the relationships between them, and
the attributes that belong to each concept. The behavior usually is not represented in
this type of model. The conceptual model is developed from a set of use-cases for the
system. The purpose of building the model is to help identify the entities that most
likely will become classes in the design stage and to help better understand the
problem domain.
22
E-Voting
Party Diagram:
23
E-Voting
acts as
actsPartys
as
Description
1
-Party Name: char
-MP Name: char
1
UserName:
-MLAchar
Name: char
-Name: char
-Age: int
-Birth place: char
-Participating place:
char
Enter Data
-Educational Back
ground: char
Registration
-NSSN: varchar
-First Name: char
-Last Name: char
-Date of birth: int
-Division: char
-Village: char
4.4Sequence Diagrams
24
E-Voting
These are the diagrams, which uses the objects of the classes and shows the action
sequence. With these diagrams, we can know the sequence of the commands. .
When the administrator enters the username and password then the database is
verified and if these are valid, then the administrator can get the administrator session.
CMCS, YTL (2015-16)
25
E-Voting
Here, he can add the data and he can modify the files. The arrows shown in the
diagrams will tell us about the command from one operation to another operation
class. The tail of the arrow contains from class and the head of the arrow contains to
the class.
4.5Collaboration Diagrams
The collaboration diagrams are the diagrams generated from the sequence
diagrams. Here we can see the sequence numbering for the commands. The boxes are
the objects of the classes.
26
E-Voting
Type
Width
Description
Varchar2
20
Primary key
Varchar2
20
Not Null
Varchar2
20
Not Null
Date
Not Null
Varchar2
20
Not Null
Varchar2
8
Not Null
Varchar2
20
Not Null
Varchar2
15
Not Null
Varchar2
20
Not Null
Varchar2
20
Not Null
Varchar2
20
Not Null
Varchar2
20
Not Null
Fig4.6.1: Table name: nssnregistration
Voting Registration:
Fieldname
NSSN
VOTERID
FIRSTNAME
LASTNAME
Type
Width
Varchar2
Varchar2
Varchar2
Varchar2
30
30
40
30
Description
Foreign key
Primary key
Not Null
Not Null
27
E-Voting
Date
Date
Not Null
Congo participants
Fieldname
PERSON
PARTY
POST
PERSONDESC
PLACE
Type
Varchar2
Varchar2
Varchar2
Varchar2
Varchar2
Width
30
30
10
40
30
Description
Not Null
Not Null
Not Null
Not Null
Primary key
Type
Width
Description
Varchar2
30
Not Null
Varchar2
30
Not Null
Varchar2
10
Not Null
Varchar2
40
Not Null
Varchar2
30
Primary key
Fig4.6.4 Table Name: tdpparticipents
Trsparticipents:
Fieldname
PERSON
PARTY
POST
PERSONDESC
PLACE
Type
Width
Description
Varchar2
30
Not Null
Varchar2
30
Not Null
Varchar2
10
Not Null
Varchar2
40
Not Null
Varchar2
30
Primary key
Fig4.6.5 Table Name: trsparticipents
28
E-Voting
Trsparticipents:
Fieldname
PERSON
PARTY
POST
PERSONDESC
PLACE
Type
Width
Description
Varchar2
30
Not Null
Varchar2
30
Not Null
Varchar2
10
Not Null
Varchar2
40
Not Null
Varchar2
30
Primary key
Fig4.6.6 Table Name: trsparticipents
Bjpparticipents:
Fieldname
PERSON
PARTY
POST
PERSONDESC
PLACE
Type
Width
Description
Varchar2
30
Not Null
Varchar2
30
Not Null
Varchar2
10
Not Null
Varchar2
40
Not Null
Varchar2
30
Primary key
Fig4.6.7 Table name: bjpparticipents
Rudhranethraparticipents:
Fieldname
PERSON
PARTY
POST
PERSONDESC
PLACE
Type
Width
Description
Varchar2
30
Not Null
Varchar2
30
Not Null
Varchar2
10
Not Null
Varchar2
40
Not Null
Varchar2
30
Primary key
Fig4.6.8 Table name: rudhranethraparticipents
29
E-Voting
Otherparticipents:
Fieldname
PERSON
PARTY
POST
PERSONDESC
PLACE
Type
Width
Description
Varchar2
30
Not Null
Varchar2
30
Not Null
Varchar2
10
Not Null
Varchar2
40
Not Null
Varchar2
30
Primary key
Fig4.6.9 Table name: otherparticipents
CongrasMP:
Fieldname
PARTY
POST
NAME
AGE
BIRTHPLACE
PARICIPAINGPLACE
EDUCTIONLBG
POLICERECORD
Type
Width
Varchar2
30
Varchar2
5
Varchar2
30
Varchar2
10
Varchar2
30
Varchar2
30
Varchar2
30
Varchar2
10
Fig4.6.10 Table name: CongrasMP
Description
Not Null
Not Null
Not Null
Not Null
Not Null
Foreign key
Not Null
Not Null
Congress MLA:
Fieldname
PARTY
POST
NAME
AGE
BIRTHPLACE
PARICIPAINGPLACE
EDUCTIONLBG
POLICERECORD
Type
Width
Varchar2
30
Varchar2
5
Varchar2
30
Varchar2
10
Varchar2
30
Varchar2
30
Varchar2
30
Varchar2
10
Fig4.6.11 Table name: Congress MLA
Description
Not Null
Not Null
Not Null
Not Null
Not Null
Foreign key
Not Null
Not Null
30
E-Voting
TDPMP:
Fieldname
PARTY
POST
NAME
AGE
BIRTHPLACE
PARICIPAINGPLACE
EDUCTIONLBG
POLICERECORD
Type
Varchar2
Varchar2
Varchar2
Varchar2
Varchar2
Varchar2
Varchar2
Varchar2
Width
30
5
30
10
30
30
30
10
Description
Not Null
Not Null
Not Null
Not Null
Not Null
Foreign key
Not Null
Not Null
TDPMLA:
Fieldname
PARTY
POST
NAME
AGE
BIRTHPLACE
PARICIPAINGPLACE
EDUCTIONLBG
POLICERECORD
Type
Varchar2
Varchar2
Varchar2
Varchar2
Varchar2
Varchar2
Varchar2
Varchar2
Width
30
5
30
10
30
30
30
10
Description
Not Null
Not Null
Not Null
Not Null
Not Null
Foreign key
Not Null
Not Null
TRSMP:
Fieldname
PARTY
Type
Varchar2
Width
30
Description
Not Null
31
E-Voting
POST
NAME
AGE
BIRTHPLACE
PARICIPAINGPLACE
EDUCTIONLBG
POLICERECORD
Varchar2
Varchar2
Varchar2
Varchar2
Varchar2
Varchar2
Varchar2
5
30
10
30
30
30
10
Not Null
Not Null
Not Null
Not Null
Foreign key
Not Null
Not Null
TRSMLA:
Fieldname
PARTY
POST
NAME
AGE
BIRTHPLACE
PARICIPAINGPLACE
EDUCTIONLBG
POLICERECORD
Type
Varchar2
Varchar2
Varchar2
Varchar2
Varchar2
Varchar2
Varchar2
Varchar2
Width
30
5
30
10
30
30
30
10
Description
Not Null
Not Null
Not Null
Not Null
Not Null
Foreign key
Not Null
Not Null
BJPMP:
Fieldname
PARTY
POST
NAME
AGE
BIRTHPLACE
PARICIPAINGPLACE
Type
Varchar2
Varchar2
Varchar2
Varchar2
Varchar2
Varchar2
Width
30
5
30
10
30
30
Description
Not Null
Not Null
Not Null
Not Null
Not Null
Foreign key
32
E-Voting
EDUCTIONLBG
POLICERECORD
Varchar2
Varchar2
30
10
Not Null
Not Null
Type
Varchar2
Varchar2
Varchar2
Varchar2
Varchar2
Varchar2
Varchar2
Varchar2
Width
30
5
30
10
30
30
30
10
Description
Not Null
Not Null
Not Null
Not Null
Not Null
Foreign key
Not Null
Not Null
RudhranethraMP:
Fieldname
PARTY
POST
NAME
AGE
BIRTHPLACE
PARICIPAINGPLACE
EDUCTIONLBG
POLICERECORD
Type
Varchar2
Varchar2
Varchar2
Varchar2
Varchar2
Varchar2
Varchar2
Varchar2
Width
30
5
30
10
30
30
30
10
Description
Not Null
Not Null
Not Null
Not Null
Not Null
Foreign key
Not Null
Not Null
33
E-Voting
RudhranehraMLA:
Fieldname
PARTY
POST
NAME
AGE
BIRTHPLACE
PARICIPAINGPLACE
EDUCTIONLBG
POLICERECORD
Type
Varchar2
Varchar2
Varchar2
Varchar2
Varchar2
Varchar2
Varchar2
Varchar2
Width
30
5
30
10
30
30
30
10
Description
Not Null
Not Null
Not Null
Not Null
Not Null
Foreign key
Not Null
Not Null
OthersMP
Fieldname
PARTY
POST
NAME
AGE
BIRTHPLACE
PARICIPAINGPLACE
EDUCTIONLBG
POLICERECORD
Type
Varchar2
Varchar2
Varchar2
Varchar2
Varchar2
Varchar2
Varchar2
Varchar2
Width
30
5
30
10
30
30
30
10
Description
Not Null
Not Null
Not Null
Not Null
Not Null
Foreign key
Not Null
Not Null
Type
Varchar2
Varchar2
Width
30
5
Description
Not Null
Not Null
34
E-Voting
NAME
AGE
BIRTHPLACE
PARICIPAINGPLACE
EDUCTIONLBG
POLICERECORD
Varchar2
Varchar2
Varchar2
Varchar2
Varchar2
Varchar2
30
10
30
30
30
10
Not Null
Not Null
Not Null
Foreign key
Not Null
Not Null
4.7 Screens:
Home page:
Fig4.7.1: Homepage
Admin main page:
35
E-Voting
36
E-Voting
37
E-Voting
38
E-Voting
39
E-Voting
40
E-Voting
41
E-Voting
42
E-Voting
43
E-Voting
44
E-Voting
45
E-Voting
46
E-Voting
47
E-Voting
CHAPTER 5
MODULE DESCRIPTION
Voting Form:
There is voting form in the project through which the voter can vote to the
candidate which they want to give but before that voter have to fill various details
about him after fill the information they get unique number by this help of that
unique number voter can give his vote to member that are participating in elections.
Party form:
There another form known as party form in this form there are different party
and very details about party the member that standing in election and the information
like agenda and leader message, party details.
48
E-Voting
Member form:
Member form in this form there is information about member for example like
background, financial background, police background.
Result form:
This is the last form. In this form voter get the information that he had vote for
the party successful and there is a thank you page in the end.
49
E-Voting
CHAPTER 6
FUTURE SCOPE & LIMITATION
6.1 Future scope:
Over the years, there have been many issues relating to electronic voting and
electronic voting systems. Various companies and software specialist have tried to
50
E-Voting
develop a system that will address electronic voting issues, but all have been unable to
develop and optimal system, or even anywhere near optimal. Society has not been
able to develop a universal, secure, user friendly and private electronic voting system.
Many electronic systems have been developed, but all have fallen short one way or
another. Often with some segment of society being left out. By continuous research,
Dr. Gilbert and his (Prime III) team have developed a unique system known nowhere
else in the world.
They have developed the Prime III electronic voting system which is
somewhat of an untouchable system compared to others, and it is the only system that
is universal enough to capture votes from all persons in society. The two main voting
procedures that have been used by developers in electronic voting are Mark-Sense
ballots where the user shades in their vote and the other is Direct Recording
Elections (DREs) which allows users to vote via touch (Kohno, Stubblefield &
Rubin). Both have fallen short in being universal, in a sense that mark-sense ballots
can only be used for sighted voters or those with hands, and issues also arise when the
scanner is unable to detect the darkest mark (Kohno, Stubblefield & Rubin). In
reference to the DREs, again the issue arises if the user is blind or does not have any
hands. There are also many other issues with these systems such as security
vulnerabilities. There are other smaller systems, however many have not been
developed enough to be used in general elections.
51
E-Voting
CHAPTER 7
CONCLUSION
This ONLINE E-VOTING SYSTEM has been developed successfully and
tested with the sample client connections, from different systems. The benefits of this
system are considerable.
It is observed that the users are able to use the system easily. As all the users
are provided with the information required by them in GUI so the user with minimum
basic knowledge about the computer can be able to operate the system easily.
The users can obtain the required information with ease and accuracy from the
system. Various validation techniques are used to implement for the accuracy of data
for the user. Since the System can be used by authorized user only, a level of security
is provided.
52
E-Voting
CHAPTER 8
BIBLIOGRAPHY & REFERENCE
8.1 Reference:
1. System Analysis & Design By Elias Awad.
2. ASP.NET (VB.NET) complete reference by MacDonald
3. Websites:
www.Planetsourcecode.com
8.2 Bibliography:
Bryan Basham, Kathy Sierra, Bert Bates, Head First Servlets & JSP
o 4th Edition, OReily Publishers, 2004.
Grady Booch, James Rumbaugh, Ivar Jacobson, The UML
o User Guide 1st Edition, Addison Wesley, 1998.
Pankaj Jalote, An integrated Approach to Software
o Engineering 2nd Edition, Narosa Publishing House, 2000.
Roger.S.Pressman, A Practitioners Approach to Software
o Engineering 6th Edition, McGraw-Hill Publishers, 2004.
Herbert Schildt, Java 2:Complete Reference, 5th Edition,
o McGraw-Hill Publishers, 2003.
Java Server Programming (J2EE 1.4) Black Book, Kogent solutions
o Inc. Dreamtech Press, 2007.
53