This is my Last Year Project Made as the Android Application

1. Online Voting System
Developed by
Saurabh Kheni
Enrollment No 003003142545

2. Index
 Project Profile
 System Information
 Existing System
 Proposed System
 Overview of the System
 Modules of the System
 Front End of the System
 Overview `
 Importance
 Limitations
 Back End of the System
 Definition
 Importance

3.  Hardware and Software Requirement
 Hardware Requirement
 Software Requirement
 Diagram
 Data Flow Diagram
 Class Diagram
 Use Case Diagram
 E-R Diagram
 Machine State
 Database Diagram
 Testing
 Description of Testing
 Screenshots
 Bibliography

4. Project Profile
Project Title Z-Vote (Online Voting System)
Project Duration From November 24, 2016
To March 25,2017
Team Strength One Member
Project Programmers Saurabh Kheni
(T.Y B.C.A, Parul Institute of Computer Application)
Organization Name
Project Guide Ms.Mitali Mistry
Submitted To Saurashtra University Rajkot

5. System Information

6. Existing System
 In existing system, if you wish to vote for someone, then
you have to go to the destination where the voting
procedure is going on and then only you can vote for him
or her.
 Existing system does not provide people the way in which
they can get the details about the nominees as well. They
can’t get to know the history of the people for whom they
are standing in queue for giving their votes.
 The problems of the existing manual system of voting
include among others the following:
 Expensive and Time Consuming
 Too Much Paper Work
 Errors during data Entry
 Loss of registration forms

7. Proposed System
 Proposed system is highly automated and greatly technical.
In this system, not even you can vote via sitting at your own
place but also you can learn about laws and regulations
related to voting.
 Also not only this but you can access the profile of the
nominees through which you can learn about their history,
their education, and their personal details and so on.
 Using this online voting android based project, end users do
not faces any difficulties as because they don’t have to
make registration before submitting their answers.

8. Overview of the System
 The Android voting system is an application which is a new
process of casting votes from any place and at any time.
 The proposed system is a flexible means of casting the votes
irrespective of the place and time of the day.
 This technique is best suited for the modern day organizations
where the management can get the opinion of the employees
regarding introduction of new policies or rules by taking votes
through this system.
 So there are less chances of multiple voting by single voter and
hence less chances of manipulation in this system of voting.

9.  The android voting system is an android application that
provides a new technique of casting votes using mobile
phones.
 This application is especially developed for organizations,
corporations and commercial businesses to get employees
opinions whenever there is any new policy implemented or
any issue being investigated or during controversies. The
project provides an effective solution in resolving all the
arguments that occurs in organizations by considering all
employees opinions.

10. Modules of the System
 Voter Module:
 In this module, user who is going to give his or her vote have
to make his or her account in order to get access to the voting
system and into the modules which contains details about the
nominees.
 Admin Module:
 Admin checks the data and the valid voter.Admin also gives the
result once the Voting is conducted.Only Admin is authorised
to check the Result.
 Voting Module:
 In this module, all the process related to voting and votes are
given into this module. Voters can access to this module via
their personal account only.

11. Front End of the System
(Android)

12. Overview of Android
 Android is an open source and Linux-based operating
system for mobile devices such as smartphones and tablet
computers.
 Android's user interface is mainly based on direct
manipulation, using touch gestures that loosely correspond
to real-world actions, such as swiping, tapping and
pinching, to manipulate on-screen objects, along with a
virtual keyboard for text input. In addition to touchscreen
devices.
 It was initially developed by Android Inc. which was later
bought by Google in 2005.

13. Importance of Android
 Faster Web Browser
 It Supports MP4, 3GP, MPEG4, MIDI
 Additional Hardware Support
 Video Calling
 Open Source Framework
 Uses of Tools are Very Simple
 Availability of Apps
 Great Social Networking Integration
 Better Notification System.
 Updated User Interface Design
 At a Time Applications
 Low Chance of Crashing

14.  Stability
 It Lets you Change Your Settings Faster
 It Gives you More Options to Fit your Budget
 Support for Extra Large Screen Sizes and Resolutions
 System Wide Copy and Paste Functionalities.
 Redesigned Multi Touch Software Keyboard
 Audio, Graphical and Input Enhancements for Game Developers.
 Improved Power Management and Application Control

15. Limitations of Android
 Little Memory for Storage
 Force Close on Large App/Games
 Data Connection
 Battery Problem
 Box of Malware Google play store

16. Back End of the System
(SQLite)

17. Overview of SQLite
 SQLite is a software library that implements a self-
contained, server less, zero-configuration, transactional SQL
database engine.
 SQLite is the most widely deployed SQL database engine in
the world. The source code for SQLite is in the public
domain.
 It is the one database, which is zero-configured, that means
like other database you do not need to configure it in your
system.
 SQLite engine is not a standalone process like other
databases, you can link it statically or dynamically as per
your requirement with your application. The SQLite accesses
its storage files directly.

18. Importance of SQLite
 Transactions are atomic, consistent, isolated, and durable
even after system crashes and power failures.
 Zero-configuration - no setup or administration needed
 Full-featured SQL implementation with advanced
capabilities like partial indexes, indexes on expressions,
JSON, and common table expressions.
 A complete database is stored in a single cross-platform
disk file. Great for use as an application file format.
 Supports terabyte-sized databases and gigabyte-sized
strings and blobs.
 Small code footprint: less than 500KiB fully configured or
much less with optional features omitted.
 Simple, easy to use API.

19.  Written in ANSI-C. TCL bindings included. Bindings for
dozens of other languages available separately.
 Well-commented source code with 100% branch test
coverage.
 Available as a single ANSI-C source-code file that is easy to
compile and hence is easy to add into a larger project.
 Self-contained: no external dependencies.
 Cross-platform: Android, iOS, Linux, Mac, Solaris, VxWorks,
and Windows (Win32, WinCE, and WinRT) are supported
out of the box. Easy to port to other systems.
 Sources are in the public domain. Use for any purpose.
 Comes with a standalone command-line interface (CLI)
client that can be used to administer SQLite databases

20. Hardware and
Software Requirement

21. Hardware Requirement
 Chipset : ARM Based
 Memory:128MB RAM 256MB Flash External
 Storage : Mini or Micro SD Card
 Primary Display: QVGA TFT LCD or larger, 16 Bit colour or
Better.
 Navigational Keys: 5-Way Navigational with 5 application
keys , Power, Camera and Volume Controls
 Mouse
 Keyboard

22. Software Requirement
 Operating System: Android
 Apache ANT (Another Neat Tool):
 It is an open-source tool that automates aspects of the
Android build process.
 Gradle:
 An advanced build toolkit that manages dependencies and
allows to define custom build logic
 The Android SDK (Software Development Kit):
 Android SDK Manager separates the APIs, tools and different
platforms into different packages which you can download.

23. Diagrams

24. DFD Diagram
 A data flow diagram (DFD) is a graphical representation of
the "flow" of data through an information system,
modelling its process aspects.
 A DFD is often used as a preliminary step to create an
overview of the system, which can later be elaborated.

25. 0 Level DFD

26. 1 Level DFD

27. Class Diagram
 In software engineering, a class diagram in the Unified
Modelling Language (UML) is a type of static structure
diagram that describes the structure of a system by showing
the system's classes, their attributes, operations (or
methods), and the relationships among objects.
 The class diagram is the main building block of object-
oriented modelling. It is used both for general conceptual
modelling of the systematic of the application, and for
detailed modelling translating the models
into programming code.

29. Use Case Diagram
 Use case diagrams are usually referred to as behaviour
diagrams used to describe a set of actions (use cases) that
some system or systems (subject) should or can perform in
collaboration with one or more external users of the system
(actors).
 Each use case should provide some observable and valuable
result to the actors or other stakeholders of the system.

31. E-R Diagram
 An entity relationship diagram (ERD) shows the
relationships of entity sets stored in a database. An entity in
this context is a component of data.
 In other words, ER diagrams illustrate the logical structure
of databases.
 At first glance an entity relationship diagram looks very
much like a flowchart. It is the specialized symbols, and the
meanings of those symbols, that make it unique.

33. Machine State
 A Statechart diagram describes a state machine. Now to
clarify it state machine can be defined as a machine which
defines different states of an object and these states are
controlled by external or internal events
 Following are the main purposes of using Statechart
diagrams:
 To model dynamic aspect of a system.
 To model life time of a reactive system.
 To describe different states of an object during its life time.
 Define a state machine to model states of an object.

35. Database Diagram
 The Database Designer is a visual tool that allows you to
design and visualize a database to which you are connected.
 When designing a database, you can use Database Designer
to create, edit, or delete tables, columns, keys, indexes,
relationships, and constraints.
 To visualize a database, you can create one or more
diagrams illustrating some or all of the tables, columns,
keys, and relationships in it.

36. Voter Module
Sr no Name Type Constraint Description
1 ID Int Primary Key ID of the Voter
2 Full Name Varchar Not null Full name of
the Voter
3 Username Varchar Not null Username of
the Voter
4 Date of Birth Date Not null Date of Birth of
Voter
5 Email Varchar Not null Email of the
Voter
6 Password Varchar Not null Password given
by the voter

37. Voting Module
Sr no Name Type Constraint Description
1 ID Int Primary Key ID of the
Question
2 Question Varchar Not null Question for
voting
3 Options(A,B,C,D) Varchar Not null Last name of
the Voter

38. Software Testing
 Testing is the process of evaluating a system or its
component(s) with the intent to find whether it satisfies the
specified requirements or not.
 In simple words, testing is executing a system in order to
identify any gaps, errors, or missing requirements in
contrary to the actual requirements.

39. Screenshots

40. Main Page

41. Voter Registration

42. Admin Login

43. Voter Login