Project Synopsis

“Online Complaint Management System”
A Project to be developed for

“Academic Project 2010” MCA-IV Semester.

International School of Informatics &Management Jaipur
Affiliated to Rajasthan Technical University, Kota

Team Members: 1. Ankit Maini 2. Gaurav Ojha 3. Charvie S. Thakore

1.) Introduction 1.1) Purpose 1.2) Scope 1.3) Definitions & Abbreviation 1.4) References 1.5) Tool to be Used 1.6) Technologies 1.7) Overview 2.) Overall Description 2.1) Product Perspective 2.2) Product functions 2.3) User characterstics 2.4) Software Interfaces 2.5) Hardware Interfaces 2.6) Communication Interfaces 2.7) Constraints 2.8) Assumption and Dependencies 3 3 4 5 6 6 6 7 7 8 8 9 9 9 10 10

3.) 4.) 5.) 6.) 7.)

Data Flow in OCM Use-Case Diagram Architecture Diagram Database Schema Entity Relationship Diagram

11 12 13 14 16


Online Complaint Management Software:

IntroductionThis project is a system that can be use either as a static system or as a dynamic system that is as an online system for managing the complaints of the city. The purpose of online complaint registration is to manage and maintain the condition of the services provided by the state government better. User of this system can register on the system and submit his complaint regarding electricity, water and telephone and sanitary problems. According to the allotted complaint number processing will be done to solve the problem. 1.1 Purpose: Purpose of online complaint management is to reduce the load of individual complaining regarding municipal services and make the problem solving faster. This system will automate the task of complaining and increases the awareness of a particular society about its problems and encourages them to take a step towards solving them. It is efficient and maintains the department specific complaints. The following key factors describe its purpose precisely and in the best manner:      Paperless Record Keeping. On line as well as a desktop system. Cost effective. Department specific complaint registration. Problem solving through computer reduces human effort. Reduces time spent in manual complaining.


1.2 ScopeThis system is designed specially for the citizens of a city. It provides a complete solution for complaining system. This system facilitates complaining through:a. Online Complaint registration. b. User can register area specific complaints. c. Administrator can view the profile of the users. 1.3 Definition, Acronyms and AbbreviationsHTML: Hypertext Markup Language is a markup language used to design static web pages. ASP.NET: The .NET Framework is the infrastructure for the Microsoft .NET platform. The .NET Framework is an environment for building, deploying, and running Web applications and Web Services. The .NET Framework contains a common language runtime and common class libraries - like ADO.NET, ASP.NET and Windows Forms - to provide advanced standard services that can be integrated into a variety of computer systems. The .NET Framework provides a feature-rich application environment, simplified development and easy integration between a numbers of different development languages. The .NET Framework is language neutral. Currently it supports C++, C#, Visual Basic, and JScript (Microsoft's version of JavaScript). Microsoft's Visual Studio.NET is a common development environment for the .NET Framework.


CSS: (cascading Style Sheets) are a way to control the look and feel of HTML documents into an organized and efficient manner. ORACLE: Oracle is currently one of the most widely used RDBMS that provides efficient solutions for the database applications. It is responsible for accurately storing the data and efficiency retrieving that data inn response to an user query. Millions of application developers and database administrators use oracle to build complex system that manage huge amount of data. It also provides open access to web services through SQL, Java, standard web interfaces. IIS: Internet Information Service is a web server application and set of feature extension modules created by Microsoft for use with Microsoft Windows.

1.4 ReferenceSearch Engines 1.4.1 1.4.2 1.4.3 1.4.3 Websites   


Books  ASP.NET Bible  Complete reference ASP.NET  Unleashed ASP.NET 3.5  Professional ASP.NET 2.0 (WROX PUBLICATION)  Database management :Korth  Oracle Database 10g: a beginner guide  System Analysis and Design by Elias M Awad

1.5. Tools to be used 1.5.1 ASP.NET 1.5.2 IIS 1.5.3 Visual Studio 2008 1.5.4 Oracle 10g 1.6. Technologies To Be Used 1.6.1 ASP.NET 1.6.2 C# 1.6.3 Cascading Style Sheet(CSS) 1.6.4 HTML. 1.7 OverviewSection 2.0 the general description gives an “executive overview” and is very client oriented. It focuses on the functional and data requirements of the application. It also lists the limitations, assumptions and dependencies of the application. Section 3.0, the specific requirement section,

includes the developer’s technical view of the client’s expectations of the application. It also touches on the performances and quality requirements of the application and provides a solid definition of the interface.

2.Overall DescriptionThe program (software) will be a desktop as well as web based application, it means it run from a browser. The product should be able to run from a remote client machine with an internet connection. This decision is made depending on where the data file is stored. If it is stored locally, then the program will run on the local machine. The external interface will be through the web browser, through HTML, JavaScript, ASP.NET, etc. The current hardware running the software in Pentium 4, 2.4 GHZ, running windows (98, 2000, ME, XP, Vista) using Oracle as a database system, IIS as web server.


2.1 Product Perspective

HTML Client


Client Software (System user)


Client Side

Application Server

Data Base Server

The web pages are present to provide the user interface on customer client side. Communication between customer and server is provided through HTTP/HTTPS protocols. The Client Software is to provide the user interface on system user client side and for this TCP/IP protocols are used. On the server side web server is for ASP.NET and database server is for storing the information.


2.2 Product FunctionsOnline Registration of Complaints. 2. Keeping the records of all the complaints. 3. Keeping the records of every category of complaint. 4. Department specific registration of complaints. 5. Online reviews of complaints by the administrator. 6. Facilitates area specific complaining. 7. View of complaint of similar kind.

2.3 User characteristics• User should have basic computer knowledge. • User is supposed to be a registered citizen of the society. • User should know English.

2.4 Software Interface: Client on Internet: Web Browser, Operating System (any)
  

Web Server: IIS Client on Intranet: Client software, web browser, Operating System(any). Data Base Server: Oracle 10g

 

Development End: ASP.NET, Oracle, OS (Windows), Web Server(IIS).

5. Hardware Interface: Client Side Processor RAM Pentium IV at 512 MB 500 MHz Server Side Pentium IV at 1GB 1 GHz Pentium IV at 1GB 1GHz

Internet Explorer 6.0 ASP.NET Oracle

Disk Space Minimum 20 GB Minimum 20 GB Minimum 20 GB

2.6 Communication Interface:  Client on Internet will be using HTTP/HTTPS protocol.  Client on Intranet will be using TCP/IP protocol. 2.7 Constraints:  GUI is only in English.  There is no maintainability of back up so availability will get affected.  User should be registered citizen of the city.  Complaint can not be resubmitted before specified period. 2.8 Assumptions and Dependencies:  Administrator is created in the system already.  User of the system should not be naive. User should have basic knowledge of computer.

 More users can only be added by Administrator.

Data Flow in Online Complaint System:

User (citizen)
Login Registers Complain t View/edit profile


User_comp_info_table User_info_table

View/edit Complaint



Use Case Diagram
Online Complaint

View/edit Profile

Change Password User (citizen) Register Complaint

View User Information

View/edit Complaints Admin


Data Base Architecture Diagram

Login Table Email id* User_type Password Sec_Q Sec_A User_info Table User name Email id* Address City State Pin Phone Mobile Complaint_no Complaint_type Complaint_status Email id Complaint_msg Complaint_date Meter_ no. Consumer_no. User_Complaint Table


Data Base Schema

1. Login Table Name
Email User_type Password Sec_Q Sec_A

Data Type
Varchar2 Varchar2 Varchar2 Varchar2 Varchar2

Email id The type of user Password of user Security question Security answer

2. User Information Table Name
User_id Email Address City State Pin Phone Moblile

Data Type
Number Varchar2 Varchar2 Varchar2 Varchar2 Number Number Number

User id Email id Address of the user City where user belongs State of the user PIN code of the city Landline number of user Mobile number of user


Complaint Info Table Data Type
Number Varchar2 Varchar2 Varchar2 Varchar2 Date Number Number

Com_No Com_type Email Status Com_msg C_date Meter_no Consumer_no

Id of the complaint Type of the complaint Mail id of the user Complaint’s current status Complaint Description Date ofcomplaint submitted Meter No of the user Consumer no of the user


E-R Diagrams

Views / Edit User (citizen)


Regist er


View/ edit Comp_Electric ity




User Information

Comp_Water 15

Sign up to vote on this title
UsefulNot useful

Master Your Semester with Scribd & The New York Times

Special offer for students: Only $4.99/month.

Master Your Semester with a Special Offer from Scribd & The New York Times

Cancel anytime.