IT Department BVM Engineering College

Chapter 1: Product Development Canvas

The major purpose of the project that is being made by us is described as below:

1.1 PRODUCT PURPOSE


Purpose of e governance is to bridge between the authority and the cizitzens
of city.

Aware citizens can know about the ongoing scenarios in their city.

The businessman can know about the upcoming or ongoing tenders of
roadways or government buildings.

1.2 PRODUCT EXPERIENCE


The User will get the instant updates of all the notices directly in his app
so he will be able to see all the notices even at the home.

Due to instant update that the user gets on in his phone when he renews
or gets a information about tenders, he will be able to know all the
information on time.

1.3 PRODUCT FUNCTION

Information’s

about Tenders.
Respected Information for Staff.

City Explorer.

Events and its notification.

Contact us and complaints.

Application Forms(Birth, Death, Marriage Certificate)

Tender Notices

Tax Paying Online

License Department

th
Design Engineering-2B 1 6 Sem
IT Department BVM Engineering College

1.4 PRODUCT FEATURES


Information’s about Tenders.

Respected Information of Staff.

City Explorer

Events and its notification

Contact us

Recruitment details



Complaints Management Time Table of Buses and Trains
1.5 PRODUCT COMPONENTS:

Web Server

Mobile

Internet connection

1.6 PRODUCT REVALIDATION


User want loan facilities

User wants to apply online for caste certificate

1.7 FUNCTION REJECT, REDESIGN AND RETAIN Reject :-


Loan Application
Redesign :-

Cast Certificate Application
Retain :-

Health Insurance

th
Design Engineering-2B 2 6 Sem
IT Department BVM Engineering College
Chapter 2 AEIOU Framework for Observation 2.1 Activity Record Sheet
1. General impression and observation

Solving Complaints :

Tender Related Activity

Issuing the Certificate(Birth, Death, Marriage)

Ambulance and Fire Brigade
2. Elements , features and special notes

Mobiles

Computers

Vehicles

3. Sketch/Photo

Figure 1:Activity Image

th
Design Engineering-2B 3 6 Sem
IT Department BVM Engineering College

Figure 2 : Activity Canvas

th
Design Engineering-2B 4 6 Sem
IT Department BVM Engineering College
2.2 Environment report sheet
1. General impression and observation style material and atmosphere

Sunny

Cloudy

Rainy

Day/Night

Urban Area

2. Elements , features and special notes


Light Poles

Dustbins

3. Scene

Figure 3: Environment Scene

th
Design Engineering-2B 5 6 Sem
IT Department BVM Engineering College

Figure 4 : Environment Canvas

th
Design Engineering-2B 6 6 Sem
IT Department BVM Engineering College

2.3 Interaction report sheet

1. General impression and observation

Water Supply and Management

Cleaning(Footpath , Roads , Garden , Putting the dustbins)

Street Light Maintenance

Tax Collection(Property, Sales, Income)

Drainage System

2. Elements , features and special notes



Ambulance Fire Truck

Light Poles

3. Scene of interaction

Figure 5 :Interaction Scene

th
Design Engineering-2B 7 6 Sem
IT Department BVM Engineering College

Figure 6 : Interaction Canvas

th
Design Engineering-2B 8 6 Sem
IT Department BVM Engineering College

2.4 Object report sheet

1. General impression and observation

Public registering the Complaints on the phone.(about streetlights,
water supply, sewage)

User needs to go to municipality office to collect the form.[
Application(Birth , Death , Marriage)]

Business Men needs to check the Newspapers daily for the Tender
Notices. (about Notices, Forms etc.)
2. Elements features and special notes

Mobile

Phone

Computer

Newspaper

Application Forms

3. Inventory objects Mobile

Computer

Web browser

th
Design Engineering-2B 9 6 Sem
IT Department BVM Engineering College

Figure 7 : Object Canvas

th
Design Engineering-2B 10 6 Sem
IT Department BVM Engineering College
2.5 User report sheet
1. General impression of people

The User wants to Complaint Online.

The Contractors wants the Notice about Tenders.

The User wants the City Explorer.

Information about Employees.

Helpline Numbers.

2. Inventory of objects

Admin

Public

Manager

Clerk

Child

3. Scene of User Context

th
Design Engineering-2B 11 6 Sem
IT Department BVM Engineering College

Figure 8 : User Canvas

th
Design Engineering-2B 12 6 Sem
IT Department BVM Engineering College
Chapter 3 Review Report of Prior Art Search

3.1 Review of Water Management Portal 1

Water management portal:

Nowadays, water has become one of the most essential necessity for
most of the metro and cosmopolitan cities. The WMP maintains a log of all
the service gainers. It provides data, maintains templates regarding the
quality of the water and the equipment carrying it.
It also provides the necessary measures to be taken by the users to
keep the water clean and safe. It takes feedback from them and fills up the
voids in their services. It holds a log of the city to the places where the water
is being circulated. This portal provides statistical data concerning the
physical, chemical and biological properties of water. It is also purposed to
provide some of the concerning factors of water like the colour, alkalinity,
taste, odour, pH and hardness of water.
This web application can be accessed by four different users: Admins,
City employees, members, non-members. Admins, City employees and
members have their respective password protected profiles. Members once
after logging into the system can report any problems they face. City
employees can view the tags that are placed by different members and can
take necessary steps to rectify their problems or can reply to the comments
placed by different users. Admin has the privilege of maintaining the quality
of the web application by deleting falsy data and managing user accounts.

The Disadvantages of The Existing System is :-

•
The user has to manually place a complaint or query with the Municipal

Corporation.
•
Time taking process, Lack of easy accessibility, User cannot check progress of his/her

complaint

Our Plan :-
• 
To provide a web accessible information base.
•
To provide templates for information entry – e.g. education, water supply pressure

report, water quality concern report, etc.
• 
Allow for easy update of information by city employees.
•
Allow for easy retrieval of feedback collected to facilitate acting on feedback

received.
 th
Design Engineering-2B 13 6 Sem
IT Department BVM Engineering College

•
To allow report of water management-related issue (dirty water, bad odour,

pollution, etc.).
• 
Allow submission of suggestions for improvement.
• 
Enable a map view of the city.


th
Design Engineering-2B 14 6 Sem
IT Department BVM Engineering College

2
3.2 Review of Project Report of Pune Municipal Corporation

Birth & Death department

Health department takes care of the health in general of the people
within the corporation limits. The department runs many health schemes like
D.P.T., Polio, Measles and other deceases. Most important customer centric
process the department has is the registration of Birth and death of the
citizens. Also department has the responsibility of issuing the food licenses.
Birth & Death department objective is to register the Birth and Death within
the corporation limit, also issue the certificate for the same.

Property Tax Department

Property tax is one of the main sources of revenue for the PMC.
Residential and commercial properties, situated within the limits of PMC, are
assessed for tax. Property tax is tax on immovable or tangible real property
such as land, buildings and permanent improvements. Based on such
assessments, all the property holders are expected to pay the property tax.
Property Tax may comprise of basic house/building tax plus service taxes
such as street tax, and conservancy/scavenging tax. It is collected either half
yearly or annually. Property tax department is responsible for billing &
collection of property tax for all residential, commercial, open plots and other
types of properties within PMC limits held privately or by government (state
& Central).
E- Procurement

The tender cell in the corporation is responsible for the publication

and sale of the tenders. The publication of the tenders is outsourced to an
organization and the same organization do the publication and upload of the
tenders on the online system. Also the sale of the tender happens online. The
proposed E-Procurement module will empower the PMC to Covers full life
cycle of purchasing (indent to receipt of goods), Connects buyers and
suppliers through electronic exchange of Tenders, catalogs, contracts, POs,
invoices etc The basic responsibility of the Tender Cell of PMC is the sale
and processing of tenders of various departments of PMC. Currently only
the sale of the Tenders is done through online system.

th
Design Engineering-2B 15 6 Sem
IT Department BVM Engineering College
Licenses department
PMC issues various types of licenses like Food Licenses, Market
Licenses, Nursing home registration, Dog licenses, Pre conception & pre
natal diagnostic techniques licenses, etc. License department’s main
objective is to issuance of new license keeping in mind various pre-requisite
factors. Also renewal of the existing licenses is undertaken.
Accounts Department
Accounts department is the back bone of any ULB and constitute of
both Accounts and Audit. The major responsibilities are To receive all
moneys payable to the Corporation and credit the same in the bank Account
of the Corporation, To make payment on account of Municipal Fund, To
estimate Income & Exp. statement for the next financial year, To make
payment of Salary and pension of the employees, To control the budget
sanctioned by the Corporation, To make scrutiny of every financial proposal
on behalf of Hon. Commissioner.
Advantages
The benefit of the e-Governance solution will be delivered to citizens
in the form of Quick response time, multiple access points/ locations, Web
enabled services, minimum personal visits, Quality of service (QOS),
paperless transactions, transparency, multiple mode of payment &
reduction in service charges.

Get timely services:

E-Governance solution will benefit the citizens with state of the art
information updates relating to the progress of the services requested. The
same can be achieved by means of SMS, Email, Web.

The backend processing of the Corporation will be supported by Workflow

and Document Management System and ERP solution to reduce the service
delivery time to the Citizens.

Correct information:
As the information is available in digitized format in the ERP solution,
this will help the citizen to get the accurate and upto date information
available publicly or by request.

th
Design Engineering-2B 16 6 Sem
IT Department BVM Engineering College

The departments of PMC will be interlinked by ERP solution which will

enable citizen to get true picture of the status / state of the information.

Availability to provide feedback:

The e-Governance solution will be equipped with the Citizen
Grievance Redressal module which will help citizen not only register the
complaints but also to provide the feedback mechanism. This helps both
Corporation & Citizen to work together in more harmonious environment.

th
Design Engineering-2B 17 6 Sem
IT Department BVM Engineering College
3.3 Review of your Vidhyanagar Municipality Website:-

 The Website is intended to reduce the efforts of an ordinary citizen who has to
make a lot of efforts to do his municipal task
 These tasks are generally considered tedious because of the lack of involvement
of the municipal officers.[2]
 The user can file online for his certificates.[2]
 The user can complain online [1]
 The user can also use the municipal properties for the personal use too.
 The website helps to citizen to accomplish the objectives of using the service
online of the municipal corporation. [1]
 The website helps the user to let him use the functionality of online complaining,
registration of marriage, birth & death online.[2]  User can get the useful links
about his city on a one stop.
 User have the City Guide Facility.
 User Can apply online for the various license. [2]

th
Design Engineering-2B 18 6 Sem
IT Department BVM Engineering College
Chapter 4 Learning Need Matrix

The major purpose of our project is to save the precious time of user. User
can complaint online.

4.1 Software/stimulation/skill/mathematical requirement

During BE II


MS Office During BE III

PHP

HTML

Web Browser
During BE IV

Web development

Java (Java media framework)

4.2 Tools/Methods/Theories/Application process involved

During BE II

Web browser

internet

During BE III

Firefox
During BE IV

File transfer protocol

4.3 Applicable standards and design specification/principles and experiments

During BE II

 Windows XP and greater version required

During BE III
th
Design Engineering-2B 19 6 Sem
IT Department BVM Engineering College

HTML or PHP to build the website
During BE IV

Sending message to admin and people through ftp principle

4.4 Components materials’ strength criteria

During BE II

Pen

Paper

Computer

During BE III

Computer

Internet

Mobile

During BE IV

Computer

Mobile

Internet

th
Design Engineering-2B 20 6 Sem
IT Department BVM Engineering College

Figure 9 : Matrix Canvas

th
Design Engineering-2B 21 6 Sem
IT Department BVM Engineering College
Chapter 5 Snapshot of Fast Prototype

Figure 10 : Snapshot 1

Figure 11 : Snapshot 2

th
Design Engineering-2B 22 6 Sem
IT Department BVM Engineering College
Chapter 6 Data Dictionary

6.1 DATABASE
6.1.1
Table Name :- Login
Table Description :- To Store User’s and Admins Login Detail.
No Field name Data Type Constraint Description
01 user_id Varchar(20) Not null Store the user id
02 password Varchar(10) Not null Store the password
Table 1:Login table

6.1.2
Table Name :- Register
Table Description :- To stores the following user information according to the user
id

No Field Name Data Type Constraint Description

01 First Name Varchar(20) Not null Store the first name
02 Middle Name Varchar(20) Not null Store the middle name
03 Surname Varchar(20) Not null Store the surname
04 E-mail id Varchar(20) Not null Store the email id
05 Birthdate Date Not null Store the birthday
06 Phone no. Number Not null Store the phone no.
07 user_id Varchar(20) Not null Store the user id
Table 2 : Register Table

6.1.3
Table Name :- Complaint
Table Description :- To store complaint detail of user side and admin side
Primary Key :- com_id
No Field Name Data Type Constraints Description
01 Com_id Int Primary Key Store the complaint id
of user
02 Name Varchar(50) Not null Store the name of
user
03 Zone Varchar(50) Not null Store the zone of user

Design Engineering-2B 23 6th Sem

IT Department BVM Engineering College
04 Ward Varchar(50) Not null Store the ward of user

05 Add Varchar(200) Not null Store the address of

user
06 Phone_no Int Not null Store the phone no of
user
07 Email Varchar(50) Not null Store the email of
user
08 Other Details Varchar(500) Not null Store the complaints
of user
Table 3 : Complaint Table
6.1.4
Table Name :- Feedback
Table description :- To store feedback details of user side and admin side
Primary key :- Feed_id
Foreign key :- User_id
No Field Name Data Type Constraint Description
01 Feed_id Int Primary Key Store the feedback id
of user
02 Name Varchar(10) Not null Store the name of
user
03 Description Varchar(500) Not null Store the feedback of
user.
Table 4 : Feedback table

6.1.5
Table Name :- Birth Registration
Table Description :- to store birth certificate details of user side and admin side.
Primary key :- Birth_id
Foreign key :- user_id
No Field Name Data Type Constraints Description
01 Birth_id Int Primary Key Store the id of user
02 Child_id Varchar(10) Not null Store the child name
03 Father_name Varchar(10) Not null Store the fathers
name of child
04 Mother_name Varchar(10) Not null Store the mothers
name of child

Design Engineering-2B 24 6th Sem

IT Department BVM Engineering College
05 Gender Varchar(10) Not null Store the gender of
child
06 Residential_add Varchar(50) Not null Stores the address of
child
07 Hospital Varchar(20) Not null Store the hospital
name
08 Hospital_add Varchar(50) Not null Store the hospital
address
09 Date Date Not null Store the date of birth

10 Time Int Not null Store the time of

birth
11 Email Int Not null Store the email
address of user
12 Mobile Int Not null Store the contact
details
13 Documents Varchar(50) Not null Store the documents
Table 5 : Birth Registration table

6.1.6
Table Name :- Death Registration
Table Description :- To store death certificate details of user side and admin side
Primary key :- Death_id
Foreign key :- User_id
No Field Name Data Type Constraints Description
01 Death_id Int Primary Key Store the id of user
02 Name of applicant Varchar(50) Not null Store the name of
user
03 Relationship Varchar(10) Not null Store the relationship
of applicant
04 Name Varchar(10) Not null Store the name of
dead person
05 Gender Varchar(10) Not null Store the gender of
dead person
06 Place Varchar(10) Not null Store the place of
death
07 Reason Varchar(50) Not null Store the reason of
death
08 Age Number Not null Store the age
Design Engineering-2B 25 6th Sem
IT Department BVM Engineering College
09 Date Date Not null Store the date of
death
10 Address Varchar(200) Not null Store the address
11 Email Varchar(50) Not null Store the email of
user
12 Phone no. Int Not null Store the contact
details
13 Documents Varchar(50) Not null Store the documents
Table 6 : Death Registration Table

6.1.7
Table Name :- Marriage Registration
Table Description :- To store marriage certificate details of user side and admin side.
Primary key :- Marriage_id
Foreign key :- User_id
No Field Type Data TypeConstraints Description
01 Marriage_id Int Primary Store the id of user
Key
02 Date Date Note null Store the date of
marriage
03 Place Varchar(200) Not null Store the place
04 Name_of_groom Varchar(200) Not null Store the name of
groom
05 Religion Varchar(10) Not null Store the religion
06 Age Number(3) Not null Store the age of
groom
07 Status_of_groom Varchar(10) Not null Store the status of
groom
08 Name_of_bride Varchar(10) Not null Store the name of
bride
09 Religion Varchar(10) Not null Store the religion
10 Age Number(3) Not null Store the age of bride
11 Status_of_bride Varchar(10) Not null Store the status of
bride
12 Name_of_father_of Varchar(10) Not null Store the father name
_groom of the groom
13 Address Varchar(100) Not null Store the address of
groom

Design Engineering-2B 26 6th Sem

IT Department BVM Engineering College
14 Name_of_father_of Varchar(10) Not null Store the father name
_bride of the bride
15 Address Varchar(100) Not null Store the address of
bride
16 Documents Varchar(50) Not null Store the name of
documents
17 Email Varchar(50) Not null Store the email of
user
18 Mob Number(10) Not null Store the mobile no
of user
Table 7 : Marriage Registration table
6.1.8
Table name :- City Hightlight
Table Description :- to store news details
Primary key :- news_id
No Field Type Data Type Constraints Description
01 Update_id Varchar(10) Not null Stores the ID of
Updates
02 Date Date Not null Store the date of
update
03 Description Varchar(500) Not null Stores the update
Table 8 : City Highlights
6.1.9
Table name :- Staff Info
Table Description :- to store the staff info
No Field type Data type Constraints Description
01 S_id Varchar(5) Not null Stores the ID of
staff
02 Ename Varchar(20) Not null Stores the name of
employee
03 Designation Varchar(10) Not null Store the
designation of
employee
04 Email Varchar(30) Not null Store the email id
of employee
05 Phone Number(10) Not null Store the phone
number of
employee
Table 9 : Staff info table
th
Design Engineering-2B 27 6 Sem
IT Department BVM Engineering College
Chapter 7: Diagrams
7.1 Use Case Diagram
1.Use:

It is used to model the system/subsystem of an application.

It is used to get an outside view of a system.

It is used to gather requirements of a system.

It is used to identify external and internal factors influencing the system.
 
It is used to show the interacting among the requirements are actors. Used to capture
the dynamic aspect of a system.

2.Symbol:

Symbol Description

System:
If a subject (or system boundary) is displayed, the use case
ellipse is visually located inside the system boundary
rectangle.

Actor:
An Actor models a type of role played by an entity that
interacts with the subject (e.g., by exchanging signals and
data), but which is external to the subject (i.e., in the sense
that an instance of an actor is not a part of the instance of its
corresponding subject). Actors may represent roles played by
human users, external hardware, or other subjects. Note that
an actor does not necessarily represent a specific physical
entity.

Use Case:
A use case is the specification of a set of actions performed
by a system, which yields an observable result that is,
typically, of value for one or more actors or other
stakeholders of the system.

Association:
An association specifies a semantic relationship that can
occur between typed instances. It has at least two ends
represented by properties, each of which is connected to the
type of the end. More than one end of the association may
have the same type.

An end property of an association that is owned by an end

class or that is a navigable owned end of the association
indicates that the association is navigable from the opposite
ends; otherwise, the association is not navigable from the
opposite ends.

Design Engineering-2B 28 6th Sem

 IT Department BVM Engineering College
Collaboration:
A collaboration specifies a view (or projection) of a set of
cooperating classifiers. It describes the required links between
instances that play the roles of the collaboration, as well as the
features required of the classifiers that specify the
participating instances. Several collaborations may describe
different projections of the same set of classifiers.

Constraint:
A condition or restriction expressed in natural language text
or in a machine readable language for the purpose of declaring
some of the semantics of an element.

Dependency:
A dependency is a relationship that signifies that a single or a
set of model elements requires other model elements for their
specification or implementation. This means that the complete
semantics of the depending elements is either semantically or
structurally dependent on the definition of the supplier
element(s).

Extend:
This relationship specifies that the behaviour of a use case
may be extended by the behaviour of another (usually
supplementary) use case. The extension takes place at one or
more specific extension points defined in the extended use
case. The same extending use case can extend more than one
use case. Furthermore, an extending use case may itself be
extended.

* Include:
Include is a Directed Relationship between two use cases,
implying that the behaviour of the included use case is inserted
into the behaviour of the including use case. The including use
case may only depend on the result (value) of the included use
case. This value is obtained as a result of the execution of the
included use case.

Generalization:
A generalization is a taxonomic relationship between a more
general classifier and a more specific classifier. Each instance
of the specific classifier is also an indirect instance of the
general classifier. Thus, the specific classifier inherits the
features of the more general classifier.

Table 10: Use case symbols

th
Design Engineering-2B 29 6 Sem
IT Department BVM Engineering College

3. Diagram:

Figure 12: Use case diagram

th
Design Engineering-2B 30 6 Sem
IT Department BVM Engineering College
7.2 Sequence Diagram
1. Use:

Uued to shows how the objects interact with others object in a particular scenario
of a use case.


It is used to capture the orders of message flowing from one object to another. It is
used to capture dynamic nature but from a different angle.
2. Symbol:
Symbol Description

Actor:
An Actor models a type of role played by an entity that
interacts with the subject (e.g., by exchanging signals and
data), but which is external to the subject (i.e., in the sense
that an instance of an actor is not a part of the instance of its
corresponding subject). Actors may represent roles played by
human users, external hardware, or other subjects. Note that
an actor does not necessarily represent a specific physical
entity.

Call Message:
A message defines a particular communication between
Lifelines of an Interaction. Call message is a kind of message
that represents an invocation of operation of target lifeline.

Create Message:
A message defines a particular communication between
Lifelines of an Interaction. Create message is a kind of
message that represents the instantiation of (target) lifeline.

Duration Constraint:
A Duration Constraint defines a Constraint that refers to a
Duration Interval. A duration used to determine whether the
constraint is satisfied.

Duration Message:
A message defines a particular communication between
Lifelines of an Interaction.
Duration message shows the distance between two time

instants for a message invocation.

th
Design Engineering-2B 31 6 Sem
IT Department BVM Engineering College
Found Message:
A found message is a message where the receiving event
occurrence is known, but there is no (known) sending event
occurrence. We interpret this to be because the origin of the
message is outside the scope of the description. This may
for example be noise or other activity that we do not want to
describe in detail.

LifeLine:
A lifeline represents an individual participant in the
Interaction.

Lost Message:
A lost message is a message where the sending event
occurrence is known, but there is no receiving event
occurrence. We interpret this to be because the message
never reached its destination.

Message:
A message defines a particular communication between
Lifelines of an Interaction.

Return Message:
A message defines a particular communication between
Lifelines of an Interaction. Return message is a kind of
message that represents the pass of information back to the
caller of a corresponded former message.

Send Message:
A message defines a particular communication between
Lifelines of an Interaction. Send message is a kind of
message that represents the start of execution.

Terminate Message:
A message defines a particular communication between
Lifelines of an Interaction. Terminate message is a kind of
message that represents the termination of execution.

Table 11: Sequence symbols

th
Design Engineering-2B 32 6 Sem
IT Department BVM Engineering College
3. Diagram:
(1) Sequence diagram for Registration and Login

Figure 13: Registration/login sequence diagram

(2) Sequence diagram for Apply for different Certificates

Figure 14: Apply for Certificate sequence diagram

(3) Sequence diagram for Tax Payment

th
Design Engineering-2B 33 6 Sem
IT Department BVM Engineering College

Figure 15: Tax Payment sequence diagram

(4) Sequence diagram for Online Complaints

Figure 16: Online Complaints sequence diagram

th
Design Engineering-2B 34 6 Sem
IT Department BVM Engineering College
7.3 Activity Diagram
1. Use:

Used to show message flow from one activity to another.

It is used for visualizing dynamic nature of a system.

It is used to construct the executable system by using forward and reverse
engineering techniques.

It is used to describe dynamic aspects of the system.

2. Symbol:
Symbol Description

Activity:
Activities may describe procedural computation. In this context,
they are the methods corresponding to operations on classes.
Activities may be applied to organizational modelling for
business process engineering and workflow. In this context,
events often originate from inside the system, such as the
finishing of a task, but also from outside the system, such as a
customer call. Activities can also be used for information system
modelling to specify system level processes.

Activity Parameter Node:

Activity parameter nodes are object nodes at the beginning and
end of flows that provide a means to accept inputs to an activity
and provide outputs from the activity, through the activity
parameters. Activity parameters inherit support for streaming
and exceptions from Parameter.
Action:
An action represents a single step within an activity, that is, one
that is not further decomposed within the activity. An activity
represents a behaviour that is composed of individual elements
that are actions. An action may have sets of incoming and
outgoing activity edges that specify control flow and data flow
from and to other nodes. An action will not begin execution until
all of its input conditions are satisfied. The completion of the
execution of an action may enable the execution of a set of
successor nodes and actions that take their inputs from the
outputs of the action.

Accept Event Action:

Accept Event Action is an action that waits for the occurrence of
an event meeting specified condition.

th
Design Engineering-2B 35 6 Sem
IT Department BVM Engineering College
Accept Time Event Action:
If the occurrence is a time event occurrence, the result value
contains the time at which the occurrence transpired. Such an
action is informally called a wait time action.

Activity Final Node:

An activity may have more than one activity final node. The
first one reached stops all flows in the activity.

Conditional Node Specification:

A conditional node is a structured activity node that represents
an exclusive choice among some number of alternatives.

Control Flow:
A control flow is an edge that starts an activity node after the
previous one is finished.

Decision Node:
A decision node accepts tokens on an incoming edge and
presents them to multiple outgoing edges. Which of the edges is
actually traversed depends on the evaluation of the guards on
the outgoing edges..

Initial Node:
An initial node is a control node at which flow starts when the
activity is invoked. An activity may have more than one initial
node.
Table 12: Activity symbols

th
Design Engineering-2B 36 6 Sem
IT Department BVM Engineering College
3. Diagram:
(1) Activity diagram for Registration and login

Figure 17: Registration/login Activity diagram

th
Design Engineering-2B 37 6 Sem
IT Department BVM Engineering College

(2) Activity diagram for Apply for different kind of Certificate

Figure 18: Apply for Certificate Activity diagram

th
Design Engineering-2B 38 6 Sem
IT Department BVM Engineering College
(3) Activity diagram for Tax Payment

Figure 19: Tax Payment Activity diagram

th
Design Engineering-2B 39 6 Sem
IT Department BVM Engineering College

(4) Activity diagram for Online Complaints

Figure 20: Online Complaints Activity diagram

th
Design Engineering-2B 40 6 Sem
IT Department BVM Engineering College

7.4 ER Diagram
1.Use:

It Used for graphical representation of entities and their relationship to each other.

Typically used in computing in regard to the organization of data within in
databases or information systems.

It help us to visualize how data is connected in general way,and are particularly useful
for constructing a relational database.
2.Symbol:

Symbol Description

Entity:
Entities are objects or concepts that represent
important data. They are typically nouns, e.g.
Customer, supervisor, location, or promotion.
Strong entities exist independently from other
entity types. They always possess one or more
attributes that uniquely distinguish each
occurrence of the entity.

Associative entity:
Associative entities are entities that associate the
instances of one or more entity types. They also
contain attributes that are unique to the
relationship between those entity instances.

Relationships:
Relationships are meaningful associations between
or among entities. They are usually verbs, e.g.
Assign, associate, or track. A relationship provides
useful information that could not be discerned
with just the entity types.

Attributes:
Attributes are characteristics of either an entity, a
many-to-many relationship, or a one-to-one
relationship.
Multivalued attribute:
Multivalued attributes are those that are capable of
taking on more than one value.

th
Design Engineering-2B 41 6 Sem
IT Department BVM Engineering College
Derived attributes :
Derived attributes are attributes whose value can
be calculated from related attribute values.

Cardinality:
Cardinality and ordinality, respectively, refer to
the maximum number of times an instance in one
entity can be associated with instances in the
related entity, and the minimum number of times
an instance in one entity can be associated with an
instance in the related entity. Cardinality and
ordinality are represented by the styling of a line
and its endpoint, as denoted by the chosen
notation style.

Table 13: ER symbols

th
Design Engineering-2B 42 6 Sem
IT Department BVM Engineering College
3. Diagram:

Figure 21: ER diagram

th
Design Engineering-2B 43 6 Sem
IT Department BVM Engineering College

7.5 Data Flow Diagram

1.Use:

It is used to identify the flow of information,where data comes from,where it goes

and how it gets stored.
Used to capture the dynamic aspect of a system.

2.symbol:

Symbol Description

Circle:
A process transforms incoming Data flow into
outgoing data flow.

Datastore/database:

Datastore/database are repositories of data in the

system. They are sometimes also referred to us files.

Dataflow:
Dataflows are pipelines through which packets of
information flow. Label the arrows with the name of
the data that moves through it.

External Entity:
External entities are objects outside the system, with
which the system communicates .External entities are
sources and destinations of the system’s inputs and
outputs.

Table 14: Dataflow Symbols

th
Design Engineering-2B 44 6 Sem
IT Department BVM Engineering College

3. Diagram:
(1) Context level diagram:

Figure 22: Context level Diagram

(2) DFD diagram for Registration, Login activity and City Updates activities

Figure 23: Registration/Login DFD diagram

th
Design Engineering-2B 45 6 Sem
IT Department BVM Engineering College

(3) DFD diagram for Apply Certificate, Online Complaint Activity

Figure 24: Certificate DFD diagram

th
Design Engineering-2B 46 6 Sem
IT Department BVM Engineering College
(4) DFD diagram for Feedback, Staff ,Tax Payment Info

Figure 25: Tax payment , Feedback, Staff info DFD diagram

th
Design Engineering-2B 47 6 Sem
IT Department BVM Engineering College
(5) DFD diagram for Certificate Registration, Online Complaint Management, Tax
Payment

Figure 26: Data Flow Diagram Level-2 Certificate Registration

Figure 27: Data Flow Diagram Level-2 Complaint Registration

Figure 28: Data Flow Diagram Level-2 TAX Payment

th
Design Engineering-2B 48 6 Sem
IT Department BVM Engineering College

Chapter 8: Implementation
 Home:

Figure 29: Home Page

Access to Vidhyanagar Municipal Corporation begins here, any new user or the registered
user or employee can access the data through this page.

th
Design Engineering-2B 49 6 Sem
IT Department BVM Engineering College
 Sign Up:

Figure 30: Signup Page

If the user is new then he can provide the details in the following snapshot, and can access the
options like Complaint Management, E-TAX Payment, and Certificate Registration.
 Login

Figure 31: Login Page

th
Design Engineering-2B 50 6 Sem
IT Department BVM Engineering College
Through this any registered user can access services, we have provided
employee login too. Employee can see the complaint in the database added
by users.
 Services

Figure 32: Service Page

These are the services provided by the Vidhyanagar municipal corp.
 Complaint Management

Figure 33 : Complaint form

This is the complaint feeling form. Which are supposed to feel by registered user.
th
Design Engineering-2B 51 6 Sem
IT Department BVM Engineering College
 Tax Payment

Figure 34: Tax Payment (1)

th
Design Engineering-2B 52 6 Sem
IT Department BVM Engineering College

figure 35 : Tax Payment (2)

Figure 36: Tax Payment form

With the help of this any registered user or employee can pay the tax online. With the
help of internet banking

th
Design Engineering-2B 53 6 Sem
IT Department BVM Engineering College

 Certificate Registration

Figure 37 : Certificate Selection

Figure 38: Birth Certificate form

th
Design Engineering-2B 54 6 Sem
IT Department BVM Engineering College

figure 39 : Death Certificate form

Figure 40 : Marriage Certificate form

With the help of this any registered person can apply for certificates such as birth,
marriage, death. And the website store that form data into database for further process.

th
Design Engineering-2B 55 6 Sem
IT Department BVM Engineering College

 Contact

Figure 41: Contact detail

This is the contact page for feedback or any queries.

 About

Figure 42:about detail

th
Design Engineering-2B 56 6 Sem
IT Department BVM Engineering College

Conclusion:

In this semester we learned about various type of diagram. By using that diagram we learned how our
project works in various aspects. We came to know various kind of activities our application performs,
the sequence of activities, different entities required for main activities, and most importantly the flow
of data in our project. In this way we learned the overall working of our project using UML diagrams.

Future Plan:

The future plan of our project is to add new features in our project and enhance the existing features
in such a way that it can help the student in best possible way and save their time by the best possible
application. We will try to update our application to maximize the comfort of students.

th
Design Engineering-2B 57 6 Sem