CHAPTER 1

INTRODUCTION
1.1 ABOUT THE ORGANIZATION
We are a boutique IT service provider specializing in design, development &
implementation of complex Enterprise solutions using 100% offshore model.Since our
incorporation in 2004, we have delivered hundreds of projects using this model to USA,
UK, Australia and Indian clients. We believe in building lasting relationship by
consistently delivering business enablers with innovative and state of the art solutions
using a cost-effective model with a clear understanding about the business objectives.
We have established ourselves as reliable and dependable partners winning the trust of
our clients with many of them giving us repeat business and have matured as long term
ongoing Relationships.
We have consistently and successfully designed and delivered 100s of projects at
premium rates. And the reason is simple. We match the productivity, domain expertise
and quality of work, of consultants who bill you USD 100 to USD 200 per hour.Our
ability to apply design thinking, even for small projects, the domain understanding and
technical depth that we bring to each engagement, the rigor with which we estimate time
lines while making promises, the discipline with which we go all out to meet those
milestones, have ensured tremendous success rate in our projects.
When you go through our sample case studies, success stories and artifacts of
delivery, you will see that our credibility is built on hard data, not hollow sales talk.
How can we help?
With manual testing, an actual user tests the system after reading through your
requirements. The benefit of this flavor of testing in QA is that it allows them to find
minor nuances that don’t follow UI standards and don’t match with your software goals.
Our team handles the entire System Testing life cycle of
o Requirements understanding
o Preparing system test plans
o Preparing system test cases
o Setting up system test environment
o Performing system testing
o Error reporting

1
 o Consolidating system test results
In a number of cases, our customers have re-used our System test cases for their
Acceptance testing. Steadfast has also provided this service as an independent system
testing team for our customers who have their in-house development teams.
Testing process we follow
1. Perform end to end System testing
2. Log each issue raised and keep track until closed
3. Prepare system summary report at the end of each release
4. Active participation in the client calls from the requirement phase as to avoid the
requirement gap
5. Active participation in design discussions, offering the input we receive from
customers
6. We are a customer-facing unit, and we hear from our customers about issues they
experience and what features they would like to see in our product
7. Provide demos to the Customer
8. Ensure we cover all the scenarios: Functional, Negative, Boundary Vales and
Exceptions Error handling
9. The customers re-use our System test cases for their User Acceptance Testing
(UAT)
10. The test materials are consistent with any erratum and are updated as needed to
reflect the current versions and status of the specification
11. Preparation of user guide and installation document
Other testing services
1. Our team is very capable of managing (preparing, maintaining, releasing) review
checklists for the different SDLC phases such as
2. Steadfast has also provided this service as an independent system testing team for
our customers who have their in-house development teams.
o Capturing Requirements
o Design review
o Code review
o System Testing
3. Provide Quality Check on marketing emails

2
1.2 OVERVIEW OF THE PROJECT
The main purpose of the project is to help the public who are facing different
problems in the localities by this online application. This project is having that potential
to reduce the gap between people and Govt. It can control unethical work of bribe and
even it can reduce the processing time. In this project identification and solution for the
complaints given by the people, rectifying them within the system generated time limit is
the main concept of the project. A clear report is generated by the system which shows
assignee name, complaint type/department, etc. All the above attributes help while
viewing the report of complaints. The admin examines weather the problem is rectified
or not within the grace period. If it is not solved, then the report is automatically
forwarded to the higher authorities so that it maintains an effective problem solving
solution. The main objective of this project is to make easy the process of complaint
reporting with very simplified and effective way .This project involves major problem
solving modules where these acts as best solution for incoming bulk complaints. For
every submission of complaint the user gets complaint acknowledgement. All these type
of acknowledgement is generated by the computer; the solution of time may differ from
the type of the complaint and category. To make any complaint, it is made mandatory for
the user to mention his contact details, so that it does not receive any anonymous
complaint details.

3
 CHAPTER 2
SYSTEM STUDY AND ANALYSIS
2.1 INTRODUCTION
This project mainly focuses on sanitation and development of a municipal
corporation. To make it possible, the people who belong to the municipal corporation are
provided with an opportunity of raising a complaint regarding any issue that take place in
their locality. To raise the complaints through Electronic Complaint Management System
(ECMS) for Municipal Corporation regarding the above categories, a simplified solution
is designed where the different type of complaints made by people are integrated.
2.2 PROBLEM DEFINITION
The issues are garbage management, water supply, electricity management, road
repairs or layering of roads and threatening of animals.
2.3 EXISTING SYSTEM
One must visit the office and complaints given through written statement. Based on
the priority, the complaint can be submitted in drop box or directly to the commissioner
or the concerned department, which may take physical effort and time consuming task.
In this existing system, one cannot get any acknowledgement that the complaint has been
received. Guarantee for problem solution is given through verbal communication. Hence,
it is not meant for problem solution.
2.3.1 Demerits of Existing System
 The main disadvantage of existing system is book keeping for all the complaints
given by the customers.
 It is paper consuming task.
 There is no complaint acknowledgement given for the user, which is used for
future references.
 People don’t get time period for problem recovery.

4
2.4 PROPOSED SYSTEM
The main purpose of the project is to help the public who are facing different
problems in the localities by this online application. This project is having that potential
to reduce the gap between people and Govt. It can control unethical work of bribe and
even it can reduce the processing time. In this project identification and solution for the
complaints given by the people, rectifying them within the system generated time limit is
the main concept of the project. A clear report is generated by the system which shows
assignee name, complaint type/ department, etc. All the above attributes help while
viewing the report of complaints. The admin examines weather the problem is rectified
or not within the grace period. If it is not solved, then the report is automatically
forwarded to the higher authorities so that it maintains an effective problem solving
solution. The main objective of this project is to make easy the process of complaint
reporting with very simplified and effective way.
2.4.1 Merits of Proposed System
This project involves major problem solving modules where these acts as best
solution for incoming bulk complaints.
 Every submission of complaint, the user gets complaint acknowledgement
 All these type of acknowledgement is generated by the computer; the solution of
time may differ from the type of the complaint and category.
 To make any complaint, it is made mandatory for the user to mention his contact
details, so that it does not receive any anonymous complaint details.

2.5 MODULES DESCRIPTION

2.5.1 Admin Module
This module provides administrator related functionalities. Administrator can
create a new account either for municipal officers or operators. By using this login id
both Municipal officers and operators will log on to this portal and do all transactions
which are assigned to them.
2.5.2 Employee Module
This module is about an operator of Municipal Corporation. By using this module
operators of Municipal Corporation can view all the complaints from different users on
different problems. Operator can maintain solved problems list and pending problems
list.

5
2.5.3 User Module
This module is about users of this portal. By using this module user can lodge any
complaint to either operators or to municipal officer about problems such as water
problem, electricity problem and sewerage problem. User must be registered with the
system. A user can check the complaint status. A user must send feedback after the
petition complaint solved by same user login.
2.5.4 E-Mail Generation System
E-mail generation system will generate e-mail when a complaint is registered, When
a department receive a particular complaint request, If any complaint is not followed up
between specific period.

2.6 SYSTEM REQUIREMENTS SPECIFICATION

2.6.1 Software Requirements Specification

Operating System : Windows 7

Front End : Asp.Net(C#)
Back End : SQL server
IDE : Visual Studio 2010

2.6.2 Hardware Requirements Specification

Processor : Intel(R) Pentium(R) CPU A1018 @ 2.10 GHz 2.10 GHz

Hard disk : 160 GB

RAM : 4 GB

2.7 FEASIBILITY STUDY

The feasibility of the project is analyzed in this phase and business proposal is put
forth with a very general plan for the project and some cost estimates. During system
analysis the feasibility study of the proposed system is to be carried out. This is to
ensure that the proposed system is not a burden to the company. For feasibility
analysis, some understanding of the major requirements for the system is essential.
Three key considerations involved in the feasibility analysis are

 Economical feasibility

6
  Technical feasibility
 Social feasibility
2.7.1 ECONOMICAL FEASIBILITY:

This study is carried out to check the economic impact that the system will have
on the organization. The amount of fund that the company can pour into the research and
development of the system is limited. The expenditures must be justified. Thus the
developed system as well within the budget and this was achieved because most of the
technologies used are freely available. Only the customized products had to be
purchased.

2.7.2 TECHNICAL FEASIBILITY:

This study is carried out to check the technical feasibility, that is, the technical
requirements of the system. Any system developed must not have a high demand on the
available technical resources. This will lead to high demands on the available technical
resources. This will lead to high demands being placed on the client. The developed
system must have a modest requirement, as only minimal or null changes are required for
implementing this system.

2.7.3 SOCIAL FEASIBILITY:

The aspect of study is to check the level of acceptance of the system by the user. This
includes the process of training the user to use the system efficiently. The user must not
feel threatened by the system, instead must accept it as a necessity. The level of
acceptance by the users solely depends on the methods that are employed to educate the
user about the system and to make him familiar with it. His level of confidence must be
raised so that he is also able to make some constructive criticism, which is welcomed, as
he is the final user of the system.

7
 CHAPTER 3

SYSTEM ARCHITECTURE AND DESIGN

3.1 INTRODUCTION
System design is the process of defining the architechture, components, modules,
interfaces and data for a system to statisfy specified requirements.System design could
be seen as the application of system theory to product development.There is some
overlap with the disciplines of system analysis and design architechture.

3.2ARCHITECTURE DESIGN

Figure 3.2

8
 3.3 DATA FLOW DIAGRAM
Level 0

Applicant details

Complaint details &complaint

management
Status system

Administrator

Applicant details

Figure 3.3.1
Level 1
Applicant deatils
Complaint
registration

Applicant Complaint reg

Applicant Id Complaint Status

status
Status Admin

Search Status
Administrator

Applicant
Officer
Status
Login
Username &password Complaint detail

Officer detail Officer reg

Administrator

Figure 3.3.2

9
Level 2

Applicant category Category Applicant category

Applicant Admin

Status Status
Name
Applicant Name

Figure 3.3.3
Level 3

Login
Administrator Authentication process

Valid officer Officer reg

Other information Officer officer information

creation
process

Authorized other

Officer account
Officer Uploaded information
modification
process

Figure 3.3.4

10
3.4 UML DIAGRAMS
A UML diagram is a diagram based on the UML (Unified Modeling Language)
with the purpose of visually representing a system along with its main actors, roles,
actions, artifacts or classes, in order to better understand, alter, maintain, or document
information about the system.
3.4.1 Use Case Diagram
A use case diagram is a graphic depiction of the interaction among the elements of a
system .A Use case diagram is methodology used in system analysis to identify ,clarify,
and organize system requirements .the actor, usually individuals involved with system
defined according to their roles.

login

complaint register

View complaint
user Department

Solve complaint

Accept complaint

Admin

Update status

Take action

FIGURE 3.4.1

11
3.4.2 Class Diagram
Class diagram is the type of static structure diagram that describe the structure of a
system by showing the systems classes, their attributes operations or methods under
relationship among the objects.

FIGURE 3.4.2

12
3.4.3 SEQUENCE DIAGRAM
A sequence diagram shows the object interaction arranged in time sequence. It
depicts the object and classes involved in the scenario and the sequence of message
exchanged between the object needed to carry out the functionally of the scenario.
Sequence diagram sometimes called the Event Diagram or Event Scenario.

Admin User Login Complaint

Check Authentication

Login

Files the complaint

Complaint register successfully

Monitor Complaints and Take steps to solve complaints

FIGURE 3.4.3

13
3.4.4 COLLOBORATION DIAGRAM
Collaboration diagrams convey the same information as sequence diagrams, but focus
on object roles instead of the times that messages are sent. In a sequence diagram, object
roles are the vertices and messages are the connecting links.

1: Check Authentication
Admin user

5: Monitor Complaints and Take steps to solve complaints

4: Complaint register successfully

2: Login

3: Files the complaint

Login
Complaint

FIGURE 3.4.4

14
3.4.5ACTIVITYDIAGRAM

An activity diagram visually presents a series of actions or flow of control in a

system similar to a flowchart or a data flow diagram.Activity diagrams are often used
in business process modeling. They can also describe the steps in a use
case diagram.Activitiesmodeled can be sequential and concurrent.

Login

User files a
complaint
Admin checks for any
complaints

No

Take action to solve the

complaints

FIGURE 3.4.5

15
3.5 TABLE DESIGN
3.5.1 Login Table

Field name Data type Constraints Description

User id Varchar(50) Not null User identification

Password Varchar(10) Not null Password

Name Varchar(50) Not null Officer Name

Phone Varchar(10) Not null Officer phone no

Category Text Not null Officer category

Department Text Not null Officer

Department

3.5.2 Admin Table:

Field Name Data type Constraints Description

Com id Numeric(18,0) Foreign key User identification

Status Text Not null Status

16
3.5.3 Complaint Registration table

Field name Data type Constraints Description

Com id Numeric(18,0) Primary key Complaint id

Name Varchar(20) Not null Complaint person

name
Address Varchar(50) Not null Person address

Phone Varchar(10) Not null Person contact

number
Email Varchar(50) Not null Person email

Ele no Varchar(10) Not null Election card number

Category Varchar(15) Not null Problem type

Ward Varchar(15) Not null Area of city

Date Date time Not null Date

Subject Varchar(50) Not null Detail of problem

17
 CHAPTER 4

TECHNICAL BACKGROUND

4.1 VISUAL STUDIO DOTNET

C# is an elegant and type-safe object-oriented language that enables developers to
build a variety of secure and robust applications that run on the.NET Framework. You
can use C# to create Windows client applications, XML Web services, distributed
components, client-server applications, database applications, and much, much more.
Visual C# provides an advanced code editor, convenient user interface designers,
integrated debugger, and many other tools to make it easier to develop applications based
on the C# language and the.NET Framework. The Visual C# documentation assumes
that you have an understanding of basic programming concepts. If you area complete
beginner, you might want to explore Visual C# Express, which is available on the Web.
You can also take advantage of books and Web resources about C# to learn practical
programming skills. C# syntax is highly expressive, yet it is also simple and easy to
learn. The curly-brace syntax of C# will be instantly recognizable to anyone familiar
with C, C++ or Java. Developers who know any of these languages are typically able to
begin to work productively in C# within a very short time. C# syntax simplifies many of
the complexities of C++ and provides powerful features such as null able value types,
enumerations, delegates, lambda expressions and direct memory access, which are not
found in Java. C# supports generic methods and types, which provide increased type
safety and performance, and iterates, which enable implementers of collection classes to
define custom iteration behaviors that are simple to use by client code. Language-

18
Integrated Query (LINQ) expressions make the strongly-typed query a first-class
language construct. As an object-oriented language, C# supports the concepts of
encapsulation, inheritance, and polymorphism. All variables and methods, including the
Main method, the application's entry point, are encapsulated within class definitions. A
class may inherit directly from one parent class, but it may implement any number of
interfaces. Methods that override virtual methods in a parent class require the override
keyword as a way to avoid accidental redefinition. In C#, a struck is like a lightweight
class; it is a stack-allocated type that can implement interfaces but does not support
inheritance. In addition to these basic object-oriented principles, C# makes it easy to
develop software components through several innovative language constructs, including
the following: Encapsulated method signatures called delegates, which enable type-safe
event notifications. Properties, which serves accesses for private member variables.
Attributes, which provide declarative metadata about types at run time. Inline XML
documentation comments. Language-Integrated Query (LINQ) which provides built-in
query capabilities across a variety of data sources. If you have to interact with other
Windows software such as COM objects or native Win32 DLLs, you can do this in C#
through a process called "Interop". Interop enables C# programs to do almost anything
that a native C++ application can do. C# even supports pointers and the concept of
"unsafe" code for those cases in which direct .NET Framework Platform Architecture
memory access is absolutely critical. The C# build process is simple compared to C and
C++ and more flexible than in Java. There are no separate header files, and no
requirement that methods and types be declared in a particular order. A C# source file
may define any number of classes, structs, interfaces, and events. The following are
additional C# resources: For a good general introduction to the language, see Chapter 1
of the C# Language Specification. For detailed information about specific aspects of the
C# language, seethe C# Reference. For more information about LINQ, seal INQ
(Language-Integrated Query). C# programs run on the.NET Framework, an integral
component of Windows that includes a virtual execution system called the common
language runtime (CLR) and a unified set of class libraries. The CLR is the commercial
implementation by Microsoft of the common language infrastructure (CLI), an
international standard that is the basis for creating execution and development
environments in which languages and libraries work together seamlessly. Source code
written in C# is compiled into an intermediate language (IL) that conforms to the CLI
specification. Their code and resources, such as bitmaps and strings, restored on disk in
19
an executable file called an assembly, typically with an extension of .exe or .dll. An
assembly contains a manifest that provides information about the assembly's types,
version, culture, and security requirements. When the C# program is executed, the
assembly is loaded into the CLR, which might take various actions based on the
information in the manifest. Then, if the security requirements are met, the CLR
performs just in time (JIT) compilation to convert the IL code to native machine
instructions. The CLR also provides other services related to automatic garbage
collection, exception handling, and resource management. Code that is executed by the
CLR is sometimes referred to as "managed code," in contrast to "unmanaged code"
which is compiled into native machine language that targets a specific system. The
following diagram illustrates the compile-time and run-time relationships of C# source
code files, the.NET Framework class libraries, assemblies, and the CLR. Language
interoperability is a key feature of the.NET Framework. Because the IL code produced
by the C# compiler conforms to the Common Type Specification (CTS), IL code
generated from C# can interact with code that was generated from the.NET versions of
Visual Basic, Visual C++, or any of more than 20 other CTS compliant languages. A
single assembly may contain multiple modules written in different .NET languages, and
the See also types can reference each other just as if they were written in the same
language.
4.2 BACK END (SQL)
SQL is a language to operate databases; it includes database creation, deletion,
fetching rows, modifying rows, etc. SQL is an ANSI (American National Standards
Institute) standard language, but there are many different versions of the SQL language.
What is SQL?
SQL is Structured Query Language, which is a computer language for storing,
manipulating and retrieving data stored in a relational database.
SQL is the standard language for Relational Database System. All the Relational
Database Management Systems (RDMS) like MySQL, MS Access, Oracle, Sybase,
Informix, Postgres and SQL Server use SQL as their standard database language.
Also, they are using different dialects, such as −
 MS SQL Server using T-SQL,
 Oracle using PL/SQL,
 MS Access version of SQL is called JET SQL (native format) etc.
Why SQL?SQL is widely popular because it offers the following advantages :
20
  Allows users to access data in the relational database management systems.
 Allows users to describe the data.
 Allows users to define the data in a database and manipulate that data.
 Allows embedding within other languages using SQL modules, libraries & pre-
compilers.
 Allows users to create and drop databases and tables.
 Allows users to create view, stored procedure, functions in a database.

CHAPTER 5
SYSTEM IMPLEMENTATION AND CODING
5.1 SAMPLE CODING
using System;
using System.Collections.Generic;
using System.ComponentModel;
using System.Data;
using System.Drawing;
using System.Linq;
using System.Text;
using System.Data.SqlClient;
using System.Windows.Forms;

namespace WindowsFormsApplication15
{

publicpartialclassForm1 : Form
{
SqlCommand cmd;
SqlConnection con;
string ps;
int us;
SqlDataReader rd;
string us1, st, ty;
publicstring cs = @"Data Source=.\SQLEXPRESS;AttachDbFilename=E:\2019-
project\aamac\municiple\WindowsFormsApplication15\Database1.mdf;Integrated
Security=True;User Instance=True";
public Form1()
{
InitializeComponent();
}

privatevoid Form1_Load(object sender, EventArgs e)

{

21
 textBox1.Text = "USER ID";
textBox1.ForeColor = System.Drawing.Color.DimGray;

textBox2.Text = "PASSWORD";
textBox2.ForeColor = System.Drawing.Color.DimGray;
con = newSqlConnection(cs);
con.Open();
}

privatevoid textBox1_Click(object sender, EventArgs e)

{
// textBox1.Text = "";
//textBox1.ForeColor = System.Drawing.Color.Black;

privatevoid textBox2_Click(object sender, EventArgs e)

{
// textBox2.Text = "";

// textBox2.ForeColor = System.Drawing.Color.Black;
}

privatevoid textbox2_Enter(object sender, EventArgs e)

{
// textBox2.Text = "";
}

privatevoid textBox1_TextChanged(object sender, EventArgs e)

{
}

privatevoid textBox2_Enter_1(object sender, EventArgs e)

{
textBox2.Text = "";

textBox2.ForeColor = System.Drawing.Color.Black;

privatevoid textBox1_Enter(object sender, EventArgs e)

{

textBox1.Text = "";

textBox1.ForeColor = System.Drawing.Color.Black;
}

privatevoid button1_Click(object sender, EventArgs e)

22
 {
cmd = newSqlCommand("select pass,st,type from tt1 where usid='" +
textBox1.Text + "'", con);
rd = cmd.ExecuteReader();
while (rd.Read())
{
ps = rd.GetString(0);
st = rd.GetString(1);
ty = rd.GetString(2);

}
rd.Close();

if (textBox2.Text == ps && ty == "CLIENT")

{
this.Hide();
Form4 F4 = newForm4(textBox1.Text);
F4.Show();
}
elseif(textBox2.Text == ps && ty=="ADMIN"&& st=="LEVEL1")
{
this.Hide();
Form5 F4 = newForm5();
F4.Show();
}

elseif (textBox2.Text == ps && ty == "ADMIN"&& st == "LEVEL2")

{
this.Hide();
Form6 F4 = newForm6();
F4.Show();
}

elseif (textBox2.Text == ps && ty == "ADMIN"&& st == "LEVEL3")

{
this.Hide();
Form7 F4 = newForm7();
F4.Show();
}
else
{
MessageBox.Show("wrong id or password");
}
}

privatevoid button2_Click(object sender, EventArgs e)

{
this.Hide();
Form2 F2 = newForm2();
F2.Show();

23
 }

privatevoid button3_Click(object sender, EventArgs e)

{
this.Hide();
Form3 F3 = newForm3();
F3.Show();
}

privatevoid panel1_Paint(object sender, PaintEventArgs e)

{

}
}

using System;
using System.Collections.Generic;
using System.ComponentModel;
using System.Data;
using System.Drawing;
using System.Linq;
using System.Text;
using System.Windows.Forms;
using System.Data.SqlClient;

namespace WindowsFormsApplication15
{
publicpartialclassForm2 : Form
{
SqlCommand cmd;
SqlConnection con;
SqlDataReader rd;
int us1, a;
public Form2()
{
InitializeComponent();
}

privatevoid Form2_Load(object sender, EventArgs e)

{
textBox1.Text = "USER NAME";
textBox1.ForeColor = System.Drawing.Color.DimGray;
textBox2.Text = "PASSWORD";
textBox2.ForeColor = System.Drawing.Color.DimGray;
textBox3.Text = "RE ENTER PASSWORD";

24
 textBox3.ForeColor = System.Drawing.Color.DimGray;
textBox4.Text = "E-MAIL ID";
textBox4.ForeColor = System.Drawing.Color.DimGray;
comboBox2.Hide();
Form1 f1=newForm1();
con = newSqlConnection(f1.cs);
con.Open();

privatevoid textBox1_Enter(object sender, EventArgs e)

{
textBox1.Text = "";
textBox1.ForeColor = System.Drawing.Color.Black;

privatevoid textBox2_Enter(object sender, EventArgs e)

{
textBox2.Text = "";
textBox2.ForeColor = System.Drawing.Color.Black;

privatevoid textBox3_Enter(object sender, EventArgs e)

{
textBox3.Text = "";
textBox3.ForeColor = System.Drawing.Color.Black;

privatevoid button1_Click(object sender, EventArgs e)

{
string a = "";
if (comboBox1.Text == "ADMIN")
{
if (textBox2.Text == textBox3.Text)
{
cmd = newSqlCommand("insert into tt1(usnam,pass,type,st,mai) values('" +
textBox1.Text + "','" + textBox2.Text + "','" + comboBox1.Text + "','" +
comboBox2.Text + "','" + textBox4.Text + "')", con);
cmd.ExecuteNonQuery();
cmd = newSqlCommand("select usid from tt1 where usnam='" +
textBox1.Text + "' and pass='" + textBox2.Text + "'", con);
rd = cmd.ExecuteReader();
while (rd.Read())
{

MessageBox.Show("YOUR ID ", rd.GetInt32(0).ToString());

}

25
 rd.Close();
}
else
{
MessageBox.Show("WRONG PASSWORD");
}
}
else
{

if (textBox2.Text == textBox3.Text)
{
cmd = newSqlCommand("insert into tt1(usnam,pass,type,st,mai) values('" +
textBox1.Text + "','" + textBox2.Text + "','" + comboBox1.Text + "','" + a + "' ,'" +
textBox4.Text + "')", con);
cmd.ExecuteNonQuery();
cmd = newSqlCommand("select usid from tt1 where usnam='" +
textBox1.Text + "' and pass= '" + textBox2.Text + "'", con);
rd = cmd.ExecuteReader();
while (rd.Read())
{

MessageBox.Show("YOUR ID ", rd.GetInt32(0).ToString());

}
rd.Close();
}
else
{
MessageBox.Show("WRONG PASSWORD");
}
}
}

privatevoid comboBox1_TextChanged(object sender, EventArgs e)

{
if (comboBox1.Text == "ADMIN")
{
comboBox2.Show();
}
}

privatevoid textBox4_Enter(object sender, EventArgs e)

{
textBox4.Text = "";
textBox4.ForeColor = System.Drawing.Color.Black;

privatevoid button2_Click(object sender, EventArgs e)

{

26
this.Hide();
Form f1 = newForm1();
f1.Show();
}

}
}

using System;
using System.Collections.Generic;
using System.ComponentModel;
using System.Data;
using System.Drawing;
using System.Linq;
using System.Text;
using System.Windows.Forms;
using System.Data.SqlClient;
using System.Net.Mail;
using System.IO;
using System.Security.Cryptography;

namespace WindowsFormsApplication15
{
publicpartialclassForm4 : Form
{
SqlCommand cmd;
SqlConnection con;
SqlDataReader rd;
int i = 0;
string us1;
List<string> tr = newList<string>();
public Form4(string us)
{
InitializeComponent();
us1 = us;
}

privatevoid Form4_Load(object sender, EventArgs e)

{
Form1 f1 = newForm1();
con = newSqlConnection(f1.cs);
con.Open();
textBox1.Text = "YOUR COMPLAINT";
textBox1.ForeColor = System.Drawing.Color.DimGray;

27
 }

privatevoid textBox1_Enter(object sender, EventArgs e)

{
textBox1.Text = "";
textBox1.ForeColor = System.Drawing.Color.Black;

privatevoid button1_Click(object sender, EventArgs e)

{
string a="", b="0";
cmd = newSqlCommand("insert into
tt2(userid,complaint,datetimes,accept,temp)values('" + us1 + "','" + textBox1.Text + "','"
+ dateTimePicker1.Value + "','" + a + "','" + b + "')", con);
cmd.ExecuteNonQuery();
cmd = newSqlCommand("select mai from tt1 where st='LEVEL1'", con);
rd = cmd.ExecuteReader();
while (rd.Read())
{
tr.Add(rd.GetString(0));

}
rd.Close();

try
{
MailMessage mail = newMailMessage();
SmtpClient SmtpServer = newSmtpClient("smtp.gmail.com");

mail.From = newMailAddress("nandsrams18@gmail.com");
mail.To.Add(tr[0]);
mail.Subject = "Complaint Mail";
mail.Body = textBox1.Text;

SmtpServer.Port = 587;
SmtpServer.Credentials = new
System.Net.NetworkCredential("nandsrams18", "nandsrams1");
SmtpServer.EnableSsl = true;

SmtpServer.Send(mail);
MessageBox.Show("mail Send");
}
catch (Exception ex)
{
MessageBox.Show(ex.ToString());
}

28
 }

privatevoid textBox2_Enter(object sender, EventArgs e)

{

privatevoid button2_Click(object sender, EventArgs e)

{
this.Hide();
Form f1 = newForm1();
f1.Show();
}

privatevoid panel1_Paint(object sender, PaintEventArgs e)

{

privatevoid button3_Click(object sender, EventArgs e)

{
this.Hide();
Form8 f8 = newForm8();
f8.Show();
}

}
}

using System;
using System.Collections.Generic;
using System.ComponentModel;
using System.Data;
using System.Drawing;
using System.Linq;
using System.Text;
using System.Windows.Forms;
using System.Data.SqlClient;
using System.Net.Mail;
namespace WindowsFormsApplication15
{
publicpartialclassForm6 : Form
{
SqlCommand cmd;
SqlConnection con;
SqlDataReader rd;
SqlDataAdapter da;

29
int i = 0;
List<string> tr = newList<string>();

List<string> tr1 = newList<string>();

public Form6()
{
InitializeComponent();
}

privatevoid Form6_Load(object sender, EventArgs e)

{
// TODO: This line of code loads data into the 'database1DataSet5.tt2' table. You can
move, or remove it, as needed.
//this.tt2TableAdapter.Fill(this.database1DataSet5.tt2);
Form1 f1 = newForm1();
con = newSqlConnection(f1.cs);
con.Open();
// TODO: This line of code loads data into the 'database1DataSet2.t2' table. You can
move, or remove it, as needed.
//this.t2TableAdapter.Fill(this.database1DataSet2.t2);
cmd = newSqlCommand("select userid,complaint,datetimes from tt2 where
temp=1", con);
da = newSqlDataAdapter(cmd);
SqlCommandBuilder sBuilder = newSqlCommandBuilder(da);
DataSet sDs = newDataSet();
da.Fill(sDs, "tt2");

dataGridView1.DataSource = sDs.Tables["tt2"];
dataGridView1.ReadOnly = true;
}

privatevoid button1_Click(object sender, EventArgs e)

{
cmd = newSqlCommand("update tt2 set temp=2 where temp=1", con);
cmd.ExecuteNonQuery();
MessageBox.Show("DONE");
}

privatevoid button2_Click(object sender, EventArgs e)

{

cmd = newSqlCommand("select mai from tt1 where st='LEVEL3' ", con);

rd = cmd.ExecuteReader();
while (rd.Read())
{
tr.Add(rd.GetString(0));

}
rd.Close();

30
 cmd = newSqlCommand("select COMPLAINT from tt2 where temp=1 ", con);
rd = cmd.ExecuteReader();
while (rd.Read())
{
tr1.Add(rd.GetString(0));
i++;
}
rd.Close();
for (int a = 0; a < i; a++)
{
try
{
MailMessage mail = newMailMessage();
SmtpClient SmtpServer = newSmtpClient("smtp.gmail.com");

mail.From = newMailAddress("nandsrams18@gmail.com");
mail.To.Add(tr[0]);
mail.Subject = "Complaint Mail";
mail.Body = tr1[a];

SmtpServer.Port = 587;
SmtpServer.Credentials = new
System.Net.NetworkCredential("nandsrams18", "nandsrams1");
SmtpServer.EnableSsl = true;

SmtpServer.Send(mail);
MessageBox.Show("mail Send");
}
catch (Exception ex)
{
MessageBox.Show(ex.ToString());
}

}
cmd = newSqlCommand("update tt2 set temp=2 where temp=1", con);
cmd.ExecuteNonQuery();
this.Hide();
Form1 f1 = newForm1();
f1.Show();

}
}
}

31
5.2 SOFTWARE TESTING
The purpose of testing is to discover errors. Testing is the process of trying to
discover every conceivable fault or weakness in a work product. It provides a way to
check the functionality of components, sub assemblies, assemblies and/or a finished
product It is the process of exercising software with the intent of ensuring that the
Software system meets its requirements and user expectations and does not fail in an
unacceptable manner. There are various types of test. Each test type addresses a specific
testing requirement.

TYPES OF TESTS:
Testing is the process of trying to discover every conceivable fault or weakness in
a work product. The different type of testing are given below:

5.2.1 UNIT TESTING:

Unit testing involves the design of test cases that validate that the internal program
logic is functioning properly, and that program inputs produce valid outputs. All decision
branches and internal code flow should be validated. It is the testing of individual
software units of the application .it is done after the completion of an individual unit
before integration.

This is a structural testing, that relies on knowledge of its construction and is

invasive. Unit tests perform basic tests at component level and test a specific business
process, application, and/or system configuration. Unit tests ensure that each unique path
of a business process performs accurately to the documented specifications and contains
clearly defined inputs and expected results.

5.2.2 INTEGRATION TESTING:

32
 Integration tests are designed to test integrated software components to
determine if they actually run as one program. Testing is event driven and is more
concerned with the basic outcome of screens or fields. Integration tests demonstrate that
although the components were individually satisfaction, as shown by successfully unit
testing, the combination of components is correct and consistent. Integration testing is
specifically aimed at exposing the problems that arise from the combination of
components.

5.2.3 FUNCTIONAL TEST:

Functional tests provide systematic demonstrations that functions tested are
available as specified by the business and technical requirements, system documentation,
and user manuals.
Functional testing is centered on the following items:

Valid Input : identified classes of valid input must be accepted.

Invalid Input : identified classes of invalid input must be rejected.
Functions : identified functions must be exercised.
Output : identified classes of application outputs must be
exercised.
Systems/ Procedures: interfacing systems or procedures must be invoked.

Organization and preparation of functional tests is focused on requirements, key

functions, or special test cases. In addition, systematic coverage pertaining to identify
Business process flows; data fields, predefined processes, and successive processes must
be considered for testing. Before functional testing is complete, additional tests are
identified and the effective value of current tests is determined.

5.2.4 SYSTEM TEST:

System testing ensures that the entire integrated software system meets requirements.
It tests a configuration to ensure known and predictable results. An example of system
testing is the configuration oriented system integration test. System testing is based on
process descriptions and flows, emphasizing pre-driven process links and integration
points.

33
WHITE BOX TESTING:
White Box Testing is a testing in which in which the software tester has knowledge
of the inner workings, structure and language of the software, or at least its purpose. It is
purpose. It is used to test areas that cannot be reached from a black box level.
BLACK BOX TESTING:
Black Box Testing is testing the software without any knowledge of the inner workings,
structure or language of the module being tested. Black box tests, as most other kinds of
tests, must be written from a definitive source document, such as specification or
requirements document, such as specification or requirements document. It is a testing in
which the software under test is treated, as a black box .you cannot “see” into it. The test
provides inputs and responds to outputs without considering how the software works.

34
5.2 SAMPLE RESULT
Home page

Login page

35
Admin Page

New User page

36
Complaint registration page

37
Complaint Accept Page

View complaint status page

38
Registration priority page

39
 CHAPTER 6
CONCLUSION
In this model, it is explained about the working procedure of the system, the roles
involved in the system and the activities and responsibilities those users. This paper
presents the overview of the analysis and development of the complaint management
system of Municipal Corporation. There will be a remarkable result will be obtained by
the implementation of this project and also they help in encouraging the development of
this type of complaint management systems or more complex systems. Generally the
complaints and other types of feedback play an important role in the development of any
organization and to interact with the customers in a better way. This system can be taken
as initiation for the systems which will be developed on future and which are related to
complaint management systems.

40
 CHAPTER 7

FUTURE ENHANCEMENT
On introduction of the project will be able to given an opportunity to common man to
make his environment better than today.In this manner the common people to deliver his
complaint and problem no municipal authority as well as let the municipal authorities to
address the issue as soon as possible.If registration is done using Aadhar card then
registration can be done authentically and problems.Relating fake complaints can be
solved.

41
 REFERENCES

[1] Fornell C., & Westbrook A. Robert, “The Vicious Circle of Consumer Complaints”,
journal of Marketing, (summer)(1984), 68-78.

[2] Razali R., Abd Halim K.N., & Jusoff K., “Quality Improvement of services in
Unversiti Teknology Mara Pahang from a Management Perspective.” Management
Science & Engineering Vol.5, No.1, (2011), pp.71-80.

[3] Najar, A.S., Al-Sukhni, H.A., & Aghakhani, N., “The Application of Service-
oriented Architecture in Ecomplaint System.” Paper presented at (ICCSN ’10) the
Second International Conference on Communication software and Networks, (2010, 26-
28 Feb.@2010).

[4] Yi, Yooujae, “A Critical Review of Customer Satisfaction”. In Review of Markiting,

Valerie A, Zeithaml, ed. Chicago, American Marketing Association, (1990).

[5] ESRAA ABD EL-AZIZ ABD EL-SADEK AFIFY, “A model for Customer
Complaint Management system using SOA”, Management Information System
Department, Modern Academy for Computer Science & Management Technology,
CAIRO, EGYPT.

WEBSITE REFERANCE

1. http://www.ibimapublishing.com/journals/JMRCS/ 2012/624789/624789.pdf

2. http://www.indiaurbanportal.in/b1estpractices/best practices81/bestpractices810.pdf

3.http://www.freeproject.co.in/source/ComplaintManagement -
System.aspx?pf=Java&t=web

4. http://grietinfo.in/projects/main/mca2012/cd-1-3doc.pdf

5.http://www.techzoo.org/projects/online-complainmanagement-system-php-project.html

42