A PROJECT REPORT ON Online Voting & Candidate Canvassing Management System Submitted in Partial Fulfillment of the Requirements for

the award of Degree Of MASTER OF COMPUTER APLLICATION By RIYAZULLAH.SYED Y11MC13027 Under the guidance of P.M.Indira Rani

DEPARTMENT OF COMPUTER SCIENCE HINDU COLLEGE P.G COURSES AMARAVATHI ROAD, GUNTUR.

ACHARYA NAGARJUNA UNIVERSITY MAY 2013

DECLARATION

I RIYAZULLAH.SYED with Regd.No Y11MC13027 here by declare that the project entitled ONLINE VOTING & CANDIDATE CANVASSING MANAGEMENT SYSTEM has been carried out by me at0 PenSoft Solution Pvt.Ltd., HYDERABAD. This Project is submitted to the Department of MCA, HINDU COLLEGE, GUNTUR for the partial fulfillment for the award degree of Master of Computer Application. The report has not been submitted for any degree or diploma of any university to the best of my knowledge.

(Riyazullah.Syed )

ACKNOWLEDGEMENTS I feel myself honored to place my warm salutation to HINDU COLLEGE, GUNTUR and Department of MCA, which gave me the opportunity to have a strong base in MCA and profound knowledge. I express my sincere thanks to Mr.CH.SUBBARAO, principal MCA PROGRAMME HINDU COLLEGE, GUNTUR for his constant support and encouraged throughout the project. I express mi immense gratitude to Mr.K.ATHMARAM, Head, Dept of MCA for his constant support and encouragement throughout the course of this project and being constant source of inspiration throughout the project. I express my immense gratitude to Miss P.M. INDIRA RANI, Asst, and Professor Dept of MCA for being the internal guide for his constant support and encouragement throughout the course of this project and being constant source of inspiration throughout the project. I also express my special thanks to Mr. L.Pradeep, Project Leader in PH Software Solution Pvt. Ltd., for his constant support and encouragement throughout the course of this project and being constant source of inspiration throughout the project. Finally, I take this opportunity to extend my full-hearted thanks, gratitude and respect to Dept. Lectures, all my friends, parents and well wishers for giving me valuable advice and constant support in all possible ways.

ABSTRACT

ABSTRACT

The objective of the project is to develop a system that enables election commission of India to conduct online elections. The purpose is to design a system that automates all the processes and activities related to elections. The system provides appropriate facilities for all the participating entities.

In the present scenario, the election process is conducted using conventional procedures. Election commission officials announce a particular date for elections. Candidates file their nominations, which are scrutinized by officials. Voters register their details with authorities. On the polling day, voters cast their vote at the polling centers. Counting of votes is done and results are announced. All these activities involve a number of officials and the process is time consuming.

The proposed system is a web based application, which allows online polling. The system allows registration of voters and allows candidates to do online canvassing. All the processes are automated and the elections can be conducted more efficiently and effectively. The system provides a number of interfaces for this purpose. Time and effort are drastically reduced.

INDEX

SNO
01 02

CONTENTS
INTRODUCTION ABOUT ORGANIZATION INTRODUCTION ABOUT PROJECT 2.1. Present System 2.2. Need For The New System 2.3. Project Scope & Objective 2.4. Problem Definition

PAGNO
1 2-3

03

SYSTEM ANALYSIS 3.1. System Description 3.2. System Constraints 3.3. System Requirements Specification 3.4. Feasibility Study

4 - 12

04

SYSTEM DESIGN 4.1. Structure Chart 4.2. E-R Diagram 4.3. DFDS 4.4. UML Diagram

13 - 40

05

SYSTEM CODING 5.1. Source Code / Pseudo Code

41 - 47

06

SYSTEM TESTING 6.1. Testing Methodologies Used For Project 6.2. Test Cases 6.3. Test Result

48 - 51

07 08 09 10 11 12

CONCLUSION FUTURE ENHANCEMENT APPENDIX A : FORM / SCREENS APPENDIX B : REPORTS APPENDIX C : DATA DICTIONARY BIBILOGRAPHY

52 53 54 - 60 61 - 63 64 66 67

INTRODUCTION ABOUT ORGANIZATION

INTRODUCTION ABOUT ORGANIZATION India, complete offshore software development company Hyderabad, India. PENSOFT TECHNOLOGY has been providing software outsourcing services for its customers across the globe since 2001. Over this time, our pool of developers has gained strong experience in handling all major programming languages and technologies. We are committed to supplying customers with state-of-the-art Java, .Net development services as well as Unix/Linux, web and database solutions. PENSOFT TECHNOLOGY mission: To enable people and companies to maximize their business success. We stick to the following principles in delivering our mission: We are able to decrease project development efforts and duration and, thus, your development costs. A separate team of software architects develops and improves architecture components that are the basis of your software or web project. Free to you. Human element is at the heart of offshore software development. In our software company we have organized two laboratories and one training center in cooperation with two major technical universities in our country. It enables us to find, select, and employ the best technical specialists and managers available on the market of software companies. PENSOFT TECHNOLOGY strives to provide you custom software solutions that will help you to remain in step with your competition by continuously improving your information technology-based business solutions. For this, we use modern software development platforms, software development tools as well as employ latest project management techniques and software engineering practices like XP (Extreme Programming) and DSDM.

INTRODUCTION ABOUT PROJECT

02. INTRODUCTION ABOUT PROJECT

Title: Online voting & candidate canvassing Management system

2.1. Present System

In the present scenario, the election process is conducted using conventional procedures. Election commission officials announce a particular date for elections. Candidates file their nominations, which are scrutinized by officials. Voters register their details with authorities. On the polling day, voters cast their vote at the polling centers. Counting of votes is done and results are announced. All these activities involve a number of officials and the process is time consuming.

2.2. Need for the New System The proposed system is a web based application, which allows online polling. The system allows registration of voters and allows candidates to do online canvassing. All the processes are automated and the elections can be conducted more efficiently and effectively. The system provides a number of interfaces for this purpose. Time and effort are drastically reduced.

2.3. Project Scope & Objective

The objective of the project is to develop a system that enables election to conduct online elections. The purpose is to design a system that automates all the processes and activities related to elections. The system provides appropriate facilities for all the participating entities. commission of India

2.4. Problem Definition

To provide flexibility to the users, the interfaces have been developed that are accessible through a browser. The GUIS at the top level have been categorized as 1. Administrative user interface 2. The operational or generic user interface

The administrative user interface concentrates on the consistent information that is practically, part of the organizational activities and which needs proper authentication for the data collection. These interfaces help the administrators with all the transactional states like Data insertion, Data deletion and Date updation along with the extensive data search capabilities.

The operational or generic user interface helps the end users of the system in transactions through the existing data and required services. The operational user interface also helps the ordinary users in managing their own information in a customized manner as per the included flexibilities.

SYSTEM ANALYSIS

3. SYSTEM ANALYSIS
3.1. SYSTEM DESCRIPTION

Number of Modules

After careful analysis the system has been identified to have the following modules:
1. Authentication and Security Module 2. Political parties Module 3. Member Assets Module 4. Party Campaign Module 5. Election Module 6. Reports Module

1. Authentication and Security Module This module allows voters to register their details and obtain a voter id card. 2. Political Parties Module This module provides details of each political party participating in the elections. Party symbol, party nominated candidates, constituency details and other information is provided. 3. Member Asset Module: This module provides details of assets held by the candidates. For each candidate ones professional details are maintained.

4. Party Campaign Module: This module maintains details of all political parties and details of candidates. The information about campaigners, cost involved and procedures are also specified. The nomination details of each candidate are available. The election officer details are also included.

5. Elections Module: This module is used to present election schedules as prepared by election commission authorities.

6. Reports Module: This module allows generation of reports based on various criteria.

3.3. SYSTEM REQUIREMENT SPECIFICATIONS

Title: Online voting & candidate canvassing Management system

Objective:

The objective of the project is to develop a system that enables election to conduct online elections.

commission of India

The purpose is to design a system that automates all the processes and activities related to elections. The system provides appropriate facilities for all the participating entities.

Existing System:

In the present scenario, the election process is conducted using conventional procedures. Election commission officials announce a particular date for elections. Candidates file their nominations, which are scrutinized by officials. Voters register their details with authorities. On the polling day, voters cast their vote at the polling centers. Counting of votes is done and results are announced. All these activities involve a number of officials and the process is time consuming.

Proposed System: The proposed system is a web based application, which allows online polling. The system allows registration of voters and allows candidates to do online canvassing. All the processes are automated and the elections can be conducted more efficiently and effectively. The system provides a number of interfaces for this purpose. Time and effort are drastically reduced.

Study of the system:

To provide flexibility to the users, the interfaces have been developed that are accessible through a browser. The GUIS at the top level have been categorized as 3. Administrative user interface 4. The operational or generic user interface

The administrative user interface concentrates on the consistent information that is practically, part of the organizational activities and which needs proper authentication for the data collection. These interfaces help the administrators with all the transactional states like Data insertion, Data deletion and Date updation along with the extensive data search capabilities.

The operational or generic user interface helps the end users of the system in transactions through the existing data and required services. The operational user interface also helps the ordinary users in managing their own information in a customized manner as per the included flexibilities.

3.4. FEASIBILITY STUDY

Feasibility Report:
Preliminary investigation examines project feasibility; the likelihood the system will be useful to the organization. The main objective of the feasibility study is to test the Technical, Operational and Economical feasibility for adding new modules and debugging old running system. All systems are feasible if they are given unlimited resources and infinite time. There are aspects in the feasibility study portion of the preliminary investigation:

Technical Feasibility Operation Feasibility Economical Feasibility

Technical Feasibility:

The technical issue usually raised during the feasibility stage of the investigation includes the following:

Does the necessary technology exist to do what is suggested? Do the proposed equipments have the technical capacity to hold the data required to use the new system? Will the proposed system provide adequate response to inquiries, regardless of the number or location of users? Can the system be upgraded if developed? Are there technical guarantees of accuracy, reliability, ease of access and data security?

Operational Feasibility:

Proposed projects are beneficial only if they can be turned out into information systems, which will meet the organizations operating requirements. Operational feasibility aspects of the project are to be taken as an important part of the project implementation. Some of the important issues raised are to test the operational feasibility of a project includes the following: -

Is there sufficient support for the management from the users? Will the system be used and work properly if it is being developed and implemented? Will there be any resistance from the user that will undermine the possible application benefits? This system is targeted to be in accordance with the above-mentioned issues. Beforehand, the

management issues and user requirements have been taken into consideration. So there is no question of resistance from the users that can undermine the possible application benefits.

The well-planned design would ensure the optimal utilization of the computer resources and would help in the improvement of performance status.

Economic Feasibility:

A system can be developed technically and that will be used if installed must still be a good investment for the organization. In the economical feasibility, the development cost in creating the system is evaluated against the ultimate benefit derived from the new systems. Financial benefits must equal or exceed the costs. The system is economically feasible. It does not require any additional hardware or software. SDLC Methodology: This document play a vital role in the development of life cycle (SDLC) as it describes the complete requirement of the system. It means for use by developers and will be the basic during testing phase. Any changes made to the requirements in the future will have to go through formal change approval process. SPIRAL MODEL was defined by Barry Boehm in his 1988 article, A spiral Model of Software Development and Enhancement. This model was not the first model to discuss

iterative development, but it was the first model to explain why the iteration models. As originally envisioned, the iterations were typically 6 months to 2 years long. Each phase starts with a design goal and ends with a client reviewing the progress thus far. Analysis and engineering efforts are applied at each phase of the project, with an eye toward the end goal of the project. The steps for Spiral Model can be generalized as follows: The new system requirements are defined in as much details as possible. This usually

involves interviewing a number of users representing all the external or internal users and other aspects of the existing system. A preliminary design is created for the new system.

 A first prototype of the new system is constructed from the preliminary design. This is usually a scaled-down system, and represents an approximation of the characteristics of the final product. A second prototype is evolved by a fourfold procedure: 1. Evaluating the first prototype in terms of its strengths, weakness, and risks. 2. Defining the requirements of the second prototype. 3. Planning an designing the second prototype. 4. Constructing and testing the second prototype. At the customer option, the entire project can be aborted if the risk is deemed too great. Risk factors might involved development cost overruns, operating-cost miscalculation, or any other factor that could, in the customers judgment, result in a less-than-satisfactory final product. The existing prototype is evaluated in the same manner as was the previous prototype, and if necessary, another prototype is developed from it according to the fourfold procedure outlined above. The preceding steps are iterated until the customer is satisfied that the refined prototype represents the final product desired. The final system is constructed, based on the refined prototype. The final system is thoroughly evaluated and tested. Routine maintenance is carried on a

continuing basis to prevent large scale failures and to minimize down time.

10

The following diagram shows how a spiral model acts like:

11

Advantages: Estimates(i.e. budget, schedule etc .) become more relistic as work progresses, because important issues discoved earlier. It is more able to cope with the changes that are software development generally entails. Software engineers can get their hands in and start woring on the core of a project earlier

Software requirements:

Operating System Technology Web Technologies IDE Web Server Database Java Version

: Windows : Java and J2EE : Html, JavaScript, CSS : My Eclipse : Tomcat : Oracle : J2SDK1.5

Hardware requirements:

Hardware RAM

: Pentium : 1GB

12

SYSTEM DESIGN

E-R Diagram

4.2. E-R DIAGRAM

CAMPAIGNITEMTYPEMASTER
CAMPAIGNTYPEITEMID CAMPAGINTYPEITEMNAME CAMPAGINTYPEITEMDESC CAMPAIGNTYPEITEMABBR

ELECTIONS
ELECTIONID ELECTIONDATE INCHARGE (FK) REMARKS

EMPADDRESSES
ADDRESSID EMPLOYEEID (FK) HNO STREET CITY STATE PINCODE PHONENO EMAILID

EMPLOYEES
EMPLOYEEID USERID (FK) FIRSTNAME LASTNAME QUALIFICATION DESIGNATION MANAGER (FK) DEPARTMENTID (FK) DOJ DOB PHOTO

CAMPAIGNCOST
COSTID COSTVALUE COSTVALUEDATE CAMPAGINDATE PARTYID (FK) COSTITEMTYPEID (FK) CAMPAIGNDATE COSTSUBMITTEDMEMBERID (FK) ELECTIONID (FK) CURRENTCOSTSUMMARY REMARKS SCRUTINIZEDOFFICER (FK) COSTVALUEDOCIMAGES REMARKSONCOST

PARTYMEMBERTYPE
MEMBERTYPEID MEMBERTYPENAME MEMBERTYPEABBR MEMBERTYPEDESCRIPTION

USERS
USERID PASSWORD USERTYPE DESIGNATION

PARTYOFFICEADDRESS
ADDRESSID PARTYID (FK) HNO STREET CITY STATE PINCODE PHONENO EMAILID WEBLINK

PARTYCOMMITTEE
MEMBERID PARTYID (FK) MEMBERNAME MEMBERTYPE (FK) CONTACTNO MEMBERSHIPSTART DUARATION CURRENTSTATUS REMARKS PHOTO

DEPARTMENTS
DEPARTMENTID DEPARTMENTNAME DEPARTMENTABBR DEPARTMENTINCHGID

ASSETS POLITICALPARTIES
PARTYID PARTYNAME PASSWORD PARTYVISIONSTATEMENT PARTYMISSIONSTATEMENT PARTYTAGLINE PARTYREGISTEREDDATE PARTYREGISTEREDBY (FK) AFFLIATEDUNITNAME PARTYACTIVATIONSTATUS PARTYTYPE PARTYFLAG PARTYSYMBOL PARTYINTROVEDEO ASSETID ASSETTYPEID (FK) COMMITTEEMEMBERID (FK) REGISTRATIONDATE SUBMITTEDCOST ASSETCOST ASSETIMAGES SCRUTINYDONEBY REGISTRATIONDOCSIMAGE REMARKSBYESCRUTINYOFFICER

ASSETSTYPE
ASSETTYPEID ASSETTYPENAME ASSETTYPEABBR ASSETTYPEDESCRIPTION ASSETTYPEIMAGE

STATEWISEELECTIONS
ELECTIONID ELECTIONTYPE STATEID (FK) ELECTIONSTARTDATE ELECTIONENDDATE CAMPAIGNSTARTDATE CAMPAIGNENDDATE CAMPAIGNCOSTLIMIT REMARKS

STATESMASTER
STATEID STATENAME STATEABBR

13

Data Flow Diagrams

4.3. DATA FLOW DIAGRAMS Data Flow Diagrams: A graphical tool used to describe and analyze the moment of data through a system manual or automated including the process, stores of data, and delays in the system. Data Flow Diagrams are the central tool and the basis from which other components are developed. The transformation of data from input to output, through processes, may be described logically and independently of the physical components associated with the system. The DFD is also know as a data flow graph or a bubble chart. DFDs are the model of the proposed system. They clearly should show the requirements on which the new system should be built. Later during design activity this is taken as the basis for drawing the systems structure charts. The Basic Notation used to create a DFDs are as follows:

1. Dataflow: Data move in a specific direction from an origin to a destination.

2. Process: People, procedures, or devices that use or produce (Transform) Data. The physical component is not identified.

14

3. Source: External sources or destination of data, which may be People, programs, organizations or other entities.

4. Data Store: Here data are stored or referenced by a process in the System.

15

System Level Context Diagram:

16

LEVEL-1 DFD

Employee

Parties Registratio n Members

User

Login

UI Displaying Set of Operations Results

General Informatio n

MemberAss ets

Reports

17

AUTHENTICATION DFD:

UI Interface

Username,Password

Authentication Server

Authentication Server

Authentication

UI Interface

NO

18

Administrator/Employee Context Level DFD

Parties

Data Output Stages Partymembe rs

MemberAsset s

Administrator /Employee

Data Input Stages

Data Output Stages Election Date

UI Screens

Results

Data Output Stages

Reports

Reports

Employees

Data Base

19

Level 1.0:-

Data Input Stage UI Interface Add Employee

Data Output Stage Data Base

Level 1.0.1:-

Data Input Stage View Employees Fetch

Data Output Stage GUI Interface

Level 1.1:-

Data Input Stage Administrator AddParty

Data Output Stage Data Base

20

Level 1.1.0:-

Data Input Stage ViewPsrties Data Base

Data Output Stage UI Interface

Level 1.2:-

UI Interface

Data Input Stage

AddMember

Data Output Stage

Data Base

Level 1.3:-

Data Input Stage UI Interface AddMemberAssets

Data Output Stage Data Base

21

Party Context Level DFD

Parties

Data Output Stages Partymembe rs

MemberAsset s

Party

Data Input Stages

Data Output Stages Election Date

UI Screens

Results

Data Output Stages

Reports

Reports

Employees

Data Base

22

Level 1.0:-

Data Input Stage ViewMembers Fetch

Data Output Stage GUI Interface

Level 1.1:-

Data Input Stage ViewAssets Data Base

Data Output Stage UI Interface

Level 1.2:-

Data Input Stage ViewElectionDate Data Base

Data Output Stage UI Interface

Level 1.3:-

Data Input Stage ViewResults Data Base

Data Output Stage UI Interface

23

Voter Context Level DFD

Parties

Data Output Stages Partymembe rs

MemberAsset s

Voter

Data Input Stages

Data Output Stages Election Date

UI Screens

Results

Data Output Stages

Reports

Reports

Employees

Data Base

24

Level 1.0:-

Data Input Stage ViewResults Fetch

Data Output Stage UI Interface

Level 1.1:-

Data Input Stage ViewElectionDates Data Base

Data Output Stage UI Interface

Level 1.2:-

Data Input Stage ViewParties Fetch

Data Output Stage UI Interface

Level 1.3:-

Data Input Stage ViewPartyMembers Data Base

Data Output Stage UI Interface

25

UML Diagrams

4.4. UML DAIGRAMS

CLASS DIAGRAMS

CLASS COLLABORATIVE DIAGRAMS

26

ElectionDAO PartyNamesDAO -id: int -id: int ~con: Connection ~con: Connection ~con: Connection +getPartyNames(): Hashtable +getMemberIds(): Hashtable +announceElections(eb: ElectionBean): boolean +viewPartis(storepath: String): CoreHash +getAssetType(): Hashtable +getItems1(): Hashtable +registerAsset(ab: AssetBean): boolean +viewAnnounceElections(storepath: String): CoreHash +viewPartyAssetMembers(storepath: String): CoreHash SecurityDAO ~con: Connection -desc: String AbstractDataAccessObject -flag: boolean -mCon: Connection StatesDAO <<create>>+SecurityDAO() -mProps: Properties +getStateNames(): Hashtable +loginCheck(regbean: Profile): String +getProperties(): Properties +loginaudit(loginid: String) +setProperties(aProps: Properties) +changePassword(regbean: Profile): boolean +getConnection(): Connection +getSequenceID(tableName: String, pkid: String): int +changeQuestion(regbean: Profile): boolean +recoverPasswordByQuestion(regbean: Profile): String +checkUser(userName: String): String CampaignDAO -id: int -id1: int -id2: int -id0: int ProfileDAO -scrutinizedOfficer: int +con: Connection -memberId: int -flag: boolean ~con: Connection +registration(regbean: Profile): boolean ~st: Statement ~partyName: String ~itemType: String PartyMemberDAO ~capaignCostValue: String -flag: boolean ~remarks: String ~id: int ~costSummary: String ~con: Connection ~documemntImage: String ~partyName: String ~photopath: String ~st: Statement ~f: File +registerMember(registerMember: MemberProfile): boolean ~fis: FileInputStream +con1() +getCampaignCostId(): Hashtable +viewPartyMembers(storepath: String): CoreHash +getItems(): Hashtable +getItems1(): Hashtable +reg1(cb: CampaignBean) +updateCampaignCost(cb: CampaignBean): boolean +registerCampaignCost(cb: CampaignBean): boolean +con1(ptype: String): int +viewCampaignCost(storepath: String, ptype: String): CoreHash +deleteCampaignCost(ptype: String): int

AssetDAO

27

USECASE DIAGRAMS

1. system Use Case Diagram

System

Voter

Ballot Crusader

Political Parties

EC Employees

28

2.Voter Use Case Diagram

Abou EC

Political PartiesDetails

Voter Election Dates

ElectionResults

29

3.Political Party Use Case Diagram

Home

PartyDetails

MembersDetails

MemberAssetDetails Political Parties Election Dates

ElectionResults

Security

30

4. Administrator Use Case Diagram

AdminHome AddPartyDetails

<<include>> <<include>>

ViewPartyDetails

PartyDetails

DeletePartyDetails <<include>> AddMenbers

MembersDetails

<<include>> <<include>>

ViewMembers

AddAssets MemberAssetDetails <<include>> <<include>> <<include>> ViewAssesnt

UpdateAssets

AnnounceDates EC Employees Election Dates <<include>> <<include>> changeDates

AddElectionResults ElectionResults <<include>> <<include>> <<include>> ViewElectionResults EmployeeProfile

<<include>>

UpdateElectionResults

ViewProfile

<<include>>

UpdateProfile Security <<include>> <<include>> changeQuestion

changePassword

31

OPERATIONAL LEVEL SEQUENCE AND COLLABORATION DIAGRAMS

1. Voter Sequence Diagram

EC Details : Voter

PartyDetails

ElectionDates

ElectionResults

1 : viewElectionDetails()

2 : viewParty,memberDetails()

3 : viewDates()

4 : viewResults()

32

2.Political Party Sequence Diagram

Home : Political Parties 1 : login()

EC Details PartyDetails

ElectionDates ElectionResults Profile

Security

logout

2 : viewElectionDetails() 3 : viewPartyDetails()

4 : viewElectionDates()

5 : viewElectionResults()

6 : view,updateProfile()

7 : changePassword,changeQuestion()

8 : logout()

9 : home()

33

3.Administrator Sequence Diagram

AdminHome : Administrator 1 : login()

PartyRegistration PartyCampaigns

PartyMembers

MembersAssets

ElectionDetails

EmpProfile

security

logout

2 : registerParty()

3 : viewCampaign()

4 : viewMemberDetails()

5 : viewMemberProperties()

6 : generateElectionDates()

7 : employeeProfile()

8 : changePassword,changeQuestion()

9 : logout()

10 : home()

34

Operation-Level Sequence Diagram 1. Login Sequence Diagram

EC Employee 1 : login()

Login

Parties

2 : login() 3 : validate() 4 : AdminHome() 5 : PartyHome()

35

2.Voter Sequence Diagram

Voter

Electiondates

Results

Party

PartyMembers

1 : viewElection() 2 : viewElectionResult()

3 : viewPartiesDetails()

4 : viewPartyMembers()

36

ACTIVITY DIAGRAMS

1. Voter Activity Diagram

Voter

Home

ElectionDates

Results

AboutEC

PartiesDetails

37

Political Party Activity Diagram

Voter

Login ifFail

Enter UserName,Password

validate ifSuccess

Home

ElectionDates

MemberAssets

Members

Results

Logout

ViewCampaingLimit

ViewAssets

Viewmembers

UpdateMember

38

2. Employee/EC Activity Diagram

Admin/Emp

Login ifFail

Enter UserName,Password

validate

ifSuccess

Home

Party

Members

Assets

Elections

Employees

Logout

AddParty DeletePart AddMember

DeleteMEmber AddAsset

UpdateAsset

AnnounceDate

Results

AddEmp

RemoveEmp

39

State Chat Diagram:

40

SYSTEM CODING

5. SYSTEM CODING

5.1. Source Code / Pseudo Code Home page <HTML> <HEAD> <TITLE>Election Commision</TITLE> <link rel="stylesheet" type="text/css" href="stylesheet.css"> <script language="javascript" src="validations.js"> </script> <script laguage="javascript"> function validations() { if (!isName(sup.txtusr.value) || !isName(sup.txtpwd.value)) { alert("Please Fill the Data"); return false; } else return true; }

function homeclicked() {window.location.href="homepage.html";} function instructionsclicked() {window.location.href="instructions.html";} 41

function contactusclicked() {window.location.href="contactus.html";} function voterenquiryclicked() {window.location.href="voterenquiry.jsp";} function resultenquiryclicked() {window.location.href="electionresults.jsp";} function scheduleenquiryclicked() {window.location.href="scheduleenquiry.jsp";} function voterlistclicked() {window.location.href="list";} function nominationsclicked() {window.location.href="newnominations.jsp";} function voterregistrationclicked() {window.location.href="newvoter.html";} function onlinevotingclicked() {window.location.href="voterlogin.jsp";} function logindiscussionclicked() {window.location.href="logindiscussion.jsp";} function viewdiscussionclicked() {window.location.href="viewdiscussion.jsp";} function hi1() {submenu1.style.visibility="visible";submenu2.style.visibility="hidden";} function hi2() {submenu2.style.visibility="visible";submenu1.style.visibility="hidden";} function byeall() { 42

submenu1.style.visibility="hidden"; submenu2.style.visibility="hidden"; } </script> </HEAD> <!--<BODY text=#000000 vLink=#999900 aLink=#ff0000 link=#990000 bgColor=#ffffff> -> <BODY background="img3.jpg" width="100" height="100"> <center> <h1><center><img src="i1.gif" height=50/></center> </h1></center><hr color=lightslategray><br> <div style="LEFT: 8px; WIDTH: 752px; POSITION: absolute; TOP: 80px; HEIGHT: 30px"> <INPUT class="btn" type="button" value="Home" style="WIDTH: 137px; CURSOR: hand; HEIGHT: 24px" size=37 onClick="homeclicked()" onMouseOver="byeall()"> <INPUT class="btn" type="button" value="Instructions" style="WIDTH: 139px; CURSOR: hand; HEIGHT: 24px" size=39 id=button1 name=button1 onClick="instructionsclicked()" onMouseOver="byeall()"> <INPUT class="btn" type="button" value="Enquiry" style="WIDTH: 163px; HEIGHT: 24px" size=46 id=button2 name=button2 onMouseOver="hi1()"> <INPUT class="btn" type="button" value="Registration" style="WIDTH: 153px; HEIGHT: 24px" size=42 id=button3 name=button3 onMouseOver="hi2()"> <INPUT class="btn" type="button" value="Contact Us" style="WIDTH: 140px; CURSOR: hand; HEIGHT: 24px" size=38 id=button4 name=button4 onClick="contactusclicked()" onMouseOver="byeall()"> </div> <div id="submenu1" style="Z-INDEX: 3; LEFT: 292px; VISIBILITY: hidden; WIDTH: 164px; POSITION: absolute; TOP: 105px; HEIGHT: 100px"> <!-- <INPUT class="btn" type="button" value="Voter Enquiry" style="BORDERBOTTOM-COLOR: moccasin; WIDTH: 163px; CURSOR: hand; HEIGHT: 24px" size=46 id=button2 name=button2 onClick="voterenquiryclicked()"> -->

43

<INPUT class="btn" type="button" value="Result Enquiry" style="BORDERBOTTOM-COLOR: moccasin; WIDTH: 163px; CURSOR: hand; HEIGHT: 24px" size=46 id=button2 name=button2 onClick="resultenquiryclicked()"> <INPUT class="btn" type="button" value="Schedule Enquiry" style="BORDERBOTTOM-COLOR: moccasin; WIDTH: 163px; CURSOR: hand; HEIGHT: 24px" size=46 id=button2 name=button2 onClick="scheduleenquiryclicked()"> <!-- <INPUT class="btn" type="button" value="Voter List" style="WIDTH: 163px; CURSOR: hand; HEIGHT: 24px" size=46 id=button2 name=button2 onClick="voterlistclicked()"> --> </div> <div id="submenu2" style="DISPLAY: list-item; Z-INDEX: 3; LEFT: 459px; VISIBILITY: hidden; WIDTH: 164px; POSITION: absolute; TOP: 105px; HEIGHT: 74px"> <!-- <INPUT class="btn" type="button" value="Nominations" style="BORDERBOTTOM-COLOR: moccasin; WIDTH: 163px; CURSOR: hand; HEIGHT: 24px" size=46 id=button2 name=button2 onClick="nominationsclicked()"> --> <INPUT class="btn" type="button" value="Voter Registration" style="BORDERBOTTOM-COLOR: moccasin; WIDTH: 163px; CURSOR: hand; HEIGHT: 24px" size=46 id=button2 name=button2 onClick="voterregistrationclicked()"> <INPUT class="btn" type="button" value="Online Voting" style="BORDER-BOTTOMCOLOR: moccasin; WIDTH: 163px; CURSOR: hand; HEIGHT: 24px" size=46 id=button2 name=button2 onClick="onlinevotingclicked()"> <INPUT class="btn" type="button" value="Login Discussion" style="BORDERBOTTOM-COLOR: moccasin; WIDTH: 163px; CURSOR: hand; HEIGHT: 24px" size=46 id=button2 name=button2 onClick="logindiscussionclicked()"> <INPUT class="btn" type="button" value="View Discussion" style="WIDTH: 163px; CURSOR: hand; HEIGHT: 24px" size=46 id=button2 name=button2 onClick="viewdiscussionclicked()"> </div> <div hideFocus style ="LEFT: 239px; WIDTH: 512px; POSITION: absolute; TOP: 114px; HEIGHT: 303px"> <CENTER><IMG src="emps.jpg" width="75" height="75" border=0 ></CENTER> <P><B><FONT face=Arial,Helvetica><FONT color=#cc6600>Election 44

Commission</FONT></FONT></B> <P><IMG src="nirvachn.jpg" align=right><FONT face=Arial,Helvetica><FONT color=black><FONT size=-1>The Election Commission (EC) is the agency that oversees the vast job of maintaining records of the electorate, managing the logistics of voter identity cards and electoral rolls, organising elections &amp; bye-elections to the national Parliament (Lok Sabha) and the legislative assemblies of the Indian states.</FONT></FONT></FONT> <P><FONT face=Arial,Helvetica><FONT size=-1>The Election Commission is headquartered at Nirvachan Sadan in New Delhi. It also has offices in the capitals of all states as well in many district headquarters. The election commission is headed by a three member group of Election Commissioners of which one is the Chief Election Commissioner (CEC). The team includes a number of assistant election commissioners, electoral officers and staff. During the elections, to facilitate polling and monitor the days of campaigning by the candidates, the Election Commission takes on thousands of government employees on deputation. The election commission is also able to summon the assistance of the police forces in the various states, the para-military and even the army if required to maintain law and order during the elections.</FONT></FONT> <P><FONT face=Arial,Helvetica><FONT size=-1>The work that goes into the organising of an election in India is awesome. India this year will have over 500 million voters on its electoral rolls. Of this on an average about 60% come out to cast their vote in the various villages &amp; towns of the country. Even if elections are staggered over 2-3 different days, an average of 100 million people need to be managed during the few hours of voting.</FONT></FONT> 45

<P><FONT face=Arial,Helvetica><FONT size=-1>In the past elections, the Election Commission has deployed large infrastructure of computing &amp; communication facilities to ease the workload and make the process more effective and secure. The election commission also posts information regularly on its website that was launched during the general elections last year.</FONT></FONT> <P><B><FONT face=Arial,Helvetica><FONT color=#3333ff><FONT size=-1>Election Commissioners</FONT></FONT></FONT></B> <UL> <LI><FONT face=Arial,Helvetica><FONT size=-1>MS Gill (Chief Election Commissioner)</FONT></FONT> <LI><FONT face=Arial,Helvetica><FONT size=-1>GVG Krishnamurthy</FONT></FONT> <LI><FONT face=Arial,Helvetica><FONT size=-1>JM Lyngdoh</FONT></FONT> </LI></UL><FONT face=Arial,Helvetica><FONT size=-1> <HR width="100%">

<CENTER><FONT face=Arial,Helvetica><FONT size=-2><B><I><FONT color=#993366>IndiaMap</FONT></I></B> is maintained by &amp; is the intellectual property of <B><FONT color=#ff6600>NixelNet</FONT></B>. All rights reserved.</FONT></FONT></CENTER> </div> <DIV style="BORDER-RIGHT: #778899 thin solid; LEFT: 9px; WIDTH: 213px; POSITION: absolute; TOP: 107px; HEIGHT: 344px">

<DIV

46

style="LEFT: 2px; WIDTH: 189px; POSITION: absolute; TOP: 80px; HEIGHT: 86px">&nbsp;&nbsp; &nbsp;&nbsp; <form name="sup" method="post" action="commisioner" onSubmit="return validations()">&nbsp;&nbsp;&nbsp;&nbsp; <STRONG>Log In : </STRONG><INPUT class=tbox id=txtusr style="WIDTH: 110px; HEIGHT: 22px" size=13 name=txtusr><BR><STRONG><br>Password : </STRONG><INPUT class=tbox id=txtpwd style="WIDTH: 112px; HEIGHT: 22px" type=password size=13 name=txtpwd> </DIV> <DIV style="LEFT: 82px; POSITION: absolute; TOP: 214px"><INPUT class=btn id=submit1 style="LEFT: 0px; WIDTH: 66px; BORDER-TOP-STYLE: ridge; BORDERRIGHT-STYLE: ridge; BORDER-LEFT-STYLE: ridge; TOP: -1px; HEIGHT: 24px; BORDER-BOTTOM-STYLE: ridge" type=submit size=27 value=Enter name=submit1> </FORM> </FONT> </BODY> </HTML>

47

SYSTEM TESTING

06. SYSTEM TESTING

INTRODUCTION TO TESTING

Testing is a process, which reveals errors in the

program. It is the major quality measure

employed during software development. During software development. During testing, the program is executed with a set of test cases and the output of the program for the test cases is evaluated to determine if the program is performing as it is expected to perform.

TESTING IN STRATEGIES

In order to make sure that the system does not have errors, the different levels of testing strategies that are applied at differing phases of software development are:
Unit Testing:

Unit Testing is done on individual modules as they are completed and become executable. It is confined only to the designer's requirements.
Each module can be tested using the following two Strategies:

Black Box Testing

In this strategy some test cases are generated as input conditions that fully execute all functional requirements for the program. This testing has following categories:
Incorrect or missing functions

been uses to find errors in the

48

Interface errors Errors in data structure or external database access Performance errors Initialization and termination errors. In this testing only the output is checked for correctness. The logical flow of the data is not checked.

White Box testing

In this the test cases are generated on the logic of each module by drawing flow graphs of that module and logical decisions are tested on all the cases. It has been uses to generate the test cases in the following cases:
Guarantee that all independent paths have been Executed. Execute all logical decisions on their true and false Sides. Execute all loops at their boundaries and within their operational bounds Execute internal data structures to ensure their validity.

Integrating Testing

Integration testing ensures that software and subsystems work together a whole. It tests the interface of all the modules to make sure that the modules behave properly when integrated together.

System Testing

Involves in-house testing of the entire system before delivery to the user. It's aim is to satisfy the user the system meets all requirements of the client's specifications.
49

Acceptance Testing

It is a pre-delivery testing in which entire system is tested at client's site on real world data to find errors.

Test Approach

Testing can be done in two ways

Bottom up approach Top down approach

Bottom up Approach

Testing can be performed starting from smallest and lowest level modules and proceeding one at a time. For each module in bottom up testing a short program executes the module and provides the needed data so that the module is asked to perform the way it will when embedded with in the larger system. When bottom level modules are tested attention turns to those on the next level that use the lower level ones they are tested individually and then linked with the previously examined lower level modules.

50

Top down approach

This type of testing starts from upper level modules. Since the detailed activities usually performed in the lower level routines are not provided stubs are written. A stub is a module shell called by upper level module and that when reached properly will return a message to the calling module indicating that proper interaction occurred. No attempt is made to verify the correctness of the lower level module.

Validation

The system has been tested and implemented successfully and thus ensured that all the requirements as listed in the software requirements specification are completely fulfilled. In case of erroneous input corresponding error messages are displayed

51

CONCLUSION

CONCLUSION

Finally conclusion the objective of the project is to develop a system that enables election commission of India to conduct online elections. The purpose is to design a system that automates all the processes and activities related to elections.

In the present scenario, the election process is conducted using conventional procedures. Election commission officials announce a particular date for elections.

The proposed system is a web based application, which allows online polling. The system allows registration of voters and allows candidates to do online canvassing.

52

FUTURE ENHANCEMENTS

FUTURE ENHANCEMENTS

1. 2. 3. 4.

Provide more user friendly Environment. The system provides number of interfaces for this purpose. Time & effort are drastically reduced. The system provides appropriate facilities for all the participating entites.

53

APPENDEX A: FORMS / SCREENS

FORM / SCREENS
0.9. Appendix: A

54

55

56

57

58

59

60

APPENDEX B : REPORTS

10. Appendix: B REPORTS

61

62

63

APPENDEX C: DATA DICTIONARY

APPENDIX C: DATA DICTIONARY

64

65

66

BIBLIOGRAPHY

BIBLIOGRAPHY
References for the Project Development Were Taken From the following Books and Web Sites.
JAVA Technologies

JAVA Complete Reference Java Script Programming by Yehuda Shiran Mastering JAVA Security JAVA2 Networking by Pistoria JAVA Security by Scotl oaks Head First EJB Sierra Bates J2EE Professional by Shadab siddiqui JAVA server pages by Larne Pekowsley JAVA Server pages by Nick Todd
HTML

HTML Black Book by Holzner

JDBC

Java Database Programming with JDBC by Patel moss. Software Engineering by Roger Pressman

67