CONTENTS

1
 TABLE OF CONTENT

S.NO CONTENTS PAGE

NO
1. ABSTRACT 3
2. INTRODUCTION 5
3. SYSTEM REQUIREMENTS 7
4. ABOUT THE SOFTWARE 10
5. PROBLEM DEFINITION AND 22
PROPOSAL
6. SYSTEM DESIGN 27
7. IMPLEMENTATION 44
• SOURCE CODE
• SCREENSHOT
8. TESTING 71
9. CONCLUSION AND FUTURE 79
ENHANCEMENT
11. REFERANCES 81

2
ABSTRACT

3
 CHAPTER 1
ABSTRACT

This project is entitled as ”Students Grievance Redressal System”. This project about
online grievance reporting which is done in college level.

A grievance is a discontent which could arise at any level in any organization is an

academic institution, then this issue become more sensitive and important. The function of the
cell is to look into the complaints lodged by any student and judge its merits. It is also
empowered to look into matters of harassment.

Anyone with a genuine grievance may approach the department members in person or in
consultation with the officer in-charge ”Grievance Redressal Cell”. In case the person is
unwilling to appear in self, grievances may be dropped in writing at the suggestion box of the
grievance cell at administrative block. Grievance may also be sent through e-mail to the officer
in-charge of the cell.

4
INTRODUCTION

5
 CHAPTER 2
INTRODUCTION

2.1 ABOUT THE PROJECT

The project entitled “STUDENT GRIEVANCE REDRESSAL SYSTEM ” Having

realized the importance of Information Technology in improving operational efficiency, is to

maintain information to monitor and enhance the performance of the departments.

The primary purpose of “ONLINE INFORMATION CENTRE” is to develop and

maintain a community information network, which provides open and free access to online

information for the students. The hallmark of this community information network is the ability

of the general public to obtain information that may not have been previously, or easily,

accessible to them.

This pertains to maintenance of details of complaints received, action taken and status of

the complaints. Users with access to the Web can enter their complaints and find out the status of

its processing. Each complaints will be assigned a unique id for reference.

6
 SYSTEM
REQUIREMENT

7
 CHAPTER 3
SYSTEM REQUIREMENTS
3.1 HARDWARE REQUIREMENTS
• PROCESSOR : i3
• RAM : 2 GB
• HARD DISK : 250 GB
• MOUSE : LOGITECH SERIAL MOUSE
• KEYBOARD : STANDARD 104 ENHANCED KEYBOARD

3.2 SOFTWARE REQUIREMENTS

• OPERATING SYSTE : WINDOWS 7,8,10
• APPLICATION SERVER : IIS SERVER
• FRONT END : ASP.NET
• SCRIPTING LANGUAGE: JAVASCRIPT
• CODE BEHIND : C#
• SOFTWARE : MICROSOFT VISUALSTUDIO 2012
• DATABASE : SQL SERVER 2008
3.3 TECHNOLOGIES USED

3.3.1 ASP.NET

ASP is a technology that enables scripts in web pages to be executed by an Internet

server. ASP.NET is a web platform that provides all the services that you require to build

enterprise-class server-based web applications. ASP.NET is built on the .NET Framework, so all

.NET Framework features are available to ASP.NET applications. Your applications can be

written in any language that is compatible with the common language runtime (CLR), including

Visual Basic and C#.

8
 ASP.NET pages have the extension .aspx, and are normally written in VB (Visual Basic)

or C# (C sharp).When a browser requests an ASP.NET file, the ASP.NET engine reads the file,

compiles and executes the scripts in the file, and returns the result to the browser as plain HTML.

3.4 DATABASE

Database used for my project is SQL Server. Microsoft SQL Server is an application

used to create computer databases for the Microsoft Windows family of server operating

systems. Microsoft SQL Server provides an environment used to generate databases that can be

accessed from workstations, the Internet, or other media such as a personal digital assistant

(PDA).A database is one or more lists of values. A computer database is one whose values are

stored in a computer medium such as a hard disk. A desktop database is one that is used in one

computer. A client/server database is a database that is stored in one computer named a server

and other computers named clients connect to the server to access and use the database.

A client/server database is a database that is stored in one computer named a server and

other computers named clients connect to the server to access and use the database.

9
ABOUT THE
SOFTWARE

10
 CHAPTER 4
ABOUT THE SOFTWARE

4.1 INTRODUCTION TO VISUAL STUDIO 2010

Visual Studio is a complete set of development tools for building ASP.NET Web

applications, XML Web Services, desktop applications, and mobile applications. Visual Basic,

Visual C++, Visual C#, and Visual J# all use the same integrated development environment

(IDE), which allows them to share tools and facilitates in the creation of mixed-language

solutions. In addition, these languages leverage the functionality of the .NET Framework, which

provides access to key technologies that simplify the development of ASP Web applications and

XML Web Services.

VISUAL STUDIO HIGHLIGHTS:

• VISUAL STUDIO TOOLS FOR OFFICE:

Microsoft Visual Studio 2010 Tools for the Microsoft Office System can help you create

solutions by extending Word 2003 documents and Excel 2003 workbooks using Visual Basic

and Visual C#. Visual Studio Tools for Office includes new Visual Studio projects for creating

code behind Word documents, Word templates, Excel workbooks, and Excel templates.

• VISUAL WEB DEVELOPER:

Visual Studio features a new Web page designer named Visual Web Developer that

includes many enhancements for creating and editing ASP.NET Web pages and HTML pages.

Visual Web Developer features improvements in all areas of Web site development. You can

11
create and maintain Web sites as local folders, in Internet Information Services (IIS), or on an

FTP or SharePoint server. The Visual Web Developer designer supports all ASP.NET

enhancements, including nearly two dozen new controls that simplify many Web development

tasks.

• SMART DEVICE APPLICATIONS:

The Visual Studio integrated environment includes tools for targeting devices such as

PDAs and Smart phones. Improvements include Visual C++ tools and native device runtimes,

managed designers that provide improved platform-specific WYSIWYG and multiple form

factor support, a new emulator, data handling tools similar to the desktop, and end-user

deployment projects that eliminate the manual editing of .in files.

• WEB FORMS:

Web Forms are an ASP.NET technology that you use to create programmable Web

pages. Web Forms render themselves as browser-compatible HTML and script, which allows

any browser on any platform to view the pages. Using Web Forms, you create Web pages by

dragging and dropping controls onto the designer and then adding code, similar to the way that

you create Visual Basic forms.

WINDOWS FORMS:

Windows Forms is for creating Microsoft Windows applications on the .NET

Framework. This framework provides a clear, object-oriented, extensible set of classes that

enables you to develop rich Windows applications. Additionally, Windows Forms can act as the

local user interface in a multi-tier distributed solution.

12
 • XML WEB SERVICES:

XML Web Services are applications that can receive requests and data using XML over

HTTP. XML Web Services are not tied to a particular component technology or object-calling

convention and can therefore be accessed by any language, component model, or operating

system.

• XML SUPPORT:

Extensible Markup Language (XML) provides a method for describing structured data.

XML is a subset of SGML that is optimized for delivery over the Web. The World Wide Web

Consortium (W3C) defines XML standards so that structured data will be uniform and

independent of applications. Visual Studio fully supports XML, providing the XML Designer to

make it easier to edit XML and create XML schemas.

4.2 INTRODUCTION TO ASP.NET

• INTRODUCTION OF DOT NET:

The dot net framework introduces the completely new model for the programming and

the deployment of the applications. . NET is Microsoft’s vision of “software as a service”, a

development environment in which you can build, create, and deploy your applications and the

next generation of components, the ability to use the web rather than your computer for various

services .

Microsoft introduced great technologies like COM, DCOM, and COM+ etc. to enable

reuse of software. According to this aspect, Microsoft realized that it’s time to come up with a

13
new technology, a better one, an easier one, a new framework, within which each programming

task is easy accomplished.

THE .NET FRAMEWORK:

The .NET Framework is a multi-language environment for building, deploying, and running

XML Web Services and applications. It consists of three main parts:

● Common Language Runtime:

Despite its name, the runtime actually has a role in both a component's runtime and

development time experiences. While the component is running, the runtime is responsible

for managing memory allocation, starting up and stopping threads and processes, and

enforcing security policy, as well as satisfying any dependencies that the component might

have on other components. At development time, the runtime's role changes slightly;

because it automates so much (for example, memory management), the runtime makes the

developer's experience very simple, especially when compared to COM as it is today. In

particular, features such as reflection dramatically reduce the amount of code a developer

must write in order to turn business logic into a reusable component.

● Unified programming classes:

The framework provides developers with a unified, object-oriented, hierarchical, and

extensible set of class libraries (APIs). Currently, C++ developers use the Microsoft

Foundation Classes and Java developers use the Windows Foundation Classes. The

framework unifies these disparate models and gives Visual Basic and J Script

programmers’ access to class libraries as well. By creating a common set of APIs across all
14
 programming languages, the common language runtime enables cross-language

inheritance, error handling, and debugging. All programming languages, from J Script to

C++, have similar access to the framework and developers are free to choose the language

that they want to use.

ASP.NET builds on the programming classes of the .NET Framework, providing a Web

application model with a set of controls and infrastructure that make it simple to build Web

applications. ASP.NET includes a set of controls that encapsulate common HTML user

interface elements, such as text boxes, buttons, and list boxes. These controls run on the

Web server, however, and render their user interface as HTML to the browser. On the

server, the controls expose an object-oriented programming model that brings the richness

of object-oriented programming to the Web developer. ASP.NET also provides

infrastructure services, such as state management and process recycling that further reduce

the amount of code a developer must write and increase application reliability. In addition,

ASP.NET uses these same concepts to enable developers to deliver software as a service.

Using XML Web Services features, ASP.NET developers can write their business logic

and use the ASP.NET infrastructure to deliver that service via SOAP.

• VISUAL C#:

Microsoft Visual C# 2008, pronounced C sharp, is a programming language designed for

building a wide range of applications that run on the .NET Framework. C# is simple, powerful,

type-safe, and object-oriented. With its many innovations, C# enables rapid application
15
development while retaining the expressiveness and elegance of C-style languages.

Visual Studio supports Visual C# with a full-featured Code Editor, project templates,

designers, code wizards, a powerful and easy-to-use debugger, and other tools. The .NET

Framework class library provides access to a wide range of operating system services and other

useful, well-designed classes that speed up the development cycle significantly.

• CREATING ASP.NET WEB APPLICATIONS (VISUAL C#):

ASP.NET provides a unified Web development model that includes the services

necessary for you to build enterprise-class Web applications. ASP.NET is part of the .NET

Framework and enables you to take full advantage of the features of the common language

runtime (CLR), such as type safety, inheritance, language interoperability, and versioning.

When you use Visual Studio to create ASP.NET Web sites, you are actually using a part

of the integrated development environment (IDE) called Visual Web Developer. Visual Web

Developer is distinct from Visual C#; it has its own designer for creating user interfaces on Web

pages and other tools for Web development and Web site administration. But when you create

code-behind pages in C# for your Web controls, you are using the C# code editor, and all the

features of the editor are available to you in Visual Web Developer just as they are in Visual C#.

INTRODUCTION TO ASP.NET WITH C#:

• ASP.NET OVERVIEW:
ASP.NET is a unified Web development model that includes the services necessary

for you to build enterprise-class Web applications with a minimum of coding. ASP.NET is part

of the .NET Framework, and when coding ASP.NET applications you have access to classes in

the .NET Framework. You can code your applications in any language compatible with the
16
common language runtime (CLR), including Microsoft Visual Basic and C#. These languages

enable you to develop ASP.NET applications that benefit from the common language runtime,

type safety, inheritance, and so on.

• CLASSIC ASP:

Asp, which is now more commonly known as Classic Asp was used extensively in

1990's. The idea of creating dynamic pages and linking them with database was the main

purpose of classic Asp. Asp used html controls for user interaction. Apart from the good features

available in Asp programming, it also lacks in some of the major areas. These areas include clean

coding as asp pages were incline pages and all the business logic as well as the interface was

coded in a single page.

ASP.NET WEB APPLICATIONS:

Asp.net is based on the .NET framework for building web applications. Since Asp.net is a

part of the Microsoft. NET Framework it has the ability to take advantage of rich class libraries

provided by Microsoft. The question is that why one should use Asp.net and not use classic asp

or any other web programming technology. Here are some of the features of Asp.net that makes

it the best web application technology.

• USE OF CONTROLS:

Asp.net provides the developer with several controls to perform basic as well as

advanced operations. Controls provided in Asp.net falls under HTML Controls, HTML Server

Controls and Web Server Controls.

17
 • HTML CONTROLS:

Html controls are the basic controls that are executed on the client machine. These

controls include textbox, label, image etc. A simple example of html control can be given by the

following code which renders an image.

HTML SERVER CONTROLS:

HTML Server Controls looks exactly like the HTML Controls with one difference that

they are executed on the server rather than the client. As you can see that the image tag or control

looks exactly like the one that we have previously discussed. But it has an additional attribute

which is run at. The run at attribute denotes that this is a HTML Server Control and will be

executed on the Server rather than the client.

WEB SERVER CONTROLS:

Web Server Controls are the most advanced controls in Asp.net. Each control comes with tons

of features that allow the developer to complete the task in less time. Web Server Controls are

executed on the Server. Web Server Controls include data grid control, data list control .calendar

control and many more.

4.3 INTRODUCTION TO SQL SERVER 2008

SQL Server 2008 introduces "studios" to help you with development and management

tasks: SQL Server Management Studio and Business Intelligence Development Studio. In

Management Studio, you develop and manage SQL Server Database Engine and notification

solutions, manage deployed Analysis Services solutions, manage and run Integration Services

packages, and manage report servers and Reporting Services reports and report models. In BI
18
Development Studio, you develop business intelligence solutions using Analysis Services

projects to develop cubes, dimensions, and mining structures; Reporting Services projects to

create reports; the Report Model project to define models for reports; and Integration Services

projects to create packages.

Both of these studios are closely integrated with Microsoft Visual Studio and the

Microsoft Office System. For more information, see Introducing SQL Server Management

Studio and Introducing Business Intelligence Development Studio.

In the studios, SQL Server 2008 provides the graphical tools you need to design, develop,

deploy, and administer relational databases, analytic objects, data transformation packages,

replication topologies, reporting servers and reports, and notification servers. Additionally, SQL

Server 2008 includes command prompt utilities to perform administrative tasks from the

command prompt. To quickly get to important high-level topics for tools and utilities, go

to Tools and Utilities Documentation Map.

SQL Server 2008 provides a number of ways to submit feedback about the product and

the documentation, as well as ways to send error reports and feature usage data automatically to

Microsoft. To learn how you can provide feedback, go to Providing Feedback on SQL

Server 2008.

Database Engine

The Database Engine is the core service for storing, processing, and securing data. The

Database Engine provides controlled access and rapid transaction processing to meet the

requirements of the most demanding data consuming applications within your enterprise.

Use the Database Engine to create relational databases for online transaction processing or online
19
analytical processing data. This includes creating tables for storing data, and database objects

such as indexes, views, and stored procedures for viewing, managing, and securing data.

• SQL SERVER FEATURES:

Microsoft SQL Server supports a set of features that result in the following benefits:

Ease of installation, deployment, and use SQL Server includes a set of administrative and

development tools that improve your ability to install, deploy, manage, and use SQL Server

across several sites.

Scalability - The same database engine can be used across platforms ranging from

laptop computers running Microsoft Windows 95 to large, multiprocessor servers running

Microsoft Windows NT, Enterprise Edition.

Data warehousing - SQL Server includes tools for extracting and analyzing summary data for

online analytical processing (OLAP). SQL Server also includes tools for visually designing

databases and analyzing data using English-based questions.

DATABASE ARCHITECTURE:

Microsoft SQL Server data is stored in databases. The data in a database is organized into

the logical components visible to users. A database is also physically implemented as two or

more files on disk.

20
 When using a database, you work primarily with the logical components such as tables,

views, procedures, and users. The physical implementation of files is largely transparent.

Each SQL Server installation has multiple databases. SQL Server has four system databases

(master, model, temp db, and MSDN) and each SQL Server installation has one or more use

databases. Some organizations have only one user database, containing all the data for their

organization.

21
 PROBLEM
DEFINITION
AND PROPOSAL

22
 CHAPTER 5
PROBLEM DEFINITION AND PROPOSAL

5.1 INTRODUCTION

This project is developed using ASP.NET as front end and SQL SERVER as backend

tool. The system is mainly developed to reduce the confusion, using for customer feedback

about the products.

It will be portable, accuracy of calculation and efficient way of analyzing the products.

Intelligent views and opinions expressed by informed customers can also help businesses

better understand the usage of their products and services and overall brand image among such

customers and also look to innovate and advance.

5.2 EXISTING SYSTEM

In the existing system, the students ought to meet the management authority directly on
their complaints within the complaint box. Students are not aware that the complaint has been
taken into action or any other steps taken regarding the complaints that has been posted by the
student. There are chances for the fake complaints and the students who posted that complaints
cannot be founded easily and quickly. In some cases the complaints papers can get missed and
also authority people can be able to misuse the complaint paper.

5.3PROPOSED SYSTEM
Students can post their complaints regarding errors name, mismatch and finance in

admission quota, complaints regarding re-evaluation and alter in schedule, changes in mark

23
sheet. All these complaints posted by students are viewed by committee and decides to forward it

to the institution or department based on the complaints. There is a separate login for institution

and department. If the institution or department receives the complaints, and once the complaint

is rectified, the status of the complaint is updated which can be directly viewed by the student.

The Advantages of the proposed system are:

● The proposed system is completely automated system

● Users easily access the application

● The facility provides the user interaction with application.

5.4FEASIBILITY STUDY
It is wise to think about feasibility of any problem we take on. Feasibility is the study of

impact, what happens in the organization by the development of a system. This system is

designed by user friendly approach that is the donor can also access and view the details of the

trust and their activities. Here the feasibility study can be performed in three ways such as

technical feasibility, economic feasibility and operational feasibility.

The feasibility study is required to analysis the capability of a project. The main

objective of the feasibility study is to measure the following:

● Operational Feasibility

● Technical Feasibility

● Economic Feasibility

24
5.4.1 Operational Feasibility
Process is too feasible to do the process of verification and security for customer. Then

the evaluation is whether or not the process within the organization will work but also if it can

work. It takes more time to communicate between the trust head and trust employee about the

activity and money transfer for the particular process. The adaptability and reusability is once

change resistance is overcome, explain how the new process will be implemented along with a

review process to monitor the process change.

5.4.2 Technical Feasibility

Technical feasibility determines whether the work for the project can be done with the

existing equipment, software technology and available personnel. Technical feasibility is

concerned with specifying equipment and software that will satisfy the requirement.

This project is feasible on technical remarks also, as the proposed system is more

beneficiary in terms of having a high security system with new technical verifications on the

system. The proposed system can run on any machines supporting Windows and Internet

services and works on the best software of ASP.NET with SQL server and hardware that had

been used while designing the system so it would be feasible in all technical terms of feasibility.

5.4.3 Economical Feasibility

Economical feasibility determines whether there are sufficient benefits in creating to

make the cost acceptable, or is the cost of the system too high. As this signifies cost - benefit

analysis and savings. On the behalf of the cost-benefit analysis, the proposed system is feasibl

and is economical regarding its pre-assumed cost for making a system,.We classified the costs of

25
project according to the phase in which they occur. The system development costs are usually

one-time costs that will not recur after the project has been completed.

For calculating the Development costs we evaluated certain cost categories viz.

26
SYSTEM DESIGN

27
 CHAPTER 6
SYSTEM DESIGN
6.1 INTRODUCTION

Many organizations look at system Design primarily as the preparation of the system

component specification; however, constructing the various system components is only one of a

set of major steps in successfully building a system. The preparation of the environment needed

to build the system, the testing of the system, and the migration and preparation of the data that

will ultimately be used by the system are equally important. In addition to designing the

technical solution, System Design is the time to initiate focused planning efforts for both the

testing and the preparation activities.

The System Design describes the system requirements, operating environment, system

and subsystem architecture, file and database design, input formats, output layouts, human-

machine interfaces, detailed design, processing logic and external interface.

Design is concerned with identifying software components specifying relationships

among components. Specifying software and providing blue print for the document phase.

Many organization look at system Design primarily as the preparation of the system

component specification; however, constructing the various system components is only one of a

set of major steps in successfully building a system.

28
6.1 COMPONENT DESCRIPTION

“A component is a non-trivial, nearly independent, and replaceable part of a system that fulfills a

clear function in the context of a well-define architecture. A component conforms to and

provides the physical realization of a set of interfaces.”

6.2MODULES DESCRIPTION
MAIN MODULES

6.2.1 Team
Add the Student information and Department Heads information and also can
view them. Will receive the grievance message directly from the students or redirected by
Department Heads. The Team respond back to the grievance and takes the action.

6.2.2 Student
Student can raise grievance to the team or the Head of Department. Student can
view his own information.

6.2.3 Department head

Can raise grievance and also respond to the students case and also can redirect the
grievance from the students to the team.

6.2.4 Report module

Generates report of all the cases received and solved.

29
6.3SUB MODULES:

6.3.1 Student Information Module:

Student information can be viewed by the Grievance team and the Department
Heads.

6.3.2 Case Information Module:

Can view the detailed information about the case and the actions that are being
taken by the team.

6.3.3 Case History Module:

Can search for a case and view its information using case id.

6.3.4FEEDBACK

Feedback module will contain feedback posted by users to either admin or specific
department. Admin / department will respond to the users feedback.

30
6.4UML DIAGRAMS

FIG: 6.4.1ENTITY RELATIONSHIP DIAGRAM

31
6.4.2 USE CASE DIAGRAM

FIG 6.4.2:ADMIN USE CASE DIAGRAM

32
6.4.3DATA FLOW DIAGRAM

LEVEL 0

33
LEVEL 1

34
LEVEL 2

35
LEVEL 3

36
6.4.4 SEQUENCE DIAGRAM

37
6.4.5 COMPONENT DIAGRAM

38
6.4.6 ACTIVITY DIAGRAM

39
6.5 TABLE DESIGN
Table design is a collection of interrelated data items. The table design for the new
system is designed by the techniques of the relational table management system. It provides
flexibility in the storage and retrieval of the data in the order to anticipate the need to meet
unexpected requirements. Normalization can be done which is a process of simplifying the
relationship between data elements to produce successive simple and manageable records
structures.

The following tables are used in the system:

1. Student Table
2. Staff Table
3. Feedback Table
4. Grievance Table

40
Table Name: student

FIELD DATATYPE CONSTRAINS DESCRIPTION

Id Int Primary key Auto increment id
Student’s register
Stregno varchar(50) Not null number
Stname varchar(50) Not null Student’s name
Stdob varchar(20) Not null Student’s gender
Student’s register
Gender varchar(10) Not null number
Student’s department
Dept varchar(50) Not null name
Batch varchar(50) Not null Student’s batch
Email varchar(150) Not null Student’s email id
Student’s mobile
Mobile varchar(50) Not null number
Address varchar(max) Not null Student’s address
Photo varchar(max) Not null Student’s photo
Username varchar(50) Not null Student’s username
Password varchar(50) Not null Student’s password

41
Table Name: staff

FIELD DATATYPE CONSTRAINS DESCRIPTION

Id Int Primary key Auto increment id
Stregno varchar(50) Not null Staff’s register number
Stname varchar(50) Not null Staff’s name
Stdob varchar(20) Not null Staff’s gender
Gender varchar(10) Not null Staff’s register number
Staff’s department
Dept varchar(50) Not null name
Qualification varchar(50) Not null Staff’s qualification
Email varchar(150) Not null Staff’s email id
Mobile varchar(50) Not null Staff’s mobile number
Address varchar(max) Not null Staff’s address
Photo varchar(max) Not null Staff’s photo
Username varchar(50) Not null Staff’s username
Password varchar(50) Not null Staff’s password

42
Table Name: feedback

FIELD DATATYPE CONSTRAINS DESCRIPTION

Id Int Primary key Auto increment id
Feedbackmessage varchar(max) Not null Feedback message
Name varchar(50) Not null Student name
Student Department
Dept varchar(10) Not null name
Regno Varchar(50) Not null Student register number

Table Name: Grievance

FIELD DATATYPE CONSTRAINS DESCRIPTION

Id Int Primary key Auto increment id
ReportID varchar(50) Not null Grievance report id
RegNo varchar(50) Not null Student register number
Emailid varchar(50) Not null Student email id
Dept varchar(300) Not null Department name
ShareTo Varchar(50) Not null Report shared to
Report Varchar(50) Not null Report
Status varchar(max) Not null Grievance status
Posteddate varchar(50) Not null Grievance posted date

43
IMPLEMENTATION

44
 CHAPTER 7
IMPLEMENTATION

7.1 INTRODUCTION
Implementation is the most crucial stage in achieving a successful system and giving the

user’s confidence that the new system is workable and effective. Implementation of a modified

application to replace an existing one, this type of conversation is relatively to handle, provide

there are no major changes in the system.

Each program is tested individually at the time of development using the data and has

verified that this program linked together in the way specified in the program specification, the

computer system and its environment is tested to the satisfaction the computer system and it

environment is tested to the satisfaction of the user. The system that has been developed is

accepted and proved to be satisfactory for the user. And so the system is going to be

implemented very soon. A simple operating procedure is included so that the user can

understand the different functions clearly and quickly.

Initially as a first step the executable from of the application is to be created and loaded

in the common server machine which is accessible to the entire user and the final stage is to

document the entire system which provides components and the operating procedure of the

system.

45
7.2 IMPLEMENTATION METHODS
There are several methods for handling the implementation and the consequent

conversion from the old to the new computerized system. The most secure method for

conversion from the old to the new system is to run the old and new system in parallel. In this

approach, a person may operate in the manual older processing system as well as start operating

the new computerized system. This method offers high security, because even if there is a flaw in

the computerized system, we can depend upon the manual system. However, the cost for

maintaining two systems in parallel is very high. This overweighs its benefits. Another

commonly method is a direct cut over from the existing manual system to the computerized

system. The change may be within a week or within a day. There are no parallel activities.

However, there is no remedy in case of a problem. This strategy requires careful planning. A

working version of the system can also be implemented in one part of the organization and the

personnel will be piloting the system and changes can be made as and when required. But this

method is less preferable due to the loss of entirety of the system.

7.3 IMPLEMENTATION PLAN

The implementation plan includes a description of all the activities that must occur to

implement the new system and to put it into operation. It identifies the personnel responsible for

the activities and prepares a time chart for implementing the systemThe implementation plan

consists of the following steps:

• List all files required for implementation.

• Identify all data required to build new files during the implementation.

• List all new documents and procedures that go into the new system.

46
The implementation plan should anticipate possible problems and must be able to deal with

them. The usual problems may be missing documents, mixed data formats between current and

files, errors in data translation, missing data etc.

47
SOURCE CODE

48
APPENDICES
APPENDIX 1 : SOURCE CODE

LOGIN.ASPX.CS
using System;
usingSystem.Collections.Generic;
usingSystem.Linq;
usingSystem.Web;
usingSystem.Web.UI;
usingSystem.Web.UI.WebControls;
usingSystem.Data;
usingSystem.Data.SqlClient;
usingSystem.Configuration;

namespaceGreivanceRedressalSystem
{
publicpartialclassindex : System.Web.UI.Page
{
SqlConnection con =
newSqlConnection(ConfigurationManager.ConnectionStrings["con"].ConnectionString);

protectedvoidPage_Load(object sender, EventArgs e)

{

protectedvoid Button1_Click(object sender, EventArgs e)

{
if (TextBox1.Text != ""&& TextBox2.Text != "")
{

if (TextBox1.Text == "admin"&& TextBox2.Text == "admin")

{
Response.Write("<script>alert('Login
successful');window.location='Gindex.aspx'</script>");

}
elseif (TextBox1.Text != ""&& TextBox2.Text != "")
{
Session["userid"] = TextBox1.Text;
SqlCommandcmd = newSqlCommand("select Password from student where stregno='" +
TextBox1.Text + "'", con);
con.Open();
string pass = Convert.ToString(cmd.ExecuteScalar());
con.Close();
if (pass == TextBox2.Text)
{
Response.Write("<script>alert('Login
successful');window.location='studentindex.aspx'</script>");

49
Session["userid"] = TextBox1.Text;
SqlCommand cmd1 = newSqlCommand("select Password from staff where stregno='" +
TextBox1.Text + "'", con);
con.Open();
string pass1 = Convert.ToString(cmd1.ExecuteScalar());
con.Close();
if (pass1 == TextBox2.Text)
{
Response.Write("<script>alert('Login
successful');window.location='staffindex.aspx'</script>");

}
else
{
Response.Write("<script>alert('Please check your credentials')</script>");
}
}
else
{
Response.Write("<script>alert('Please enter your credentials')</script>");
}
}
}
}

POSTGRIEVANCE.ASPX.CS
using System;
usingSystem.Collections.Generic;
usingSystem.Linq;
usingSystem.Web;
usingSystem.Web.UI;
usingSystem.Web.UI.WebControls;
usingSystem.Data;
usingSystem.Data.SqlClient;
usingSystem.Configuration;

namespaceGreivanceRedressalSystem
{
publicpartialclasspostgrievance : System.Web.UI.Page
{
SqlConnection con =
newSqlConnection(ConfigurationManager.ConnectionStrings["con"].ConnectionString);

protectedvoidPage_Load(object sender, EventArgs e)

{
TextBox2.Text = Session["userid"].ToString();
50
Random r = newRandom();
intgenRand = r.Next(10, 900000000);
TextBox1.Text = ("RP" + genRand);

SqlCommandcmd = newSqlCommand("select * from student where stregno='" + TextBox2.Text +

"'", con);

con.Open();
DataTabledt = newDataTable();
SqlDataReadersdr = cmd.ExecuteReader();
dt.Load(sdr);
con.Close();

if (dt.Rows.Count> 0)
{
TextBox3.Text = dt.Rows[0]["email"].ToString();
TextBox4.Text = dt.Rows[0]["dept"].ToString();
}

protectedvoid Button1_Click(object sender, EventArgs e)

{
SqlCommand cmd1 = newSqlCommand("insert into
Grievance(ReportID,RegNo,Emailid,Dept,ShareTo,GrievanceType,Report,status,PostedDate)
values('" + TextBox1.Text + "','" + TextBox2.Text + "','" + TextBox3.Text + "','" +
TextBox4.Text + "','" + DropDownList1.SelectedItem.ToString() + "','" +
DropDownList2.SelectedItem.ToString() + "','" + TextBox5.Text +
"','Open','"+DateTime.Now.ToString()+"')", con);
con.Open();
cmd1.ExecuteNonQuery();
con.Close();
Response.Write("<script>alert('Grievance posted
Successfully');window.location='postgrievance.aspx'</script>");
}
}
}

VIEWGRIEVANCE.ASPX.CS
using System;
usingSystem.Collections.Generic;
usingSystem.Linq;
usingSystem.Web;
usingSystem.Web.UI;
usingSystem.Web.UI.WebControls;
usingSystem.Data;
usingSystem.Data.SqlClient;
usingSystem.Configuration;

namespaceGreivanceRedressalSystem
{
51
publicpartialclassviewgrievance : System.Web.UI.Page
{
SqlConnection con =
newSqlConnection(ConfigurationManager.ConnectionStrings["con"].ConnectionString);

protectedvoidPage_Load(object sender, EventArgs e)

{
Label2.Text = Session["userid"].ToString();

SqlCommandcmd = newSqlCommand("select * from student where stregno='" + Label2.Text +

"'", con);

con.Open();
DataTabledt = newDataTable();
SqlDataReadersdr = cmd.ExecuteReader();
dt.Load(sdr);
con.Close();

if (dt.Rows.Count> 0)
{
Label1.Text = dt.Rows[0]["stname"].ToString();
Label3.Text = dt.Rows[0]["dept"].ToString();
Label4.Text = dt.Rows[0]["email"].ToString();
}

SqlCommand cmd1 = newSqlCommand("select * from Grievance where RegNo='" + Label2.Text +

"' and status='Open'", con);

con.Open();
DataTable dt1 = newDataTable();
SqlDataReader sdr1 = cmd1.ExecuteReader();
dt1.Load(sdr1);
con.Close();

if (dt1.Rows.Count > 0)
{
DataList1.DataSource = dt1;
DataList1.DataBind();
}
}

protectedvoid LinkButton1_Click(object sender, EventArgs e)

{
LinkButton link = (LinkButton)sender;
DataListItem parent = (DataListItem)link.NamingContainer;
if (parent.Controls.Count> 0)
{
Label lb1 = (Label)parent.FindControl("Label2");
Label lb2 = (Label)parent.FindControl("Label4");
Label lb3 = (Label)parent.FindControl("Label5");

Session["ReportID"] = lb1.Text;
Session["PostedDate"] = lb2.Text;

52
Session["Report"] = lb3.Text;

Response.Redirect("viewreply.aspx");
}
}

STAFFREPLY.ASPX.CS
using System;
usingSystem.Collections.Generic;
usingSystem.Linq;
usingSystem.Web;
usingSystem.Web.UI;
usingSystem.Web.UI.WebControls;
usingSystem.Data;
usingSystem.Data.SqlClient;
usingSystem.Configuration;
usingSystem.Web.Services;
using System.IO;
using System.Net;
usingSystem.Net.Mail;

namespaceGreivanceRedressalSystem
{
publicpartialclassstaffreply : System.Web.UI.Page
{
SqlConnection con =
newSqlConnection(ConfigurationManager.ConnectionStrings["con"].ConnectionString);

protectedvoidPage_Load(object sender, EventArgs e)

{
Rno.Text = Session["userid"].ToString();

SqlCommand cmd0 = newSqlCommand("select * from staff where stregno='" + Rno.Text + "'",

con);

con.Open();
DataTable dt0 = newDataTable();
SqlDataReader sdr0 = cmd0.ExecuteReader();
dt0.Load(sdr0);
con.Close();

if (dt0.Rows.Count > 0)
53
 {
Name.Text = dt0.Rows[0]["stname"].ToString();
Dept.Text = dt0.Rows[0]["dept"].ToString();
Emailid.Text = dt0.Rows[0]["email"].ToString();
}

Rid.Text = Session["ReportID"].ToString();
date.Text = Session["PostedDate"].ToString();
Report.Text = Session["Report"].ToString();
studemailid.Text = Session["Emailid"].ToString();
}

[WebMethod]
//[ScriptMethod(UseHttpGet = true)]
publicstaticbool Save(string rid, stringmsg, string name, stringstudemailid, string
Report)
{
try
{

using (MailMessagemailMsg = newMailMessage())

{
stringmail_id = "[email protected]";
stringmail_pwd = "ehzllljftmgsdyah";
intsmtpport = 587;
SmtpClient client = newSmtpClient("smtp.gmail.com", smtpport);
client.Credentials = newSystem.Net.NetworkCredential(mail_id, mail_pwd);
client.EnableSsl = true;

mailMsg.To.Add(newMailAddress(studemailid));

mailMsg.Subject = "Welcome to Grievance Redressal System.";

mailMsg.Body = "Reply from Department HOD <br /> Report ID : " + rid + "<br /> Report :"
+ Report + "<br /> Reply Message :" + msg;

mailMsg.IsBodyHtml = true;
mailMsg.From = newMailAddress(mail_id);
client.Send(mailMsg);
//return true;
}

SqlConnection con =
newSqlConnection(ConfigurationManager.ConnectionStrings["con"].ConnectionString);
SqlCommand cmd1 = newSqlCommand("insert into tbl_Replies(Rid,UserId,Msg,UserName)
values('" + rid + "','" + HttpContext.Current.Session["userid"].ToString() + "','" + msg
+ "','"+name+"')", con);
con.Open();
cmd1.ExecuteNonQuery();
con.Close();
// Implement your logic to save EmpList in Database

//MailMessage mail = new MailMessage();

//SmtpClientsmtpserver = new SmtpClient("smtp.mail.yahoo.com");
//mail.From = new MailAddress("[email protected]");

54
//mail.To.Add(Emailid.Text);
//mail.Subject = ("Response to your Feedback: ");
//mail.Body = "Reply from admin: " + TextBox2.Text;
//smtpserver.UseDefaultCredentials = false;
//smtpserver.Port = 465;
//smtpserver.Credentials = new System.Net.NetworkCredential("[email protected]",
"mail2kaccesss");
//smtpserver.EnableSsl = true;
//smtpserver.Send(mail);
//Response.Write("<script>alert('Mail Sent')</script>");
}
catch (Exception ex)
{
// Log Error
returnfalse;
}

returntrue;
}
[WebMethod]
//[ScriptMethod(UseHttpGet = true)]
publicstaticList<Chats>loaddata(string rid = "")
{
List<Chats> chats = newList<Chats>();
//string query = "select * from tbl_Chat";
SqlConnection con =
newSqlConnection(ConfigurationManager.ConnectionStrings["con"].ConnectionString);
SqlCommandcmd = newSqlCommand("select * from tbl_Replies where rid='" + rid + "'", con);

con.Open();
DataTabledt = newDataTable();
SqlDataReadersdr = cmd.ExecuteReader();
dt.Load(sdr);
con.Close();
//var data = db.select_reader(query);
if (dt.Rows.Count> 0)
{
for (inti = 0; i<dt.Rows.Count; i++)
{
Chats chat = newChats();
chat.Message = dt.Rows[i]["Msg"].ToString();
chat.Senderid = dt.Rows[i]["UserId"].ToString();
chat.SenderName = dt.Rows[i]["UserName"].ToString();
chat.datetime = dt.Rows[i]["datetime"].ToString();
chats.Add(chat);
}
}
return chats;
}
publicclassChats
{
publicstring Message { get; set; }
publicstringSenderid { get; set; }
publicstringSenderName { get; set; }
publicstringdatetime { get; set; }

55
 }
}
}

ADMINREPLY.ASPX.CS
using System;
usingSystem.Collections.Generic;
usingSystem.Linq;
usingSystem.Web;
usingSystem.Web.UI;
usingSystem.Web.UI.WebControls;
usingSystem.Data;
usingSystem.Data.SqlClient;
usingSystem.Configuration;
usingSystem.Web.Services;
using System.IO;
using System.Net;
usingSystem.Net.Mail;

namespaceGreivanceRedressalSystem
{
publicpartialclassadminreply : System.Web.UI.Page
{
SqlConnection con =
newSqlConnection(ConfigurationManager.ConnectionStrings["con"].ConnectionString);

protectedvoidPage_Load(object sender, EventArgs e)

{
Rno.Text = "A1000";

SqlCommandcmd = newSqlCommand("select * from Grievance where ReportID='" +

Session["ReportID"].ToString() + "'", con);

con.Open();
DataTabledt = newDataTable();
SqlDataReadersdr = cmd.ExecuteReader();
dt.Load(sdr);
con.Close();

//if (dt.Rows.Count> 0)
//{
// Name.Text = dt.Rows[0]["stname"].ToString();
// Dept.Text = dt.Rows[0]["dept"].ToString();
// Emailid.Text = dt.Rows[0]["email"].ToString();
//}

Rid.Text = Session["ReportID"].ToString();
date.Text = Session["PostedDate"].ToString();
Report.Text = Session["Report"].ToString();
studemail.Text = Session["Emailid"].ToString();
}
56
 [WebMethod]
//[ScriptMethod(UseHttpGet = true)]
publicstaticbool Save(string rid, stringmsg, string name, stringstudemail, string Report)
{
try
{

using (MailMessagemailMsg = newMailMessage())

{
stringmail_id = "[email protected]";
stringmail_pwd = "ehzllljftmgsdyah";
intsmtpport = 587;
SmtpClient client = newSmtpClient("smtp.gmail.com", smtpport);
client.Credentials = newSystem.Net.NetworkCredential(mail_id, mail_pwd);
client.EnableSsl = true;

mailMsg.To.Add(newMailAddress(studemail));

mailMsg.Subject = "Welcome to Grievance Redressal System.";

mailMsg.Body = "Reply from Grievance Team <br /> Report ID : " + rid + "<br /> Report :"
+ Report + "<br /> Reply Message :" + msg;
mailMsg.IsBodyHtml = true;
mailMsg.From = newMailAddress(mail_id);
client.Send(mailMsg);
//return true;
}

//MailMessage mail = new MailMessage();

//SmtpClientsmtpserver = new SmtpClient("smtp.mail.gmail.com");
//mail.From = new MailAddress("[email protected]");
//mail.To.Add(studemail);
//mail.Subject = ("Response to your Feedback: ");
//mail.Body = "Reply from admin: " + msg;
//smtpserver.UseDefaultCredentials = false;
//smtpserver.Port = 587;
//smtpserver.Credentials = new System.Net.NetworkCredential("[email protected]",
"ehzllljftmgsdyah");
//smtpserver.EnableSsl = true;
//smtpserver.Send(mail);

SqlConnection con =
newSqlConnection(ConfigurationManager.ConnectionStrings["con"].ConnectionString);
SqlCommand cmd1 = newSqlCommand("insert into tbl_Replies(Rid,UserId,Msg,UserName)
values('" + rid + "','A1000','" + msg + "','" + name + "')", con);
con.Open();
cmd1.ExecuteNonQuery();
con.Close();
// Implement your logic to save EmpList in Database
}
catch (Exception ex)
{
// Log Error
returnfalse;
}

57
returntrue;
}
[WebMethod]
//[ScriptMethod(UseHttpGet = true)]
publicstaticList<Chats>loaddata(string rid = "")
{
List<Chats> chats = newList<Chats>();
//string query = "select * from tbl_Chat";
SqlConnection con =
newSqlConnection(ConfigurationManager.ConnectionStrings["con"].ConnectionString);
SqlCommandcmd = newSqlCommand("select * from tbl_Replies where rid='" + rid + "'", con);

con.Open();
DataTabledt = newDataTable();
SqlDataReadersdr = cmd.ExecuteReader();
dt.Load(sdr);
con.Close();
//var data = db.select_reader(query);
if (dt.Rows.Count> 0)
{
for (inti = 0; i<dt.Rows.Count; i++)
{
Chats chat = newChats();
chat.Message = dt.Rows[i]["Msg"].ToString();
chat.Senderid = dt.Rows[i]["UserId"].ToString();
chat.SenderName = dt.Rows[i]["UserName"].ToString();
chat.datetime = dt.Rows[i]["datetime"].ToString();
chats.Add(chat);
}
}
return chats;
}
publicclassChats
{
publicstring Message { get; set; }
publicstringSenderid { get; set; }
publicstringSenderName { get; set; }
publicstringdatetime { get; set; }
}
}
}

58
SCREENSHOTS

59
APPENDIX 2 : SCREENSHOTS
ADMIN LOGIN PAGE:

ADMIN INDEX PAGE:

60
ADD STUDENT PAGE :

VIEW STUDENT PAGE:

61
ADD STAFF PAGE:

VIEW STAFF PAGE:

62
VIEW GRIEVANCE PAGE:

GRIEVANCE REPLAY PAGE:

63
FEEDBACK PAGE:

STAFF LOGIN PAGE :

64
STAFF INDEX PAGE:

VIEW GRIEVANCE PAGE:

65
REPLAY GRIEVANCE PAGE:

VIEW PROFILE PAGE:

66
POST FEEDBACK PAGE:

STUDENT LOGIN PAGE:

67
STUDENT INDEX PAGE:

POST GRIEVANCE PAGE:

68
VIEW GRIEVANCE PAGE:

VIEW REPLAY PAGE:

69
VIEW PROFILE PAGE:

POST FEEDBACK PAGE:

70
TESTING

71
 CHAPTER 8
TESTING

8.1 TESTING INTRODUCTION

Any software must undergo testing before it is acknowledged. System testing is actually a

series of different tests, whose primary purpose is to fully exercise the computer-based system.

System testing is the state of implementation that is aimed at assuring that the system works

accurately and efficiently. Testing is vital to the success of the system. System testing makes the

logical assumption that if all parts of the system are correct, the goal will be successfully

achieved.

8.2 TESTING STRATEGIES

A software testing strategy provides a road map for the software developer. Testing is a

set activity that can be planned in advance and conducted systematically.

8.2.1 WHITE BOX TESTING

The testing is also called as Glass box testing. In this testing, by knowing the specific functions

that a product has been design to perform test can be conducted that demonstrate each function.

It is a test case design method that uses the control structure of the procedural design to drive test

cases. Basis path testing is a white box testing.

72
8.2.2 BLACK BOX TESTING

In this testing by knowing the internal operation of a product, test can be conducted to

ensure that “all gears mesh”, that is the internal operation performs according to specification

and all internal components have been adequately exercised. It fundamentally focuses on the

functional requirements of the software.

8.2.3 INTEGRATION TESTING

Integration testing is a systematic technique for constructing the program structure while

at the same time conducting test to uncover errors associated with individual modules, which are

highly prone to interface errors, should not be assumed to work instantly when we put them

together. The problem of course is “putting them together”- interfacing.

8.2.4 PROGRAM TESTING

The logical and syntax errors have been pointed out by program testing. A syntax error is

an error in a program statement that in violates one or more rules of the language in which it is

written. An improperly defined field dimensions or omitted keywords are common syntax error.

These errors are shown through error messages generated by the computer. A logic error on the

other hand deals with incorrect data fields, out-off-range items and invalid combinations. Since

the compiler will not deduct logical error, the programmer must examine the output.

8.2.5 VALIDATION TESTING

At the culmination of integration testing, software is completely assembled as a package.

Interfacing errors have been uncovered and corrected and a final series of software test-

73
validation testing begins. Validation testing can be defined in many ways, but a simple definition

is that validation succeeds when the software functions in manner that is reasonably expected by

the customer. Software validation is achieved through a series of black box tests that demonstrate

conformity with requirement. After validation test has been conducted, one of two conditions

exists.

8.2.6 USER ACCEPTANCE TESTING

User acceptance of the system is key factor for the success of any system. The system

under consideration is tested for user acceptance by constantly keeping in touch with prospective

system and user at the time of developing and making changes whenever required. This is done

in regarding to the following points:

1. Input screen design.

2. Output screen design.

8.3 TEST PROCEDURE

8.3.1 SYSTEM TESTING

Testing is performed to identify errors. It is used for quality assurance. Testing is an

integral part of the entire development and maintenance process. The goal of the testing during

phase is to verify that the specification has been accurately and completely incorporated into the

design, as well as to ensure the correctness of the design itself. For example the design must not

have any logic faults in the design is detected before coding commences, otherwise the cost of

fixing the faults will be considerably higher as reflected.

74
8.4 TEST CASE AND OUTPUT

8.4.1 UNIT TESTING:

Unit testing is the one where in, when a module is completed it has to be checked

whether the desired functionality is achieved completely or not.Unit testing is conducted to

verify the functional performance of each modular component of the software. It focuses on the

smallest unit of the software design in the module.

8.4.2 FUNCTIONAL TESTING:

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.

8.4.3 PERFORMANCE TEST:

Performance testing are conducted to identify the bottlenecks in the systems and to find

overall performance of the system. It determines the amount of execution time spent in various

75
parts of the unit, program throughput, and response time and device utilization by the program

unit.

8.4.4 STRESS TEST :

Stress testing involves overloading the system in various ways and observing the

behavior (i.e.) it depends on network traffic. The system is tested with high network traffic and

with more number of clients.

8.4.5 INTEGRATION TESTING

Integration testing is the procedural technique for developing the programming concept

along with conduction the test of error involved in the interface of the system which has been not

cover in the unit testing.

Integration testing is a systematic technique for construction the program structure while

at the same time conducting tests to uncover errors associated with interfacing, i.e integration

testing is the complete testing of the set of modules which makes up the product. The objective is

to take untested modules and build a program structure tester should identify critical modules.

Critical modules should be tested as early as possible. One approach is to wait until all the units

have passed testing, and then combine them and then tested. This approach is evolved from

unstructured testing of small programs.

76
8.5 TEST CASES:
Form name: registration
Test Test case Test case Test steps & results test case
case Name Descript- status
Steps Input Expected Actual
id tion
Data results results
001 Validate To verify type a Subha “Entered “Entered success
name field that the name name name
of field name exceeding should not should not
registration does not 20 letters exceed 10 exceed 100
accept a and click letters” letters”
name register
exceeding button
20 letters
002 Validate To verify type a sa “Entered Entered success
name field that the name with name name
of field name minimum 2 should not should not
registration has at letters and be less be less than
least 3 click than 2 2 letters”
letters register letters”
button
003 Validate To verify Type a Abberdf “Entered “Entered success
contact no that the numeric erf contact no contact no
field of field and click should not should not
registration contact no register have have
does not button alphabet” alphabet”
accept a
alphabet
value
004 Validate To verify Type a 9876532 “Entered “Entered Success
contact no that the contact no 10 contact no contact no
field of field exceeding should not should not
registration contact no 10 numbers exceed 10 exceed 10
not accept and click numbers” numbers”
a number register
exceeding button
10

77
 numbers
005 Validate To verify Type a dob 11/11/20 Enter the Enter the success
dob field of that the (dd/mm/yy 00 dob dob
registration field dob y) and click (dd/mm/y (dd/mm/yy
to accept register yyy) yy) format
(dd/mm/y button format
yy)
006 Validate To verify Type a subha@ Enter the Enter the success
email field that the mailed gmail.co email id email id
of field email using @ m
registration to accept and click
register
button

78
 CONCLUSION
AND FUTURE
ENHANCEMENT

79
 CHAPTER 9

CONCLUSION AND FUTURE ENHANCEMENT

9.1 CONCLUSION
Finally coming to the conclusion of the project report I would like to express my

sincere gratitude to all those who have helped us in this project to complete successfully. The

project “STUDENTS GRIEVANCE REDRESSAL SYSTEM” has been designed and

developed to the satisfaction of the end user. The system has been built with the latest

technology to make the best of all resources. It is very user-friendly, simple and interactive

system thus makes work easier. The application is tested well and errors are properly debugged.

We have tried out level best to make this application as easy as possible to use. We would be

very delighted to find this project useful. We together as a group made the maximum effort to

obtain the best and reliable software components for use with our coding.

9.2 FUTURE ENHANCEMENT

It is not possible to develop a system that makes all the requirements of the user. User

requirements keep changing as the system is being used. Some of the future enhancements that

can be done to this system are:

➢ As the technology emerges, it is possible to upgrade the system and can be adaptable to

desired environment.

➢ Because it is based on object-oriented design, any further changes can be easily

adaptable.

➢ Based on the future security issues security can be improved using emerging technology

80
REFERENCES

81
 CHAPTER 10
REFERENCES
10.1 Reference Books:

1. John Kauffman & Chris Ullman, (2007), ’Beginning ASP.NET 2.0 with C#’.

2. G. Andrew Duthie, (2002), ‘Microsoft ASP.NET Step-by-Step’.

3. Rod Colledge, (2009), ‘SQL Server 2008 Administration in Action’.

4. Kogent, (2011), ‘ASP.NET 4.0 in Simple Steps’.

10.2 REFERENCE WEBSITES

1. www.tutorialspoint.com

2. www.asp.net-tutorials.com

3. www.w3schools.com

4. www.aspsnippets.com

82
83