final ultimate

8/8/2019 Final Ultimate

1/35

Online National Polling Version 1.0

Software Requirement Specification Date : 16 th Nov, 2009

Ultimate National Institute of Science and Technology

Ultimate / Orissa 2009

NATIONAL INSTITUTE OF SCIENCE AND TECHNOLOGY

ONLINE NATIONAL POLLING

Software Requirement Specification

Team

Ultimate

Project Guide

Mr. Debanand Kanhar

Team Members

Keshab Charana Acharya

Sibani Dash

Kanhu Charan Panigrahi

Lopamudra Panigrahy


2/35





TABLE OF CONTENT

1 INTRODUCTION ............................................................. 3

1.1 Purpose: .................................................................................................................... 3

1.2 Scope: ........................................................................................................................ 3

1.3 Abbreviations ............................................................................................................ 4

1.4 References ................................................................................................................. 5

1.5 Technologies ............................................................................................................. 5

1.6 Overview ................................................................................................................... 5

2. OVERALL DESCRIPTION: .............................................. 6

2.1 Product Perspective ................................................................................................... 6

2.2 Software Interface: .................................................................................................... 6

2.3 Hardware Interface: .................................................................................................. 7

2.4 Product Function: ...................................................................................................... 7

2.5 User Characteristics: ................................................................................................. 8

2.6 Constraints: ............................................................................................................... 8

2.7 Use Case Model Survey ............................................................................................ 9 2.8 Database Design: .................................................................................................... 12

2.9 Assumptions and Dependencies: ............................................................................ 13

3. SPECIFIC REQUIREMENTS ......................................... 13

3.1 USECASE REPORT: ............................................................................................. 13

3.2 Supplementary Requirements: ................................................................................ 34


3/35





1 INTRODUCTION

1.1 Purpose:

Online National Polling is for making the election available on the World Wide Web with

different functionalities. As we know India is a democratic country and everyone have

the right to vote but due to some local activities like terrorism, pressure of political

parties, naxlites and bad weather the percentage of votes is getting less. So its on

initiative by the Election Commission of India to make it available at home.

1.2 Scope:

Statistics of all the elections have done so far is available in all prospective. Candidate can campaign through chat rooms and forums. Any user can send mail to any one. Administrator can track all the users through logs. Manage all account details of candidate, field officer, voter, and administrator.

Any user can send their complaints to administrator 24 hours. Maintain history of candidates, MPs, constituencies, parties and election laws. Provides secure access of confidential data i.e user details. Allow authorized voter to vote. Maintain all the details about candidates constituency wise. Views the current statistics as well as how many vote each candidate have got

constituency, area, and region wise.

Views the map of the polling stations (polling internet centers). Website is highly customizable and flexible enough to easily deploy. All users are authenticated to avail the service.


4/35





Confirmation link is sent to the new user and employee when signing up. Java based client for officers and administrator. Chat facility is available for working officers as well as candidates. FAQ section is also included for users benefit. Duplication of vote is not possible.

1.3 Abbreviations

HTML Hypertext Markup Language is to create static websites .

J2EE Java 2 Enterprise Edition is a programming platform and it is the part of the java platform for developing and running distributed java applications.

WAS CE Web sphere application server community edition is an applicationserver that runs and supports the J2EE and web service applications.

RSA Rational Software Architect is a designer toolkit which is designed fordevelop more complex projects by providing fully dynamic web service.

RAD Rational Application developer is a development toolkit which is

designed for developing dynamic web application.

DB2 Database 2 is the database management system that provides a flexibleand efficient database platform to erect strong on demand business applications.

XML - Extensive Markup Language used for data transfer and XML is storednaturally in DB2.

EJB Enterprise java bean, it is architecture for the development anddeployment of transactional, distributed object applications-based.

HTTP Hypertext transfer protocol is a transaction oriented client/serverprotocol between web browser and a web server.

HTTPS Secure hypertext transfer protocol is a hypertext transfer protocol oversecure socket layer.


5/35





1.4 References

IEEE SRS format Project specification requirement (provided by IBM)

1.5 Technologies

J2EE: Application Architecture DB2 Express C: Database RAD: Development Tool

WAS CE: Web Server Rational: Design Tool

1.6 Overview

SRS will include two sections:

Overall Description will describe major components of the system,interconnection and external interfaces.

Specific Requirements will describe the functions of actors, their role in thesystem and constraints.


6/35





2. OVERALL DESCRIPTION:Describe the general factors that affect the product and its requirements.

2.1 Product Perspective

2.2 Software Interface: Client on Internet : Web Browser, Operating System (any)Client on Intranet : JAVA based Client Software, Operating System

Web Server : WAS CE, Operating System (any)

Data Base Server : DB2, Operating System (any)

Development End : RAD (J2EE, Java, Servlets, HTML),

DB2, OS (Windows), Web Server.

DATABASE

IBM DB2

WSA CE

User BrowserFor

Public andcandidate

Java Basedclient for

Administrator

HTTP/ HTTPS

JREENVIRONMENT

CLIENTAPPLICATION

SEVER DATABASE


7/35





2.3 Hardware Interface:

CLIENT SIDE

Processor Ram Disk space

Internet Explorer6.0

Pentium II at 500MHz

64 MB 1 GB

SERVER SIDE Web sphereapplication serverCE

Pentium III at 1GHz

512 MB 2 GB

DB2 express C 9.7 PentiumIV at 2.5GHz

512 MB 1GB (Excludingdata size)

2.4 Product Function: The election related data are maintained here. There four users are there

1. General Public2. Administrator3. Field Officer4. Candidate

Java based client for user 3 and user 4. Administrator is fixed. Logs can be maintained by administrator. The entire user can change their passwords. Documents can be uploaded. Finger print authentication is available for user 3 and 4.


8/35





2.5 User Characteristics:

Every user should be comfortable of working with computer and net browsing.He must have basic knowledge of English too.

Only people more than 18 years are allowed to operate on this site.

2.6 Constraints:

GUI is only in English. Login and password is used for identification of customer

This system is working for single server. There is no maintainability of back up so availability will get affected. Limited to HTTP/HTTPS. User 3 and 4 cannot operate without having a JRE environment.


9/35





2.7 Use Case Model Survey

[USE CASE DIAGRAM]


10/35





1. ADMINISTRATOR: He/she (Chief Electoral Officer) responsible for managing

field officer, managing party, managing constituency, marinating database, producing

final result, publishing reports.

Managing Field officers: It includes appointing a field officer for aconstituency at the time of general election.CEO will create different roles like,

Returning Officer, DEC (District Election Officer), Counting Officer for

performing more than one tasks.

Managing Party: It includes adding or removing parties after validation.

Manage Constituencies: Add a new constituency or delete/join constituencies. Manage Database: Admin maintains the entire database and he is the only

authorized person to add/remove/edit records provided he/she has to get the

order from the highest designation.

Publish Result: After completion of election Admin will produce the finalresult of polling(constituency wise, party wise)

Publish Notice: It includes notices, maps, date of polling area wise, detail aboutpolling procedures, history during election

View log: Responsible for checking the logs of different system user forauditing and maintaining the integrity of the system.

2. FIELD OFFICERS: These officers are mainly responsible for verification of

candidates, verification of voters and for counting offline votes. These works has been

done by Returning Officers, DECs and counting officers respectively.

(i).Returning Officers: They are responsible for verifying candidates by considering all

the documents submitted by the candidate.

Verify Candidate: Based upon the details provided bye the nominees they will

verify it.


11/35





(ii).Sub-collector: Responsible for verifying voters, issuing voter id card, generate

report.

Verify Voter: Verifies voter details that have been applied by general public. Generate Report: Produces report on voter application. Issue Voter ID card: After acceptance of the report about voter registration by

administrator, issue the voter ID card.

(iii).Counting Officer: Responsible for submitting offline result to the admin so that

he/she can produce the final score.

3. CANDIDATES: They can apply for nomination, see result, campagain, and makecomplain.

Apply for Nomination: They can apply for nomination with proper documents,which will include their personal and professional details, along with the party

detail which they want to be a part of.

See Result: They can see result of all the candidates who are participating. Making Complains: They can make complains and that will be accepted by the

administrator.

Campaigning: They will do campaigning for publicity or popularity throughforums and chat-room.

4. GENERAL PUBLIC: They can register for voting, can vote, can see electoralrole, can see the polling schedule, and can see details about candidate, party.

Apply for voter registration: General public can apply for voter registration bygiving documents of birth certificate, resident certificate,address,photo.

View Report: General public can see weather their name is there in voter list ornot.

Vote: Can give vote through this web site. See details: It includes seeing details about constituency, candidates, party and

about election schedules.


12/35





2.8 Database Design:


13/35





2.9 Assumptions and Dependencies:

The details related to the election, verification, notices provided manually. Administrator is created in the system already. Roles and tasks are predefined.

3. SPECIFIC REQUIREMENTS

3.1 USECASE REPORT:

(1)Administrator: : He/she (Chief Electoral Officer) responsible for managing field

officer, managing party, managing constituency, maintain database, producing final

result, publishing reports.

Manage Field officers: It includes appointing a field officer for a constituency at

the time of general election.CEO will create different roles like, Returning

Officer, DEC (District Election Officer), Counting Officer for performing more

than one tasks.

Manage Party: It includes adding or removing parties after validation. Manage Constituencies: Add a new constituency or delete/join constituencies. Manage Database: Admin maintains the entire database and he is the only

authorized person to add/remove/edit records provided he/she has to get the order

from the highest designation.

Publish Result: After completion of election Admin will produce the final result

of polling(constituency wise, party wise)

Publish Notice: It includes notices,maps,date of polling area wise,detail about

polling procedures, history during election.

View log: Responsible for checking the logs of different system user for auditing

and maintaining the integrity of the system.


14/35





Managing field office:

Name of use case : Add field Officer

Description : Here the the administrator will enter all the details of a field

officer to create a new officer.

Preconditions:

Administrator is already logged in.

Normal flow of events: The constituency will be selected. Query will be submitted. On success completion it will show a confirmation message and a mail will be

sent to the officer regarding his details

Alternate flow of events: if the user is committing some mistake then he have to fill the

form again.

Post Condition: A filed officer will be appointed.


15/35





FIGURE: Add field Officer

Name of use case : Remove Field Officer

Description : Here the administrator will delete a particular field officer.

Preconditions:

Administrator is already logged in. Field officer is already appointed in that constituency.

Normal flow of events:

The constituency will be selected.

Query will be submitted. On success completion it will show a confirmation message that the field officer

is deleted.

Alternate flow of events: none

Post Condition: Administrator have to appoint a field officer immediately after deletion.


16/35





FIGURE: Remove Field Officer

Name of use case : update field officer

Description : Here the administrator will update a particular field officer.

Preconditions:

Administrator is already logged in. Field officer is already appointed in that constituency.


The field officer will be selected for updating. Query will be submitted. On success completion it will show a confirmation message that the field officer

is updated.

Alternate flow of events: Wrong details will lead administrator to enter the information

again.

Post Condition: A mail will be sent to field officer about updating details.


17/35





FIGURE: update field officer

Manage party.


18/35





Name of use case : Add a Party

Description : Here the the administrator will verify all the details of

newly registered party and then add it..

Preconditions:



The application will be selected. Query will be submitted. On success completion it will show a confirmation message and a mail will be

sent to the party leader regarding his details


form again.

Post Condition: A Party will be added to the list.

FIGURE: Add a Party


19/35





Name of use case : Remove a party

Description : Here the administrator will remove a party.

Preconditions:

Administrator is already logged in. There is a party with valid reason for removal from the list.


The party will be selected. Query will be submitted.

On success completion it will show a confirmation message to the party leaderthat his party has been deleted.


Post Condition: none.

FIGURE: Remove a Party


20/35





Name of use case : update party details

Description : Here the administrator will update the details of a party.

Preconditions:

Administrator is already logged in. A record of the party already exists.


A party will be selected for updating. Query will be submitted. On success completion it will show a confirmation message that the party is

updated.


again.

Post Condition: A mail will be sent to the party members about updating details.

FIGURE: update party details


21/35





Manage constituency:

Name of use case : Add a constituency

Description : Here the the administrator will verify all the details of

newly registered constituency and then add it..

Preconditions:



The application will be selected. Query will be submitted. On success completion it will show a confirmation message and a mail will be

sent to the ECO.


form again.

Post Condition: A contituency will be added to the map.


22/35





FIGURE: Add a constituency

Name of use case : update constituency details

Description : Here the administrator will update the details of aconstituency.

Preconditions:

Administrator is already logged in. Verified detail record of a constituency has been recorded.


A area will be selected for updating. Query will be submitted. On success completion it will show a confirmation message that the party is

updated.


again.



23/35





FIGURE: update constituency details

(2).Field Officer: These officers are mainly responsible for verification of candidates,

verification of voters and for counting offline votes. These works has been done by

Returning Officers, DECs and counting officers respectively.

(i).Returning Officers: They are responsible for verifying candidates by considering all

the documents submitted by the candidate.

Verify Candidate: Based upon the details provided bye the nominees they will

verify it.

(ii).Sub-collector: Responsible for verifying voters, issuing voter id card, generate

report.

Verify Voter: Verifies voter details that have been applied by general public. Generate Report: Produces report on voter application.


24/35





Issue Voter Id Card: After acceptance of the report about voter registration by

administrator, issue the voter id card.

(iii).Counting Officer: Responsible for submitting offline result to the admin so that

he/she can produce the final score.

Submit offline result: Submitting offline result to the admin.

Verify candidates:

Name of use case : see candidate details

Description : here the Field Officer (Returning Officer) can see the

details of all the candidates.

Preconditions:

Returning Officer is already logged in. Details about all the candidates have been recorded.

Normal flow of events: An option will be selected i.e whether see the candidate details area wise or

constituency wise or as a whole etc.

Query will be submitted. On success completion it will show a report to the Returning Officer.



25/35


26/35





FIGURE: issue id and password

Name of use case : Allow for campaigning

Description : Here the Field Officer (Returning Officer) can allow the

candidates for campaigning online.

Preconditions:

Returning Officer is already logged in. Details about all the candidates and their request for campaigning have been

recorded.


An id address will be provided to the candidate. Query will be submitted.

On success completion it will show a report to the candidate.Alternate flow of events: none



27/35





FIGURE: Allow for campaigning

Name of use case : issue id and password

Description : here the Field Officer (sub-collector) can issue id and

password for registered voters.

Preconditions: Returning Officer is already logged in. Details about all the voters have been recorded.


an unique id and password will be selected for each registered voters. Query will be submitted. On success completion it will show a report to the voter.




28/35





FIGURE: issue id and password

Verify voter:


29/35





Name of use case : see voter details

Description : here the Field Officer (Sub-collector) can see the details of

all the voters.Preconditions:

Returning Officer is already logged in. Details about all the voters have been recorded.


An option will be selected i.e whether see the voters details area wise or

constituency wise or as a whole etc.

Query will be submitted.

On success completion it will show a report to the sub-collector.



FIGURE: see voter details


30/35





Generate report:

Name of use case : view % of votingDescription : here the Field Officer (counting officer) will produce the %

of voting party wise or area wise etc depending upon the demand.

Preconditions:

Counting Officer is already logged in. Details about no of voters have been voted recorded.


An option will be selected i.e wheather see the voting result area wise orconstituency wise or as a whole etc.

Query will be submitted. On success completion it will show a report to the counting officer.




31/35





FIGURE: view % of voting

(3).Candidate: They can apply for nomination, see result, campaign, and make complain.

Apply for Nomination: They can apply for nomination with proper documents,

which will include their personal and professional details, along with the party

detail which they want to be a part of.

See Result: They can see result of all the candidates who are participating. Making Complains: They can make complains and that will be accepted by the

administrator.

Campaigning: They will do campaigning for publicity or popularity throughforums and chat-room


32/35





(4). General Public: They can register for voting, can vote, can see electoral role, can see

the polling schedule, can se details about candidate, party.

Apply for voter registration: General public can apply for voter registration by

giving documents of birth certificate, resident certificate, address, and photo.

View Report: General public can see weather their name is there in voter list or

not.

Vote: Can give vote through this web site. See details: It includes seeing details about constituency, candidates, party and

about election schedules.


33/35






34/35





3.2 Supplementary Requirements:

Have hours of operation that are 24 x 7 - Because system can be an automated

process, so it can stay open for 24 hours a day. If the base is now the entire world,

staying open 24 hours a day becomes critical. System is required to be available

24X7 so UPS support must be on server site for at least 8 hours in case of power

failure. System will remain inaccessible to users at 2:00 to 4:00 am for backup

and maintenance purpose.

Reduce the cost of a sales transaction - To the extent that one can automate the

sales process through this system, one can start to reduce the cost of that salestransaction. This is particularly true of mundane sales transactions where the

customer knows what they want.

Make the existing Web site more dynamic in nature - Many early Web

implementations consisted of static HTML pages. This becomes very difficult to

manage if the number of pages gets too large. An effective system should be

largely dynamic taking advantage of technology that automates this process rather

than relying on manual processes. Application should serve dynamic user based

customized web pages to its clients from server.

Tie the existing Web site into existing enterprise systems Any existing Web

site that relies on the manual duplication of data from another system is one that

can be improved. Most of the business data in the world today exists in enterprise

servers that can be connected to the Web servers to make this process far more

effective.

Provide good performance and the ability to scale the server The Web

Application Server should provide good performance and the ability to manage

performance with techniques, such as support for caching, clustering, and load

balancing.


35/35




Providing session management capability - Web application developers should

not spend valuable time worrying about how to maintain sessions within the

application. The Web Application Server should provide these services.