7.

E- SEVA
Abstract

The case discusses E-Seva (Electronic Service), an e-government project

initiated by the state government of Andhra Pradesh (GoAP) in India. The E-
Seva project aimed at integrating and offering a wide range of government to
citizen (G2C) services at a single location. The case highlights the objectives of
the E-Seva project. It provides detailed information on the implementation of
the project, its IT architecture, and the hardware and software used. The case
describes the G2C services offered by the GoAP and the benefits reaped by the
citizens and the GoAP after the implementation of the project.

In the E-seva there are many types of online bill payments (electric bill,
phone bill etc).and there is an online ticket reservation system. The electronic
bill presentment & payment application (EBPP) is a web based application
which helps billers and their customers settle their transitions online.
Problem Statement
E-seva is the online payments. In the e-seva there are many types of
online bill payments (electric bill, phone bill etc).and there is an online ticket
reservation system. The electronic bill presentment & payment application
(EBPP) is a web based application which helps billers and their customers settle
their transitions online.
Briefly speaking billers and issue bills (e-bill) Online and send them to
their customers electronically. The users can select to view and pay their e-bills
in multiple languages. The system will also keep tractions history between
billers and customers. EBPP system should be reasonably accessible to potential
user. And online ticket reservation system. Railways wishes to develop a
ticketing and reservation system .this must support advance booking of the
tickets, cancellation of tickets and change of class of a ticket. The system will
also have a web interface where their user can register themselves and purchase
ticket online... The system will also have a querying facility that allows user to
check train time –tables, Fares and availability of tickets.

Existing System:
As per previous contract, all the assets created by existing Service
Provider stands transferred to ESD at the end of the contract. These assets on
„as is where is‟ condition will be available for use free of charge to new service
provider during the entire contract period

Disadvantages:
1. Spoofing: In this practice, the attacker attempts to gain the access of the E-
Governance system by using fallacious identity either by stealth or by using
false IP address. Once the access is gained, the assailant abuses the E-
Governance system by elevation of the privileges.
2. Tampering of E-Governance system: As soon as the system is compromised
and privileges are raised, the classified information of the E-Governance
mechanism becomes very much susceptible to illegal adjustments.
3. Repudiation: Even the attacker can mount refutation attack during the E-
Governance transaction, which is the ability of the user to reject its
performed transaction.

Proposed System:
E-seva is probably one of the best e-governance in India. It is a one –shop-stop
for a range of citizen‟s friendly system.
USE CASE DIAGRAM:
A use case diagram is a set of scenarios that describes the interaction between user
and system. The use case is an external view of a system that represents some action the user
might perform in order to complete a task.

telephone
bill housetax

watertax

electricity bill logi maintain

pay
n ing
bills
(fromuseca.
databas
..
(fromuseca...
e
(fromuseca...

movieticket
s
consu (fromuseca...
opera
me r tor dba
(from
ac...) (from (from ac...)
bus ac...)
reservation
birth
s
death (fromuseca...

v
e passp
ort

certifi
competeti
cates exams
(fromuseca...

applications
(fromuseca...

tradelicense vehiclelicense
licences
(fromuseca...

Fig: Use case diagram for E-seva

 Regester Biller <<include>>

UnRegester user Verify Information

<<include>>

Regester Customer

usto e P yment E ine y q

Biller C m r a ng M S l

Fig: Use case diagram for register

<<include>>

Issue Bill Enter e-bill

information

Biller

<<include>>
Update Trancation

MySql

<<include>>
Verify Customer
information

cancel Issue
e-bill screen

Fig: Use case diagram for issue bills

 Cancel Pay bill
Action

Customer Payment Information

Valdiation

Payment engine
<<include>>

Enter Payment
Information
UpDate Trancation
Information

Fig: Use case diagram for pay bills

SEQUENCE DIAGRAM:
The sequence diagram is very simple and has immediate visual appeal---this is it‟s
great strength. A sequence diagram is an alternative way to understand the over all flow of
control of a program. Instead of looking at the code and trying to find out the over all
sequence of behavior.

Fig: Sequence diagram for register

Fig: Sequence diagram for issue bills

Fig: Sequence diagram for pay bills

Fig: Sequence diagram for view account information
Fig: Sequence diagram for update user information
 s ys te m
: c o ns ume r : ope ra tor
1: re q ue sts for a ti cket

2: spe c i fi es the detai ls

3: enters the b us no.,d a te ,ti me

4: not a va i la ble

5: the ti cke t is not avai lab le

6: vali d

7: re q ue sts the a mo unt

8: ta kes the a m o unt

9: enq ui re s the na me

10 : ente rs the na me

11 : i ss ue s the ti cket

12 : re c e i vce s the ti cket

Fig: Sequence diagram for ticketing

COLLABORATION DIAGRAM:
It represents collaboration between the objects. It is nothing but a set of objects
related in a particular content and interaction.

: consumer

1: requests for a ticket

2: specifies the details
8: takes the amount

5: the ticket is not available

7: requests the amount
9: enquires the name
12: receivces the ticket

4: not available
6: valid
11: issues the ticket : operator

3: enters the bus no.,date

,time 10: enters the name
system

Fig: Collaboration diagram for E-seva

ACTIVITY DIAGRAM:
It is used to model an entire business process. It provides a flow of programs. It is
used to show internal state of an object but events may appear in them.

login

password not accepted

password accepted

select type of service

from menu

service selected

service not selected

more services

perform the
service

no more services
exit from the
service menu

Fig: Activity diagram for E-seva

CLASS DIAGRAM:
Class diagrams are widely used to describe the types of objects in a system and their
relationships. Class diagrams model class structure and contents using design elements such
as classes, packages and objects.
customer
(from Use Case View)
cname
servicetype

provide data()
receive receipt()

certificate 1,n licence

(from Use Case View) (from Use Case View)
name vehicleno
fname sercharge
mname cname
place interacts
date get details()
provide licenses()
get details() 1,n
receipt() 1,n

1,n OPERATOR
(from Use Case View)
issues id issues
password
1 1
+login()
+update()
reservation
bill 1 (from Use Case View)
(from Use Case View)
busno
billno seatno
amount give out reserve source
fine destination
date 1,n 1,n
get data()
pay bill() resticket()
reciept() get ticket()

movie ticket
(from Use Case View)
application
seatno (from Use Case View)
sercharge 1,n 1,n
type
show
provide sercharge
tname reserve
provide app()
get details()
bookmovietickets()

Fig: Class diagram for E-seva

STATE TRANSITION DIAGRAM:
State chart diagrams are used to describe the behavior of the system. These statements
describes all possible states of an object as an event occurs.

idle state

login

per form
transaction

error maintena
in transaction nce

transaction successful

update
transaction

log out

Fig: State chart diagram for E-seva

COMPONENT DIAGRAM:
The component diagram contains components and dependencies. Components
represents the physical packaging of a module. The dependencies between the components
show how changes made to one component may affect the other components. Component
diagram can also show the interfaces used by the components to communicate each other.

Login D ataba se Re s e rva t i o n

ticket

C us to me r Ma i nt a i n
B i lls D ata base

Fig: Component diagram for E-seva

 DEPLOYMENT DIAGRAM:
A deployment diagram shows processors, devices and connections. Each model
contains a single deployment diagrams which show the connection between the processors
and devices and its allocations from processor to processor. Processor specification, device
specifications enable you to display and modify the respective properties.

Fig: Deployment diagram for e-seva

Viva Voice Questions:

1. What are Relationships?
Ans: There are different kinds of relationships:
Dependencies,
Generalization and
Association.

Dependencies are relationships between two entities.

A change in specification of one thing may affect another thing.
Most commonly it is used to show that one class uses another class as an argument in the
signature of the operation.

Generalization is relationships specified in the class subclass scenario, it is shown when one
entity inherits from other.

Associations are structural relationships that are:

a room has walls,