E-Voting Management System UML Diagram

Posted By freeproject on March 19, 2018

E-Voting Management System Activity Diagram

Posted By freeproject on March 13, 2018

This is the Activity UML diagram of E-Voting Management System which shows the flows between the activity of Register, , Citizen, Result, Candidate. The main activity involved in this UML Activity Diagram of E-Voting Management System are as follows:

  • Register Activity
  • Activity
  • Citizen Activity
  • Result Activity
  • Candidate Activity

Features of the Activity UML diagram of E-Voting Management System

  • Admin User can search Register, view description of a selected Register, add Register, update Register and delete Register.
  • Its shows the activity flow of editing, adding and updating of
  • User will be able to search and generate report of Citizen, Result, Candidate
  • All objects such as ( Register, , Candidate) are interlinked
  • Its shows the full description and flow of Register, Result, Candidate, Citizen,
E-Voting Management System Activity Diagram

E-Voting Management System Class Diagram

Posted By freeproject on August 2, 2017

E-Voting Management System Class Diagram describes the structure of a E-Voting Management System classes, their attributes, operations (or methods), and the relationships among objects. The main classes of the E-Voting Management System are Voting, Register, Candidate, Citizen, Polling, Result.

Classes of E-Voting Management System Class Diagram:

  • Voting Class : Manage all the operations of Voting
  • Register Class : Manage all the operations of Register
  • Candidate Class : Manage all the operations of Candidate
  • Citizen Class : Manage all the operations of Citizen
  • Polling Class : Manage all the operations of Polling
  • Result Class : Manage all the operations of Result

Classes and their attributes of E-Voting Management System Class Diagram:

  • Voting Attributes : voting_candidate_id, voting_citizen_id, voting_date, voting_type, voting_timing, voting_description
  • Register Attributes : register_id, register_candidate_id, register_citizen_id, register_name, register_type, register_description
  • Candidate Attributes : candidate_id, candidate_voter_id, candidate_name, candidate_mobile, candidate_email, candidate_username, candidate_password, candidate_address
  • Citizen Attributes : citizen_id, citizen_voter_id, citizen_name, citizen_mobile, citizen_email, citizen_username, citizen_password, citizen_address
  • Polling Attributes : pooling_id, pooling_name, pooling_type, pooling_description
  • Result Attributes : result_id, result_candidate_id, result_date, result_type, result_description

Classes and their methods of E-Voting Management System Class Diagram:

  • Voting Methods : addVoting(), editVoting(), deleteVoting(), updateVoting(), saveVoting(), searchVoting()
  • Register Methods : addRegister(), editRegister(), deleteRegister(), updateRegister(), saveRegister(), searchRegister()
  • Candidate Methods : addCandidate(), editCandidate(), deleteCandidate(), updateCandidate(), saveCandidate(), searchCandidate()
  • Citizen Methods : addCitizen(), editCitizen(), deleteCitizen(), updateCitizen(), saveCitizen(), searchCitizen()
  • Polling Methods : addPolling(), editPolling(), deletePolling(), updatePolling(), savePolling(), searchPolling()
  • Result Methods : addResult(), editResult(), deleteResult(), updateResult(), saveResult(), searchResult()

Class Diagram of E-Voting Management System :

Class Diagram Image: 
E-Voting Management System Class Diagram

E-Voting Management System Component Diagram

Posted By freeproject on February 8, 2018

This is a Component diagram of E-Voting Management System which shows components, provided and required interfaces, ports, and relationships between the Result, Citizen, Voting, Candidate and . This type of diagrams is used in Component-Based Development (CBD) to describe systems with Service-Oriented Architecture (SOA). E-Voting Management System UML component diagram, describes the organization and wiring of the physical components in a system.

Components of UML Component Diagram of E-Voting Management System:

  • Result Component
  • Citizen Component
  • Voting Component
  • Candidate Component
  • Component

Featues of E-Voting Management System Component Diagram:

  • You can show the models the components of E-Voting Management System.
  • Model the database schema of E-Voting Management System
  • Model the executables of an application of E-Voting Management System
  • Model the system's source code of E-Voting Management System
Component Diagram: 

E-Voting Management System Dataflow Diagram

Posted By namita on July 2, 2017

E-Voting Management System Data flow diagram is often used as a preliminary step to create an overview of the E-Voting without going into great detail, which can later be elaborated.it normally consists of overall application dataflow and processes of the E-Voting process. It contains all of the userflow and their entities such all the flow of Voting, Register Candidate, Candidate, Citizen, Polling Result, Confirmation, Login. All of the below diagrams has been used for the visualization of data processing and structured design of the E-Voting process and working flow.


Zero Level Data flow Diagram(0 Level DFD) of E-Voting Management System :

This is the Zero Level DFD of E-Voting Management System, where we have eloborated the high level process of E-Voting. It’s a basic overview of the whole E-Voting Management System or process being analyzed or modeled. It’s designed to be an at-a-glance view of Polling Result,Confirmation and Login showing the system as a single high-level process, with its relationship to external entities of Voting,Register Candidate and Candidate. It should be easily understood by a wide audience, including Voting,Candidate and Polling Result In zero leve DFD of E-Voting Management System, we have described the high level flow of the E-Voting system.

High Level Entities and proccess flow of E-Voting Management System:

  • Managing all the Voting
  • Managing all the Register Candidate
  • Managing all the Candidate
  • Managing all the Citizen
  • Managing all the Polling Result
  • Managing all the Confirmation
  • Managing all the Login
Zero Level Data flow Diagram(0 Level DFD) of E-Voting Management System

First Level Data flow Diagram(1st Level DFD) of E-Voting Management System :

First Level DFD (1st Level) of E-Voting Management System shows how the system is divided into sub-systems (processes), each of which deals with one or more of the data flows to or from an external agent, and which together provide all of the functionality of the E-Voting Management System system as a whole. It also identifies internal data stores of Login, Confirmation, Polling Result, Citizen, Candidate that must be present in order for the E-Voting system to do its job, and shows the flow of data between the various parts of Voting, Candidate, Confirmation, Login, Polling Result of the system. DFD Level 1 provides a more detailed breakout of pieces of the 1st level DFD. You will highlight the main functionalities of E-Voting.

Main entities and output of First Level DFD (1st Level DFD):

  • Processing Voting records and generate report of all Voting
  • Processing Register Candidate records and generate report of all Register Candidate
  • Processing Candidate records and generate report of all Candidate
  • Processing Citizen records and generate report of all Citizen
  • Processing Polling Result records and generate report of all Polling Result
  • Processing Confirmation records and generate report of all Confirmation
  • Processing Login records and generate report of all Login
First Level Data flow Diagram(1st Level DFD) of E-Voting Management System

Second Level Data flow Diagram(2nd Level DFD) of E-Voting Management System :

DFD Level 2 then goes one step deeper into parts of Level 1 of E-Voting. It may require more functionalities of E-Voting to reach the necessary level of detail about the E-Voting functioning. First Level DFD (1st Level) of E-Voting Management System shows how the system is divided into sub-systems (processes). The 2nd Level DFD contains more details of Login, Confirmation, Polling Result, Citizen, Candidate, Register Candidate, Voting.

Low level functionalities of E-Voting Management System

  • Admin logins to the system and manage all the functionalities of E-Voting Management System
  • Admin can add, edit, delete and view the records of Voting, Candidate, Polling Result, Login
  • Admin can manage all the details of Register Candidate, Citizen, Confirmation
  • Admin can also generate reports of Voting, Register Candidate, Candidate, Citizen, Polling Result, Confirmation
  • Admin can search the details of Register Candidate, Polling Result, Confirmation
  • Admin can apply different level of filters on report of Voting, Citizen, Polling Result
  • Admin can tracks the detailed information of Register Candidate, Candidate, Citizen, , Polling Result
Second Level Data flow Diagram(2nd Level DFD) of E-Voting Management System

E-Voting Management System ER Diagram

Posted By freeproject on July 17, 2017

This ER (Entity Relationship) Diagram represents the model of E-Voting Management System Entity. The entity-relationship diagram of E-Voting Management System shows all the visual instrument of database tables and the relations between Register, Citizen, Voting, Result etc. It used structure data and to define the relationships between structured data groups of E-Voting Management System functionalities. The main entities of the E-Voting Management System are Voting, Register, Candidate, Citizen, Polling and Result.

E-Voting Management System entities and their attributes :

  • Voting Entity : Attributes of Voting are voting_candidate_id, voting_citizen_id, voting_date, voting_type, voting_timing, voting_description
  • Register Entity : Attributes of Register are register_id, register_candidate_id, register_citizen_id, register_name, register_type, register_description
  • Candidate Entity : Attributes of Candidate are candidate_id, candidate_voter_id, candidate_name, candidate_mobile, candidate_email, candidate_username, candidate_password, candidate_address
  • Citizen Entity : Attributes of Citizen are citizen_id, citizen_voter_id, citizen_name, citizen_mobile, citizen_email, citizen_username, citizen_password, citizen_address
  • Polling Entity : Attributes of Polling are pooling_id, pooling_name, pooling_type, pooling_description
  • Result Entity : Attributes of Result are result_id, result_candidate_id, result_date, result_type, result_description

Description of E-Voting Management System Database :

  • The details of Voting is store into the Voting tables respective with all tables
  • Each entity (Result, Candidate, Polling, Register, Voting) contains primary key and unique keys.
  • The entity Candidate, Polling has binded with Voting, Register entities with foreign key
  • There is one-to-one and one-to-many relationships available between Polling, Citizen, Result, Voting
  • All the entities Voting, Polling, Candidate, Result are normalized and reduce duplicacy of records
  • We have implemented indexing on each tables of E-Voting Management System tables for fast query execution.
E-Voting Management System ER Diagram

E-Voting Management System Sequence Diagram

Posted By freeproject on January 31, 2018

This is the UML sequence diagram of E-Voting Management System which shows the interaction between the objects of , Register, Voting, Result, Candidate. The instance of class objects involved in this UML Sequence Diagram of E-Voting Management System are as follows:

  • Object
  • Register Object
  • Voting Object
  • Result Object
  • Candidate Object

This is the UML sequence diagram of E-Voting Management System which shows the interaction between the objects of , Register, Voting, Result, Candidate. The instance of class objects involved in this UML Sequence Diagram of E-Voting Management System are as follows:

  • Object
  • Register Object
  • Voting Object
  • Result Object
  • Candidate Object

E-Voting Management System Use Case Diagram

Posted By freeproject on July 24, 2017

This Use Case Diagram is a graphic depiction of the interactions among the elements of E-Voting Management System. It represents the methodology used in system analysis to identify, clarify, and organize system requirements of E-Voting Management System. The main actors of E-Voting Management System in this Use Case Diagram are: Super Admin, System User, Voter, Candidate, who perform the different type of use cases such as Manage Voting, Manage Register, Manage Candidate, Manage Citizen, Manage Polling, Manage Result, Manage, Manage Users and Full E-Voting Management System Operations. Major elements of the UML use case diagram of E-Voting Management System are shown on the picture below.

The relationships between and among the actors and the use cases of E-Voting Management System:

  • Super Admin Entity : Use cases of Super Admin are Manage Voting, Manage Register, Manage Candidate, Manage Citizen, Manage Polling, Manage Result, Manage, Manage Users and Full E-Voting Management System Operations
  • System User Entity : Use cases of System User are Manage Voting, Manage Register, Manage Candidate, Manage Citizen, Manage Polling, Manage Result, Manage
  • Voter Entity : Use cases of Voter are Vote to Candidate, Check Vote, Search Candidate
  • Candidate Entity : Use cases of Candidate are Check Votes, Update Profile, Voting Reports

Use Case Diagram of E-Voting Management System :

E-Voting Management System Use Case Diagram