Report On

ONLINE LIVE VOTING SYSTEM

Prepared by : Guided by:

Manu Vardhan Prof. Huma Kauser

Kritika Gupta
Stuti Jain
Raghav Tyagi
1.Introduction

1.1 Purpose:

The purpose of on-line live voting system is to take online poll in an efficient manner and no
time wasting by doing it offline. It provides a competitive platform, where a participant not only
judges their skill but also they can improve their skill at the same
time. For participant it is easy to participate in the competition and not go anywhere.Participant
need not go anywhere outside and waste i\his time and energy.

1.2 Scope:

Scope of this project is very broad in ,which help the participant to become self paced learners to
make them aware of their skills and capabilities . Help participants to go beyond their normal
curriculum and learn about various other competitions which are apart from their comfort zone.
To provide a competition system where, there is virtually no scope of errors and the results are
much faster. And the system is more transparent. To provide an environment where participants
not only can learn but also analyze their performance simultaneously. To train the participants to
work within time limit with constraints .

1.3 Benefits :

This application reduces the manual work, maintaining accuracy, increasing efficiency and
saving time. Also institutes need not go to develop a new software each time, instead they just
make changes in database and conduct a test. For participants, it saves time of going to far away
centers and also they can view their result then and there.

1.4 References:

Codeproject.com

Csharpcorner.com

1.5 Overview :

The rest of this document describes the various system requirements, interfaces, features and
functionalities in detail.

2. Overall Description

In Online live competition voting system institute can register to conduct a online competition and view
the results later. Participants can give their work and their respective records, which include their
photos,videos,audios for each competition participated by them, others will be maintained separately. No
student can take a particular competition more than once.
2.1 Perspective :

A. User interfaces

The application will have a user friendly and menu based interface. Following screens will be
provided:

(i) A login screen for entering the username, password will be provided. Access to different
screens will be based upon the user.
(ii) There is a screen for displaying information regarding various competitions.
(iii) There is a screen for displaying information regarding filling of competitions according to
their guidelines.
(iv) There is a screen for displaying information regarding entering student list for the particular
competitions.
(v) There is a screen for displaying information menu regarding what options the participants
will select while filling entries(entering material, participant info, entering details).
(vi) There is a screen for displaying competition details to the participants when they are taking
exams.
(vii) There is a screen for taking part for the competitions.
(viii) There is a screen for displaying of results of participants after taking the competition.

B. Hardware interfaces

(i) Support for speakers to listen to audio

(ii) Support video card to view video.
(iii) Screen resolution of at least 800X600 is required for proper and complete viewing of
screens. Higher resolution will be accepted.

C. Software interfaces

(i) Any windows based operating system.

(ii) MS Access 2000 as the DBMS-for database.
(iii) visual studio for developing code

D. Communications interfaces: None

E. Memory Constraints: At least 512 MB RAM and 5 MB space on hard disk will be
required for running the application.

F. Site Adaptation Requirements : Internet with cookies enabled.

2.2 Product Functions:

The website will allow access only to authorised users with specific roles (Administrator-
maintains the website,admin conducts competitions, Participants-Give take competitions online)
A summary of the major functions that the website will perform:
a. Provide facility participants to register to conduct a competition online .
b. Admin can enter the number of competitions , like dislike by the viewers.
c. Participants can login and give their work for competitons.
2.3 User Characteristics :

a. Educational level: Users should be comfortable with the English language.

b. Experience : Users should have prior information regarding the online competitions.
c. Skills : Users should have basic knowledge and should be comfortable using general purpose
applications on computers.

2.4 Constraints : Registered users can only access the upload functionality of the site.

2.5 Assumptions : The competitions are all with votings. Participants can give each material in a
competition just once.

2.6 Apportioning of Requirements : The future versions of the website will be having a better
database to handle larger number of records, in a more secure way. Also separate profile will be
maintained later for all participants so that he can view all his previous performances.

3. Specific Requirements : This section provides software requirements to a level of detail

sufficient to enable designers to design the system and testers to test the system.

3.1 Functional Requirements:

It deals with the functionalities required from the system which are as follows:

a. The website will help the colleges/organizations/companies to conduct their online

competitions.
b. Only authorized person can access related details.
c. The Participants will register themselves on the website for participating in their competitions.
d. Participant can change their information regarding themselves.
e. The participants can login through ID and PASSWORD and give their exams.
f. Administrator will be responsible for updating the site.
g. The admin can change guidelines whenever they want.

3.2 External Interface Requirements:

3.2.1 User Interfaces:

3.2.1.1 Registration Screen: Various fields available on this screen will be:

a. Name
b. Email Id
c. Password
d. gender
e.city
Name: Eg. Satish gupta

Email Id: Eg. sg@gmail.com

Password:

Gender: M F

City ; (CITY NAME HERE)

3.2.1.2 Login Screen: Fields available on this screen are:

a. Login Name
b. Password

Name Eg. Satish Gupta

Password Eg. he@145y

3.2.1.3 Registrtion page: Various Fields are:

a. name
b. ID
c.password
d. city
e. gender

Name:

Id:

password:

city:

gender:

Passing Marks:

3.2.1.6 Admin Login Screen: Various Fields are:

a. Admin ID
b. Password

Admin Id:
Password:

3.2.1.8 Result Displaying Screen: Various Fields are:

a. Result of winner

3.2.2 Hardware interfaces:

a. Support for printer for printing results then and there.

b. Screen resolution of at least 800X600 is required for proper and complete viewing of screens.
Higher resolution will be accepted.

3.2.3 Software interfaces:

a. Any windows based operating system.

b. my sql for database.
c. visual studio for developing code.

3.2.4 Communications interfaces: None

3.3 Software Product Features:

3.3.1 Validity Checks:

C# provides validity checks for various fields in the forms.

3.3.2 Sequencing Information: All the information regarding competition details, participant
list, guideline details, display of result should be handled sequentially that is data should be
stored only in a particular sequence to avoid any inconvenience.

3.3.3 Error Handling: If any of the validations or sequencing flows does not hold true then
appropriate error messages will be prompted to the user for doing the needful.

3.4 Performance Requirements:

This subsection specifies numerical requirements placed on the software or on the human
interaction with the software, as a whole. Numerical requirements will include:
a. the size of file must not exceed the accepted size
b. Only formats specified in the guidelines will be accepted.
c. All the transactions will be processed within seconds.

3.5 Design Constraints: None

3.6 Software System Attributes:

3.6.1 Security: Only authorized users will be able to access the website by entering the correct
login name and corresponding password.

3.6.2 Maintainability: The website can be maintained in present or future. It will be easy to
incorporate new requirements in the individual modules.

3.6.3 Portability: As the website is online so will be easily portable on various systems.
The website will be also easily portable on any windows based system that has VS
installed.

3.7 Logical Database Requirements: The following information will be placed

in the database:

a. Participant Details: Name, Email, Password.

b. participant List: S id, S name,
c. competition detals; competition to be held
d. admin details; login id , password

3.8 Other Requirements: None

Use Case Diagram

A use case diagram at its simplest is a representation of a user's interaction with the system that
shows the relationship between the user and the different use cases in which the user is involved.
A use case diagram can identify the different types of users of a system and the different use
cases and will often be accompanied by other types of diagrams as well.
Data Flow Diagram

A data flow diagram (DFD) maps out the flow of information for any process or system. It uses
defined symbols like rectangles, circles and arrows, plus short text labels, to show data inputs,
outputs, storage points and the routes between each destination. Data flowcharts can range from
simple, even hand-drawn process overviews, to in-depth, multi-level DFDs that dig progressively
deeper into how the data is handled. They can be used to analyze an existing system or model a
new one.