SRS

Introduction
Purpose:
The purpose of this document is to design a feedback form.

Scope:
To design a feedback module which includes student’s interaction to give feedback about
their respective faculties.

1. Overall Description
Functions:
1. Admin
 Can insert/delete/update new student.
 Can insert/delete/update new staff member.
 Can view suggestions/comments given by students.
 View the final feedback report of all faculties.

2. Faculty
 Can view only their own evaluated feedback given by the students.

3. Students
 Can give comments and compliments to the respective staff member
for any improvements.
 Will give feedback to all the subjects and practical’s (Batch wise).

User Classes and Characteristics

Identify the various user classes that you anticipate will use this product. User classes may be
differentiated based on frequency of use, subset of product functions used, technical
expertise, security or privilege levels, educational level, or experience. Describe the pertinent
characteristics of each user class. Certain requirements may pertain only to certain user
classes. Distinguish the most important user classes for this product from those who are less
important to satisfy.

Operating Environment
The system will run on following platforms:
 Windows
 Linux
Design and Implementation Constraints
Describe any items or issues that will limit the options available to the developers. These
might include: corporate or regulatory policies; hardware limitations (timing requirements,
memory requirements); interfaces to other applications; specific technologies like html ,css,
editing tools like atom & bracket, and databases to be used php using mysql; parallel
operations; language requirements; communications protocols; security considerations;
design conventions or programming standards (for example, if the customer’s organization
will be responsible for maintaining the delivered software).

User Documentation
User manuals will be delivered along with the software to the staff coordinators.

Assumptions and Dependencies:

 Same faculty might be assigned to teach more than one subject to the different
classes.
 Faculties can teach in other departments also.
 Faculties may get changed for a single subject in same semester.
 Different faculty teaching different batches of same subject.

External Interface Requirements

Hardware Interfaces

 2GB RAM

 Dual core Processor

Software Interfaces
 Browser
 Tomcat server
 MySQL
 Atom/Bracket

Communications Interfaces
The main communication function is web browser which can access the website through
HTTP.

System Features
 Registration of students (will be done by admin).
 Login for student, staff coordinator & Admin.
 Feedback Form for students.
 Admin panel for admin with added functionalities.
Use Case Diagram:
Use case Diagram:Staff

Login

Change Password
Staff

View Feedback

Logout
 ER Diagram: User_id Profile Password

Admin/HOD Manage (Add,

Student
Update,delete)
e

User_id Password
Feedback

Manage (Add,
Update,delete)
e

Faculty

Profile User_id

View Password
Flow Diagram :

Start

Student Registration

Student Login

Dashboard

Feedback Form

Start

Ok

List of feedback questions along

with respective faculty and their
subjects

Feedback questions for theory

subjects along with their
respective faculty

Submit

Logout