8.aca Report

Active City Administration
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.
Department of Computer Science/ BCA
Page 1
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 NGOs (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.
Page 2

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.
Department of Computer Science/ BCA Page 3
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 IBMs 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.
Page 4

2.5 Development tool RAD: IBM Rational Application Developer for WebSphere software (RAD) is an integrated development
environment (IDE), made by IBMs 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 IBMs 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 opensource 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.
Page 5
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.
Page 7

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.
Page 8
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 classs 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.
Page 9

5.1.2 NGO Registration
The NGOs 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.
Page 10

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.
Page 11

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.
Page 12

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.
Page 13

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.
Page 14

5.2 Client Server Architecture
Figure 5.2 Product perspective
Three-tier is a clientserver 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
Page 15

5.3 Entity-Relationship Diagram
Figure 5.3 Entity Relationship Diagram
Page 16

5.4 Use case Survey
Figure 5.4 Use Case Model Survey
Page 17

5.4.1 Citizen use-case report
Figure 5.4.1 Use Case diagram for citizen
USE CASE LoginIn View profile Update profile Issue complaint Suggestions Feedback View Complaint Check Complaint Status Groups Sign out
DESCRIPTION The citizen has to LogIn in order to. Every registered citizen has his/her own profile containing personal details. The citizen has the option to update his/her own profile. The citizen can file complaint to LMA. The citizen can view already posted suggestion and he can give suggestion. The citizen can view already given feedback and he can post feedback. The citizen can browse through other complaints and he can post complaints. The citizen can check the status of his complaints. The citizen can create group where he can post his views, search groups created by other users and he can those join groups. The citizen can sign out of his profile.
Page 18

5.4.2 Admin use-case report
Figure 5.4.2 Use Case diagram for Administrator
USE CASE LogIn View complaint Feedbacks Suggestions Department Heads NGOs Delete Users Sign-out
DESCRIPTION Admin has to LogIn in order to start begin his work. Admin views the complaint sent by other users Admin can delete improper feedbacks posted by users. Admin can delete improper suggestions posted by users. Admin has authority to create new officers or LMAs. Admin can view list of NGOs who are registered. Admin has the authority to delete users. Admin can sign out of his profile.
Page 19

5.4.3 LMA use case report
Figure 5.4.3 Use Case diagram for LMA
USE CASE LogIn View profile Update profile View complaint View suggestion View Feedback NGOs Sign out
DESCRIPTION LMA has to LogIn in order to: LMA has its own profile containing personal details. LMA has the option to update profile. LMA views the complaint and take necessary action. LMA can view suggestion posted by the users. LMA can view feedback posted by the users. LMA can view list of NGOs who are registered. LMA can sign out of his profile.
Page 20
5.4.4 NGO use case report
Figure 5.4.4 Use Case diagram for NGO
USE CASE LogIn View profile Update profile Social Cause Groups Sign out
DESCRIPTION NGO has to LogIn in order to: NGO has its own profile containing personal details. NGO has the option to update profile. NGO can publish their social cause. NGOs can search groups and join them to post comments. NGO can sign out of his profile.
Page 21

5.5 Sequence Diagram
5.5.1 Users Login Sequence Diagram
Page 22

5.5.2 Lodge Complaint Sequence Diagram
5.5.3 Authenticate User Sequence Diagram
Page 23

5.5.4 Resolving Complaint Sequence Diagram
Page 24

5.6 Class diagram
Figure 5.6 Schema diagram
Page 25

5.7 Database Design
5.7.1 Table Name: LOGIN Column Field Username Password Data Type Varchar Varchar Size 30 30 Primary Key Foreign Key
5.7.2 Table Name: LMAOFF
Column Field Lmaid Password Name Region Emailed Mobile
Data Type Varchar Varchar Varchar Varchar Varchar Bigint
Size 20 30 30 20 30 30
Primary Key
Foreign Key
5.7.3 Table Name: CITIZEN
Column Field Userid Password V_password Fname Lname
Data Type Varchar Varchar Varchar Varchar Varchar
Size 30 30 30 30 30
Primary Key
Foreign Key
Page 26

Age Gender Email Mobile Occupation Address City District Pin Bigint varchar varchar Bigint Varchar Varchar Varchar Varchar Bigint 2 10 15 10 30 50 20 15 10
5.7.4 Table Name: COMPLAINT
Column Field Complaintno Categoryno Complaintdesc Date Statusno Userid
Data Type Bigint Char Varchar Char Bigint Char
Size 10 10 25 10 8 30
Primary Key
Foreign Key
5.7.5 Table Name: FEEDBACK
Column Field Feedbackno Categoryno
Data Type Bigint Char
Size 8 10
Primary Key
Foreign Key
Page 27

Feedback Date Userid varchar Date Char 25 4 30
5.7.6 Table Name: NGOREG
Column Field Ngoid Password Vpassword Ngoname Email Contact Purpose Address City District State Pin
Data Type Char Char Char Char Char Char Char Char Char Char Char Bigint
Size 30 30 40 40 20 20 20 50 30 30 30 8
Primary Key
Foreign Key
5.7.7 Table Name: SUGGESTION
Column Field Suggestionno
Data Type Bigint
Size 20
Primary Key
Foreign Key
Page 28

Categoryno Suggestion Date Userid Char Varchar Date Char 20 250 4 30
5.7.8 Table Name: CATEGORY
Column Field Categoryno Category
Data Type Char Char
Size 20 20
Primary Key
Foreign Key
5.7.9 Table Name: CGROUP
Column Field Groupid Groupname Category Date Owner
Data Type bigint Char Char Date Char
Size 8 30 10 4 30
Primary Key
Foreign Key
5.7.10 Table Name: GROUPCNT Column Field Groupid Nomembers Owner Data Type bigint bigint Char Size 8 8 30 Primary Key Foreign Key
Page 29
5.7.11 Table Name: SOCIAL
Column Field Slno Cause Date Ngoid Purpose
Data Type bigint Char Date Char Char
Size 8 200 4 30 10
Primary Key
Foreign Key
5.7.12 Table Name: STATUS
Column Field Statusno Status
Data Type Bigint Char
Size 8 30
Primary Key
Foreign Key
Page 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);
Page 31

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;
Page 32

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>
Page 33

<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 1 2 3
Test case Correct User Login Incorrect User Login Citizen signup form
Expected output
Test Result Success Success Success
Success message and user home page.

Message displaying Incorrect user login.
Citizen is signed up if all relevant data is entered.
Page 35

Citizen module testing
Sl.no 1 2 3 4 5 6 7 8 9 Test case Citizen login Issue complaint Submit Feedback Suggestions Complaint status Create Group Joined Group Search group View profile Expected output Success message and citizen home page Your complaint has been successfully registered Your feedback has been successfully submitted Your suggestion has been successfully submitted Table displaying the status of the complaint To create a group with group name and category Table displaying the list of user joined groups Table displaying the all the groups User can view and edit his profile Test Result Success Success Success Success Success Success Success Success Success
LMA Officer module testing

Sl.no 1 2 3 4 5 6 Test case Officer login Profile View Complaints Suggestions Feedback NGOs Expected output Success message and respective officer home page Officer can view and edit his profile Table displaying suggestions given by citizens Table displaying suggestions given by citizens Table displaying suggestions given by citizens List of registered NGOs Test result Success Success Success Success Success Success
Page 36

Admin module testing
Sl no 1 2 3 4 5 6
Test case Admin login View complaints Add LMA officer Suggestions Feedback Delete users
Expected output Success message and respective officer home page List of complaints from citizens List of LMA officers List of suggestions given by the citizens List of Feedbacks given by the citizens List of users admin want to delete
Test result Success Success Success Success Success Success
NGO module testing

Sl no 1 2 3 4 5 6 Test case NGO login Social Programme View profile Create Group Joined Group Search group Expected output Success message and respective officer home page Social cause has been added by NGO NGO can view and edit his profile To create a group with group name and category Table displaying the list of user joined groups Table displaying the all the groups Test result Success Success Success Success Success Success
Page 37

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. state. 2.
Any defects are tested in progress through the sequence of states in the specified
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.
Page 38

7.4 SNAPSHOTS
HOME PAGE
CITIZEN LOGIN
Page 39

8.aca Report

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

8.aca Report

Caricato da

Copyright:

Formati disponibili

Active City Administration

Department of Computer Science/ BCA

Active City Administration

1.1 AIM OF THE PROJECT

1.2 OVERVIEW OF THE PROJECT

Department of Computer Science/ BCA

Active City Administration

1.4 PROBLEM SOLUTION

Active City Administration

Department of Computer Science/ BCA

Active City Administration

Department of Computer Science/ BCA

Active City Administration

3.1 Software requirements:

3.2 Hardware Requirements:

Active City Administration

4.2.1 Users of the system

Department of Computer Science/ BCA

Active City Administration

Department of Computer Science/ BCA

Active City Administration

5.1.1 User Registration Activity

Department of Computer Science/ BCA

Active City Administration

Department of Computer Science/ BCA

Active City Administration

Department of Computer Science/ BCA

Active City Administration

Department of Computer Science/ BCA

Active City Administration

Department of Computer Science/ BCA

Active City Administration

Department of Computer Science/ BCA

Active City Administration

Figure 5.2 Product perspective

Department of Computer Science/ BCA

Active City Administration

Figure 5.3 Entity Relationship Diagram

Department of Computer Science/ BCA

Active City Administration

Figure 5.4 Use Case Model Survey

Department of Computer Science/ BCA

Active City Administration

Figure 5.4.1 Use Case diagram for citizen

Department of Computer Science/ BCA

Active City Administration

Figure 5.4.2 Use Case diagram for Administrator

Department of Computer Science/ BCA

Active City Administration

Figure 5.4.3 Use Case diagram for LMA

Department of Computer Science/ BCA

Active City Administration

5.4.4 NGO use case report

Figure 5.4.4 Use Case diagram for NGO

Department of Computer Science/ BCA

Active City Administration

5.5.1 Users Login Sequence Diagram

Department of Computer Science/ BCA

Active City Administration

5.5.3 Authenticate User Sequence Diagram

Department of Computer Science/ BCA

Active City Administration

Department of Computer Science/ BCA