lOMoARcPSD|32413716

ONLINE COMPLAINT REGISTRATION AND MANAGEMENT

SYSTEM PROJECT REPORT

A MINI PROJECT REPORT

Submitted by

DELHI GANESH V (20104086)

GURUPRASAD V (20104093)

GOKULAN V (20104091)

AJAY R (20104070)

in partial fulfillment for the award of the degree

of

BACHELOR OF ENGINEERING
in

COMPUTER SCIENCE AND ENGINEERING

HINDUSTHAN COLLEGE OF ENGINEERING AND TECHNOLOGY

Approved by AICTE, New Delhi, Accredited with ‘A’ Grade by NAAC
(An Autonomous Institution, Affiliated to Anna University, Chennai)
Valley Campus, Pollachi Highway, Coimbatore – 641 032

DECEMBER 2022
 lOMoARcPSD|32413716

Hindusthan College of Engineering And Technology

Approved by AICTE, New Delhi, Accredited with ‘A’ Grade by NAAC
(An Autonomous Institution, Affiliated to Anna University, Chennai)
Valley Campus, Pollachi Highway, Coimbatore – 641 032

BONAFIDE CERTIFICATE
Certified that this project report “ONLINE COMPLAINT
REMANAGEMENT SYSTEM” is the bonafide work of “DELHI GANESH
V (20104086), GURUPRASAD V (20104093), GOKULAN V (20104091),
AJAY
R (20104070)” who carried out the project work under my supervision.

SIGNATURE
SIGNATURE
Ms SATHYA S, M.E.,
Dr SHANKAR S, M.E., Ph.D.,
SUPERVISOR
HEAD OF THE DEPARTMENT
Assistant Professor
Computer Science and Engineering
Computer Science and Engineering
Hindusthan College of Engineering and
Hindusthan College of Engineering and
Technology,
Technology,Coimbatore-32
Coimbatore-32

Submitted for the Anna University Mini Project Viva-Voce conducted on

INTERNAL EXAMINER EXTERNAL EXAMINER

 lOMoARcPSD|32413716

ACKNOWLEDGEMENT
We take this opportunity to express our whole hearted thanks and our
profound respect to all those who guided and inspired us in the completion of
this project work.

We extend our sincere thanks to the Founder and Chairman of

Hindusthan Educational and Charitable Trust Shri.T.S.R. Khannaiyann and
the Managing Trustee Smt. Sarasuwathi Khannaiyann and Executive Trustee
& Secretary Mrs. Priya Satish Prabhu for providing essential infrastructure.

We would like to reveal our profound thanks to our respected Principal,

Dr.J.JAYA, who happens to be striving force in all endeavours.

We would like to express our gratitude to the Head of the Department

Dr.S.SHANKAR, for bringing out the project successfully and for
strengthening the ray of hope.

We express our immense pleasure and thankfulness to our Class Advisor

and Project Coordinator, Ms.S.SATHYA, Assistant Professor, and all other
Faculty members of the Department of Computer Science and Engineering,
technical staffs and friends who helped us for the successful completion of this
project. We express our earnest gratitude to our family members who
encouraged us and strengthened us in perilous path, encountered during our
task.
 lOMoARcPSD|32413716

ACKNOWLEDGEMENT

We are using this opportunity to express our gratitude to everyone who supported us
throughout this project. We would like to thank the Almighty God for blessing us
with his grace.

We express our thanks to the Managing Trustee Smt.T.R.K.Sarasuwathi

Khannaiyann, for providing the essential infrastructure and helping us to carry out
this project.

We would like to express our sincere gratitude to the Principal Dr.C.Natarajan,

Ph.D., for helping us in bringing out the project successfully and for strengthening
the ray of hope towards us.

We are profoundly indebted and very grateful to Dr.A.Jameer Basha MTech.,

Ph.D., Professor and Head of the Department, Computer Science and Engineering for
providing the right ambience needed for carrying out this project successfully.

We are profoundly indebted and very grateful to Mr. Biju Balakrishnan M.E.,
(Ph.D.,) Assistant Professor, Department of Computer Science and Engineering, who
is also our project guide for innumerable acts of timely advice, encouragement and
sincerely express our gratitude towards her.
We would like to extend our thanks to allot her faculty members of the Department of
Information Technology who helped us for the completion of the project.
Finally, we thank our friends and those who helped us directly and indirectly for
successfully completing this project.

3
 lOMoARcPSD|32413716

TABLE OF CONTENTS

CHAPTER TITTLE PAGE

NO
ABSTRACT 4
LIST OF FIGURES
1. INTRODUCTION 7
BASIC INTRODUCTION 7
SCOPE OF THE PROJECT 7
2. MODULE DESCRIPTION 8

MODULE DESCRIPTION 9

3. EXISTING AND PROPOSED 12

SYSTEM
EXISTING SYSTEM 12
PROPOSED SYSTEM 13

4. SYSTEM REQUIREMENT 17
System Requirements 17
Functional requirement 18
Non-functional requirements. 19
Technical Requirements 20

5
 lOMoARcPSD|32413716

5. SYSTEM DESIGN 22
Introduction 22
Purpose of the system 23
Design Goal 24
Current software architecture 25

6. RESULTS AND DISCUSSIONS 26

Result (Conclusion) 26

Future Scope 27

Screen Shots and Coding 28

REFERENCES 48

6
 lOMoARcPSD|32413716

ABSTRACT

The main purpose of this project is to help the public in knowing their place details
and getting their problems solved in online without going to the officer regularly until
the problem is solved.
By this system the public can save his time and eradicate corruption in government
offices.
Its main purpose is to provide a smart and easy way through android or web
Application for Complaint registration and its Tracking and eradicating system and
thus to prevent Corruption.
As technology is growing rapidly, we are also moving to a technical world where
everything we want is to be online.
The system will be developed using HTML, CSS, JavaScript and using Php
MyAdmin.

4
 lOMoARcPSD|32413716

CHAPTER 1

INTRODUCTION

BASIC INTRODUCTION
The main purpose of this project is to help the public in knowing their place details
and getting their problems solved in online without going to the officer regularly until
the problem is solved.

We want to develop web application for Complaint management .To transform the
existing manual compliant management system into an automate system. For the
better management of complaints to improve efficiency.
The main purpose of this project is to help the public in knowing their place details
and getting their problems solved in online without going to the officer regularly until
the problem is solved.

SCOPE OF THE PROJECT

The objective of this website is to help the public in knowing their place details and
getting their problems solved in online without going to the officer regularly until the
problem is solved.

7
 lOMoARcPSD|32413716

CHAPTER 2

MODULE DESCRIPTION

USER

Register
Post Complaint
Location Mark in Google Map
View complaint status
Feedback
Get Admin Contact details

OFFICER

Register
View Complaint
Update status
Update proof of work

ADMIN

Generate id & password for officer

The administrator has the full-fledged rights over the OES.
Create/delete an account.
view the accounts.
Change the password.
Hide any kind of features from the both of users.
Insert the information available on OES.
Access all the accounts of the officer

8
 lOMoARcPSD|32413716

2.1 MODULE DESCRIPTION

USER

Registration Module

Another main function of our proposed system is registration, in order to

register with the unique application details such as name; password, email, place and
time are required.

Post Complaint

User posts their complaint through this application. That is they can’t get water
regular manner in their area and about the problem description.

Location Mark in Google Map

In this module is used to the user marks their location in the Google Map for the
betterment of the complaint registration.

View Status

If the user to compliant the problems they need to a current status of the compliant so
it helps to user views the status about their complaint.

9
 lOMoARcPSD|32413716

Feedback

It helps to give a feedback for after completed the compliant the user to give a
feedback about the action what they done in a compliant.

OFFICER

View Complaint

In this module is used to officer view the complaint details who posted the user
complaint using the Google map location mark.

Update status

In this module is used to officer updates status for user compliant,

update the current status what going on in a compliant.

Update completed proof

It used to if the related compliant work is completed they give a proof using photo
format, Officer Update photo proof of work.

10
 lOMoARcPSD|32413716

ADMIN

Generate id & password for officer

In this module is used for generate the unique id and password for the Public Work
Department (PWD) officer.

Create/ delete an account

The admin can create an account for new user and also if it’s not need an account,
admin can remove the user account.

View the accounts

In this module used for admin to view all the users account for the reference, it helps
to know the users strength.

Change the password

In this module is used for to change the password for the security purpose.

Insert the information of available on OES

Admin want to insert the information of available on Office Economic Stabilization

(OES).

11
 lOMoARcPSD|32413716

CHAPTER 3

EXISTING SYSTEM AND PROPOSED SYSTEM

EXISTING SYSTEM

In the existing system only a compliant can be manual reported, also it has more
workload for the authorized person, but in the case of proposed system, the user can
register the site and send the first information report or compliant about a particular
compliant registration.

To avoid these limitations and make the working more accurately the system needs to
be computerized in a better way.

DRAWBACKS OF EXISTING SYSTEM

Its manual process for earlier system.

Its more time consume for all process.

Need for more resources.

There is chance to not resolve user problems.

Management is chance to forget user complaints.

12
 lOMoARcPSD|32413716

PROPOSED SYSTEM

We want to replace existing manual CMS (Complaint Management System) to an

android application changing the way of maintaining the society complaints will also
prove to be beneficial, improve efficiency and save us time.

By using this application people can register their complaints in easy and proper
format. Mainly they can mark their location in Google Map while placing the
complaint so that it will help the people in easy manner.

They will also well aware about their complaints progress.

They can also provide feedback about their complaints progress weather they are
satisfied or not.

Also they user can post their requirements through this system and they will receive
needed items by admin within couple of hours ,its depending on the needed item and
you can also look your status about your requirements.

These user complaints, needs requirements maintain by admin. The User post
feedback of these CMS system and admin can view this feedback.

13
 lOMoARcPSD|32413716

ADVANTAGES OF PROPOSED SYSTEM

To compliant our problem at any time.

Minimum time needed for the various processing.

The system is greater efficiency and better service .

User friendliness and interactive .

Minimum time required and also minimise manual data entry.

Practice to be presented

To solve complaint the officers have their own rules and standards written in
document

form for complaint user.

The complaint decision is announced to user on notice board.

To face complaint users bring a applicants letter from anywhere physically to

officers.

Officers allow to access information about the authority of the user.

The employee of officers must have full reason to solve their complain.

If the user wants to face their complain different reason first they must apply
to lowest level and then continue to next branch of office such as department
head ,college dean ,HRM, Finance Directorate, and etc.

If one wants to leave from DBU before he/she fills the form leave form he/she
must

return all working material to respected department otherwise they will be

rejected.

14
 lOMoARcPSD|32413716

Forms and other documents of existing system

There are a number of forms and documents which are used by the existing system.

The forms are used during the period of accepting and solving process for the
employee to control business rules of the system.

The uses of these forms are to assure the correctness of their activity and to generate
reports.

The following is sample form taken from Finance Directorate.

Bottlenecks of the existing system

Grievance handling officers decide the decision by wasting much time and wasting
high labor force.

Also customers cannot get quick decision.

In case of performance of the existing system the condition is manual so customers or

applicants contact physically with the officers in order to face their complaint.

The basic bottlenecks of existing system are:

The process is tedious for officers and users.

Those who do not have time to go to one of the offices have no alternative way
to report about their problem.

Customers who fears to report thinking something wrong might happen to them
do not have other means to place their complaint.

Report generation in general is very difficult in current system.

Much of the current system of the Compliant Management Systemis done

heavily inhuman interaction with the officers.

15
 lOMoARcPSD|32413716

proposed solution for the new system

To improve the current complaint handling system for the University, we have
proposed mobile based complaint management system.

The system simplifies registration process of Complaints.

The system enables users of the system to register complaints by sending SMS
message to the system. Users can follow status of the registered complaint using
SMS. The proposed system of this project intends to design and implement Mobile
based integrative compliant management system. This system designed to create
alternative way of complain management system for the university. It reduce burden
for the grievance handling office and any customers simply use the system from
anywhere at anytime.

The registered complaint automatically forwarded to the office in charge of

handling the issue.

This will reduce time needed to process and provide a solution for complaint.

Provide a very good and fast service for the users by computerised system.

The system that are developed solves the problems appear in the current system.

The new system enables users to register compliant information.

to view users notification, and officers to replay solution to submitted customer

notice to customer, allows coordination among workers, allows authorized users

to access the system .

The new system increases the security, availability and performance of the
system.

In this system user can easily register complain by sitting at his/her computer or
smart phone using the system, rather than going to office.

16
 lOMoARcPSD|32413716

CHAPTER 4

System Requirement Specifications

System Requirements

Requirement specifications develops a recommended process improvement action

which can include quick fix for serious problem, modification of existing manual
systems or the initiation of the an organization re-engineering process.

There are two main types of system requirement specification this are functional and
non- functional requirement.

Functional requirements are function that the system undertakes, whereas non-
functional requirement are restrictions that the system consider.

Functional requirement

The functional requirements are concerned with the actual performance of the system
that is going to be developed. Functional requirements describe the functionality or
service provided by the new system:

The system is capable of request complain to handling grievance office.

The system capable Recording new complaint and complain information to the
database in the main process of the system.

Allow registering complaints by sending SMS text.

Enabling the users to take or get the registered complain that they registered
orderly.

Document the file which is placed on the system of the data base to be accessed
as registers information.

17
 lOMoARcPSD|32413716

Allow workers to view registered complaints to update the status of the

complaint.

It organizes and makes searchable sites.

The system generates a report: Allow to generating different types of reports

which include types of complaints registered on specific date, month or
year, viewing summarized report.

Allow the administrator to manage access to the system.

Non-functional requirements

Non-functional requirement is a requirement that specifies criteria that can be used

to judge the operation of a system.

Non-functional requirements place constraints on how the system will do so.

The non-functional requirement elaborates a performance characteristic of the

system.

Also these requirements relate to system attributes such as reliability and response
time and they can arise due to user requirements.

Any requirement which specifies how the system performs a certain function
Considered when designing the solution.

The following are non-functional requirement associated with the system :

Performance :

The system error free when accessing huge amount of data. And the system should be
accessed by many users and should have fast response time.

18
 lOMoARcPSD|32413716

User interface:

The system user friendly. The developed system provide mobile based
application user interface and are compatible with browsers like internet
explorer, Mozilla Firefox, Google chrome.

Users can have access to the system from anywhere using their desktop or
mobile phones.

We should make the system simple and easy to understand and to interact with.

It should be easy and painless for the user to register and view information user can
understand the system either by English or Amharic (local) languages.

Resources:

The system is compatible with the specified hard ware and software
requirement and the system should have compatible with any environment.

The system is usable to anyone who have skill of English and Amharic language.
The capacity to retrieve data from the stored data base.

19
 lOMoARcPSD|32413716

Technical Requirements

A technical requirement pertains to the technical aspect that your system must
as performance related issue ,reliability issues, and availability issues, and many tech
nical requirements can actually be thought of as constraints, and in fact constraints
can apply to either technical or business issues. Some of the technical requirements of
the compliant management systems are :

Scalability:

The ability to add capacity (and users) to a deployed system over time.
Scalability typically involves adding resources to the system but should not require
changes to the deployment architecture.

Availability:

The system to be available 7 days a week and 24 hours a day. And A measure of how
often a system’s resources and services are accessible to end users, often expressed as
the uptime of a system.

Performance:

The systems have high performance and error free and the measurement of response
time and latency with respect to user load conditions.As the system is a mobile based
systemic can be accessed by many users simultaneously. So, the system should be
capable of handling as many users as possible while maintaining the performance of
the system.

20
 lOMoARcPSD|32413716

Security:-

A complex combination of factors that describe the integrity of a system and its users.

Security includes authentication and authorization of users as well as secures

compliant information.

The system shall ensue that data is protected from unauthorized access.

Any user who wants to login to the system must identify themselves using a login
name and password.

Only users who are authorized in this way may access protected data.

A user in any section will be given the right to access and/or modify the
data related to that section.

In addition, the system allows only one user to use a single user name at a time.

Generally, the system should be secure to a level that, even when it is available
online, critical information should not be available to non-authorized users.

Error Handling :

The system is expected to handle errors while input. The system validates data entry
for correctness.

Errors that occurred from the wrong doing of users will be handled by appropriate
exception handling mechanisms.

If an error occurs, for instance if required fields missed while the user submit
complaint using website, the system will identify the error and notify the user so
that he/she can take the appropriate corrections.

System Modifications

Over time the system can be enhanced with additional features like including
customer speech and image messages, therefore the application is designed in such a
way that whenever any change is initiated to easily incorporate with the system.

21
 lOMoARcPSD|32413716

Purpose of the system

The purpose of the Software Design Document is to provide a description of
the design of a Compliant Management System fully enough to allow for us
to proceed with an understanding of how this system is developed.

The Software Design Document provides information necessary to

provide description of the details for the software and system to be built.

Design Goal
The design goals represent the desired qualities of the system and provide a
consistent set of criteria that must be considered when making design decisions.

Design goals of the system are presented as follows

End user criteria:

This project is very simple to use. Anyone who can read English or Amharic
can use the system, because, to use the system only clicking a button, it does not need
to write commands and to think how to use it.

This program will have a well-defined and easily understood interface. The processes
will be easy to understand and use by a user of any level.

User Interface:

User interface of the system should be attractive and simple since the system
supports both Amharic and English languages so that the user of the system will
easily interact with the system.

No technical jargon is to be presented to the user at any time. The interface must
be designed taking into consideration those who do not work with computers on a
day-to-day basis.

Documentation:

A document which contains all features of the system should be provided for
the users of the system.

23
 lOMoARcPSD|32413716

CHAPTER 5

SYSTEM DESIGN

5.1 Introduction

The Design Phase seeks to develop detailed specifications that emphasize the
physical solution to the user's information technology needs.

The system requirements and logical description of the entities, relationships, and
attributes of the data that were documented during the Requirements Analysis Phase
are further refined and allocated into system and database design specifications that
are organized in a way suitable for implementation within the constraints of a
physical environment. (e.g., like computer, database, facilities etc).

A formal review of the high-level architectural design is conducted prior to detailed

design of the automated system/application to achieve confidence that the design
satisfies the system requirements, is in conformance with the enterprise architecture
and prescribed design standards.

To raise and resolve any critical technical and/or project-related issues, and to
identify and mitigate project, technical, security, and/or business risks affecting
continued detailed design and subsequent lifecycle activities.

During the Design Phase, the initial strategy for any necessary training is also begun.
Estimates of project expenses are updated to reflect actual costs and estimates for
future phases.

In addition, the work planned for future phases is redefined, if necessary, based on
information acquired during the Design Phase.

22
 lOMoARcPSD|32413716

Performance:

The system will complete the task quickly to allow easy input of data and to
retrieve data from the server.

The system will be accessible from any computer and will be accessible anytime a
user would want to use the program.

The system serves a number of users which are expected to access it concurrently.

Robustness :

The system should be designed in such a way that users cannot proceed having
entered invalid input or data in all cases of interacting with the system.

Availability:

The system should be available 24 hours a day to enable registering complaints

any time convenient for users of the system.

Security :

The system must prevent unauthorized users to access part of the system which is
restricted for authorized users.

Authorized users must be provided with user name and password.

It is designed to visit the system for new members when the system is open for guest.

The end user of the system most of the time will be asked for authorization login
except if the system developer has set its own criteria to access the system.

Modifiability :

Whenever any change needed to be made on the system it should be possible to easily
modify the system.

For this purpose, Object Oriented approach should be used so that modification to
some part of the system could not affect other parts.

24
 lOMoARcPSD|32413716

Portability:

The system should be designed in such a way that users can access the server
side being on various platforms like Android, Windows, UNIX or Macintosh using
common browsers.

5.4 Current software architecture

Since the current system is manual the complaint solution process is paper based
there is no any software architecture to support the system.

Proposed software architecture

The communication between the client and server is through Http protocol.

The second component of the system is a web server on which an application runs
and communicates with database to provide responses for the user.

The third component is mobile user which sends SMS message to the system.

The message sent to the system reaches the system through GSM
network.

The system accepts and sends SMS message through GSM mobile attached with the
computer or using GSM modem.There are three tier architecture for the system.

The presentation tier:

Clients directly interacted to provide GUI and allow the client gaining
access of the system.

Logical tier (middle tier) :

acts as bridge between client and server.

Data access tier :

supports data persistence mechanism and storage to the data.The following figure
shows the architecture of the system.

25
 lOMoARcPSD|32413716

CHAPTER 6

RESULTS AND DISCUSSIONS

This chapter provides me an opportunity to do self-introspection of what value I have

added to my knowledge and skill set and to the project.

Result (Conclusion)

What value I have added to my knowledge

Domain Experience

TCIL is working on various technologies. Also the individual responsibilities are more. So, I have

learnt a lot.

6.1. 2. Exposure to entirely different technology

Working on ASP.NET for the first time was a very enriching experience. I had never

worked on this platform earlier. So it added to my list of know how and the computer

languages known to me.

6.1. 3. Database Implementation

I had earlier made database but worked on SQL Server for the first time. I learnt

many new things about database creation, concept of stored procedure etc. We learn

26
 lOMoARcPSD|32413716

but here I got a chance to apply my knowledge practically and enhance it

also at the same time.

.4. Implementation of Business Logic Layer (BLL)

I have implemented the classes for BLL, which provides the interface

between UI Layer and Data Access Layer. This layer contains all the

business logic, i.e. Programming Methodology to implement the

functionality of the system.I had always read about N-Tier architecture but

this was again the first time I got to implement 3-Tier logical architecture.

So it was a very new and realistic experience.

6.1.5. Implementation of User Interface Layer (UI Layer)

I have also designed the UI layer that contains the web pages designed in

Jsp and Java Script. Also it contains the Code Behind pages to implement

the programming logic.

Future Scope

Completion of the development process will result in a software package that will

provide user-friendly environment, which is very easy to work with, even for people

with very little knowledge of computer.

27
 lOMoARcPSD|32413716

ANNEXURE

Screen Shots and Coding :

Design for Login Page

<%@ Master Language="C#" AutoEventWireup="true"

CodeFile="MasterPage.master.cs" Inherits="MasterPage" %>

<html>
<head>
<title>Customer Resource Management </title>
<link href="default.css" rel="stylesheet" type="text/css"
media="screen" />
</head>
28
 lOMoARcPSD|32413716

<body>
<form id="form1" runat="server">
<!-- start header -->
<div id="header">
<div id="logo">
<h1><a href="#">Customer <span> Resource</span>
Management </a></h1>
</div>
</div>
<div id="menu">
<ul id="main">
<asp:HyperLink ID="HyperLink1" runat="server"
NavigateUrl="~/frmlogin.aspx">Home</asp:HyperLink>
<asp:HyperLink ID="HyperLink2"
runat="server">About Us</asp:HyperLink>

</ul>
</div>

<!-- end header -->

<div id="wrapper">
<!-- start page -->
<div id="page">
<div id="sidebar1" class="sidebar">
<ul>
<li>
<h2>
<asp:Label ID="Label3"
runat="server" Text=""></asp:Label></h2>
</li>
<li>
<ul>
<asp:ContentPlaceHolder
ID="ContentPlaceHolder2" runat="server">
</asp:ContentPlaceHolder>
</ul>
</li>
<li>
<h2>SITE VISITED</h2>
</li>
<li>

<asp:ContentPlaceHolder
ID="ContentPlaceHolder3" runat="server">

29
 lOMoARcPSD|32413716

<table border="1" style="width:

236px">
<tr>
<td>
<asp:Label ID="Label1"
runat="server" style="font-size: x-large" Text="Label"
ForeColor="#EC7600"></
asp:Label>
</td>
</tr>
</table>
</asp:ContentPlaceHolder>

</li>

</ul>
</div>
<!-- start content -->
<div id="content">
<div class="post">

<h1 class="title"><a href="#">Welcome to

Complaint Board</a></h1>
<div class="entry">

<asp:ContentPlaceHolder
ID="ContentPlaceHolder1" runat="server">
</asp:ContentPlaceHolder>
</div>
</div>
</div><!-- end content -->
<!-- start sidebars -->
<div id="sidebar2" class="sidebar">
<ul>
<li>
<h2>Categories</h2>
</li>
<li>
<ul>
<asp:ContentPlaceHolder
ID="ContentPlaceHolder4" runat="server">
</asp:ContentPlaceHolder>
</ul>
30
 lOMoARcPSD|32413716

</li>
<li>
<h2>Current Users</h2>
</li>
<li>

<asp:ContentPlaceHolder
ID="ContentPlaceHolder5" runat="server">
<table border="1" style="width:
236px">
<tr>
<td>
<asp:Label ID="Label2"
runat="server" style="font-size: x-large" Text="Label"
ForeColor="#EC7600"></
asp:Label>
</td>
</tr>
</table>
</asp:ContentPlaceHolder>

</li>

</ul>
</div>
<!-- end sidebars -->
<!-- end sidebars -->
<div style="clear: both;">&nbsp;</div>
</div>
<!-- end page -->
&nbsp;</div>

<div id="footer">
<p class="copyright">&copy;&nbsp;&nbsp;2009 All
Rights Reserved &nbsp;&bull;&nbsp; Design by Vikrant
Sood.</p>
</div>
</form>
</body>
</html>

31
 lOMoARcPSD|32413716

Design for Admin Panel

Code :

<%@ Master Language="C#" AutoEventWireup="true"

CodeFile="MasterPage.master.cs"
Inherits="admin_MasterPage" %>

<html>
<head>
<meta http-equiv="content-type" content="text/html;
charset=utf-8" />
<title>Complaint Board</title>
<meta name="keywords" content="" />
<meta name="Cool Black" content="" />
<link href="../default.css" rel="stylesheet" type="text/
css" media="screen" />
<style type="text/css">
.style2
{
font-size: large;
}
32
 lOMoARcPSD|32413716

.style3
{
text-align: left;
}
.style4
{
width: 144%;
height: 30px;
border-style: solid;
border-width: 1px;
}
</style>
</head>
<body>
<form id="form1" runat="server">
<!-- start header -->
<div id="header">
<div id="logo" class="style3">
<h1><a href="#"><span>Complaint </span>Board</
a></h1>

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb
sp;&nbsp;<span
class="style2">Welcome:<asp:Label
ID="lbusrnam" runat="server" Text=""></asp:Label>

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb
sp;&nbsp;&nbsp;
<br />
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&nbsp;
</span>
<asp:LinkButton ID="lksgnout" runat="server"
Font-Underline="True"
CausesValidation="False"
onclick="lksgnout_Click1"
>Sign Out</asp:LinkButton>
</div>
</div>
<div id="menu">
33
 lOMoARcPSD|32413716

<ul id="main">
<asp:HyperLink ID="HyperLink1"
runat="server" NavigateUrl="~/admin/frmara.aspx">Home</
asp:HyperLink>
<asp:HyperLink ID="HyperLink2"
runat="server" >About Us</asp:HyperLink>

</ul>
</div>

<!-- end header -->

<div id="wrapper">
<!-- start page -->
<div id="page">
<div id="sidebar1" class="sidebar">
<ul>
<li>
<h2>NAVIGATIONS</h2>
</li>
<li>
<ul>
<asp:ContentPlaceHolder
ID="ContentPlaceHolder2" runat="server">
<P>
<table border="1" style="height:
353px" >
<tr>
<td valign="top" >
<asp:TreeView ID="TreeView1"
runat="server" DataSourceID="SiteMapDataSource1"
Height="195px"
Width="232px">
</asp:TreeView>
</td>
</tr>
</table>
</
P>
<P> <asp:SiteMapDataSource
ID="SiteMapDataSource1" runat="server" />
</P>
</asp:ContentPlaceHolder>
</ul>
</li>

34
 lOMoARcPSD|32413716

</ul>
</div>
<!-- start content -->
<div id="content">
<div class="post">
<h1 class="title"><a href="#">Welcome
Administrator</a></h1>
<br />
<div class="entry">
<asp:ContentPlaceHolder
ID="ContentPlaceHolder1" runat="server">
</asp:ContentPlaceHolder>
</div>
</div>
</div><!-- end content -->
<!-- start sidebars -->
<div id="sidebar2" class="sidebar">
<ul>
<li>
</li>
</ul>
</div>
<!-- end sidebars -->
<div style="clear: both;">&nbsp;</div>
</div>
<!-- end page -->
</div>
<div id="footer">
<p class="copyright">&copy;&nbsp;&nbsp;2009 All
Rights Reserved &nbsp;&bull;&nbsp; Design by Richa</a>.</
p>
</div>
</form>
</body>
</html>

35
 lOMoARcPSD|32413716

Design for Client Panel:

Code :

<%@ Master Language="C#" AutoEventWireup="true"

CodeFile="MasterPage.master.cs"
Inherits="client_MasterPage" %>

<html>
<head>
<title>Customer Resource Management </title>
<link href="../default.css" rel="stylesheet" type="text/
css" media="screen" />
<style type="text/css">
.style2
{
font-size: large;
}
.style3
{
width: 144%;
height: 31px;
36
 lOMoARcPSD|32413716

border-style: solid;
border-width: 1px;
}
</style>
</head>
<body>
<form id="form1" runat="server">
<!-- start header -->
<div id="header">
<div id="logo">
<h1><a href="#">Customer <span> Resource</span>
Management </a></h1>

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&nbsp;<span
class="style2">Welcome:<asp:Label
ID="lbusrnam" runat="server" Text=""></asp:Label>
</span>
<asp:LinkButton ID="lksgnout" runat="server"
Font-Underline="True" onclick="lksgnout_Click1"
>Sign Out</asp:LinkButton>
</div>
</div>
<div id="menu">
<ul id="main">
<li class="current_page_item">
<asp:HyperLink ID="HyperLink1"
runat="server"
NavigateUrl="~/client/
frmprf.aspx">Home</asp:HyperLink>
</li>
<asp:HyperLink ID="HyperLink2"
runat="server">About Us</asp:HyperLink>
</ul>
</div>

<!-- end header -->

<div id="wrapper">
<!-- start page -->
<div id="page">
<div id="sidebar1" class="sidebar">
<ul>
<li>
<h2>NAVIGATIONS</h2>
37
 lOMoARcPSD|32413716

</li>
<li>
<ul>
<asp:ContentPlaceHolder
ID="ContentPlaceHolder2" runat="server">
<P>
<table border="1" style="height:
353px" >
<tr>
<td valign="top" >
<asp:TreeView ID="TreeView1"
runat="server" DataSourceID="SiteMapDataSource1"
Height="195px"
Width="232px">
</asp:TreeView>
</td>
</tr>
</table>
</
P>
<P> <asp:SiteMapDataSource
ID="SiteMapDataSource1" runat="server"
SiteMapProvider="xyz"
/>
</P>
</asp:ContentPlaceHolder>
</ul>
</li>

</ul>
</div>
<!-- start content -->
<div id="content">
<div class="post">
<h1 class="title"><a href="#">Welcome
Client</a></h1>
<br />
<div class="entry">
<asp:ContentPlaceHolder
ID="ContentPlaceHolder1" runat="server">
<table class="style3">
<tr>
<td>
&nbsp;</td>
</tr>
38
 lOMoARcPSD|32413716

</table>
</asp:ContentPlaceHolder>
</div>
</div>
</div><!-- end content -->
<!-- start sidebars -->
<div id="sidebar2" class="sidebar">
<ul>
<li>
</li>
</ul>
</div>
<!-- end sidebars -->
<div style="clear: both;">&nbsp;</div>
</div>
<!-- end page -->
</div>
<div id="footer">
<p class="copyright">&copy;&nbsp;&nbsp;2009 All
Rights Reserved &nbsp;&bull;&nbsp; Design by Vikrant
Sood</p>
</div>
</form>
</body>
</html>

39
 lOMoARcPSD|32413716

Design For Employee Panel

Code :

<%@ Master Language="C#" AutoEventWireup="true"

CodeFile="MasterPage.master.cs" Inherits="emp_MasterPage"
%>

<html>
<head>
<meta http-equiv="content-type" content="text/html;
charset=utf-8" />
<title>Customer Resource Management </title>
<link href="../default.css" rel="stylesheet" type="text/
css" media="screen" />
<style type="text/css">
.style2
{
font-size: large;
}
.style3
{
40
 lOMoARcPSD|32413716

width: 144%;
height: 31px;
border-style: solid;
border-width: 1px;
}
</style>
</head>
<body>
<form id="form1" runat="server">
<!-- start header -->
<div id="header">
<div id="logo">
<h1><a href="#">Customer <span> Resource</span>
Management </a></h1>

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&nbsp;<span
class="style2">Welcome:<asp:Label
ID="lbusrnam" runat="server" Text=""></asp:Label>
</span>
<asp:LinkButton ID="lksgnout" runat="server"
Font-Underline="True" onclick="lksgnout_Click1"
>Sign Out</asp:LinkButton>
</div>
</div>
<div id="menu">
<ul id="main">
<li class="current_page_item">
<asp:HyperLink ID="HyperLink1"
runat="server" NavigateUrl="~/emp/frmprf.aspx">Home</
asp:HyperLink>
</li>
<asp:HyperLink ID="HyperLink2"
runat="server">About Us</asp:HyperLink>
</ul>
</div>

<!-- end header -->

<div id="wrapper">
<!-- start page -->
<div id="page">
<div id="sidebar1" class="sidebar">
<ul>
<li>
41
 lOMoARcPSD|32413716

<h2>NAVIGATIONS</h2>
</li>
<li>
<ul>
<asp:ContentPlaceHolder
ID="ContentPlaceHolder2" runat="server">
<P>
<table border="1" style="height:
353px" >
<tr>
<td valign="top" >
<asp:TreeView ID="TreeView1"
runat="server" DataSourceID="SiteMapDataSource1"
Height="195px"
Width="232px">
</asp:TreeView>
</td>
</tr>
</table>
</
P>
<P> <asp:SiteMapDataSource
ID="SiteMapDataSource1" runat="server"
SiteMapProvider="pqr"
/>
</P>
</asp:ContentPlaceHolder>
</ul>
</li>

</ul>
</div>
<!-- start content -->
<div id="content">
<div class="post">
<h1 class="title"><a href="#">Welcome
Employeee</a></h1>
<br />
<div class="entry">
<asp:ContentPlaceHolder
ID="ContentPlaceHolder1" runat="server">
<table class="style3">
<tr>
<td>
&nbsp;</td>
42
 lOMoARcPSD|32413716

</tr>
</table>
</asp:ContentPlaceHolder>
</div>
</div>
</div><!-- end content -->
<!-- start sidebars -->
<div id="sidebar2" class="sidebar">
<ul>
<li>
</li>
</ul>
</div>
<!-- end sidebars -->
<div style="clear: both;">&nbsp;</div>
</div>
<!-- end page -->
</div>
<div id="footer">
<p class="copyright">©&nbsp;&nbsp;2009 All Rights
Reserved &nbsp;•&nbsp; Design by Vikrant Sood</p>
</div>
</form>
</body>
</html>

43
 lOMoARcPSD|32413716

Interface:
public interface intcontyp
{
Int32 contypcod
{
get;
set;
}
String contypnam
{
get;
set;
}
}

Property Class

public class clscontypprp : intcontyp

{
private Int32 prvcontypcod;
private String prvcontypnam;
#region intcontyp Members

public int contypcod

{
ge
t
{ return prvcontypcod;

}
se
t prvcontypcod = value;
{

}
}

public string contypnam

{
ge {
t
{

}
se
t
 lOMoARcPSD|32413716

return
prvcontypnam;

44
 lOMoARcPSD|32413716

prvcontypnam = value;
}
}

#endregion
}

Connection Class:

public abstract class clscon

{
protected SqlConnection con = new
SqlConnection();
public clscon()
{
con.ConnectionString =
ConfigurationManager.ConnectionStrings["cn"].ConnectionSt
ring;
}
}
Main Class:

public class clscontyp : clscon

{
public void save_rec(clscontypprp p)
{
if (con.State == ConnectionState.Closed)
{
con.Open();
}

SqlCommand cmd = new SqlCommand("inscontyp",

con);
cmd.CommandType =
CommandType.StoredProcedure;
cmd.Parameters.Add("@contypnam",
SqlDbType.VarChar, 50).Value = p.contypnam;
cmd.ExecuteNonQuery();
cmd.Dispose();
con.Close();
}
public void update_rec(clscontypprp p)
{
if (con.State == ConnectionState.Closed)
{

45
 lOMoARcPSD|32413716

con.Open();
}

SqlCommand cmd = new SqlCommand("updcontyp",

con);
cmd.CommandType =
CommandType.StoredProcedure;
cmd.Parameters.Add("@contypcod",
SqlDbType.Int).Value = p.contypcod;
cmd.Parameters.Add("@contypnam",
SqlDbType.VarChar, 50).Value = p.contypnam;
cmd.ExecuteNonQuery();
cmd.Dispose();
con.Close();
}
public void delete_rec(clscontypprp p)
{
if (con.State == ConnectionState.Closed)
{
con.Open();
}

SqlCommand cmd = new SqlCommand("delcontyp",

con);
cmd.CommandType =
CommandType.StoredProcedure;
cmd.Parameters.Add("@contypcod",
SqlDbType.Int).Value = p.contypcod;
cmd.ExecuteNonQuery();
cmd.Dispose();
con.Close();
}
public List<clscontypprp> disp_rec()
{
if (con.State == ConnectionState.Closed)
{
con.Open();
}
SqlCommand cmd = new SqlCommand("dspcontyp",
con);
cmd.CommandType =
CommandType.StoredProcedure;
SqlDataReader dr = cmd.ExecuteReader();
List<clscontypprp> obj = new
List<clscontypprp>();
46
 lOMoARcPSD|32413716

while (dr.Read())
{
clscontypprp k = new clscontypprp();
k.contypcod = Convert.ToInt32(dr[0]);
k.contypnam = dr[1].ToString();
obj.Add(k);
}
dr.Close();
cmd.Dispose();
con.Close();
return obj;

public List<clscontypprp> find_rec(Int32

contypcod)
{
if (con.State == ConnectionState.Closed)
{
con.Open();
}
SqlCommand cmd = new SqlCommand("fndcontyp",
con);
cmd.CommandType =
CommandType.StoredProcedure;
cmd.Parameters.Add("@contypcod",
SqlDbType.Int).Value = contypcod;
SqlDataReader dr = cmd.ExecuteReader();
List<clscontypprp> obj = new
List<clscontypprp>();
if (dr.HasRows)
{
dr.Read();
clscontypprp k = new clscontypprp();
k.contypcod = Convert.ToInt32(dr[0]);
k.contypnam = dr[1].ToString();
obj.Add(k);
}
dr.Close();
cmd.Dispose();
con.Close();
return obj;

}
}
47
 lOMoARcPSD|32413716

REFERENCES
1. www.w3schools.com/html/

2. online MSDN

3. www.codeproject.com

4. www.csharpfriend.com

5. www.dotnetspinder.com

6. www.gotdotnet.com

7. HTML Styles CSS (w3schools.com)

8. JavaScript Tutorial (w3schools.com)

9. Apps Script samples overview | Google Developers HTML Color Codes

48