01-07-2013, 02:49 PM
Online Grievance Redressal System
Online Grievance.doc (Size: 109.5 KB / Downloads: 20)
Introduction
Purpose of this Document
The people need not go to the higher authorities always when they face problems. They can use the service of this software browser and can give their complaint and the complaint is taken up by the employee of specified department and he solves the problem.
Scope of the Development Project
The goal is to design software for an organization in which the public will register and enter complaints on the unfair happened to them, those details are taken by the respective department in order to perform redressal for the complaint of the person. The complaint is directed to the director public grievance assesses the grievance and forward it to the subordinate department for prompt redress, ministry of subordinate examines to redress and prepare a reasoned reply, and with the approval of competent authority action taken and reply is sent to the complainant. Hence the public can keep in contact with the higher authority.
3. Update access privileges: The software must be able to update the access privileges onto a particular user’s details and project details and the database where the privileges themselves will be modifiable only by the system administrators
Overview
The remaining sections of this document provide a general description, including characteristics of the users of this project, the product's hardware, and the functional and data requirements of the product. General description of the project is discussed in section 2 of this document. Section 2 gives the functional requirements, data requirements and constraints and assumptions made while designing the multi-utility system. It also gives the user viewpoint of product use. Section 3 gives the specific requirements of the product. Section 3.0 also discusses the external interface requirements and gives detailed description of functional requirements.
Product Functions
The product should be able to perform the following operations:
1. It must be able to authenticate the user by matching the User ID and the access code against the values stored in the database.
2. It must be able to check the Project / Employee status by querying the database for any reservation requests made earlier.
3. It must be able to record the user’s presence by writing the user’s ID in the corresponding database table. Thus for one login, two write operations will be performed: one into the central repository and other into the backup database server. For each login the time in/out will also be recorded and the total time spent in the application will be computed by subtracting the time when user started the application with the time when the user came out of the application.
4. The software must be able to update the access privileges onto a particular user’s ID and password and the database where the privileges themselves will be modifiable only by the system administrators (or some authorized staff members).
5. The software must be able to determine whether a particular user has been denied access from a particular lab due to some policy violation. The results of this operation will be viewable by the admin only.