8.aca report

Active City Administration

Department of Computer Science/ BCA

CHAPTER-1

INTRODUCTION

In the present world all the government and non-government processes are

getting automated by the use of software and web technologies. One of them is City

administration which is a vital department for any City. Traditional approach faces

various hindrances, slow working, more paper work, less interactivity among normal

citizens and Local Municipal officers. Overcoming all these hurdles and providing

better user friendly web application is a big challenge.

Active City Administration (ACA) is a web application which provides online

services to citizen and Local Municipal officers at their doorstep. This is an online

platform where people can share ideas, invoke discussions, issue complaints, create

suggestion/petitions for improvement of city administration. This application is

effective which provides quick services to citizens who can lodge a complaint online,

check the complaint status online. The citizen can login and interact with any Local

Municipal officer present in his city. Using Google Maps a special functionality has

been provided to get information about the nearby Hospitals, Colleges, Banks &

Hotels.

The Municipal officers are provided with the facility of maintaining each of

their department in detail. He can access all the complaints, suggestions from users.

Invoke proper activity in response to valid complaints, or redirect inappropriate

complaints to the Citizens. He can also accept or reject the various given complaints.

The admin can create Municipal officers, remove users, filter the content reported as

inappropriate and handle threats. He is also responsible for maintaining the

database of the system.



1.1 AIM OF THE PROJECT

To create a user-friendly online interface for citizens to communicate with

administrative body and, reduce the distance and time barrier between citizens and

administration. To create a online platform where people can share ideas, invoke

discussions, issue complaints, create suggestion/petitions for improvement of city

administration. To encourage the citizens to actively participate in city administration to

bring transparency and flexibility in system.

1.2 OVERVIEW OF THE PROJECT

The purpose of this project is to create a new application called: Active City

Administration. This project provides an easy environment for citizens of city, local

municipal authority, administrators and NGO’s (Non Government Organization) to

invoke discussions, issue complaints for improvement of effective city administration.

The initial idea is to encourage the citizens to actively participate in city

administration to bring flexibility and transparency in the system. The user has an

account where he can lodge complaints, response details and can give feedback.

Authorities are involved in invoking proper activity in response to valid complaints, or

redirect inappropriate complaints to the administrator.

This project is based on intranet application which can be accessed through the

internet. It helps to interact with the local municipal authority. The complaint registration

is done through online and hence it maintains the closer relationship between the citizen

and administrative body. It helps to reduce the time barrier and the maintenance of file

system in the organization.

The contributions of this project are twofold. First, motivates people exhibiting

their responsibilities towards society. Secondly, limited hour service availability in the

current system is deployed.



1.3 PROBLEM STATEMENT

As compared to file system, working is slow in conventional method. Due to

slow working it provides less interactivity among the citizens and Municipal

Department. It consumes more paper work and lot of time. As a result citizens get

hindrances and lack of involvement of people in exhibiting their responsibilities towards

society.

1.4 PROBLEM SOLUTION

To create a user-friendly online interface for citizens to communicate with

administrative body and, reduce the distance and time barrier between citizens and

administration. To create a online platform where people can share ideas, invoke

discussions, issue complaints, create suggestion/petitions for improvement of city

administration. To encourage the citizens to actively participate in city administration to

bring transparency and flexibility in system.

1.5 SCOPE

There are four basic users – Citizen, Local Municipal Authority (LMA),

Administrator and Non-Government Organizations (NGO).

To create different authority and assign corresponding privileges.

To maintain a centralized database to provide security to the information this can be

accessed only by the admin.

To allow LMA (municipal officers) to log on to his account to view complaints,

suggestions and feedbacks that are sent by citizens.

To create Municipal officers to departments like Education, Health, Garbage

Collection, Water Supply, Roads and other departments as the first time setup.

To provide transfer and promotion feature for employees.

To track all the citizens and their contact details.

To authenticate all users to utilize the service.

To include FAQ section for users benefit.



CHAPTER-2

LITERATURE SURVEY

2.1 JAVA: Java is an object-oriented programming language developed by Sun

Microsystems a company best known for its high end UNIX workstations.

Java language was designed to be small, simple and portable across platforms

operating systems, both at the source and at the binary level, which means

that java programs can run on any machine that has the Java virtual machine

(JVM) installed.

2.2 J2EE: Java Platform Enterprise Edition or Java EE is a widely used platform

for server programming in the Java programming language. The Java

platform(Enterprise Edition) differs from the Java Standard edition

Platform(Java SE) in that it adds libraries which provide functionality to

deploy fault-tolerant, distributed, multi-tier Java software, based on modular

components running on an application server.

2.3 AJAX: AJAX is an acronym for Asynchronous JavaScript and XML. AJAX

is a technique for creating fast and dynamic web pages. It allows web pages

to be updated asynchronously by exchanging small amounts of data with the

server behind the scenes. This means that it is possible to update parts of a

web page, without reloading the whole page. Classic web pages, (which do

not use AJAX) must reload the entire page if the content should change.

2.4 Web server- WASCE: WebSphere Application Server Community

edition is a free, certified java EE 5 server for building and managing Java

applications. It is IBM’s supported distribution of Apache Geronimo that uses

Tomcat for servlet container and Axis 2 for web services. Over 15 WASCE

developers are committers in the Apache Geronimo project.



2.5 Development tool – RAD: IBM Rational Application Developer for

WebSphere software (RAD) is an integrated development

environment (IDE), made by IBM’s Rational Software division, for

visually designing, constructing, testing and deploying Web services,

portals and Java (J2EE) applications.

2.6 Database platform – DB2: Database is the database management

system that delivers a flexible and cost effective database platform to

build robust on demand business applications and supports the j2EE

and web services standards.

2.7 Design tool- Rational Software Modeler: IBM Rational Software

Modeler (RSM) made by IBM’s Rational software division, is a

Unified Modeling Language UML 2.0-based visual modeling and

design tool. Rational Software Modeler is built on the Eclipse open-

source software framework and includes capabilities focused on visual

modeling and model-driven development (MDD) with the UML for

creating resilient, through-out applications and web services.

2.8 Operating system-windows 7 -Windows 7 is the member of the

Microsoft windows family of products and is successor of windows

vista with some added functionality compared to windows vista. These

features can be experienced while using Internet Explorer and some

multimedia related things.



CHAPTER-3

SYSTEM REQUIREMENT SPECIFICATION

System requirements set out the system services and constraints in detail. This

requirement also provides information about the operational environment for the

application. System requirements are further classified into two types:

Software requirements

Hardware requirements

3.1 Software requirements:

This provides information about all the software that is needed to develop the

application.

The required softwares are:

Microsoft Windows 7

Java and J2EE platform

IBM DB2 9.7 Express-C

IBM Rational Application Developer 7.5

IBM WebSphere Application Server 7.0

3.2 Hardware Requirements:

This provides the information about the hardware to be used for the application.

Client Side

Processor: Intel Pentium IV

RAM: 512 MB

Disk Space: 300 MB

Server Side:

Processor: Intel Pentium IV

RAM: 1 GB

Disk Space: 3.5 GB



CHAPTER-4

SYSTEM DESIGN

4.1 EXISTING SYSTEM

Slow working in conventional method.

Various hindrances for the citizens

Less interactivity among the citizens and Municipal Department.

More paper work that consumes lot of time.

Lack of involvement of people in exhibiting their responsibilities towards society.

4.2 PROPOSED SYSTEM

4.2.1 Users of the system

Citizen

LMA(Local Municipal Authority)

Administrator

NGO(Non-Government Organization)

Users (Citizens)

Users should be able to create new account, log-in to their existing accounts

which will give them the authority to use the services provided by the system.

Authenticated users should be able to issue complaints, check complaint status,

submit feedback and browse through other complaints and their feedback.

Authenticated users should be able to create suggestions/petitions; other users can

support or make suggestions for petitions; forward petitions to corresponding

authority for possible implementation.

Users can to create groups where users can share their experiences; discuss

common problems, and the possible solution.



Municipal Authorities (LMA)

Municipal authorities can log-in to their accounts as created by administrator.

Authorities can access all the complaints, suggestions from users.

Invoke proper activity in response to valid complaints, or redirect inappropriate

complaints to the administrator.

Give response to complaints with activity reports.

Administrators

Create, and monitor accounts of authorities.

Filter the content reported as inappropriate and handle threats.

Handle complaints about improper response by municipal authorities.

NGO's:

NGO can form user groups similar to other users.

NGO's can publicize their social causes on the site.



CHAPTER-5

DETAILED DESIGN

5.1 Data Flow Diagram

The Data flow diagram provides a view of flows and what is going on inside a

use case or among several classes. It can also be used to represent a class’s method

implementation. It contains activities representing in the performance of operations and

their transitions that are triggered by the completion of operation.

5.1.1 User Registration Activity

Initially user is made to fill all mandatory fields filled in registration form. Once

the user clicks submit, the username is verified. If the username is already present, then

the user is again taken back, so that he can change the username. If the username is

not present then it checks for password and remaining mandatory fields. If any of the

mandatory field is left empty or filled incorrect, then the user is informed to enter the

correct values. Once all these verifications are succeeded, then the registration is done.



5.1.2 NGO Registration

The NGO’s needs to fill all mandatory fields filled in registration form. Once

they click submit, the username is verified. If the username is already present, then they

are again taken back, so that they can change the username. If the username is not

present then it checks for password and remaining mandatory fields. If any of the

mandatory field is left empty or filled incorrect, then they are informed to enter the

correct values. These details are sent to admin for verification and the admin verifies the

data and approves registration and grants privileges.



5.1.3 User Login Activity

User is made to enter the username and password, if he is signing in through User ID,

User ID has to be entered, then entered values are verified. If it is a valid username and

password, then the user is logged in, or else they are asked to re-enter the correct values.



5.1.4 Lodging a Complaint Activity

The citizen enters the complaint text and sends it to admin and the system

generated Complaint_ID is returned to user.



5.1.5 Replying a Complaint Activity

The admin views the complaint and then he may reply to the user or he may

select the respective department and forwards the complaint to Department head.



5.1.6 Participating in a Discussion Forum Activity

The system displays all the posts to the users. The user can select a thread from

the recent posts and can reply for that post or he/she can create the new post. The user

can directly create a new thread and in that he/she can create a new post. The user can

also search for a particular topic and can select a thread from the results and can create a

new post.



5.2 Client Server Architecture

Figure 5.2 Product perspective

Three-tier is a client–server architecture in which the user interface, functional process

logic ("business rules"), computer data storage and data access are developed and

maintained as independent modules, most often on separate platforms. A model in which

a server communicates with both a client and with a database.

Client Side: AJAX and HTML.

Server Side: Java Server Pages

Database: DB2



5.3 Entity-Relationship Diagram

Figure 5.3 Entity Relationship Diagram



5.4 Use case Survey

Figure 5.4 Use Case Model Survey



5.4.1 Citizen use-case report

Figure 5.4.1 Use Case diagram for citizen

USE CASE DESCRIPTION

LoginIn The citizen has to LogIn in order to.

View profile Every registered citizen has his/her own profile containing personal details.

Update profile The citizen has the option to update his/her own profile.

Issue complaint The citizen can file complaint to LMA.

Suggestions The citizen can view already posted suggestion and he can give suggestion.

Feedback The citizen can view already given feedback and he can post feedback.

View Complaint The citizen can browse through other complaints and he can post complaints.

Check Complaint Status The citizen can check the status of his complaints.

GroupsThe citizen can create group where he can post his views, search groups created by other users and he can those join groups.

Sign out The citizen can sign out of his profile.



5.4.2 Admin use-case report

Figure 5.4.2 Use Case diagram for Administrator


LogIn Admin has to LogIn in order to start begin his work.

View complaint Admin views the complaint sent by other users

Feedbacks Admin can delete improper feedbacks posted by users.

Suggestions Admin can delete improper suggestions posted by users.

Department Heads Admin has authority to create new officers or LMA’s.

NGO’s Admin can view list of NGO’s who are registered.

Delete Users Admin has the authority to delete users.

Sign-out Admin can sign out of his profile.



5.4.3 LMA use case report

Figure 5.4.3 Use Case diagram for LMA


LogIn LMA has to LogIn in order to:

View profile LMA has its own profile containing personal details.

Update profile LMA has the option to update profile.

View complaint LMA views the complaint and take necessary action.

View suggestion LMA can view suggestion posted by the users.

View Feedback LMA can view feedback posted by the users.

NGO’s LMA can view list of NGO’s who are registered.

Sign out LMA can sign out of his profile.



5.4.4 NGO use case report

Figure 5.4.4 Use Case diagram for NGO


LogIn NGO has to LogIn in order to:

View profile NGO has its own profile containing personal details.

Update profile NGO has the option to update profile.

Social Cause NGO can publish their social cause.

Groups NGO’s can search groups and join them to post comments.

Sign out NGO can sign out of his profile.



5.5 Sequence Diagram

5.5.1 Users Login Sequence Diagram



5.5.2 Lodge Complaint Sequence Diagram

5.5.3 Authenticate User Sequence Diagram



5.5.4 Resolving Complaint Sequence Diagram



5.6 Class diagram

Figure 5.6 Schema diagram



5.7 Database Design

5.7.1 Table Name: LOGIN

Column Field Data Type Size Primary Key Foreign Key

Username Varchar 30 ¸

Password Varchar 30

5.7.2 Table Name: LMAOFF


Lmaid Varchar 20 ¸

Password Varchar 30

Name Varchar 30

Region Varchar 20

Emailed Varchar 30

Mobile Bigint 30

5.7.3 Table Name: CITIZEN


Userid Varchar 30 ¸

Password Varchar 30

V_password Varchar 30

Fname Varchar 30

Lname Varchar 30



Age Bigint 2

Gender varchar 10

Email varchar 15

Mobile Bigint 10

Occupation Varchar 30

Address Varchar 50

City Varchar 20

District Varchar 15

Pin Bigint 10

5.7.4 Table Name: COMPLAINT


Complaintno Bigint 10 ¸

Categoryno Char 10

Complaintdesc Varchar 25

Date Char 10

Statusno Bigint 8 ¸

Userid Char 30 ¸

5.7.5 Table Name: FEEDBACK


Feedbackno Bigint 8 ¸

Categoryno Char 10



Feedback varchar 25

Date Date 4

Userid Char 30 ¸

5.7.6 Table Name: NGOREG


Ngoid Char 30 ¸

Password Char 30

Vpassword Char 40

Ngoname Char 40

Email Char 20

Contact Char 20

Purpose Char 20 ¸

Address Char 50

City Char 30

District Char 30

State Char 30

Pin Bigint 8

5.7.7 Table Name: SUGGESTION


Suggestionno Bigint 20 ¸



Categoryno Char 20

Suggestion Varchar 250

Date Date 4

Userid Char 30 ¸

5.7.8 Table Name: CATEGORY


Categoryno Char 20 ¸

Category Char 20

5.7.9 Table Name: CGROUP


Groupid bigint 8 ¸

Groupname Char 30

Category Char 10 ¸

Date Date 4

Owner Char 30

5.7.10 Table Name: GROUPCNT


Groupid bigint 8 ¸

Nomembers bigint 8

Owner Char 30



5.7.11 Table Name: SOCIAL


Slno bigint 8 ¸

Cause Char 200

Date Date 4

Ngoid Char 30 ¸

Purpose Char 10 ¸

5.7.12 Table Name: STATUS


Statusno Bigint 8 ¸

Status Char 30



CHAPTER-6

IMPLEMENTATION

6.1 Introduction

The goal of the implementation phase is to translate the design of the system produced

during the design phase into a source code through a programming language which can

be executed by the computer and which performs the computation specified by the

design. For a given design, the aim is to implement the design in best possible manner.

6.2 Implementation details

This section aims to provide the implementation details which essentially consist of the

information about how the front and back ends are implemented.

JDBC Connectivity

JDBC driver plays a vital role in the connection to the DB2. It opens the connection

between the DB2 and J2EE component. The JDBC driver used in this project is

“com.ibm.db2.jcc.DB2driver”.

1. Loading the JDBC driver:

JDBC Driver can be loaded using the following method

Class.forName(“com.ibm.db2.jcc.DB2driver”);

2. Connect to the DB2:

Once driver is loaded, the J2EE component must connect to the DBMS using the

DriverManager.getConnection() method.

Connection con=DriverManager.getConnection(“jdbc:db2:ACA”);

3. Create and Execute a SQL statement:

String query1=”SELECT * from CITIZEN”;

4. Process data returned by the DBMS by the db2:

Statement datarequest; Connection db;

Datarequest=db.createStatement();

Resultset results=datarequest.executeQuery(“SELECT * FROM CITIZEN”);



5. Terminate the connection to the DB2:

The connection to the DB2 is terminated by using the close() method.

Connection Db;

Db.close();

6.3 Code of the Module

<script type="text/javascript">

function checklogin()

{

var uname=encodeURI(document.getElementById("username").value);

var pwd=encodeURI(document.getElementById("password").value);

var xmlhttp;

if (window.XMLHttpRequest)

{

xmlhttp=new XMLHttpRequest();

}

else

{

xmlhttp=new ActiveXObject("Microsoft.XMLHTTP");

}

xmlhttp.open("GET","login.jsp?username="+uname+"&password="+pwd+"",true);

xmlhttp.onreadystatechange=function()

{

if (xmlhttp.readyState==4 && xmlhttp.status==200)

{

var response = xmlhttp.responseText;

document.getElementById('login_response').innerHTML = response;



if(response.indexOf("username")!=-1)

{

document.getElementById('login_response').innerHTML = response;

}

else

{

window.location="citizenframe.jsp";

}

}

}

xmlhttp.send();

return false;

}

</script>

To login, we have created two fields as username and password. The variables for

username as usrname and password as pwd. After entering the details, the request() is

activated and both the fields are checked for validation. If the details are true, then the

control is redirected to page “Citizen.frame.jsp” else it returns false.

<form onsubmit="return checklogin()" method="post">

<table border="0" cellpadding="0" cellspacing="1">

<tbody>

<tr><td width="104">User Name:</td>

<td width="186"><input type="text" name="username" id="username" size="20"></td>

</tr>

<tr><td width="104"><br>

</td><td width="186"><br>

</td></tr>



<tr>

<td width="104">Password:</td>

<td width="186"><input type="password" name="password" id="password" size="20">

</td>

</tr>

<tr><td width="104"><br>

</td>

<td width="186"></td>

</tr>

<tr><td width="104" ><input id="tabbutton" title="Log into your account" type="submit" name="SignIn" value="SignIn" ></td>

<td width="186"><span id="login_response"></span></td>

</tr>

</tbody>

</table>

</form>

<%

String comno=request.getParameter("complaintno");

String query1="update complaint set statusno=3 where complaintno="+comno;

statement.executeUpdate(query1);

String msg="Your Complaint has been Accepted";

%>

<jsp:forward page="lmacomplaints.jsp"></jsp:forward>

To register the complaint, the complaintno parameter is taken. To update the complaint

status number and the complaint,the above code is written. After the complaint

registration,the message is displayed as, " Your Complaint has been Accepted" . As a

result the page is redirected to "lmacomplaints.jsp".



CHAPTER-7

TESTING

7.1 TESTING SCOPE

Testing is a major part of any project development cycle. A project is incomplete without

successful testing and implementation. A program or system design is perfect only when

communication between the user and designer is complete and clear. A successful

system design helps in efficient testing and implementation. Testing is vital to the

success of the system. This chapter concentrates on testing conducted on the project.

Testing has helped us in developing and improving the project especially the user

interface.

7.2 UNIT TESTING

In this testing each sub module was tested individually with test data and then

integrated into the overall system. Unit testing focuses verification effort on the smallest

unit of software design in the module or component. All modules of the system are tested

separately and also tested on integration. This testing was carried out during the coding

stage itself.

System User module testing:

Sl.no Test case Expected output Test Result

1 Correct User Login Success message and user home page. Success

2 Incorrect User Login Message displaying Incorrect user login. Success

3 Citizen signup form Citizen is signed up if all relevant data is entered. Success



Citizen module testing

Sl.no Test case Expected output Test Result

1 Citizen login Success message and citizen home page Success

2 Issue complaint Your complaint has been successfully registered Success

3 Submit Feedback Your feedback has been successfully submitted Success

4 Suggestions Your suggestion has been successfully submitted Success

5 Complaint status Table displaying the status of the complaint Success

6 Create Group To create a group with group name and category Success

7 Joined Group Table displaying the list of user joined groups Success

8 Search group Table displaying the all the groups Success

9 View profile User can view and edit his profile Success

LMA Officer module testing

Sl.no Test case Expected output Test result

1 Officer login Success message and respective officer home page Success

2 Profile Officer can view and edit his profile Success

3 View Complaints Table displaying suggestions given by citizens Success

4 Suggestion’s Table displaying suggestions given by citizens Success

5 Feedback Table displaying suggestions given by citizens Success

6 NGO’s List of registered NGO’s Success



Admin module testing

Sl no Test case Expected output Test result

1 Admin login Success message and respective officer home page Success

2 View complaints List of complaints from citizens Success

3 Add LMA officer List of LMA officers Success

4 Suggestions List of suggestion’s given by the citizens Success

5 Feedback List of Feedback’s given by the citizens Success

6 Delete users List of users admin want to delete Success

NGO module testing

Sl no Test case Expected output Test result

1 NGO login Success message and respective officer home page Success

2 Social Programme Social cause has been added by NGO Success

3 View profile NGO can view and edit his profile Success

4 Create Group To create a group with group name and category Success

5 Joined Group Table displaying the list of user joined groups Success

6 Search group Table displaying the all the groups Success



7.3 Integration Testing

Complete System Testing is carried after completing pages are tested successfully. Tests

against the transfer of data from page to page is tested, also ensures consistency and data

integrity .Major considerations for Complete System Testing are:

1. Any defects are tested in progress through the sequence of states in the specified

state.

2. All processing is carried out within time constraints laid down in Required

Specification.

3. System is tested against no fatal error. Correct navigation around forms and form

to form is maintained.



7.4 SNAPSHOTS

HOME PAGE

CITIZEN LOGIN

8.aca report

Documents

citizens of city

active city administration

issue complaints

inappropriate complaints

valid complaints

local municipal officers

local municipal authority

normal citizens