Professional Documents
Culture Documents
Municipality Website Report
Municipality Website Report
The major purpose of the project that is being made by us is described as below:
Mobile
Phone
Computer
Newspaper
Application Forms
3. Inventory objects Mobile
Computer
Web browser
Admin
Public
Manager
Clerk
Child
3. Scene of User Context
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.
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.
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.
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]
The major purpose of our project is to save the precious time of user. User can
complaint online.
During BE II
PHP
HTML
Web Browser
During BE IV
Web development
Java (Java media framework)
During BE II
Web browser
internet
During BE III
Firefox
During BE IV
During BE II
During BE III
Design Engineering-2B 19 6th Sem
IT Department BVM Engineering College
HTML or PHP to build the website
During BE IV
During BE II
Pen
Paper
Computer
During BE III
Computer
Internet
Mobile
During BE IV
Computer
Mobile
Internet
Figure 10 : Snapshot 1
Figure 11 : Snapshot 2
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
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
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
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.
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.
3. Diagram:
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.
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.
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.
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
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.
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.
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:
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.
3. Diagram:
(1) Context level diagram:
(2) DFD diagram for Registration, Login activity and City Updates activities
Chapter 8: Implementation
Home:
Access to Vidhyanagar Municipal Corporation begins here, any new user or the registered
user or employee can access the data through this page.
Login
Complaint Management
Tax Payment
Certificate Registration
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.
Contact
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.