Gravience Management
Gravience Management
Student satisfaction is a major concern for any educational institute. However, many a
time the students fail to express their concerns & issues or fail to reach out for proper
support from the organization. Neither is there any system to address the conflicts or
issues faced by the students.
This eventually leads to students‘ dissatisfaction. Hence, to maintain the dignity of the
college or institute by ensuring a conflict-free atmosphere by promoting good student-
teacher relationships we have developed a Student Grievance System that will address
the students‘ issues & grievances. The students can lodge their complaints through
this system which will be redressed by the institute. This python-based student
grievance cell will also look into matters of harassment thus creating a protective
environment for students.
Therefore, a need for a system that could detect student‘s problems and provide them
with suitable feedback is raised. Also, this paper describes the Complaint
Management System oriented by Web-application which will be used by students in
order to make complaints about their dissatisfaction on provided services. This system
will be able to handle complaints by recording and giving feedback for each raised
complaint. Results of the study can be a good reference to find out users‘ needs from
e-complaint and the handling process of this complaint in the body of any
organizations.
VI
GRIEVANCE MANAGEMENT SYSTEM INTRODUCTION
CHAPTER 1
INTRODUCTION
1.1 Background of the Study
Academic growth can be of various concerns in an academic environment to promote
social and functioning educational system. For an effective educational system to take
place there are some issues in an academic environment that should be properly
addressed, take for instance issue of complaints management system in the university.
This issue had created a lot of problems for an academic growth in the various aspects
of the educational system. To support this approach, this project identifies a range of
options that can be used to manage and resolve Academic complaints. This includes,
where the opportunity presents itself, the need for an administrator to make every
effort to resolve potential or actual academic complaints as informally as possible in
the first instance.
Handling complaints often involve first, to listen and understand, empathize, offer a
solution, execute the solution and then follow up. Dogan and Wilkinson (2016)
defined complaint as any expression of dissatisfaction about services(s) or about any
professional conduct. it prompts more prominent clarity and consistency of executive
activities to determine the protests. Design and implementation of online complaint
management system is to maintain an effective, timely, and equitable complaint
handling system which is easily accessible and offered to complainants (students) at
no charge. This project defines the policy and steps for handling and resolving
complaints and also to appeal for an un-favored situation and for this process to take
place there must be automation of the system that will handle the complaints process
and appeal method of registration. Automation can be defined as the aspects involved
in using a computer system for the tasks or process such as circulation,
implementation etc. In relation to the above preposition by Marcus, it is possible for
the design and implementation of an online complaint management system to yield
substantial benefits for the users (Marcus, 2000).
The key to building lasting customer relationships is to create superior value and
satisfaction of the customers which can be achieved through effective customer
complaint management system. Every cooperate must make complaint management
system is one of the key strategies needed if they must succeed in their businesses
.The significance of customer complaint management system in the performance of
corporate organizations cannot be overstressed. Customer complaints are inevitable in
any corporate organization; no matter how good such an organization may be. Some
complaints serve as a feedback mechanism for corporate organizations. Customers of
such organizations may want to express their feelings and impressions on the quality
of the product or service produced by the organization. Some complaints tend to relay
a message on the taste and preference of the customers. Customers‘ complaints
become useful when such complaints attract quick and effective response from the
organization. Corporate organizations are expected to hold their customers in high
esteem since the customers are the lifeblood of any corporate organization.
Coupled with the foregoing, the use of information technology to manage customers‘
complaints in India is at its infancy stage. Majority of the business organizations in
the country use archaic or primitive methods to manage customers‘ complaints. It is
only few companies that use information technology or software to manage their
customers. This has negatively affected the performance of such erring corporate
organizations. There is evidently a wide gap between the expectation and the actual.
However, this research work is designed to address these challenges which business
organizations have in managing customer complaints.
Users
Admin
Manage users
Users
User Registration
User forgot Password
Complaint History
Profile Management
Change Password
1. Lack of fitting security and upkeep of the complaint record in the system
that makes an avenue for disappointment and control of information.
2. Lack of legitimate precise, concise data about the student implicit rules
and character.
3. Poor performance of the manual system may lead into the missing or
exploitative of the complaint by the staff or any member of the
management,
CHAPTER 2
LITERATURE SURVEY
Firstly, we have studied the current system available for complaint collection in
college and also meet the principal of college for collecting there requirements. Then
we also studied various website which were providing some relevant features.
Grievance is a depressing state of affairs caused by any evil or hardship you are
suffering from a person, which makes valid reasons for complaining as well the
complaint requires remedial action. The grievance redressed system is part of standard
equipment of any handling.
How to fix it will not lodge complaints not only for the refusal to return documents or
confirms, any irregularities in the admission process, but also complaints about
harassment that includes harassment. The standard grievance redressed system (GRS)
is shown in Fig. 1, and it works activities for a number of purposes including securing
a democratic institution , to inform all teachers and students of their rights and thus to
ensure quality and capacity building of the organization. In addition,
Considering the nature of the complaint and the magnitude of the complaint, a
thorough investigation is conducted by members, followed by the imposition of a fine
if anyone is found guilty
In the literature, periodic reporting is available on the need for and use of GRS for
various domains such as e-governance, public administration, Municipality Company,
harassment cases in the student community, and sexual harassment in the area
organization. Important comments during the literature review are listed below. In , to
analyze the various online services offered, especially the four Indians provinces, also
introduced the importance of online grievance redressed mechanisms. It is highlighted
in the fight against corruption in the empire. Various metrics GRS related factors have
been considered and estimates have been made. Provincial performance is measured
on a scale. Dipankar evaluates the implementation of the petition registration system
in India. Afraid of revealing your identity makes the complainant anonymous or false.
It is a difficult task for the authorities to know the plaintiff‘s authenticity. Therefore, a
solution was presented so that the plaintiffs could complain brave, at the same time
allowing the authorities to investigate the emergence of complaints. In , corrective
processes are considered essential for basic bias. Active job-system suspension is
possible if both the demand and the supply side are working properly. It also reveals
that grievances are addressed in terms of basic needs, delivery is not sufficiently
developed in most countries and deserves more analysis, investigation, and
subsistence. Success in the electronic governance system, the online public grievance
redressed system(OPGRS), in the opinion of Indian citizens is assessed using an
integrated IS success model. The model incorporates features such as system quality,
information quality, service quality, thought provoking, easy- to-use function,
perceived satisfaction, perceived risk, and ethical purpose. It is therefore emphasized
as a useful tool for a transparent and corruption-free world. Research in shows that the
role of insurance ombudsman complaint is very important and the continued increase
in the number of complaints received by various ombudsmen throughout India shows
that policyholders are benefiting their self-confidence and their reliance on the
Insurance Mediator institution. The research shown in expands on the
recommendations and outcomes of response strategies and open criticism related to
the services provided and managed.
are provided to students, and how their grievances are addressed at various
educational institutions and find out where they are lagging behind or what they are
lagging behind. Using analyzed facts and information, we suggest some additional
features and attributes to fill the hole in the current system. There has been a variety
of research done and papers available in the GRS but they are all owned by state-
owned companies, municipal companies, and e-governance systems or contain only
one or two problems facing students in educational institutions but not in them.
include each domain of student-related complaints. In addition, many systems fail to
deliver complaints in a timely manner so that they can be resolved in a timely and
understandable manner. There is also a need for transparency and proven solutions.
Proper tracking means a systematic approach or process of appealing complaints by
categorizing them by their nature, intensity, and urgency and by referring them to the
relevant authorities. No work has been done directly in the context of the problems
that students face in educational institutions, especially in India. Therefore, there is a
need to create a strong, transparent, fair system that allows for quick and reliable
solutions to all the problems students face. Therefore, a communication gap between
students and the system may be created by the GRS automated system, where students
are often unaware of their rights and therefore do not know what to do and what steps
to take in times of difficulty or difficulty. This lack of knowledge and ignorance of
students is simply due to the vague approach. Sometimes, students do not want to
disclose their identity because of the magnitude of the complaint or fear of harm, and
no such arrangement is available in the current programs of various educational
institutions in India.
Student satisfaction is a major concern for any educational institute. However, many a
time the students fail to express their concerns & issues or fail to reach out for proper
support from the organization. Neither is there any system to address the conflicts or
issues faced by the students. This eventually leads to students' dissatisfaction. Hence,
to maintain the dignity of the college or institute by ensuring a conflict-free
atmosphere by promoting good student-teacher relationships we have developed a
Student Grievance System that will address the students' issues & grievances. The
students can lodge their complaints through this system which will be redressed by
the institute. This python-based student grievance cell will also look into matters of
harassment thus creating a protective environment for students.
CHAPTER 3
SYSTEM ANALYSIS
3.1 EXISITNG SYSTEM:
The existing system is completely manual. In order to write the complaint, the student
either Visits the related department or registers his complaint in the respective
complaint register, which is monitored by the respective Department heads. • Existing
system requires manual process (i.e., sending grievance from lower level to critical
level requires manual process.)
DISADVANTAGES:
Some of the records and information cannot be shared and it is not available
because of the confidentiality. It is a big limitation.
The present study contains only brief information, but not a full pledged and
thorough analysis
Grievance can be lodged based on the level (i.e., university, college, course
and department) and also based on the category (i.e., transportation,
scholarship, lecture time table etc…).
Students can able to track the grievance once the complaint has been
registered.
Students and cell members are provided with a chat box where they can
discuss regarding the grievance.
Student can provide any document as a proof, which makes the complaint
strong.
Cell Member can track the pending and completed grievances.
ADVANTAGES:
CHAPTER 4
Database : MYSQL
CHAPTER 5
SYSTEM DESIGN
In the previous chapter we have identified the functional and non-functional
requirements of the system and produced the analysis model. The following are
discussed in this chapter: design goals, system architecture, system decomposition,
deployment and database design.
The part of the system to be used for the record office should have a fast response
time (real time) with maximum throughput. Furthermore, the system should not be
taking up too much space in memory. The record officer has chosen fast response
time over throughput and hence the system should try to be more interactive. In the
case of the timetabling subsystem, the system should be more reliable in order to
satisfy the constraints than fast response time.
5.1.2 Dependability
The school needs the system to be highly dependable as it is expected to be used by
non- IT professionals. The system should be robust and fault tolerant. Furthermore,
as the system is handling sensitive data of the school, high emphasis should be given
with regards to security, as there are subsystems to be accessed through web.
5.1.3 Maintenance
The system should be easily extensible to add new functionalities at a later stage. It
should also be easily modifiable to make changes to the features and functionalities.
Usability: Usability is the extent to which a product can be used by specified users
to achieve specified goals with effectiveness, efficiency and satisfaction in a
specified context of use. From the end users‘ perspective the system should be
designed in such a way that it is easy to learn and use, efficient and having few
errors if any.
Trade-off is inevitable in trying to achieve a particular design goal. One best case is
the issue of security versus response time. Checking User-Id and Password before a
member can enter to the SMS creates response time problem/overhead. The other
case is the issue of response time versus quality. There is some amount of time taken
by the system to generate the timetable. So the user has to wait a little after telling
the system to generate the timetable and getting the result to get a quality timetable.
The middle tier (web/application server) implements the business logic, controller
logic and presentation logic to control the interaction between the application‘s clients
and data. The controller logic processes client requests such as requests to view
student‘s result, to record attendance or to retrieve data from the database. Business
rules enforced by the business logic dictate how clients can and cannot access
application data and how applications process data.
The client tier is the applications user interface containing data entry forms and client
side applications. It displays data to the user. Users interact directly with the
application through user interface. The client tier interacts with the web/application
server to make requests and to retrieve data from the database. It then displays to the
user the data retrieved from the server.
Enter Detail
No
Password
Conditions exists?
Display customer
Welcome Screen
Send email
Confirmation
Profile Modification
Customer
Login
Yes
Update database
Send confirmatoin
START
END
UML stands for Unified Modeling Language. UML is a language for specifying,
visualizing and documenting the system. This is the step while developing any
product after analysis. The goal from this is to produce a model of the entities
involved in the project which later need to be built. The representation of the entities
that are to be used in the product being developed need to be designed.
Sequence Diagram
Collaboration Diagram
Activity Diagram
Use case diagram can be useful for getting an overall view of the system and
clarifying who can do and more importantly what they can‘t do.
Use case diagram consists of use cases and actors and shows the interaction between
the use case and actors.
The purpose is to show the interactions between the use case and actor.
It is an association between the use cases and actors. An actor represents a real-
world object. Primary Actor – Sender, Secondary Actor, Receiver.
CHAPTER 6
The execution arranges in a system reach out to the benefit of possess right. It
additionally incorporates:
Carefully planned.
Investigation for future work.
Developers should be trained.
6.1 PROJECT MODULES
Student Registration.
University.
Description: This module helps us to register user. The contents are id, name, address
country, state, contact no, mail_id, pan card no, credit card no, and password. After
registration he can book a car, if he is valid. Here we can update, delete, this form.
Sub modules:
Update user details: In this sub module we can update the details of the user
like student name, gender, address, country, state, Contactno,mail_id And we
store these details in database.
Unregistered user: In this sub module the unregistered user can sign up and
do new registration
Search Password: In this sub module we can search the password if the user
forget his password by specifying his full name and E-Mail address.
View users’ details: In this sub module we can view the entire details of the
users who are registered.
The specifications are Student name, marks obtained by him/her in previous study,
type of stream (science/arts) he/she wants to join .They can update search for
colleges by changing their specifications.
Sub modules:
Update Search
Delete specifications
Search college.
View college details.
Update Search: In this sub module we modify the details of the search.By
changing the type of course.
Delete Specifications: In this sub module we delete the specifications and
start a new search if we do not like the college obtained in search
Search College: In this sub module we can search the details of the college.
And the user can select college as their wish.
View College details: In this sub module we can view the college such as
address of college, year of establishment of college. Different types of courses the
college is offering apart from the course we require.
6.3 CODING
<?php
session_start();
error_reporting(0);
include("includes/config.php");
if(isset($_POST['submit']))
$num=mysql_fetch_array($ret);
if($num>0)
$extra="change-password.php";//
$_SESSION['login']=$_POST['username'];
$_SESSION['id']=$num['id'];
$host=$_SERVER['HTTP_HOST'];
$uip=$_SERVER['REMOTE_ADDR'];
$status=1;
$uri=rtrim(dirname($_SERVER['PHP_SELF']),'/\\');
header("location:http://$host$uri/$extra");
exit();
else
$_SESSION['login']=$_POST['username'];
$uip=$_SERVER['REMOTE_ADDR'];
$status=0;
$extra="login.php";
if(isset($_POST['change']))
$email=$_POST['email'];
$contact=$_POST['contact'];
$password=md5($_POST['password']);
$num=mysql_fetch_array($query);
if($num>0)
else
?>
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<!--external css-->
<script type="text/javascript">
function valid()
if(document.forgot.password.value!= document.forgot.confirmpassword.value)
document.forgot.confirmpassword.focus();
return false;
return true;
</script>
</head>
<body>
<!--
*********************************************************************
*********************************************************************
****************
MAIN CONTENT
*********************************************************************
*********************************************************************
***************** -->
<div id="login-page">
<div class="container">
<?php if($errormsg){
echo htmlentities($errormsg);
}?></p>
<?php if($msg){
echo htmlentities($msg);
}?></p>
<div class="login-wrap">
<br>
<label class="checkbox">
<span class="pull-right">
</span>
</label>
<hr>
</form>
<div class="registration">
Create an account
</a>
</div>
</div>
<div class="modal-dialog">
DEPT OF CSE BGSP 25 2021-22
GRIEVANCE MANAGEMENT SYSTEM CODING & IMPLEMENTATION
<div class="modal-content">
<div class="modal-header">
</div>
<div class="modal-body">
<div class="modal-footer">
</div>
</div>
</div>
</div>
</form>
</div>
</div>
<!-- js placed at the end of the document so the pages load faster -->
<script src="assets/js/jquery.js"></script>
<script src="assets/js/bootstrap.min.js"></script>
<!--BACKSTRETCH-->
<!-- You can use an image of whatever size. This script will stretch to fit in any
screen size.-->
<script>
</script>
</body>
</html>
session_start();
error_reporting(0);
include("include/config.php");
if(isset($_POST['submit']))
$username=$_POST['username'];
$password=md5($_POST['password']);
$num=mysql_fetch_array($ret);
if($num>0)
$extra="change-password.php";//
$_SESSION['alogin']=$_POST['username'];
$_SESSION['id']=$num['id'];
$host=$_SERVER['HTTP_HOST'];
$uri=rtrim(dirname($_SERVER['PHP_SELF']),'/\\');
header("location:http://$host$uri/$extra");
exit();
else
$extra="index.php";
$host = $_SERVER['HTTP_HOST'];
$uri = rtrim(dirname($_SERVER['PHP_SELF']),'/\\');
header("location:http://$host$uri/$extra");
exit();
?>
<!DOCTYPE html>
<html lang="en">
<head>
</head>
<body>
<div class="navbar-inner">
<div class="container">
</a>
CMS | Admin
</a>
</ul>
</div>
<div class="wrapper">
<div class="container">
<div class="row">
<div class="module-head">
<h3>Sign In</h3>
</div>
<div class="module-body">
<div class="control-group">
</div>
</div>
<div class="control-group">
</div>
</div>
</div>
<div class="module-foot">
<div class="control-group">
<div class="controls
clearfix"><button type="submit" class="btn btn-primary pull-right"
name="submit">Login</button>
</div>
</div>
</div>
</form>
</div>
</div>
</div>
</div><!--/.wrapper-->
<div class="footer">
<div class="container">
</div>
</div>
</body>
CHAPTER 7
TESTING
7.1 Testing Objectives
Programming Testing is the most critical piece of the developer where the blunders or
blames or the disappointments of the framework is discernable. Programming testing
is one of the predetermined parts of planning, nature of the product and the execution
of code, where the disappointments happens the framework won't gives the legitimate
yield to clients. Disappointments are happened because of the developer's issues, so it
can simple to recognize by the software engineers. It might bring about the
disappointment for the framework, so the software engineer ought to know about
outlining devices, scraps for changing the conduct of framework. In the wake of
creating stage, programming testing is vital to break up the deficiencies rapidly.
Testing is a synchronized procedure where the data is taken care by improvement
group.
Dissimilar to every module gives the required yield, the assurance of test designer
prompts the rightness of framework projects. The last module stage is intended to
maintain a strategic distance from the disappointments and to expel deficiencies. So
it's ideal to give the testing stage to the advancement of the venture.
―A successful test to be carried out which holds the capability of finding errors.‖
―Planning of testing phase may required long time.‖
―The tests are performed according to the clients need.‖
―Effective test should require for detecting all errors.‖
―Exhaustive testing is not possible‖
the exercises performed for programming testing and its serves to approve the yield
work.
Unit Test
Integration Test
System Test
b. Interface errors
d. Performance errors
As shown in the following figure of Black box testing, we are not thinking of the
internal workings, just we think about
Unit testing
Integration testing
Functionality testing
System testing
Unit Testing
Unit testing focuses on the building blocks of the software system, that is, objects and
sub system. There are three motivations behind focusing on components. First, unit
testing reduces the complexity of the overall tests activities, allowing us to focus on
smaller units of the system. Second, unit testing makes it easier to pinpoint and
correct faults given that few components are involved in this test.Third, unit testing
allows parallelism in testing activities that is each component can be tested
independently of one another. Hence the goal is to test the internal logic of module.
Integration Testing
In the integration testing test modules are combined into subsystems, which are the n
tested. The goal here is to see if the modules can be integrated properly, the emphasis
being on testing module interaction. After structural testing and functional testing I
get error free modules. These modules are 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.
System Testing
In system testing the entire software is tested. The reference document for this process
is the requirement document and the goal is to see whether the software meets its
requirements. The system was tested for various test cases with various inputs
Incorrect path Allows user to enter correct tem path Incorrect system path
system
Correct path Console Console
Pass: yes Conditional pass Fail
Test description Machine should identify the written digit from the image
CHAPTER 8
SNAPSHOTS
CONCLUSION
The project ―STUDENT GRIEVANCE READDRESAL CELL‖ is designed in order
to reduce the burden of maintaining bulk of records of all students‘ grievance details
of who study in Educational Institution. Maintaining the project and database is also
easy and manageable. The fact that there are hardly such systems prevailing curtailing
to the complaint redressed for students enrolled in numerous organizations. This
project has demonstrated a proposed Grievance system for the grievance redressed of
students covering various domains of complaints which could be lodged easily and
thus leading to easy and sure solutions to the problems being faced by a student on a
regular basis. Inserting, Retrieving, Updating the details of all users are easy. ―Finally,
online student grievance system comes out as better, quicker, simpler management
analyser‖.
Future Enhancement
System works on the grounds for resolving student grievances and currently serves as
a Web application between various members as well the intended audience. To
expand this to meet various needs, the following enhancements are suggested:
1. Although many future improvements to the operating system are possible, The
main focus includes the development of mobile application to increasing application
mobility as the future separates the use of mobile applications and as it seems mobile
devices are ubiquitous which will make it easier to get all the notifications in the cell
call by members and students associated with the application also increase the
reliability of the system and the level of problem solving.
3. A toll- free hotline can be obtained 24*7 on the basis of victims to lodge
emergency complaints or to seek legal advice in the event of a disaster. 4. Above all,
the tracker can be added as part of future ideas to track the performance of the various
committee members involved in the system on the basis of the provided aspect of the
report production .
BIBLIOGRAPHY
[1] A Prototype for Grievance Redressal System (2018): ShaligramPrajapat,
Vaibhav Sabarwal and Varun Wadhwani.
[2] Online Grievance Redressal System (2019): Mukesh Buldak, Shrikant
Pandhekar, Afzal Gigani, AmreshsinhKachwah.
[3] Complaints and Grievance Management System: prof. H.N.Renushe, prof. Mrs
S.V.Deshmukh, prof.Mrs.D.Y.Jadhav
[6] Subhash, C., Ashwani K.: Assessing grievances redressing mechanism in India.
Int. J. Comput. Appl. 52(5), 12–19 (2012)
[7] Dipankar, M.: Solution towards effective complaint registration system in Indian
scenario. In: IJCA Proceedings on National Conference on Advancement of
Technologies—Information Systems & Computer Networks (ISCON—2012),
vol. 1, pp. 1–2 (2012)
[8] Varun, G.: Redressing grievances and complaints regarding basic service
delivery. World Dev. 41, 109–119 (2013)
[9] Nripendra, P.R., Yogesh, K.D., Michael, D.W., Vishanth, W.: Investigating
success of an e-government initiative: validation of an integrated IS success
model. Inf. Syst. Front. 17(1), 127–142 (2015)
[10] Rajesh, K.Y., Sarvesh, M.: Role of insurance ombudsman and grievance
management in life insurance services in Indian perspective. Int. Lett. Soc.
Humanist. Sci. 31, 9–13 (2014)