Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 97

ONLINE CAMPUS GRIEVANCE

A Project Report
In partial fulfilment of the requirements for the Award of the Degree of

MASTER OF SCIENCE IN COMPUTER SCIENCE

By

G.Ezhilarasi
[BP120507]

Under the Guidance of

Ms. M. Poovizhi, MCA., M.Phil

DEPARTMENT OF COMPUTER SCIENCE


SACRED HEART COLLEGE
(Autonomous, affiliated to the Thiruvalluvar University)
Tirupattur - 635601
Vellore Dt .
APRIL – 2014
CERTIFICATE
This is to certify that the project entitled ‘Online Campus Grievance’ being submitted to Sacred
Heart College (Autonomous), Tirupattur, by G.Ezhilarasi for the partial fulfillment for the
award of degree of Master of Computer Science is a bonafide record of the work carried out by
them, under my guidance and supervision.

Date: ______________

Project Guide

Submitted for Viva-Voce examination on _________________

Examiners:
1.
2.
AKNOWLEDGEMENT
We thank almighty god for his blessing and graces by which we were able to complete project
successfully. We sincerely thank our parents who have gifted us this life to attain our
achievements.

We extremely thank Rev.Dr.C.M.Varghese , principal of Sacred Heart College (Autonomous),


Tirupattur. We express our deep sense of gratitude to Dr.L.Ravi, Head of Department, who is
the source of inspiration to pursue with every efficient work.

We heartfully honour our guide Ms.M.Poovizhi, Asst Professor for her valuable guidance and
encouragement of our every activities.

We would like to thank the entire teaching and non-teaching staffs of the Department of
computer science for helping us to complete the project successfully. Finally, we thank each and
every friend of us, especially who have assisted us in completing our project work.

G.Ezhilarasi
TABLE OF CONTENTS

S.No Contents Page No


1 Introduction
1.1 Summary of the Project
2 Requirements Analysis
2.1 System Study
2.2 Vision Document
2.3 Use Case Specification
3 Design Document
3.1 Architectural Design
3.2 Database Design
3.3 Class Diagram
3.4 Sequence Design
3.5 Component Diagram
3.6 Interface Design
3.7 Test Case Design
4 Implementation
4.1 Overview of the Implementation
5 Test Case Document
5.1 Unit Testing
5.2 Integration Testing
5.3 System Testing
6 Conclusion
6.1 Summary
6.2 Future Enhancements
References
Appendices
Appendix A
Project Proposal
Appendix B
Project Plan
Appendix C
Project Review Record – I
Project Review Record – II
Project Review Record – III
Project Review Record – IV
Project Review Record – V
Appendix D
Screen shots
Program Code
1. Introduction

1.1 Summary of the Project


“Online Campus Grievance” is used to gather all the complaints in the Sacred Heart College
campus and give required solution through online without need of any manual entries and update
it automatically so that less time consuming and more efficient. The person who want to post a
complaint about any person, equipments, environment, food in canteen and sports in the campus
post their complaint through this application. The solution for the compliant will be given by the
admin.
2. Requirements Analysis

2.1. System Study

2.1.1 Introduction
Online Campus Grievance is a web based system. This is helpful for the students , staffs and all
officials to get the solutions to their problems in online. Also the each individual person can post
their problem and solution will be given by the admin.
2.1.2 Existing System
There are many existing system which are all static so we need to manually update all the details
about the complaints regularly. For this purpose there is a need of a dynamic web pages which
was the reason for the existence of this project
Drawback of Existing System

The problems, which are perceived by the users in existing systems, are

 It is time consuming.
 It leads to error results.
 It consumes lot of manpower to better results.
 It lacks of data security.
 Retrieval of data takes lot of time.
 Percentage of accuracy is less.

2.1.3 Proposed System:

The main need for the proposed system is everything is dynamic no needed to be updated
manually everything is updated automatically and less human resource is needed and less time
consuming for rectifying the problem.
proposed system has several advantages
 To reduce the manual work.
 To save the time.
 Error free
 More Storage Capacity
2.1.4 List of Modules
1. Admin
2. Students Grievance
2.1 Grievance on staff
2.2 Grievance on student
2. 3 Grievance on equipments
2.4 Grievance on Environment
2.5 Grievance on food in canteen
2.6 Grievance on sports
2.7 General Grievance
3. Staffs Grievance
3.1 Grievance on student
3.2 Grievance on staff
3. 3 Grievance on equipments
3.4 Grievance on Environment
3.5 Grievance on food in canteen
3.6 Grievance on sports
3.7 General Grievance
4. Non teaching staffs Grievance
4.1 Grievance on student
4.2 Grievance on staff
4. 3 Grievance on equipments
4.4 Grievance on Environment
4.5 Grievance on food in canteen
4.6 Grievance on sports
4.7 General Grievance
5. Lab technicians Grievance
5.1 Grievance on student
5.2 Grievance on staff
5. 3 Grievance on equipments
5.4 Grievance on Environment
5.5 Grievance on food in canteen
5.6 Grievance on Sports
5.7 General Grievance
2.1.5 Description of Modules
Module No: 1
Module Name:
Admin
Description:
Admin module is used to view all the posted grievances and can give solution to the
grievances by admin.
Activities:
Activity: 01
Activity name:
Admin
Purpose:
The purpose of this activity is to view and give solution to the grievances by admin.
Entry Criteria:
Authorized Login
Input:
View grievances, give solution.
Output:
Solutions to the grievances will be given by admin
Exit Criteria:
Solutions are send through email.
Alternative Flow:
In case the solutions are not send to the complainer email id due to some problem, show
the user that the mail sending failed.

Module No: 2
Module Name:
Students Grievance
Description:
Students Grievance module is used to post the grievance on staff, student, equipment,
environment, food in canteen, sports and general grievances only by the students. And also
the students can receive the solution from the admin.
It works with 7 sub modules
Sub module 1: Grievance on staff
Sub module 2: Grievance on student
Sub module 3: Grievance on equipment
Sub module 4: Grievance on environment
Sub module 5: Grievance on food in canteen
Sub module 6: Grievance on sports
Sub module 7: General Grievance
Sub Module No: 1
Module Name:
Grievance on staff
Description:
Grievance on staff module is used to post grievance on staff by the students .
Activities:
Activity: 01
Activity name:
Grievance on staff
Purpose:
The purpose of the activity is to post the grievance on staff by the students.
Entry Criteria:
Authorized Login
Input:

Complainer name, indict on whom, designation, department, shift, grievance description,


when did this incident occur, expected solution, expected by when, mailing address, date
of post.
Output:
Grievance on staff is posted successfully by the students
Exit Criteria:
Uploaded grievances on staff are stored in the data base.
Alternative Flow:
In case the grievances on staff details are not stored in the database due to some problem,
show the user that the details are not stored in the database.
Sub Module No: 2
Module Name:
Grievance on student
Description:
Grievance on student module is used to post grievance on student by the students.
Activities:
Activity: 01
Activity name:
Grievance on student
Purpose:
The purpose of the activity is to post the grievance on student by the students.
Entry Criteria:
Authorized Login
Input:
Complainer name, indict on whom, department, year, shift, grievance description, when
did this incident occur, expected solution, expected by when, mailing address, date of
post.
Output:
Grievance on student is posted successfully
Exit Criteria:
Uploaded grievances on student are stored in the data base.
Alternative Flow:
In case the grievances on student details are not stored in the database due to
some problem, show the user that the details are not stored in the database.
Sub Module No: 3
Module Name:
Grievance on equipment
Description:
Grievance on equipment module is used to post grievance on equipment by the
students.
Activities:
Activity: 01
Activity name:
Grievance on equipment
Purpose:
The purpose of the activity is to post the grievance on equipment.
Entry Criteria:
Authorized Login
Input:
Complainer name, department, grievance description, expected solution, expected
by when, mailing address, date of post.
Output:
Grievance on equipment is posted successfully
Exit Criteria:
Uploaded grievances on equipment are stored in the data base.
Alternative Flow:
In case the grievances on equipment details are not stored in the database due to some
problem, show the user that the details are not stored in the database.
Sub Module No: 4
Module Name:
Grievance on environment
Description:
Grievance on environment module is used to post grievance on environment by the
students.
Activities:
Activity: 01
Activity name:
Grievance on environment
Purpose:
The purpose of the activity is to post the grievance on environment by the students.
Entry Criteria:
Authorized Login
Input:
Complainer name, department, grievance description, expected solution, expected by
when, mailing address, date of post.
Output:
Grievance on environment is posted successfully
Exit Criteria:
Uploaded grievances on environment are stored in the data base.

Alternative Flow:
In case the grievances on environment details are not stored in the database due to
some problem, show the user that the details are not stored in the database.
Sub Module No: 5
Module Name:
Grievance on food in canteen
Description:
Grievance on food in canteen module is used to post grievance on food provided in
canteen by the students.
Activities:
Activity: 01
Activity name:
Grievance on food in canteen
Purpose:
The purpose of the activity is to post the grievance on food in canteen by the students.
Entry Criteria:
Authorized Login
Input:
Complainer name, grievance description, expected solution, expected by when, mailing
address, date of post.
Output:
Grievance on food in canteen is posted successfully
Exit Criteria:
Uploaded grievances on food in canteen are stored in the data base.
Alternative Flow:
In case the grievances on food in canteen are not stored in the database due to some
problem, show the user that the details are not stored in the database.
Sub Module No: 6
Module Name:
Grievance on sports
Description:
Grievance on sports module is used to post grievance on sports by the students.
Activities:
Activity: 01
Activity name:
Grievance on sports
Purpose:
The purpose of the activity is to post the grievance on sports by the students.
Entry Criteria:
Authorized Login
Input:
Complainer name, indict on whom grievance description, when did this incident occur,
expected solution, expected by when, mailing address, date of post.
Output:
Grievance on sports is posted successfully
Exit Criteria:
Uploaded grievances on sports are stored in the data base.
Alternative Flow:
In case the grievances on sports are not stored in the database due to some problem,
show the user that the details are not stored in the database.
Sub Module No: 7
Module Name:
General grievance
Description:
General grievance module is used to post grievance on general things by the
students.
Activities:
Activity: 01
Purpose:
The purpose of the activity is to post the general grievance by the students.
Entry Criteria:
Authorized Login
Input:
Complainer name, indict on whom grievance description, when did this incident occur,
expected solution, expected by when, mailing address, date of post.
Output:
General grievance is posted successfully
Exit Criteria:
Uploaded general grievances are stored in the data base.

Alternative Flow:
In case the general grievance details are not stored in the database due to some
problem, show the user that the details are not stored in the database.
Module No: 3
Module Name:
Staffs Grievance
Description:
Staffs Grievance module is used to post the grievance on staff, student, equipment,
environment, food in canteen, sports and general grievances only by the staffs. And also the
staff can receive the solution from the admin.
It works with 7 sub modules
Sub module 1: Grievance on staff
Sub module 2: Grievance on student
Sub module 3: Grievance on equipment
Sub module 4: Grievance on environment
Sub module 5: Grievance on food in canteen
Sub module 6: Grievance on sports
Sub module 7: General Grievance
Sub Module No: 1
Module Name:
Grievance on staff
Description:
Grievance on staff module is used to post grievance on staff by the staff .
Activities:
Activity: 01
Activity name:
Grievance on staff
Purpose:
The purpose of the activity is to post the grievance on staff.
Entry Criteria:
Authorized Login
Input:
Complainer name, indict on whom, designation, department, shift, grievance description,
when did this incident occur, expected solution, expected by when, mailing address, date
of post.
Output:
Grievance on staff is posted successfully by the staff
Exit Criteria:
Uploaded grievances on staff are stored in the data base.
Alternative Flow:
In case the grievances on staff details are not stored in the database due to some problem,
show the user that the details are not stored in the database.
Sub Module No: 2
Module Name:
Grievance on student
Description:
Grievance on student module is used to post grievance on student by the staff.
Activities:
Activity: 01
Activity name:
Grievance on student
Purpose:
The purpose of the activity is to post the grievance on student by the staff.
Entry Criteria:
Authorized Login
Input:
Complainer name, indict on whom, department, year, shift, grievance description, when
did this incident occur, expected solution, expected by when, mailing address, date of
post.
Output:
Grievance on student is posted successfully
Exit Criteria:
Uploaded grievances on student are stored in the data base.
Alternative Flow:
In case the grievances on student details are not stored in the database due to
some problem, show the user that the details are not stored in the database.
Sub Module No: 3
Module Name:
Grievance on equipment
Description:
Grievance on equipment module is used to post grievance on equipment by the
staff.
Activities:
Activity: 01
Activity name:
Grievance on equipment
Purpose:
The purpose of the activity is to post the grievance on equipment.
Entry Criteria:
Authorized Login
Input:
Complainer name, department, grievance description, expected solution, expected
by when, mailing address, date of post.
Output:
Grievance on equipment is posted successfully
Exit Criteria:
Uploaded grievances on equipment are stored in the data base.
Alternative Flow:
In case the grievances on equipment details are not stored in the database due to some
problem, show the user that the details are not stored in the database.
Sub Module No: 4
Module Name:
Grievance on environment
Description:
Grievance on environment module is used to post grievance on environment by the staff.
Activities:
Activity: 01
Activity name:
Grievance on environment
Purpose:
The purpose of the activity is to post the grievance on environment by the staff.
Entry Criteria:
Authorized Login
Input:
Complainer name, department, grievance description, expected solution, expected by
when, mailing address, date of post.
Output:
Grievance on environment is posted successfully
Exit Criteria:
Uploaded grievances on environment are stored in the data base.

Alternative Flow:
In case the grievances on environment details are not stored in the database due to
some problem, show the user that the details are not stored in the database.
Sub Module No: 5
Module Name:
Grievance on food in canteen
Description:
Grievance on food in canteen module is used to post grievance on food provided in
canteen by staff.
Activities:
Activity: 01
Activity name:
Grievance on food in canteen
Purpose:
The purpose of the activity is to post the grievance on food in canteen by the staff.
Entry Criteria:
Authorized Login
Input:
Complainer name, grievance description, expected solution, expected by when, mailing
address, date of post.
Output:
Grievance on food in canteen is posted successfully
Exit Criteria:
Uploaded grievances on food in canteen are stored in the data base.
Alternative Flow:
In case the grievances on food in canteen are not stored in the database due to some
problem, show the user that the details are not stored in the database.
Sub Module No: 6
Module Name:
Grievance on sports
Description:
Grievance on sports module is used to post grievance on sports by the staff.
Activities:
Activity: 01
Activity name:
Grievance on sports
Purpose:
The purpose of the activity is to post the grievance on sports by the staff.
Entry Criteria:
Authorized Login
Input:
Complainer name, indict on whom grievance description, when did this incident occur,
expected solution, expected by when, mailing address, date of post.
Output:
Grievance on sports is posted successfully
Exit Criteria:
Uploaded grievances on sports are stored in the data base.
Alternative Flow:
In case the grievances on sports are not stored in the database due to some problem,
show the user that the details are not stored in the database.
Sub Module No: 7
Module Name:
General grievance
Description:
General grievance module is used to post grievance on general things by the staff.
Activities:
Activity: 01
Purpose:
The purpose of the activity is to post the general grievance by the staff.
Entry Criteria:
Authorized Login
Input:
Complainer name, indict on whom grievance description, when did this incident occur,
expected solution, expected by when, mailing address, date of post.
Output:
General grievance is posted successfully
Exit Criteria:
Uploaded general grievances are stored in the data base.

Alternative Flow:
In case the general grievance details are not stored in the database due to some problem, show
the user that the details are not stored in the database.
Module No: 4
Module Name:
Non Teaching Staffs Grievance
Description:
Non Teaching Staffs Grievance module is used to post the grievance on staff, student,
equipment, environment, food in canteen, sports and general grievances only by thenon
teaching staffs. And also the non teaching staff can receive the solution from the admin.
It works with 7 sub modules
Sub module 1: Grievance on staff
Sub module 2: Grievance on student
Sub module 3: Grievance on equipment
Sub module 4: Grievance on environment
Sub module 5: Grievance on food in canteen
Sub module 6: Grievance on sports
Sub module 7: General Grievance
Sub Module No: 1
Module Name:
Grievance on staff
Description:
Grievance on staff module is used to post grievance on staff by the non teaching staffs .
Activities:
Activity: 01
Activity name:
Grievance on staff
Purpose:
The purpose of the activity is to post the grievance on staff.
Entry Criteria:
Authorized Login
Input:

Complainer name, indict on whom, designation, department, shift, grievance description,


when did this incident occur, expected solution, expected by when, mailing address, date
of post.
Output:
Grievance on staff is posted successfully by the non teaching staffs.
Exit Criteria:
Uploaded grievances on staff are stored in the data base.
Alternative Flow:
In case the grievances on staff details are not stored in the database due to some problem,
show the user that the details are not stored in the database.
Sub Module No: 2
Module Name:
Grievance on student
Description:
Grievance on student module is used to post grievance on student by the non
teaching staffs.
Activities:
Activity: 01
Activity name:
Grievance on student
Purpose:
The purpose of the activity is to post the grievance on student by the non teaching staff.
Entry Criteria:
Authorized Login
Input:
Complainer name, indict on whom, department, year, shift, grievance description, when
did this incident occur, expected solution, expected by when, mailing address, date of
post.
Output:
Grievance on student is posted successfully
Exit Criteria:
Uploaded grievances on student are stored in the data base.
Alternative Flow:
In case the grievances on student details are not stored in the database due to
some problem, show the user that the details are not stored in the database.
Sub Module No: 3
Module Name:
Grievance on equipment
Description:
Grievance on equipment module is used to post grievance on equipment by the
non teaching staffs.
Activities:
Activity: 01
Activity name:
Grievance on equipment
Purpose:
The purpose of the activity is to post the grievance on equipment.
Entry Criteria:
Authorized Login
Input:
Complainer name, department, grievance description, expected solution, expected
by when, mailing address, date of post.
Output:
Grievance on equipment is posted successfully
Exit Criteria:
Uploaded grievances on equipment are stored in the data base.
Alternative Flow:
In case the grievances on equipment details are not stored in the database due to some
problem, show the user that the details are not stored in the database.
Sub Module No: 4
Module Name:
Grievance on environment
Description:
Grievance on environment module is used to post grievance on environment by the
non teaching staff.
Activities:
Activity: 01
Activity name:
Grievance on environment
Purpose:
The purpose of the activity is to post the grievance on environment by the non
teaching staffs.
Entry Criteria:
Authorized Login
Input:
Complainer name, department, grievance description, expected solution, expected by
when, mailing address, date of post.
Output:
Grievance on environment is posted successfully
Exit Criteria:
Uploaded grievances on environment are stored in the data base.

Alternative Flow:
In case the grievances on environment details are not stored in the database due to
some problem, show the user that the details are not stored in the database.
Sub Module No: 5
Module Name:
Grievance on food in canteen
Description:
Grievance on food in canteen module is used to post grievance on food provided in
canteen by staff.
Activities:
Activity: 01
Activity name:
Grievance on food in canteen
Purpose:
The purpose of the activity is to post the grievance on food in canteen by the non
teaching staff.
Entry Criteria:
Authorized Login
Input:
Complainer name, grievance description, expected solution, expected by when, mailing
address, date of post.
Output:
Grievance on food in canteen is posted successfully
Exit Criteria:
Uploaded grievances on food in canteen are stored in the data base.
Alternative Flow:
In case the grievances on food in canteen are not stored in the database due to some
problem, show the user that the details are not stored in the database.
Sub Module No: 6
Module Name:
Grievance on sports
Description:
Grievance on sports module is used to post grievance on sports by the non teaching staffs.
Activities:
Activity: 01
Activity name:
Grievance on sports
Purpose:
The purpose of the activity is to post the grievance on sports by the non teaching staff.
Entry Criteria:
Authorized Login
Input:
Complainer name, indict on whom grievance description, when did this incident occur,
expected solution, expected by when, mailing address, date of post.
Output:
Grievance on sports is posted successfully
Exit Criteria:
Uploaded grievances on sports are stored in the data base.
Alternative Flow:
In case the grievances on sports are not stored in the database due to some problem,
show the user that the details are not stored in the database.
Sub Module No: 7
Module Name:
General grievance
Description:
General grievance module is used to post grievance on general things by the non
teaching staff.
Activities:
Activity: 01
Purpose:
The purpose of the activity is to post the general grievance by the non teaching staffs.
Entry Criteria:
Authorized Login
Input:
Complainer name, indict on whom grievance description, when did this incident occur,
expected solution, expected by when, mailing address, date of post.
Output:
General grievance is posted successfully
Exit Criteria:
Uploaded general grievances are stored in the data base.

Alternative Flow:
In case the general grievance details are not stored in the database due to some problem, show
the user that the details are not stored in the database.
Module No: 5
Module Name:
Staffs Grievance
Description:
Lab technicians Grievance module is used to post the grievance on staff, student,
equipment, environment, food in canteen, sports and general grievances only by the lab
technicians. And also the lab technicians can receive the solution from the admin.
It works with 7 sub modules
Sub module 1: Grievance on staff
Sub module 2: Grievance on student
Sub module 3: Grievance on equipment
Sub module 4: Grievance on environment
Sub module 5: Grievance on food in canteen
Sub module 6: Grievance on sports
Sub module 7: General Grievance
Sub Module No: 1
Module Name:
Grievance on staff
Description:
Grievance on staff module is used to post grievance on staff by the lab technicians .
Activities:
Activity: 01
Activity name:
Grievance on staff
Purpose:
The purpose of the activity is to post the grievance on staff.
Entry Criteria:
Authorized Login
Input:
Complainer name, indict on whom, designation, department, shift, grievance description,
when did this incident occur, expected solution, expected by when, mailing address, date
of post.
Output:
Grievance on staff is posted successfully by the lab technicians.
Exit Criteria:
Uploaded grievances on staff are stored in the data base.
Alternative Flow:
In case the grievances on staff details are not stored in the database due to some problem,
show the user that the details are not stored in the database.
Sub Module No: 2
Module Name:
Grievance on student
Description:
Grievance on student module is used to post grievance on student by the lab technicians.
Activities:
Activity: 01
Activity name:
Grievance on student
Purpose:
The purpose of the activity is to post the grievance on student by the lab technicians.
Entry Criteria:
Authorized Login
Input:
Complainer name, indict on whom, department, year, shift, grievance description, when
did this incident occur, expected solution, expected by when, mailing address, date of
post.
Output:
Grievance on student is posted successfully
Exit Criteria:
Uploaded grievances on student are stored in the data base.
Alternative Flow:
In case the grievances on student details are not stored in the database due to
some problem, show the user that the details are not stored in the database.
Sub Module No: 3
Module Name:
Grievance on equipment
Description:
Grievance on equipment module is used to post grievance on equipment by the
lab technicians.
Activities:
Activity: 01
Activity name:
Grievance on equipment
Purpose:
The purpose of the activity is to post the grievance on equipment.
Entry Criteria:
Authorized Login
Input:
Complainer name, department, grievance description, expected solution, expected
by when, mailing address, date of post.
Output:
Grievance on equipment is posted successfully
Exit Criteria:
Uploaded grievances on equipment are stored in the data base.
Alternative Flow:
In case the grievances on equipment details are not stored in the database due to some
problem, show the user that the details are not stored in the database.
Sub Module No: 4
Module Name:
Grievance on environment
Description:
Grievance on environment module is used to post grievance on environment by the lab
technicians.
Activities:
Activity: 01
Activity name:
Grievance on environment
Purpose:
The purpose of the activity is to post the grievance on environment by the lab technicians.
Entry Criteria:
Authorized Login
Input:
Complainer name, department, grievance description, expected solution, expected by
when, mailing address, date of post.
Output:
Grievance on environment is posted successfully
Exit Criteria:
Uploaded grievances on environment are stored in the data base.

Alternative Flow:
In case the grievances on environment details are not stored in the database due to
some problem, show the user that the details are not stored in the database.
Sub Module No: 5
Module Name:
Grievance on food in canteen
Description:
Grievance on food in canteen module is used to post grievance on food provided in
canteen by staff.
Activities:
Activity: 01
Activity name:
Grievance on food in canteen
Purpose:
The purpose of the activity is to post the grievance on food in canteen by the lab
technicians.
Entry Criteria:
Authorized Login
Input:
Complainer name, grievance description, expected solution, expected by when, mailing
address, date of post.
Output:
Grievance on food in canteen is posted successfully
Exit Criteria:
Uploaded grievances on food in canteen are stored in the data base.
Alternative Flow:
In case the grievances on food in canteen are not stored in the database due to some
problem, show the user that the details are not stored in the database.
Sub Module No: 6
Module Name:
Grievance on sports
Description:
Grievance on sports module is used to post grievance on sports by the lab technicians.
Activities:
Activity: 01
Activity name:
Grievance on sports
Purpose:
The purpose of the activity is to post the grievance on sports by the lab technicians.
Entry Criteria:
Authorized Login
Input:
Complainer name, indict on whom grievance description, when did this incident occur,
expected solution, expected by when, mailing address, date of post.
Output:
Grievance on sports is posted successfully
Exit Criteria:
Uploaded grievances on sports are stored in the data base.
Alternative Flow:
In case the grievances on sports are not stored in the database due to some problem,
show the user that the details are not stored in the database.
Sub Module No: 7
Module Name:
General grievance
Description:
General grievance module is used to post grievance on general things by the lab
technicians.
Activities:
Activity: 01
Purpose:
The purpose of the activity is to post the general grievance by the lab technicians.
Entry Criteria:
Authorized Login
Input:
Complainer name, indict on whom grievance description, when did this incident occur,
expected solution, expected by when, mailing address, date of post.
Output:
General grievance is posted successfully
Exit Criteria:
Uploaded general grievances are stored in the data base.

Alternative Flow:
In case the general grievance details are not stored in the database due to some problem, show
the user that the details are not stored in the database.
2.1.6 Data flow diagram
Level: 0

Level: 1
2.2 Vision Document

2.2.1 Introduction
Online Campus Grievance is a web based system. This is helpful for the students , staffs and
all officials to get the solutions to their problems in online. Also the each individual person can
post their problem and solution will be given by the admin
2.2.2 Scope
This vision document applies to online campus grievance which is to maintain all the
grievances from different areas in the campus. Analyses and rectify the problems and maintain
the record of all the posted grievances and also get the solution from the admin.
2.2.3 Positioning:
Business opportunity:
Online campus grievance will support to add some features to the present existing system of
getting grievances manually. The current system is not reliable because it is time consuming. So
the new system will enable the students, staffs, non teachings staffs and lab technicians interact
through this application regarding grievances.

Problem Statement:
The problem of OCG (ONLINE CAMPUS GRIEVANCE)

Affects Staff, student , all the other workers and higher authorities

The impact of which is Manually visiting each person and posting the complaint is very

difficult and gives more work and stress to the faculties

A successful solution Computerized system helpful to admin, staffs, students, non

would be teaching staffs and lab technicians to post their grievances

Product position statement:

For The students, staffs, other workers and higher authorities


Product Online campus grievance
name
Who For time consume
That Help the staff as well as students and other workers to get solution

Unlike Existing manual system


This Reduces the manual work.
application

Key stakeholder needs:

Need Priorities Current solution Proposed solution


Automating the activities High Manual system Computerized
grievances system

Stakeholder and user descriptions:


This stakeholder and user description solution describes the members of sacred heart
college.All the stake holders are user.
Name Responsibility Description
Staffs Adds the grievances through Who post their grievances
online.
Student Adds the grievances through Who post their grievances
online.
Admin View the grievances Responsible person will give solution for the
grievances

User Environment:
The users are well known to computers.

Hardware environment;
processor : Intel Pentium
RAM : 2 GB
Hard disk : 500 GB

Software environment
Front End : Asp.net (Microsoft visual studio
2010)
Back End : Sql server 2008
Programming : C#
language
Scripting language : Java script
Browser : Mozilla fire fox, Internet explorer
Web server : IIS

Product features:
This section describes a high level view of online campus grievance.
Data Maintenance:
1. Maintaining staff grievances.
2. Maintaining student’s grievances.
3. Maintaining non teaching staffs grievances
4. Maintaining lab technicians grievances
Quality Ranges:
Quality ranges section defines the quality range for performance robustness, fault tolerance and
similar characteristic for online campus grievance.
Availability:
The system shall be available for 14 hours a day 7 days in a week.
Usability:
The System shall be easy to use and shall be appropriate for eh students and computer literate
the system shall include easy navigation for the user.
Maintainability:
The system shall be designed for ease of maintenance
2.3 Use Case Specification
Use case UC01
Use case Name Registration
Description To maintain registration
Actor User
Basic flow 1. Registration
Select the support data such as dept, shift and class
Enter name and Reg No
Click on registration

Alternative flow Registration


Save the record without filling the mandatory fields
Record should not be saved and message should be handled to
get complete and correct data

Preconditions 1.Admin should login to the system


2.support data for dept, course and class should be available
Post conditions grievance should be saved/edited/deleted
Validation Regno, username and password should be unique
Frequency Daily
Priority High

Module Name User


Use case UC02
Use case Name Login
Description To post the grievances
Actor User
Basic flow 1. Login
Give username and password
Click login

Alternative flow
If User name and password in not correct. User can’t post grievances

Preconditions 1.Admin should login to the system


2.support data for dept, course and class should be available
Post conditions grievance details should be saved/edited/deleted
Validation Username and password should be unique
Frequency Daily
Priority High

Module Name User


Use case UC03
Use case Name Enter the grievance
Description To maintain grievance
Actor User
Basic flow 1. Add grievance
Select the support data such as dept, course and class
Enter name and Reg No
Click on post

Alternative flow Add grievance


Save the record without filling the mandatory fields
Record should not be saved and message should be handled to
get complete and correct data

Preconditions 1.Admin should login to the system


2.support data for dept, course and class should be available
Post conditions grievance should be saved/edited/deleted
Validation Regno, username and password should be unique
Frequency Daily
Priority High

Module Name User


Use case UC04
Use case Name post the grievance
Description To post grievance
Actor User
Basic flow 1. Add grievance
Select the support data such as dept, course and class
Enter name and Reg No
Click on post
Alternative flow Add grievance
Save the record without filling the mandatory fields
Record should not be saved and message should be handled to
get complete and correct data

Preconditions 1.Admin should login to the system


2.support data for dept, course and class should be available
Post conditions grievance should be saved/edited/deleted
Validation Regno, username and password should be unique
Frequency Daily
Priority High

Module Name User


Use case UC05
Use case Name Give feedback
Description To maintain feedback
Actor User
Basic flow 1. Add feedback
Select the support data such as dept, course and class
Enter name and Reg No
Click on Submit
2. Delete feedback
Select the record to be deleted
Click on delete
3. View feedback
1. Added grievance details will be listed

Alternative flow Add feedback


Save the record without filling the mandatory fields
Record should not be saved and message should be handled to
get complete and correct data

Preconditions 1.Admin should login to the system


2.support data for dept, course and class should be available
Post conditions feedback should be saved/deleted
Validation Regno, username and password should be unique
Frequency Daily
Priority High
Module Name Admin
Use case UC01
Use case Name Login
Description To view and give solution to grievances
Actor User
Basic flow 1. Login
Give username and password
Click login

Alternative flow
If User name and password in not correct. Admin can’t view and give
solution to the posted grievances
Preconditions 1.Admin should login to the system
2.support data for dept, course and class should be available
Post conditions Solution will send to responsible person
Validation Username and password should be unique
Frequency Daily
Priority High

Module Name Admin


Use case UC02
Use case Name View the grievances
Description To view grievance
Actor Admin
Basic flow 1. View grievance
1. Added grievance will be listed
2. Delete grievances
Select the record to be deleted
Click on delete

Alternative flow view grievance


Save the record without filling the mandatory fields
Record should not be viewed

Preconditions 1.Admin should login to the system


2.support data for dept, course and class should be available
Post conditions grievance should be viewed
Validation Username and password should be unique
Frequency Daily
Priority High

Module Name Admin


Use case UC03
Use case Name Give solution
Description To give solution to the posted grievances
Actor Admin
sBasic flow 1. View grievance details
1. Added grievances will be listed
2. Give solution

Preconditions 1.Admin should login to the system


2.View the posted grievances
Post conditions Solution will be given
Validation Username and password should be unique
Frequency Daily
Priority High

3. Design Document

3.1. Architecture Diagram


3.2. Database Design

Registration :
Field Type Constraints Description
Username Varchar(20) - Specifies the user name of the user
Password Varchar(20) - Specifies the password of the user
Confirm password Varchar(20) - Specifies the confirm password of the user
Email address Varchar(20) - Specifies the email address of the user
Phone number Int - Specifies the phone no of the user
Date Date - Specifies register date of the user

Grievance on staff:
Field Type Constraints Description
Complainer name Varchar(20) - Specifies the Name of the complainer
Indict on whom Varchar(20) - Specifies the name of the indict
Designation Varchar(20) - Specifies the designation of indict
Department Varchar(20) - Specifies the department of the indict
Shift Varchar(2) - Specifies the shift of the indict
Grievance description Varchar(MAX - Specifies grievance description by
) complainer
When did this incident Date - Specifies the date of incident occurred
occur
Expected solution Varchar(MAX - Specifies expected solution by complainer
)
Expected by when Date - Specifies the date of the expected solution
Mailing address Varchar(20) - Specifies the mailing address of the
complainer
Date of post Date - Specifies the date when the grievance is
posted by complainer

Grievance on student:
Field Type Constraints Description
Complainer name Varchar(20) - Specifies the Name of the complainer
Indict on whom Varchar(20) - Specifies the name of the indict
Designation Varchar(20) - Specifies the designation of indict
Department Varchar(20) - Specifies the department of the indict
Year Varchar(3) - Specifies the year of the indict
Shift Varchar(2) - Specifies the shift of the indict
Grievance description Varchar(MAX - Specifies grievance description by
) complainer
When did this incident Date - Specifies the date of incident occurred
occur
Expected solution Varchar(MAX - Specifies expected solution by complainer
)
Expected by when Date - Specifies the date of the expected solution
Mailing address Varchar(20) - Specifies the mailing address of the
complainer
Date of post Date - Specifies the date when the grievance is
posted by complainer

Grievance on equipment:
Field Type Constraints Description
Complainer name Varchar(20) - Specifies the Name of the complainer
Department Varchar(20) - Specifies the department of the indict
Grievance description Varchar(MAX - Specifies grievance description by
) complainer
Expected solution Varchar(50) - Specifies expected solution by complainer
Expected by when Date - Specifies the date of the expected solution
Mailing address Varchar(MAX - Specifies the mailing address of the
) complainer
Date of post Date - Specifies the date when the grievance is
posted by complainer

Grievance on environment:
Field Type Constraints Description
Complainer name Varchar(20) - Specifies the Name of the complainer
Department Varchar(20) - Specifies the department of the indict
Grievance description Varchar(MAX - Specifies grievance description by
) complainer
Expected solution Varchar(MAX - Specifies expected solution by complainer
)
Expected by when Date - Specifies the date of the expected solution
Mailing address Varchar(20) - Specifies the mailing address of the
complainer
Date of post Date - Specifies the date when the grievance is
posted by complainer

Grievance on food in canteen:


Field Type Constraints Description
Complainer name Varchar(20) - Specifies the Name of the complainer
Grievance description Varchar(MAX - Specifies grievance description by
) complainer
Expected solution Varchar(MAX - Specifies expected solution by complainer
)
Expected by when Date - Specifies the date of the expected solution
Mailing address Varchar(20) - Specifies the mailing address of the
complainer
Date of post Date - Specifies the date when the grievance is
posted by complainer
Grievance on sports:
Field Type Constraints Description
Complainer name Varchar(20) - Specifies the Name of the complainer
Indict on whom Varchar(20) - Specifies the name of the indict
Grievance description Varchar(MAX - Specifies grievance description by
) complainer
When did this incident Date - Specifies the date of incident occurred
occur
Expected solution Varchar(MAX - Specifies expected solution by complainer
)
Expected by when Date - Specifies the date of the expected solution
Mailing address Varchar(20) - Specifies the mailing address of the
complainer
Date of post Date - Specifies the date when the grievance is
posted by complainer

General grievance:
Field Type Constraints Description
Complainer name Varchar(20) - Specifies the Name of the complainer
Indict on whom Varchar(20) - Specifies the name of the indict
Grievance description Varchar(MAX - Specifies grievance description by
) complainer
When did this incident Date - Specifies the date of incident occurred
occur
Expected solution Varchar(MAX - Specifies expected solution by complainer
)
Expected by when Date - Specifies the date of the expected solution
Mailing address Varchar(20) - Specifies the mailing address of the
complainer
Date of post Date - Specifies the date when the grievance is
posted by complainer
3.4 Sequence Diagram
3.5 Component Diagram
3.6 User Interface Design
3.7 Test Case Design

S.no Test Condition Test Data Expected Result Status


Registration
TC1 Registration User name details stored in Registration
password database successful
Confirm
password Error message
Email id If all the will be displayed
Mobile number required field is
not filled

TC2 Login User name and Enter the Navigate to user


password username and page
password

Incorrect Error message


username and will be displayed
password

TC3 Grievance on Complainer Grievance on Grievance on


student name, indict on student is posted student is posted
whom, grievance successfully successfully
description,
expected
solution,
expected by
when, date of
post
Complainer
TC4 Grievance on name, indict on Grievance on Grievance on
staff whom, staff is posted staff is posted
designation, successfully successfully
grievance
description,
expected
solution,
expected by
when, date of
post
Complainer
TC5 Grievance on name, grievance Grievance on Grievance on
equipment description, equipment is equipment is
expected posted posted
solution, successfully successfully
expected by
when, date of
post
Complainer
TC6 Grievance on name, Grievance on Grievance on
environment department, environment is environment is
grievance posted posted
description, successfully successfully
expected
solution,
expected by
when, grievance
description , date
of post

TC7 Grievance on Complainer Grievance on Grievance on


food in canteen name, expected food in canteen food in canteen
solution, is posted is posted
expected by successfully successfully
when, grievance
description , date
of post

TC8 Grievance on Complainer Grievance on Grievance on


sports name, indict on sports is posted sports is posted
whom, expected successfully successfully
solution,
expected by
when, grievance
description , date
of post

TC9 General Complainer General General


grievances name, indict on grievances is grievances is
whom, expected posted posted
solution, successfully successfully
expected by
when, grievance
description , date
of post
4 Implementation

4.1 Overview of the Implementation

SQL Server 2008

SQL Server 2008 is a relational database management system developed by Microsoft. As a


database, it is a software product whose primary function is to store and retrieve data as
requested by other software applications, be it those on the same computer or those running on
another computer across a network (including the Internet). There are at least a dozen different
editions of Microsoft SQL Server aimed at different audiences and for workloads ranging from
small single-machine applications to large Internet-facing applications with many concurrent
users.

ASP.NET

ASP.NET is a server-side Web application framework designed for Web development to


produce dynamic Web pages. It was developed by Microsoft to allow programmers to build
dynamic web sites, web applications and web services. It was first released in January 2002 with
version 1.0 of the .NET Framework, and is the successor to Microsoft's Active Server
Pages (ASP) technology. ASP.NET is built on the Common Language Runtime (CLR), allowing
programmers to write ASP.NET code using any supported .NET language. The
ASP.NET SOAP extension framework allows ASP.NET components to process SOAP
messages.
5. Test Case Document

5.1 Unit testing:

Unit testing is testing the module individually when the modules are not integrated.
Unit name: Registration

S.No Test case Normal input Expected Actual result


Description result
1 Registration is  Usernam Registered Registered
e
used for user to details must be details must be
 Password
register their  Confirm stored in the stored in the
details. Using password database database
 Email
this user can address
enter into this  Phone no
 date
system.

Unit Name: Login


S.No Test case Normal input Expected Actual result
Description result
1 Login is used to Valid username User is logged User is logged in
login to this and password in successfully successfully and
system and redirected redirected to user page
to user page

Unit Name: admin


S.No Test case Normal input Expected Actual result
Description result
1 Admin module To Mail has been Mail has been sent
is used to view subject sent successfully
the posted message successfully
grievances and
give solution to
the grievances
through mail

Unit Name: Grievance on staff


S.No Test case Normal input Expected Actual result
Description result
1 Grievance on  Complainer Grievance on Grievance on staff is
staff module is name staff is posted posted successfully.
used to post  Indict on successfully
the grievance whom
on staff  Designation
 Department
 Shift
 Grievance
description
 When did this
incident occur
 Expected
solution
 Expected by
when
 Mailing
address
 Date of post

S.No Test case Normal input Expected Actual result


Description result
1 Grievance on  Complainer Grievance on Grievance on staff is
staff module is name staff is posted posted successfully.
used to post  Indict on successfully
the grievance whom
on staff  Designation
 Department
 Shift
 Grievance
description
 When did this
incident occur
 Expected
solution
 Expected by
when
 Mailing
address
 Date of post

Unit Name: Grievance on student


S.No Test case Normal input Expected Actual result
Description result
1 Grievance on  Complainer Grievance on Grievance on student
student module name student is is posted successfully.
is used to post  Indict on posted
the grievance whom successfully
on student

 Department
 Year
 Shift
 Grievance
description
 When did this
incident occur
 Expected
solution
 Expected by
when
 Mailing
address
 Date of post

Unit Name: Grievance on equipment


S.No Test case Normal input Expected Actual result
Description result
1 Grievance on  Complainer Grievance on Grievance on
equipment name equipment is equipment is posted
module is used  Department posted successfully.
to post the  Grievance successfully.
grievance on description
equipment  Expected
solution
 Expected by
when
 Mailing
address
 Date of post
Unit Name: Grievance on environment
S.No Test case Normal input Expected Actual result
Description result
1 Grievance on  Complainer Grievance on Grievance on
environment name environment is environment is posted
module is used  Department posted successfully.
to post the  Grievance successfully.
grievance on description
equipment  Expected
solution
 Expected by
when
 Mailing
address
 Date of post

Unit Name: Grievance on food in canteen


S.No Test case Normal input Expected Actual result
Description result
1 Grievance on  Complainer Grievance on Grievance on food in
food in canteen name food in canteen canteen is posted
module is used  Grievance is posted successfully.
to post the description successfully.
grievance on  Expected
food in canteen solution
 Expected by
when
 Mailing
address
 Date of post

Unit Name: Grievance on sports


S.No Test case Normal input Expected Actual result
Description result
1 Grievance on  Complainer Grievance on Grievance on sports is
sports module name sports is posted posted successfully.
is used to post  Indict on successfully.
the grievance whom
on equipment  Grievance
description
 When did this
incident occur
 Expected
solution
 Expected by
when
 Mailing
address
 Date of post

Unit Name: General grievance


S.No Test case Normal input Expected Actual result
Description result
1 General  Complainer General General grievances
grievance name grievances are are posted
module is used  Indict on posted successfully.
to post the whom successfully.
grievance on  Grievance
general description
problems  When did this
incident occur
 Expected
solution
 Expected by
when
 Mailing
address
 Date of post

5.2 Integration Testing:

Testing performed on groups of modules to ensure data are passed properly among the
modules.

S.No Test case Normal input Expected Actual result


Description result
1 Admin Module Username and It navigates to Navigates to admin page
password is admin page
entered by
admin
Admin views Navigates to Navigates view grievances
the posted view grievances page.
grievances by page.
clicking the
links
Admin send the Mail has been Mail has been sent
solution sent successfully.
through mail successfully

S.No Test case Normal input Expected Actual result


Description result
1 User Module If the user is It navigates to Navigates to registration page.
new to the the Registration
system the user page
must register
their details in
the registration
from.user
Click the
registration link
Username and Navigates to Navigates to user page.
password is userpage .
filled by the
user
User click the Navigates to Navigates to that page.
link on whom that page.
they want to
post the
grievance
User filled the All the required All the required fields are
required fields fields are filled filled
User post the Grievance Grievance posted successfully
grievance posted
successfully
5.3 System Testing:

A pre determined combination of tests that when executes successfully satisfy all the
requirements that the system meets.

Admin
Serial Test Case Functionality Input Result Expected Output
Number Number
Login success,
1 TC01 Success Admin page will be display.
login Username
Password Login failed error message will
Fails be display

Students View the grievances


grievance Success
View Staff Error message will be display.
2 TC02
grievance Fails
Non
teaching
staff
grievance
Lab
technicians
grievance
Mail has been sent successfully
To Success
Send mail Subject Mail sending failed.
3 TC03
message Fails
Serial Test Case Functionality Input Result Expected Output
Number Number

Delete Success user deleted successfully.


4 TC04 Delete user

Fails Error message will be display.

User :
Serial Test Case Functionality Input Result Expected Output
Number Number
Username Registration successful,
5 TC05 Password Success login page will be display.
Register Confirm
password Error message will be display
Mail address Fails
phone no
login success,
Username Success user page will be display
6 TC06 Login Password

Fails Error message will be display.


Grievances are post successfully
Required Success and the data will be stored in the
Post fields is database
filled by the Error messages will be display
users and Fails
post
7 TC07 grievance

6 Conclusion
6.1. Summary
Online campus grievance for sacred heart college is developed to computerizing the work of
collecting grievances from sacred heart college campus. It is capable to provide easy and
effective storage of grievances.

6.2 Future Enhancement

 Online video chat will be added to this application.


 Suggestion on college functions module will be added.

References

Books
1. Mathew MacDonald, “ASP.NET: The Complete Reference”, Tata McGraw Hill Publishing
Company Ltd., New Delhi.
2. Dino Eesposito,”Introducing Microsoft ASP .NET 2.0”, Prentice Hall of India, New Delhi
2006
3. Stephen Walther,” ASP.NET 2.0 Unleashed “Second Edition Pearson Education 2005

Websites
1. www.aspdotnet-suresh.com
2. http://www.codeproject.com/
3. http://www.tutorialspoint.com/asp.net/
4. http://www.w3schools.com/aspnet/

Appendices

Appendix-A
Project Proposal
Executive Summary
“Online Campus Grievance” is used to gather all the complaints in the campus and
give required solution through online without need of any manual entries and update it
automatically so that less time consuming and more efficient. The person who want to post a
complaint about any person, equipments, environment, food in canteen and sports in the campus
can post their complaint through this application, The solution for the compliant will be given by
the admin.
The main objective of this project is
 The process eliminates the most of the manual work.
 The system helps in efficient time consumption
 The website shall be designed ease of use and navigate.

INTRODUCTION
I am G. EZHILARASI working on this project, doing MSC Computer Science in
sacred heart college, Tirupattur. As an academic requirement, I am taking this project for the
client Sacred heart college, Tirupattur as a final year project. I play all the roles in the software
development process since it is individual and academic project.
Online Campus Grievance is a web based system. This is helpful for the students , staffs
and all officials to have solutions to their problems in online. Also the each individual person can
post their problem and solution will be given by the admin.
PROBLEM STATEMENT
Students, staffs, non teaching staffs and other workers in the college campus post their

complaints in the complaint box. But there is no proper system to record the details of the
complaints and maintain the reports of complaints .College management finds it difficult to
record the complaint details and maintain the reports. To avoid this problem Online Campus
Grievance is proposed. This application is useful for storing the complaints.

PROPOSED SOLUTION
The main need for the proposed system is everything is dynamic no needed to be updated
manually everything is updated automatically and less human resource is needed and less time
consuming for rectifying the problem.

Proposed system has several advantages:


 To reduce the manual work.
 To save the time.
 Error free
 More Storage Capacity

PROOF OF CONCEIVED SOLUTION


Available Input: Grievance process Manual Details
Excepted Output: Campus Grievance Website
Report of each Grievance Event
Reports will be directed to the admin of the College
Process Logic: Validating the username and password by security mechanisms
Stake Holders: students, staffs, non teaching staffs, higher authorities
End User:students, staffs, non teaching staffs, higher authorities
TECHONOLOGY REQUIREMENTS

1. Project Title : Online Campus Grievance

2. Module : 1. Admin
2. Students Grievance
2.1 Grievance on staff
2.2 Grievance on student
2. 3 Grievance on equipments
2.4 Grievance on Environment
2.5 Grievance on food in canteen
2.6 Grievance on sports
2.7 General Grievance
3. Staffs Grievance
3.1 Grievance on staff
3.2 Grievance on student
3. 3 Grievance on equipments
3.4 Grievance on Environment
3.5 Grievance on food in canteen
3.6 Grievance on sports
3.7 General Grievance
4. Non teaching staffs Grievance
4.1 Grievance on student
4.2 Grievance on staff
4. 3 Grievance on equipments
4.4 Grievance on Environment
4.5 Grievance on food in canteen
4.6 Grievance on sports
4.7 General Grievance
5. Lab technicians Grievance
5.1 Grievance on student
5.2 Grievance on staff
5. 3 Grievance on equipments
5.4 Grievance on Environment
5.5 Grievance on food in canteen
5.6 General on sports
5.7 General Grievance

3. Database : Sql server 2008

4. Packages/GUI Tools : Microsoft Visio2003

5. Server Side : IIS


6. Client Side : ASP.NET
7. Hardware/Software Requirement:
A. Web Server Specification

1. Hardware
Processor: Intel pentium, RAM: 2GB
2. Operating System
Windows 7 Ultimate
B. Client Specification
1. Hardware
Processor: Intel pentium, RAM: 2GB
2. Operating System
Windows 7
3. Software
GUI based web browser, Microsoft visual studio 2010
TERMS AND CONDITIONS
1. Project Duration: The duration of the academic project is five months of the even
semester.
2. Project Initiation: Student upon receiving approval from the Project Guide shall start
the requirement study and analysis and complete it as per the project schedule agreed
upon by the Department.
3. Development: The project development will be done only in the college lab.

Signature: Signature:
Guide Name: M.Poovizhi Name: G.Ezhilarasi
Date: 1/8/2014 Date: 1/8/2014

Appendix B
Project plan

Project Area Work Start End Date Status


products Date [C/
NC]
Project  Project 25/11/201 4/12/2013 C
Management Proposal 3
 Project Plan 05/12/201 09/12/201 C
3 3
Project 10/12/201 13/12/201 C
Review 3 3
Record-1
Requirements  System Study 16/12/201 20/12/201 C
(SSD) 3 3
 Vision 08/01/201 10/01/201 C
Document 4 4
(VSD)
 Supplementar 11/01/201 17/01/201 C
y 4 4
Specification
(SSN)
 Use-Case 18/01/201 20/01/201 C
Diagram 4 4
 Use-Case 21/01/201 22/01/201 C
Model (UCS) 4 4
Project Review 23/01/201 24/01/201 C
Record-2 4 4
FIRST Draft Report 25/01/201 27/01/201 C
REVIEW (Combination of 4 4
all work
products)
Analysis and  Sequence 28/01/201 29/01/201 C
Design Diagram 4 4
 Data 30/01/201 31/01/201 C
Dictionary, 4 4
Database
Design
(Table
Design, Data
integrity &
Constraints)
 Class 03/02/201 04/02/201 C
Diagram 4 4
 Test Case 05/02/201 06/02/201 C
Design 4 4
 User 07/02/201 08/02/201 C
Interface 4 4
Design
Project Review 10/02/201 12/02/201 C
Record-3 4 4
MID -TERM  Draft Report 14/02/201 15/02/201 C
EVALUATIO (Combination 4 4
N (Second of all work
Review) products)
Project 17/02/201 18/02/201 C
Evaluation 4 4
Report-1
Implementatio  Pseudo code 19/02/201 21/02/201 C
n 4 4
 Program code 24/02/201 25/02/201 C
4 4
Project Review 26/02/201 28/02/201 C
Record-4 4 4
Test  Unit, 03/03/201 04/03/201 C
Integration, 4 4
System test
plan
 Test Case 05/03/201 06/03/201 C
Results 4 4
Project Review 07/03/201 10/03/201 C
Record-5 4 4
EVALUATIO Project 10/03/201 11/03/201 C
N (Third Report 4 4
Review)  Project 12/03/201 13/03/201 C
Presentation 4 4
 Application 17/03/201 20/03/201 C
Demo 4 4
Signature: Signature:
Guide Name: Miss.M.Poovizhi Name: G.Ezhilarasi
Date: 1/8/2014 Date: 1/8/2014

Appendix c

Department of Computer Science


Project Work Review Report – I

Name: G.Ezhilarasi Class: M.Sc Computer science Dept.No:Bp120507

Project title: Online Campus Grievance

Date: 1/8/2014 Time: Duration:

Review of Tasks: (Task Completed)

No Description Status Comment


1. Project Proposal Completed
2. Project Plan Completed
Status: C- Completed NC – Not Completed

Expected Activities: (Task to be carried out)

Description Nature Deliverables Due Date


1 System Study Documentation System Study 10 Jan 14
2 Vision Document Documentation Vision 27 Jan 14
Document
3 Use Case Specification Documentation Use Case 3 Feb 14
Specification

Next Consultation on ______31/1/2014____ at _3.45pm________

Nature:

LB: Lab Work CN: Consultation IG: Information gathering


DG: Design DO: Documentation

Signature: Signature:
Guide Name: Miss.M.Poovizhi Name: G.Ezhilarasi
Date: 1/8/2014 Date: 1/8/2014
Department of Computer Science
Project Work Review Report – II

Name: G.Ezhilarasi Class: M.Sc Computer science Dept.No:Bp120507

Project title: Online Campus Grievance

Date: 21/1/2014 Time: Duration:

Review of Tasks: (Task Completed)

No Description Status Comment


1. System Study Completed
2. Vision Document Completed
3. Use Case Specification Completed

Status: C- Completed NC – Not Completed


Expected Activities: (Task to be carried out)

Description Nature Deliverables Due Date


1 Sad Diagrams Documentation SAD 25 Jan 14
2 Design Documentation Design 12 Feb 14

Next Consultation on ______31/1/2014____ at _3.45pm________

Nature:

LB: Lab Work CN: Consultation IG: Information gathering


DG: Design DO: Documentation

Signature: Signature:
Guide Name: Miss.M.Poovizhi Name: G.Ezhilarasi
Date: 1/8/2014 Date: 1/8/2014
Department of Computer Science
Project Work Review Report – III

Name: G.Ezhilarasi Class: M.Sc (cs) II year Dept No: Bp120507


Project title: Online Campus Grievance
Date: 7/2/2014 Time: Duration:

Review of Tasks: (Task Completed)

No Description Status Comment


1 Architecture Diagram Completed
2 Database Design Completed
3 Component Diagram Completed
4 Sequence Diagram Completed
5 Class Diagram Completed
6 User Interface Design Completed

Status: C- Completed NC – Not Completed


Expected Activities: (Task to be carried out)

No Description Nature Deliverables Due Date


1 Design Consultation Website Design 12-feb-14
2 Implementation Information Program code 18-feb-14
Gathering

Next Consultation on _____19/2/2014____ at __3.45pm_____________

Nature:

LB: Lab Work CN: Consultation IG: Information gathering


DG: Design DO: Documentation

Signature: Signature:
Guide Name: Miss.M.Poovizhi Name: G.Ezhilarasi
Date: 7/2/2014 Date: 7/2/2014
Department of Computer Science
Project Work Review Report – IV

Name: G.Ezhilarasi Class: M.Sc Computer science Dept.No:Bp120507

Project title: Online Campus Grievance

Date: 12/2/2014 Time: Duration:

Review of Tasks: (Task Completed)

No Description Status Comment


1. Implementation Completed

Status: C- Completed NC – Not Completed


Expected Activities: (Task to be carried out)

Description Nature Deliverables Due Date


1 Test Documentation Testing 18 Feb 14

Next Consultation on ______18/2/2014____ at _3.45pm________

Nature:

LB: Lab Work CN: Consultation IG: Information gathering


DG: Design DO: Documentation

Signature: Signature:
Guide Name: Miss.M.Poovizhi Name: G.Ezhilarasi
Date: 12/2/2014 Date: 12/2/2014
Department of Computer Science
Project Work Review Report – V

Name: G.Ezhilarasi Class: M.Sc Computer science Dept.No:Bp120507

Project title: Online Campus Grievance

Date: 18/2/2014 Time: Duration:

Review of Tasks: (Task Completed)

No Description Status Comment


1. Unit Testing Completed
2. Integration Testing Completed
3. System Testing Completed

Status: C- Completed NC – Not Completed


Expected Activities: (Task to be carried out)

Description Nature Deliverables Due Date


1 Demo Information System Study 7 March 14
gathering

Next Consultation on ______7/3/2014____ at _3.45pm________

Nature:

LB: Lab Work CN: Consultation IG: Information gathering


DG: Design DO: Documentation

Signature: Signature:
Guide Name: Miss.M.Poovizhi Name: G.Ezhilarasi
Date: 18/2/2014 Date: 18/2/2014
Appendix D

Screenshots
Home
Student’s Grievance
Staffs Grievance

Non teaching staffs grievances


Lab technician’s grievance
Program code

Home
using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
using System.Web.UI;
using System.Web.UI.WebControls;

public partial class home : System.Web.UI.Page


{
protected void Page_Load(object sender, EventArgs e)
{
if (DateTime.Now.Hour < 12)
{
lblGreeting.Text = "Good Morning !";
lblDate.Text = Convert.ToString(DateTime.Now);
}
else if (DateTime.Now.Hour < 17)
{
lblGreeting.Text = "Good Afternoon !";
lblDate.Text = Convert.ToString(DateTime.Now);
}
else
{
lblGreeting.Text = "Good Evening !";
lblDate.Text = Convert.ToString(DateTime.Now);
}

}
}
Grievance on student
using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Data;
using System.Data.SqlClient;
using System.Windows.Forms;

public partial class grievance_on_student : System.Web.UI.Page


{
SqlConnection con = new SqlConnection("Data Source=SYSSOFT-PC;Initial
Catalog=ocg;Integrated Security=True");
SqlCommand cmd = new SqlCommand();
SqlDataAdapter da = new SqlDataAdapter();
DataSet ds = new DataSet();
protected void Page_Load(object sender, EventArgs e)
{

protected void Button1_Click(object sender, EventArgs e)


{
con.Open();
cmd.CommandText = "insert into gostudent1 values('" +
cname.Text.ToString().Trim() + "','" + indict.Text.ToString().Trim() + "' ,'" +
department.Text.ToString().Trim() + "' ,'" + year.Text.ToString().Trim() + "' ,'" +
shift.Text.ToString().Trim() + "' ,'" + gdescription.Text + "','" +
occur.Text.ToString().Trim() + "' ,'" + esolution.Text.ToString().Trim() + "' ,'" +
when.Text.ToString().Trim() + "' ,'" + mail.Text.ToString().Trim() + "' ,'" +
DateTime.Now.ToString() +"')";
cmd.Connection = con;
cmd.ExecuteNonQuery();
da.InsertCommand = cmd;
MessageBox.Show("posted successfully", "post");
Response.Redirect("grievance_on_student.aspx");
con.Close();

}
protected void Button2_Click(object sender, EventArgs e)
{
cname.Text = "";
indict.Text = "";
department.Text = "";
year.Text = "";
shift.Text = "";
gdescription.Text = "";
occur.Text = "";
esolution.Text = "";
when.Text = "";
mail.Text = "";
}
}

You might also like