E-Governance System UML Diagram

Posted By freeproject on March 19, 2018

E-Governace System Activity Diagram

Posted By freeproject on March 13, 2018

This is the Activity UML diagram of E-Governace System which shows the flows between the activity of Government Services, Customer, Exchange of Information, Petition, Bill. The main activity involved in this UML Activity Diagram of E-Governace System are as follows:

  • Government Services Activity
  • Customer Activity
  • Exchange of Information Activity
  • Petition Activity
  • Bill Activity

Features of the Activity UML diagram of E-Governace System

  • Admin User can search Government Services, view description of a selected Government Services, add Government Services, update Government Services and delete Government Services.
  • Its shows the activity flow of editing, adding and updating of Customer
  • User will be able to search and generate report of Exchange of Information, Petition, Bill
  • All objects such as ( Government Services, Customer, Bill) are interlinked
  • Its shows the full description and flow of Government Services, Petition, Bill, Exchange of Information, Customer
E-Governace System Activity Diagram

E-Governace System Class Diagram

Posted By freeproject on August 2, 2017

E-Governace System Class Diagram describes the structure of a E-Governace System classes, their attributes, operations (or methods), and the relationships among objects. The main classes of the E-Governace System are Bill, Petition, Payment, Customer, Exchange of Information, Government Services.

Classes of E-Governace System Class Diagram:

  • Bill Class : Manage all the operations of Bill
  • Petition Class : Manage all the operations of Petition
  • Payment Class : Manage all the operations of Payment
  • Customer Class : Manage all the operations of Customer
  • Exchange of Information Class : Manage all the operations of Exchange of Information
  • Government Services Class : Manage all the operations of Government Services

Classes and their attributes of E-Governace System Class Diagram:

  • Bill Attributes : bill_id, bill_customer_id, bill_number, bill_type, bill_receipt, bill_description
  • Petition Attributes : pettion_id, pettion_customer_id, pettion_name, pettion_type, pettion_description
  • Payment Attributes : payment_id, payment_customer_id, payment_date, payment_amount, payment_description
  • Customer Attributes : customer_id, customer_name, customer_mobile, customer_email, customer_username, customer_password, customer_address
  • Exchange of Information Attributes : information_id, information_name, information_type, information_description
  • Government Services Attributes : government_service__id, government_service__customer_id, government_service__charge, government_service__type, government_service__description

Classes and their methods of E-Governace System Class Diagram:

  • Bill Methods : addBill(), editBill(), deleteBill(), updateBill(), saveBill(), searchBill()
  • Petition Methods : addPetition(), editPetition(), deletePetition(), updatePetition(), savePetition(), searchPetition()
  • Payment Methods : addPayment(), editPayment(), deletePayment(), updatePayment(), savePayment(), searchPayment()
  • Customer Methods : addCustomer(), editCustomer(), deleteCustomer(), updateCustomer(), saveCustomer(), searchCustomer()
  • Exchange of Information Methods : addExchange of Information(), editExchange of Information(), deleteExchange of Information(), updateExchange of Information(), saveExchange of Information(), searchExchange of Information()
  • Government Services Methods : addGovernment Services(), editGovernment Services(), deleteGovernment Services(), updateGovernment Services(), saveGovernment Services(), searchGovernment Services()

Class Diagram of E-Governace System :

Class Diagram Image: 
E-Governace System Class Diagram

E-Governace System Component Diagram

Posted By freeproject on February 8, 2018

This is a Component diagram of E-Governace System which shows components, provided and required interfaces, ports, and relationships between the Exchange of Information, Government Services, Payment, Bill and Customer. This type of diagrams is used in Component-Based Development (CBD) to describe systems with Service-Oriented Architecture (SOA). E-Governace System UML component diagram, describes the organization and wiring of the physical components in a system.

Components of UML Component Diagram of E-Governace System:

  • Exchange of Information Component
  • Government Services Component
  • Payment Component
  • Bill Component
  • Customer Component

Featues of E-Governace System Component Diagram:

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

E-Governance System Dataflow Diagram

Posted By freeproject on April 17, 2017

E-Governance System Data flow diagram is often used as a preliminary step to create an overview of the E-Governance without going into great detail, which can later be elaborated.it normally consists of overall application dataflow and processes of the E-Governance process. It contains all of the userflow and their entities such all the flow of Bills, Petition, Payment, Customer, Exchange Information, Government Services, Tax. All of the below diagrams has been used for the visualization of data processing and structured design of the E-Governance process and working flow.


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

This is the Zero Level DFD of E-Governance System, where we have eloborated the high level process of E-Governance. It’s a basic overview of the whole E-Governance System or process being analyzed or modeled. It’s designed to be an at-a-glance view of Exchange Information,Government Services and Tax showing the system as a single high-level process, with its relationship to external entities of Bills,Petition and Payment. It should be easily understood by a wide audience, including Bills,Payment and Exchange Information In zero leve DFD of E-Governance System, we have described the high level flow of the E-Governance system.

High Level Entities and proccess flow of E-Governance System:

  • Managing all the Bills
  • Managing all the Petition
  • Managing all the Payment
  • Managing all the Customer
  • Managing all the Exchange Information
  • Managing all the Government Services
  • Managing all the Tax
Zero Level DFD E-Governance System

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

First Level DFD (1st Level) of E-Governance 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-Governance System system as a whole. It also identifies internal data stores of Tax, Government Services, Exchange Information, Customer, Payment that must be present in order for the E-Governance system to do its job, and shows the flow of data between the various parts of Bills, Payment, Government Services, Tax, Exchange Information 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-Governance.

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

  • Processing Bills records and generate report of all Bills
  • Processing Petition records and generate report of all Petition
  • Processing Payment records and generate report of all Payment
  • Processing Customer records and generate report of all Customer
  • Processing Exchange Information records and generate report of all Exchange Information
  • Processing Government Services records and generate report of all Government Services
  • Processing Tax records and generate report of all Tax
First Level DFD E-Governance System

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

DFD Level 2 then goes one step deeper into parts of Level 1 of E-Governance. It may require more functionalities of E-Governance to reach the necessary level of detail about the E-Governance functioning. First Level DFD (1st Level) of E-Governance System shows how the system is divided into sub-systems (processes). The 2nd Level DFD contains more details of Tax, Government Services, Exchange Information, Customer, Payment, Petition, Bills.

Low level functionalities of E-Governance System

  • Admin logins to the system and manage all the functionalities of E-Governance System
  • Admin can add, edit, delete and view the records of Bills, Payment, Exchange Information, Tax
  • Admin can manage all the details of Petition, Customer, Government Services
  • Admin can also generate reports of Bills, Petition, Payment, Customer, Exchange Information, Government Services
  • Admin can search the details of Petition, Exchange Information, Government Services
  • Admin can apply different level of filters on report of Bills, Customer, Exchange Information
  • Admin can tracks the detailed information of Petition, Payment, Customer, , Exchange Information
Second Level DFD E-Governance System

E-Governace System ER Diagram

Posted By freeproject on July 17, 2017

This ER (Entity Relationship) Diagram represents the model of E-Governace System Entity. The entity-relationship diagram of E-Governace System shows all the visual instrument of database tables and the relations between Petition, Customer, Bill, Government Services etc. It used structure data and to define the relationships between structured data groups of E-Governace System functionalities. The main entities of the E-Governace System are Bill, Petition, Payment, Customer, Exchange of Information and Government Services.

E-Governace System entities and their attributes :

  • Bill Entity : Attributes of Bill are bill_id, bill_customer_id, bill_number, bill_type, bill_receipt, bill_description
  • Petition Entity : Attributes of Petition are pettion_id, pettion_customer_id, pettion_name, pettion_type, pettion_description
  • Payment Entity : Attributes of Payment are payment_id, payment_customer_id, payment_date, payment_amount, payment_description
  • Customer Entity : Attributes of Customer are customer_id, customer_name, customer_mobile, customer_email, customer_username, customer_password, customer_address
  • Exchange of Information Entity : Attributes of Exchange of Information are information_id, information_name, information_type, information_description
  • Government Services Entity : Attributes of Government Services are government_service__id, government_service__customer_id, government_service__charge, government_service__type, government_service__description

Description of E-Governace System Database :

  • The details of Bill is store into the Bill tables respective with all tables
  • Each entity (Government Services, Payment, Exchange of Information, Petition, Bill) contains primary key and unique keys.
  • The entity Payment, Exchange of Information has binded with Bill, Petition entities with foreign key
  • There is one-to-one and one-to-many relationships available between Exchange of Information, Customer, Government Services, Bill
  • All the entities Bill, Exchange of Information, Payment, Government Services are normalized and reduce duplicacy of records
  • We have implemented indexing on each tables of E-Governace System tables for fast query execution.
E-Governace System ER Diagram

E-Governace System Sequence Diagram

Posted By freeproject on January 31, 2018

This is the UML sequence diagram of E-Governace System which shows the interaction between the objects of Payment, Exchange of Information, Government Services, Petition, Bill. The instance of class objects involved in this UML Sequence Diagram of E-Governace System are as follows:

  • Payment Object
  • Exchange of Information Object
  • Government Services Object
  • Petition Object
  • Bill Object

This is the UML sequence diagram of E-Governace System which shows the interaction between the objects of Payment, Exchange of Information, Government Services, Petition, Bill. The instance of class objects involved in this UML Sequence Diagram of E-Governace System are as follows:

  • Payment Object
  • Exchange of Information Object
  • Government Services Object
  • Petition Object
  • Bill Object

E-Governace 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-Governace System. It represents the methodology used in system analysis to identify, clarify, and organize system requirements of E-Governace System. The main actors of E-Governace System in this Use Case Diagram are: Super Admin, System User, User, Anonymous Users, who perform the different type of use cases such as Manage Bill, Manage Petition, Manage Payment, Manage Customer, Manage Exchange of Information, Manage Government Services, Manage Users and Full E-Governace System Operations. Major elements of the UML use case diagram of E-Governace System are shown on the picture below.

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

  • Super Admin Entity : Use cases of Super Admin are Manage Bill, Manage Petition, Manage Payment, Manage Customer, Manage Exchange of Information, Manage Government Services, Manage Users and Full E-Governace System Operations
  • System User Entity : Use cases of System User are Manage Bill, Manage Petition, Manage Payment, Manage Customer, Manage Exchange of Information, Manage Government Services
  • User Entity : Use cases of User are Create Petitions, Add Comments, Search Petitions, Invite Peoples, Search Government Services
  • Anonymous Users Entity : Use cases of Anonymous Users are View Information, Fill Contact Us, Search Content

Use Case Diagram of E-Governace System :

E-Governace System Use Case Diagram

Project Category