Feedback

Feedback System
1 . INTRODUCTION
1.1 Existing System

At present, any college management is collecting the feedback for their
faculty from students manually. The management gives papers containing the subjects and
faculty of a particular section. They give questions and a sheet for marking the answers.
According to the feedback given by the students, the evaluation process of the feedback is
doneby the management.
Disadvantages of Existing System

1. This takes more time for the process.
2. The management has to go for each and every class.
3. It involves more paper work.
4. The manual calculation is a very complicated job.
1.2 Proposed System

The Proposed System is the one in which collecting the feedback from student is
being computerized. The administrator of a college provides a feedback form to the
students according to their branch, year, semester and section. The student fills the given
feedback form and submits it. Later, the college management views the reports that are
calculated according to the given feedback.
1.2.1 Key Features of Proposed System

• The management need not go to each and every class to collect feedback from
student. They can take feedback in the lab from all the students at a time.
• It doesnot need any papers.
• Given feedback is evaluated automatically and reports are generated within
minutes.
1
Feedback System
1.2.2 Scope and Purpose of the System

The Scope of the Project is :
• The students of a college or University can give feedback about a particular course
or class.
• The application will provide a feedback form for the students with some options so
that students can select an option and send it to the server.
• The consolidated results can be viewed by the college management later.
1.2.3 System Description

In this project Feedback System, there will be 3 main modules.
 Administrator Module
 Student Module
 Management Module
1.2.3.1 Administrator Module

The administrator of the college is the one who conducts this feedback process.
Before conducting this feedback he/she has to do the following activities.
 Login
 View Faculty Details
 View Subjects Details
 View Questions Details
 Map Subjects and Faculty
 Delete Existed Mapping
 Delete Existed Feedback
 Start Feedback
 Logout
 Login
The administrator of the college will be given a unique admin id and password.
He/She should use them to login. The administrator may change the password, if
he/she wants.
2
Feedback System
 View the Faculty Details

The administrator can view the faculty details of all branches. The details
include branch, faculty name and unique code given to them. Here, the administrator
has 3 options.
• New
If any new faculty is appointed, their details are entered here. If the
administrator selects ‘New’ option, a form appears asking to enter the branch,
faculty name and the unique code.
• Update
If there is any situation that the branch or faculty name or code is to be
modified, the administrator can select the ‘Update’ option so that the present data
will be replaced with the modified data.
• Delete
If any existing faculty leaves the college, the administrator can delete
his/her details per manently.
 View Subjects Details

The administrator can view the subjects details of all branches. The details
include branch, subject name and unique code of each subject. Here also, the
administrator has 3 options.
• New
If any new subject is introduced for any branch, its details are entered
here. If the administrator selects ‘New’ option, a form appears asking to enter the
branch, subject name and the unique code.
• Update
If there is any situation that the branch or subject name or code is to be
modified, the administrator can select the ‘Update’ option so that the present data
will be replaced with the modified data.
3
Feedback System
• Delete
If any existing subject is removed from the syllabus, the administrator can
delete his/her details permanently.
 View the Questions Details

The administrator can configure the questions as per the college
requirement. These question will be same for every branch. The details include
question number, question, and the weightage given to that question. Here, the
administrator has 2 options.
• New
If the college management wants to add a new question for the
feedback, the administrator can do it by selecting the ‘New’ option.
• Delete
If the college management doesnot need a particular question for the
feedback, the administrator can delete it by selecting the ‘Delete’ option.
 Map Subjects and Faculty

This is the option where the subjects and faculty are mapped according to
the existing branch, year, semester, sections, their subjects and the respective faculty.
 Delete Existed Mapping

If the mapping changes at any time, the existed mapping of a particular
section will be deleted and those are mapped again by the administrator.
 Start Feedback
When the administrator chooses this option, the feedback forms are
displayed to the students with the faculty names, subject names and questions
automatically displayed. Each question will have 4 options as Below Average, Average,
Good and Excellent.
4
Feedback System
 Delete Existed Feedback

If the feedback session is being conducted second time for any reason, the
existed feedback must be deleted for that particular section before conducting new session.
 Log Out
After his/her job is completed, the administrator can logout.
1.2.3.2 Student Module

The students will be given a URL address by the administrator. When the student
gives that URL in the browser, the home page of the application will be loaded. Later
when the student clicks on feedback, the feedback form will be displayed. The student will
fills the form and submits it.
1.2.3.3 Management Module

This module belongs to the college management where they can see the given
feedback in the form of reports. The activities that are done by the administrator are:
 Login
 View reports
 Logout
 Login
The management will be given a unique management id and password.
He/She should use them to login. The management may change the password, if
he/she wants.
 View Reports
The management can view the feedback reports for all faculty members
branch wise. That report can be exported to excel and can take a printout of the report.
5
Feedback System
1.2.4 Advantages of Proposed System

 Time can be saved.
 Calculation part can be done automatically.
 Reports are generated within minutes.
 This system is highly secure.
 Easy to maintain the data.
6
Feedback System
2. REQUIREMENT ANALYSIS
2.1 Hardware And Software Requirements
2.1.1 Hardware Requirements :

Microprocessor : Pentium IV
Hard Disk : 160 GB
Main Memory : 1 GB
Floppy Disk : 1.44 MB
2.1.2 Software Requirements :

Operating System : Windows Xp
Front end : HTML, JSP, JDBC
Database : Oracle 10G
Server : Apache Tomcat 5.5 or Later Versions
MS-Office Tools : MS-Excel
2.1.3 Functional Requirements:

Input:
The inputs and outputs of the system are categorized module wise. Basically all
the information is maintained by the software. To access the data, one has to produce his
identity by entering his user id and password which is different for all the users.
Output:
The major outputs of the system are reports. These reports carry the gist of entire
information that flows across the system
.
7
Feedback System
2.2 Software Requirement Specification (SRS)
2.2.1 Vision
For corresponding college management who would like to review student feedback
for their teachers and courses in a detailed manner by generating reports .
For students of a college or University who would like to provide feedback about a
current lecture.
For the corresponding teacher who would like to receive feedback and view results.
The FeedBack System is a computerised system that makes the management to be

able to take the feedback from the students with no use of paper work and to view the
feedback in an easily understandable way.
Unlike the present feedback mechanism, our product does not need any paper
work. This system is an useful application that provides elegant forms / reports.
2.2.1 Glossary
Student Any student of a college or University

Management The college or University management
Administrator The person who belongs to college
2.2.2 Scope
The students of a college or University can give feedback about a particular course
or class. The application will provide a feedback form for the students with some options
so that students can select an option and send it to the server. The consolidated results can
be viewed by the lecturer of the class or the college management later.
8
Feedback System
Exclusions
• Reports are represented in the form of graphs.
Assumptions:
• Only administrator can do the main operations.
• The students completely fill the feedback form.
• The student’s id is not revealed.
• Mapping of subjects and faculty is possible.
• Updating of faculty and subject details is possible.
• The questions are configurable.
2.2.3 System Functions
SNO SYSTEM Feed Back Administration
FUNCTION
1 S1.10 Add respective courses, branches, sections and subjects
2 S2.20 Mapping of the subject and faculty names
3 S3.30 Updation of details of faculty
4 S4.40 Updation of details of subjects
5 S5.50 Provision of a feedback form for both subjects and
laboratories
6 S6.60 Generation of the feedback report for a teacher
9
Feedback System
2.2.4 Detailed Software Requirements
2.2.4.1 Use case model
Actor Name Administrator

Actor Id ACT-01
The administrator of the college conducts the feedback
Description
process
Selection of branch ,year, semester and section for
Main Activities which course the feedback is to be provided.
Providing feedback form to the students
Frequency of Use High
Work Environment /
Browser
Location
Number of Users 1
Actor Name Student

Actor Id ACT-02
Description The students of a college
Gives the feedback for all the subjects and labs of a
Main Activities
particular branch,year,semester and section
Work Environment /
Browser
Location
Number of Users Any number
Actor Name Management

Actor Id ACT-03
The college management which checks the feedback
Description
report
Main Activities Views the reports for each faculty
10
Feedback System

Work Environment /
Browser
Location
Number of Users Few
2.2.4.2 List of Use Cases

• Conducting Feedback
• Submit Feedback
• View feedback by management
Use Case Name Conducting feedback

Use Case ID UC1
Actor(s) Administrator
Goal Provide a feedback form to the students of respective section
Summary The administrator first selects the corresponding branch, year,
semester and section. Then he inserts the details of all the
subjects and faculty respectively. Later he provides a feedback
form to the students.
Preconditions Admin must have a login id and password
Main Flow 1. The administrator login to 1.1 The administrator gives
the page. the id and password and
enters into his page. There he
will have 9 options.
S1. To insert the details of
subjects and faculty.
S2. To update the details of
S3. To delete the details of
S4. To create new questions
S5. To delete existed
questions
11
Feedback System
S6. To map the subjects and

faculty
S7.To delete existed mapping
of subjects and faculty
S8. To start a feedback for
students.
S9. To delete the existed
feedback.
2. User selects one of the 2.1 The selected option (sub

options: for S1 to S9. For all flow) is executed.
these, the branch, year,
semester and section should
be selected
Sub Flows
S1: Insert the details of subject and faculty
1.User selects S1. 1.1 System displays the
Input fields to the user to
enter the details of subjects
and faculty with respect to
branch, year, semester and
section
S2: Update the details of subjects and faculty

modify the details of
subjects and faculty with
respect to branch, year,
S3: Delete the details of subjects and faculty
12
Feedback System
1.User selects S3. 1.1 System prompts the user

whether to delete particular
details or not.
1.2 If user chooses to delete,
it will delete the details
S4: Inserting new questions

enter the question number,
question and weightage of
the question
S5: Delete the existed questions

1.User selects S5. 1.1 System prompts the user
whether to delete particular
question or not.
1.2 If user chooses to delete,
it will delete the question
S6: Map subjects and faculty

map subjects and faculty
according to the sections
S7: Delete Mapping

1.User selects S7. 1.1 The administrator can
delete the existed mapping
and do new mapping
S8: Start a feedback for students

1.User selects S8. 1.1 System displays a
feedback form for subjects
and labs
S9: Delete Existed Feedback

1.User selects S9. 1.1 Administrator can delete
13
Feedback System
the existed feedback and

conduct new feedback.
Exception E1. If any subject or faculty name is not properly inserted, it

Flows gives an error message
E2. While starting feedback all the subjects and faculty must
be already inserted. Otherwise, system displays a message
Post Conditions Feedback form should be displayed.
Cross References S1.10, S2.20, S3.30,S4.40,S5.50
Assumptions Only the administrator can do these operations
Business Rules  Only the administrator can select the branch and
section, not the student.

 Only the administrator can insert or modify the details
of a teacher and his course.
A d m i n is tra to S tu d e n t
r
System 1 : s e le c ts b ra n c h ,ye a r ,s e m e s te r a n d s e c tio n o f s tu d n e ts

Sequence
2 : P ro vi d e s fe e d b a c k fo rm
Diagram
14
Feedback System
login
administrator
initialise feedback
Fig. 2.2.4.2.1 Conducting Feedback
Use Case Submit feedback

Name
Use Case ID UC2
Actor(s) Student
Goal Submits the completely filled feedback form
Summary The student first fills the feedback form for all subjects and labs
and submits the form.
Preconditions Mapping of the subjects and faculty should be there
Main Flow 1. The student will be given a 1.1 The student fills the
feedback form. feedback form
Sub Flows No subflows

Exception E1. If the user donot give the feedback properly, it will not be
Flows submitted.
Post The feedback form is submitted
Conditions
Cross -
References
Assumptions The feedback is filled properly by the student
Business Only the students can view the feedback form.
Rules Only the student should give the feedback.
15
Feedback System
student administrator
1: submits the feedback
student provide feedback
Fig. 2.2.4.2.1 Submit Feedback
Use Case Name View feedback

Use Case ID UC3
Actor(s) Management
Goal Views the feedback reports generated for all subjects and
faculty
16
Feedback System
Summary The Management can view the feedback for all the subjects and
faculty and informs it to the respective faculty.
Preconditions The given feedback should be there already
Main Flow 1.The management 1.1 The management views the
login to the page feedback reports.
S1: Generate Reports
S2:Export Reports to Excel
Sub Flows S1: Generate reports

1.User selects S1. 1.1 The system displays
the results of the
feedback in the form of
reports.
S2: Export Report to Excel

1.User selects S2. 1.1 The report is
exported to excel.
Exception E1. If there is no feedback for any faculty, the message should
Flows be displayed
Post Conditions The reports should be presented
Cross References S6.60
Assumptions The reports are presented in percentages
Business Rules Only the management can view these reports.
view feedback report
Management
generate report
Fig. 2.2.4.2.1 View Feedback
17
Feedback System
2.2.5 Functional Capabilities
 The feedback providers' identities should not be known.

 The subject names and faculty names should be automatically displayed.
2.2.6 Business Rules / Validations
 Only the administrator can select the branch and section, not the student.
 Only the management or faculty can view the feedback report.
 Only the administrator can insert or modify the details of a teacher and his course.
2.2.7 Security Requirements
2.2.7.1 User Management and Authentication
 The administrator will be authenticated by means of an adminId and a password.

 The teacher will be authenticated by means of an Id and password.
2.2.7.2 User roles and access control

 Only authorized administrator will be allowed to access the teacher-course
information.
 The system has to authenticate a user, determine whether he is a teacher or

administrator.
 Different user work with different applications (even though the database is
shared), hence the concept of roles is not needed here.
2.2.8 Other Non-functional requirements
 There should be no text output. It must be graphical. (Usability)

 The application should support the case of intermittent network connectivity i.e. the
student should be able to submit the feedback form in multiple sessions (one or more
responses at a time). (Reliability and Supportability)
18
Feedback System
 The form should load within 2 seconds. (Performance)

 Flexible service based architecture will be highly desirable for future extension
(Supportability)
 The system should be available 24 X 7. (Reliability/ availability)
3. SYSTEM DESIGN
3.1 Data Dictionary
TABLE NAME : ADMINS
SNo ATTRIBUTE DATA TYPE CONSTRAINTS DESCRIPTION

NAME
1 ADMINID VARCHAR2 (30) PRIMARY KEY Admin Login Id
2 ADMINPWD VARCHAR2 (30) PRIMARY KEY Admin Password
19
Feedback System
TABLE NAME : FACULTY
ATTRIBU DATA TYPE CONSTRAINTS DESCRIPTION

SNO TE
1 NAME
BRANCH VARCHAR2 (30) PRIMARY KEY Branch of a Particular
Faculty
2 FACNAM VARCHAR2 (100) PRIMARY KEY Name of Faculty
E
3 CODE NUMBER (10) PRIMARY KEY Unique code of
Faculty
TABLE NAME : SUBJECTS
ATTRIBUT DATA TYPE CONSTRAINT DESCRIPTION

SNO E S
1 NAME
BRANCH VARCHAR2 (30) PRIMARY KEY The branch related to
a particular subject
2 FACNAME VARCHAR2 (100) PRIMARY KEY Name of Subject
3 CODE VARCHAR2(30) PRIMARY KEY Unique code of

Subject
TABLE NAME : QUESTIONS

SNO TE
1 NAME
QNO NUMBER(10) PRIMARY KEY The no. of a question
2 QNAME VARCHAR2 (100) PRIMARY KEY The question
3 WTAGE VARCHAR2(30) Weightage given to a

Question
20
Feedback System
TABLE NAME : GRADES

SNO TE
1 NAME
GRADE NUMBER(10) PRIMARY KEY The grades given to
each option
2 EXPL VARCHAR2 (30) NOT NULL The explanation of
the grade
TABLE NAME : IDENTIFY
ATTRIBUTE DATA TYPE CONSTRAINTS DESCRIPTION

SNO NAME
1 BID NUMBER (30) PRIMARY KEY The id given for a

particular branch,
year, semester and
2 BRANCH VARCHAR2 (30) NOT NULL Branch
section
3 YEAR NUMBER (10) NOT NULL Year
4 SEM NUMBER(10) NOT NULL Semester

5 SEC NUMBER(10) NOT NULL Section
Table Name: MAP_FACULTY
21
Feedback System
ATTRIBUTE DATA TYPE CONSTRAINT DESCRIPTION

SN NAME S
1O BID NUMBER (30) PRIMARY KEY Id of a particular
branch, year,
semester and section
2 FAC1 VARCHAR2 (100) NOT NULL Faculty1
TABLE NAME : IPS

SNO TE
1 NAME
IP VARCHAR2(30) PRIMARY KEY It stores the ip
addresses of clients
Table Name: MAP_SUBJECTS
22
Feedback System
ATTRIBUTE DATA TYPE CONSTRAINT DESCRIPTION

SN NAME S
1O BID NUMBER (30) PRIMARY KEY Id of a particular
branch, year,
semester and section
2 SUB1 VARCHAR2 (100) NOT NULL Subject1
23
Feedback System
TABLE NAME : FEEDBACK
ATTRIBUT DATA TYPE CONSTRAINTS DESCRIPTION

SNO E
1 NAME
BID NUMBER(10) PRIMARY KEY Id of a particular
branch, year, semester
and section
2 FACNAME VARCHAR2 (100) NOT NULL The Faculty Name
3 SUBNAME VARCHAR2(100) NOT NULL The Subject Name
4 QNO NUMBER(10) NOT NULL The question no.

5 GRADE NUMBER(10) NOT NULL Grade for an option
6 COUNT VARCHAR2(50) NOT NULL Howmany no. of
grades for a particular
TABLE NAME : SUGGESTION row
SNo ATTRIBU DATA TYPE CONSTRA DESCRIPTION

TE INTS
1 NAME
BID NUMBER(10) PRIMARY Id of a particular
KEY branch, year, semester
2 COMM VARCHAR2 (3000) and section
Suggestions
TABLE NAME : MGMT
SNo ATTRIBUTE DATA TYPE CONSTRAI DESCRIPTION

NAME NTS
1 MGMID VARCHAR2(30) PRIMARY Login Id of
KEY Management
2 MGMPWD VARCHAR2 (30) PRIMARY Password of
KEY Management
24
Feedback System
3.2 UML Diagrams

The Unified Modeling Language is a standard language for Specifying,
Visualizing, Constructing and Documenting the software system and its components. It is a
graphical language, which provides a vocabulary and set of semantics and rules.
3.2.1 Usecase Diagrams
Use cases model the system from the end users point of view, with the following
objectives
 To define the functional and operational requirements of the system by defining a

scenario of usage.
 To provide a class and unambiguous description of how the end user and the
system interact with one another.
 To provide a basis for validation testing.
M ap S ub je cts a nd F a culty
adm inistra tor
Initialise Fe e db a ck
S ub m it Fe edba ck S tudents
V iew Re p orts M anag em ent
25
Feedback System
Fig. 3.2.1 Usecase Diagram
3.2.2 Class Diagram

The Class diagram shows the building blocks of any object-orientated system.
Class diagrams depict a static view of the model, or part of the model,
describing what attributes and behavior it has rather than detailing the methods
for achieving operations. Class diagrams are most useful in illustrating
relationships between classes and interfaces. Generalizations, aggregations, and
associations are all valuable inreflecting inheritance, composition or usage, and
connections respectively.
Administrator
admin_id Provides feedback form
admin_pwd
Student
Insert faculty details()
Insert subject details() Submit Feedback()
Insert questions details() Submits feedback form
Map subjects and faculty()
Start Feedback()
Management
mgmt_id()
mgmt_pwd()
View reports()
Fig. 3.3.2 Class Diagram
26
Feedback System
3.2.3 Sequence Diagram

A Sequence diagram is an interaction diagram that emphasizes the time
ordering of messages. A sequence diagram shows a set of objects and the
messages sent and received by those objects. The objects are typically named or
anonymous instances of classes, but may also represent instances of other things,
such as collaborations, components, and nodes.
Administrato Student
r
1: Provides Feedback Form
2: Submits Feedback Form
Fig. 3.3.3 Sequence Diagram
3.3.4 Collaboration Diagram
27
Feedback System
They show the relationship between objects and the order of messages
passed between them. The objects are listed as icons and arrows indicate the messages
being passed between them.. As the name suggests, they show the sequence of the
messages s they are passed between the objects. A simple 1, 2, 3… format can be used as
the example below shows for more detail and complex diagrams a 1, 1.1, 1.2, 1.2.1…….
schemes can be used.
1: Provides Feedback Form

Administr Student
ator
2: Submits Feedback Form
Fig. 3.3.4 Collaboration Diagram
3.3.5 State Chart Diagram
The diagrams describes the state of activities by showing the sequence of activities
performed.
28
Feedback System
Feedback
Started
Feedback
Submitted
Reports
Generated
Fig. 3.3.5 State chart Diagram
3.3.6 Activity Diagram
29
Feedback System
login Mgmt
Admin
Enter Faculty Select
Details branch
Enter Subject View

Details Reports
Enter Question
Details
Select
branch,year,sem,sect
If Mapping
exists
Yes No
Do Mapping of
subjects and faculty
Start
Feedback
Students Submit
Feedback
Fig. 3.3.6 Activity Diagram
4. SYSTEM IMPLEMENTATION
30
Feedback System
4.1 Selected Software
4.1.1 HTML
HTML - HYPER TEXT MARKUP LANGUAGE
Html is a language which is used to create web pages with html marking up
a page to indicate its format, telling the web browser where you want a new line to
begin or how you want text or images aligned and more are possible.
4.1.1.1 HTML Tags

Tags are instructions that are directly embedded into the text of a document.
An HTML tag is a signal to the browser that it should do something other than just
throw text up on the screen other than just throw text up on the screen. By
convention all HTML tags begin with an open angle bracket (<) and with a close
angle bracket (>). We utilized the following tags in our project.
<font size=”size” >…..</font>

The text that appears between the opening and closing tags is displayed in the size
specified in the size attribute of the font tag.
<form>…</form>
The form tag is used to create an HTML form and is placed within the body tag of the
web page. The form tag has 2 attributes.
Method: The value of this attribute describes how data collected in the form is sent to the
Server. The default value of Method is GET.
Action: The value of this attribute defines the server-side component that is called to
process the form.
<input type=”text” name=”name” size=”size”>
This tag creates a text box. The value of the ‘type’ attribute is “text”. The value of the
‘name’ attribute is the field name. The field name is used to identify data that is entered
into the field when the data is sent to the processing component.
The value of ‘size’ attribute is the number of characters wide the text box appears.
<input type=”password” name=”name” size=”size”>
31
Feedback System
This tag creates a password box in that a user is able to enter free-form text. Characters
entered into a password box are replaced on te screen with either bullets or asterisks.
Characters that are actually entered by the user are assigned to the field name defined in
the ‘name’ attribute.
<textarea name=”name” rows=”no” cols=”no”></textarea>
This tag creates a textarea. The value of ‘rows’ attribute defines the height of the textarea
on the form. The value of the ‘cols’ attribute defines the width on the browser.
<input type=”radio” name=”name” value=”value”>
This tag creates a set of radio buttons that are used by aperson to choose on of a set of
options. Whenever a radio button within the set is selected by the user, all the other radio
buttons within the set are unselected.
<input type=”checkbox” name=”name” value=”value”>
This tag creates checkboxes which are grouped into sets. A user can select multiple
check boxes within the same group.
<select name=”name”><option value=”value”>…</select>
This tag creates a menu. The value of ‘name’ attribute is the field name. The value of
‘value’ attribute is the data that is associated with the option.
<input type=”submit” value=”value”>
A submit button, when selected by a user, is the button that causes the browser to extract
the field name and data from the form and send them to the processing component.
<input type=”reset” value=”value”>
A reset button resets fields to their values when the form was originally displayed on the
web page.
<table><tr><th><td>…</td></th></tr></table>
This tag creates a table. The TR tag defines a row. The TH tag defines cell header. The
TD tag defines data cell.
32
Feedback System
4.1.2 JavaScript
JavaScipt is designed to add interactivity to HTML pages and it is a scripting
language. This is used in millions of web pages to improve the design, validate forms and
much more. JavaScript was developed by Netscape and works in all major browsers.
JavaScript
• Gives HTML designers a programming tool.
• Can put dynamic text into an html page.
• Can react to events.
• Can read and write HTML elements.
• Can be used to validate data.
4.1.2.1 Tags and Attributes

<script> Identifies the script section in the document.
language=”javascript” Specifies the scripting language.
type=”text/javascript” Provides the script MIME type.
4.1.2.2 Functions
A function is a reusable code-black that will be executed by on event, or when the
function is called.
function functionName ( parameterName)
{
Statements;
}
4.1.2.3 Events
Events are actions that can be detected by JavaScript. Every element on a web page has
certain events which can trigger a JavaScript.
Event Description
1) onLoad This event is triggered when the user enters the page.
It
33
Feedback System
is used to check the visitor’s browser type and

version.
2) onUnload This event is triggered when the user leaves the page
and closes the web page.
3) onSubmit This event is used to validate all from fields before
submitting it. This function returns either true or
false.
If true the from will be submitted, otherwise the
submit
will be cancelled.
4) onMouseOver This event is generated when mouse is moved over
an
image.
5) onMouseOut This event is generated when mouse is moved out of
window.
4.1.3 JSP
The JSP language has a simple development and maintenance process. A JSP file
that has the extension .jsp is converted into a servlet .java which is dynamically compiled,
loaded and executed. Only when there is a change in a JSP file, the conversion,
compilation and loading process is then performed.
A .jsp file can contain JSP elements, fixed template data or any combination’s of
two. There are 3 types of JSP elements:
1. Directives
2. Scripting Elements
3. Actions
34
Feedback System
4.1.3.1 Directives
Directives are instructions to the JSP container that describes what code should be
generated.
<%@ directive name [attribute=”value” attribute=”value”…%>
Page Directive
This directive is used to specify the attributes for JSP page as a whole.
<%@ page [attribute=value”…%>
Include Directive
This directive merges the content of another file as translation time into the .jsp
sources input stream.
<%@ include file=”filename”%>
Taglib Directive
This directive makes the custom actions available in the current page to the use of a
tag library.
<%@ taglib uri=”taglibraryuri” prefix=”tag prefix” %>
4.1.3.2 Scripting Elements

There are 3 types of scripting elements.
Expressions
JSP provides a simple means for accessing the value of a java variable or other
expressions and merging that value or other expression and merging that value with the
HTML in the page.
<%= expression %>
Scriplets
Scriptlets is a set of one or more java language statements is intended to be use
process on HTTP request.
<% statements; %>
Declarations
Declaration section can be used to declare class or instance variables or methods, or
inner classes.
<%! Statement %>
35
Feedback System
4.1.3.3 Actions
Actions are high level JSP elements that creates, modify or use other objects. A JSP
action is executed when a JSP page is requested. They represent dynamic actions that take
place at runtime, as opposed to JSP directives that are used only during the translation
phase.
<prefix:action-name attr1=”value1” attr2=”value2”>
action_body
</prefix:action_name>
4.1.4 Database
Every business enterprise maintains large volume of data for its operations.
With more and more people accessing this data for their work the need to maintain
its integrity and relevance increase. Normally, with the traditional methods of
storing data and the information in files, the changes that the data loses its integrity
and validity are very high. Oracle 10g is an Object Relational Database
management system (ORDBMS). It offers capabilities of both relational and object
oriented database systems. In general, objects can be defined as reusable software
codes which are location independent and perform a specific task on any application
environment with little or no change to the code.
4.1.4.1 Drivers
JDBC driver specification classifies JDBC drivers into 4 groups. Each group
is referred to as a JDBC driver type and addresses a specific need for
communicating with various DBMSs.
Type 1 JDBC-to-ODBC Driver
Microsoft was the first company to devise a way to create a DBMS-

independent database program. The JDBC-to-ODBC Driver, also called the
JDBC/ODBC Bridge, is used to translate DBMS calls between the JDBC
specification and the ODBC specification. The JDBC-to-ODBC driver receives
messages from a J2EE component. Those messages are translated by this driver into
36
Feedback System
ODBC message format, which is then translated into the message format understood
by the DBMS.
Type 2 Java/Native code Driver
This driver uses Java classes to generate platform-specific code- that is, code
understood by a specific DBMS. The disadvantage fo this driver is the loss of some
portability of code. The API classes for the Java/Native code driver probably won’t
work with another manufacuturer’s DBMS.
Type 3 JDBC Driver
This driver also referred to as the Java Protocol, is the most commonly used
JDBC driver. This driver converts SQL queries into JDBC- formatted statements.
These statements are translated into the format required by the DBMS.
Type 4 JDBC Driver
This driver is also known as Type 4 database protocol. This driver is similar
to the type 3 jdbc driver except SQL queries are translated into the format required
by the DBMS. SQL queries donot need to be converted to JDBC-formatted systems.
This is the fastest way to communicate SQL queries to the DBMS.
4.1.4.2Tools of Oracle
The tools provided by Oracle are so user friendly that a person with
minimum skills in the field of computers can access them with ease. The main tools
are:
SQL*plus
SQL*Plus is a Structured query language supported by Oracle. Through

SQL*plus we can store, retrieve, edit, enter and run SQL commands and PL/SQL
blocks. Using SQL*Plus we can perform calculations, list column definitions for
any table and can also format query results in the form of a report.
37
Feedback System
PL/SQL
PL/SQL is an extension of SQL. PL/SQL block can contain a number of

SQL statements integrated with flow of control statements. Thus PL/SQL combines
the data manipulating power of SQL with data processing power of procedural
languages.
Forms
This is a graphical too used for generating and executing forms based
applications. A form basically comprises blocks and fields. Multiple tables can be
accessed over a single form, based on the application with the help of transaction
commands. Oracle Forms Builder is the design component of Oracle forms. We
can build, generate and run an Oracle Forms application form the builder.
Reports
It is an application development tool of oracle for developing, executing,

displaying and printing reports. We can create a wide variety of reports, which have
various modes that are explained in later chapters. Oracle reports are powerful, yet
easy to use.
38
Feedback System
4.1.5 Tomcat
The Tomcat server is a Java-based Web Application container that was
created to run Servlet and Java Server Pages (JSP) Web applications. It has become
the reference implementation for both the Servlet and JSP specifications.
The Java Servlet and JSP specifications are being developed by Sun under
the “Java Community Process.” Tomcat 5.0.25 implements Servlets 2.3 and JSP 1.2
API Specifications.
Tomcat Environment Setup

1. Create a folder from the root directory called tomcat.
2. Download the Jakarta-tomcat.zip from jakarta.apache.org to the tomcat folder.
3. Unzip Jakarta-tomcat.zip. The extraction process should create the following folders in
the
tomcat directory: bin, conf, doc, lib, src and webapps.
4. Use a text editor and edit the JAVA_HOME variable in the tomcat.bat file, which is
located
in the \tomcat\bin folder. Make sure the JAVA_HOME variable is assigned the path
where
the JDK is installed on your computer.
5. Open a DOS window and type \tomcat\bin\tomcat to start Tomcat.
39
Feedback System
4.2 Sample Code

admin_view2.jsp
<%@ page import="java.sql.*"%>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html >
<head>
<title>ADITYA INSTITUTIONS..</title>
<link href="styles1.css" rel="stylesheet" type="text/css" media="screen" >
<script lang="javascript">
function backButtonOverride()
{
setTimeout("backButtonOverrideBody()", 1);
}
function backButtonOverrideBody()
{
try
{
history.forward();
}
catch (e)
{
}
}
function show(theSelectBox) {
var Idx = theSelectBox.selectedIndex;
var Url = theSelectBox.options[Idx].value;
40
Feedback System
location = Url;
}
function infoscroll(seed,looped)
{
var text1 = "Developed by Aditya Engineering Students
Sharmitha.....Sirisha.....Alekhya.....Anusha..... ";
var text2 = " Under guidance of Mr.Bhaskar.......(Thankq....,) ";
var msg=text1+text2;
var putout = " ";
var c = 1;
if (looped > 10)
{ window.status="<Thanks !>"; }
else if (seed > 100)
{
seed--;
var cmd="infoscroll(" + seed + "," + looped + ")";
timerTwo=window.setTimeout(cmd,100);
}
else if (seed <= 100 && seed > 0)
{
for (c=0 ; c < seed ; c++)
{ putout+=" "; }
putout+=msg.substring(0,100-seed);
seed--;
window.status=putout;
}
41
Feedback System
else if (seed <= 0)

{
if (-seed < msg.length)
{
putout+=msg.substring(-seed,msg.length);
seed--;
}
else
{
window.status=" ";
looped += 1;
var cmd = "infoscroll(100," + looped + ")";
timerTwo=window.setTimeout(cmd,75); // 75
}
}
}
// -->

</script>
</head>
<body onLoad="backButtonOverride()">
<div id="sitebg">
<div id="sitebg2">
42
Feedback System
<div id="content">



<div id="main">
<div id="header">
<div id="wel">Welcome To FeedBack System</div>
<div id="logo">
<h1><a href="#">ADITYA</a></h1>
<h2><a href="#" >ENLIGHTENS THE NESCIENCE</a></h2>
</div>
<div id="menu">
<ul>
<li id="button1"><a href="index.html" title="">HOME</a></li>
<li id="button2"><a href="mgmt_login.html"
title="">REPORTS</a></li>
<li id="button3"><a href="view_faculty.jsp"
title="">FACULTY</a></li>
<li id="button4"><a href="view_subjects.jsp"
title="">SUBJECTS</a></li>
<li id="button4"><a href="view_questions.jsp"
title="">QUESTIONS</a></li>
</ul>
</div>
</div>
<div id="right">
<div id="righttop">
<br><br><br><br><br><br><br><br><br>
43
Feedback System
<%
try
{
Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
Connection con=DriverManager.getConnection("jdbc:odbc:feed","system","intel123");
Statement st=con.createStatement();
ResultSet rs;
%>
<form action="session1.jsp" method="post">
<center>
<br><br><br><br>
<table align=center>
<tr>
<th><font color="#6d0202" size=3>Branch</th></font>
<th>
<select name="branch"><option value="sel">[select]</option>
<option value="CSE">CSE</option>
<option value="IT">IT</option>
<option value="ECE">ECE</option>
<option value="EEE">EEE</option>
<option value="MEC">MECH</option>
<option value="CIV">CIVIL</option>
<option value="BSE">BSE</option>
</select>
</th>
<th><font color="#6d0202" size=3>Year</th></font>
<th>
<select name="year"><option value="sel">[select]</option>
44
Feedback System
<option value="1">1</option>
</select>
</th>
</tr>
<tr >
<th colspan=4> </th>
</tr>
<tr>
<th><font color="#6d0202" size=3>Semester</th></font>
<th>
<select name="sem"><option value="sel">[select]</option>
</select>
</th>
<th><font color="#6d0202" size=3>Section</th></font>
<th>
<select name="sect"><option value="sel">[select]</option>
</select>
</th>
</tr>
<tr>
<th> </th>
45
Feedback System
</tr>
<th colspan=5><input type="submit" value="Start Session"></th>
</tr>
</table>
</center>
</form>
<%
}
catch(Exception e)
{
out.println(e);
}
%>
</div>
<div id="post">
<div class="more"><a href="#"></a></div>
</div>
</div>
<div id="left">
<div style="line-height:23px;" > </div>
<div style="float:left; padding-left:35px;"><img
src="images/emblem.jpg" alt="testing"/></div>
<div style="float:left; padding-left:65px; padding-top:35px;"><img
src="images/feedback.jpg" alt="testing"/></div>
</div>
46
Feedback System
<div id="footer">
<p><font size=6 type="callibri" color="white"><i>ADITYA ENGINEERING
COLLEGES</i></font></p>
</div>
</div>
</div>
</div>

</body>
</html>
mapping.jsp
<html >
<head>
<link href="styles1.css" rel="stylesheet" type="text/css" media="screen" />
{
}
{
try
{
47
Feedback System
history.forward();
}
catch (e)
{
}
}
location = Url;
}
{
var putout = " ";
var c = 1;
if (looped > 10)
{
seed--;
}
48
Feedback System

{
for (c=0 ; c < seed ; c++)
{ putout+=" "; }
seed--;
}
else if (seed <= 0)
{
{
seed--;
}
else
{
window.status=" ";
looped += 1;
}
}
49
Feedback System
}
// -->

</script>
</head>
<div id="sitebg">
<div id="sitebg2">
<div id="content">
<div id="main">
<div id="header">
<div id="logo">
</div>
<div id="menu">
<ul>
<li id="button1"><a href="index.html" title="">Home</a></li>
<li id="button2"><a href="delete_mapping.jsp" title="">DELETE
MAP</a></li>
50
Feedback System
<li id="button3"><a href="feed_back1.jsp"

title="">FEEDBACK</a></li>
</ul>
</div>
</div>
<div id="right">
<div id="righttop">
<%
try
{
Statement st1=con.createStatement();
ResultSet rs;
ResultSet rs1;
String branch=(String)application.getAttribute("branch1");
String year=(String)application.getAttribute("year1");
String sem=(String)application.getAttribute("sem1");
String sect=(String)application.getAttribute("sect1");
String sub1=request.getParameter("sub1");
51
Feedback System
String fac1=request.getParameter("fac1");
int bid,b;
rs=st.executeQuery("select bid from identify where branch=Upper('"+branch+"') and
year='"+year+"' and sem='"+sem+"' and sec='"+sect+"'");
if(rs.next())
{
bid=rs.getInt(1);
52
Feedback System
st3.executeUpdate("insert into map_subjects

values("+bid+",'"+sub1+"','"+sub2+"','"+sub3+"','"+sub4+"','"+sub5+"','"+sub6+"','"+sub7
+"','"+sub8+"','"+sub9+"','"+sub10+"','"+sub11+"','"+sub12+"')");
st4.executeUpdate("insert into map_faculty
values("+bid+",'"+fac1+"','"+fac2+"','"+fac3+"','"+fac4+"','"+fac5+"','"+fac6+"','"+fac7+"','
"+fac8+"','"+fac9+"','"+fac10+"','"+fac11+"','"+fac12+"')");
%>
<br><br>
<center><font size=4 color="#6d0202">Subjects and Faculty are
Mapped</font></center>
<%
}
else
{
rs1=st1.executeQuery("select max(bid) from identify");
if(rs1.next())
{
b=rs1.getInt(1);
b+=1;
st2.executeUpdate("insert into identify
values("+b+",Upper('"+branch+"'),"+year+","+sem+","+sect+")");
st3.executeUpdate("insert into map_subjects
values("+b+",'"+sub1+"','"+sub2+"','"+sub3+"','"+sub4+"','"+sub5+"','"+sub6+"','"+sub7+"'
,'"+sub8+"','"+sub9+"','"+sub10+"','"+sub11+"','"+sub12+"')");
st4.executeUpdate("insert into map_faculty
values("+b+",'"+fac1+"','"+fac2+"','"+fac3+"','"+fac4+"','"+fac5+"','"+fac6+"','"+fac7+"','"
+fac8+"','"+fac9+"','"+fac10+"','"+fac11+"','"+fac12+"')");
%>
<br><br>
53
Feedback System
<center><font size=4 color="#6d0202">Subjects and Faculty are

Mapped</font></center>
<%
}
}
}
catch(Exception e)
{
%>
<br><br>
<br><br><br><br><br><br>
<font size=3 color="#6d0202"><center>Details Already Exist</center></font>
<%
}
%>
</div>
<div id="post">
</div>
</div>
<div id="left">
src="images/feedback.jpg" alt="testing"/></div> </body></html>
action_faculty.jsp
54
Feedback System

<html >
<head>
<link href="styles1.css" rel="stylesheet" type="text/css" media="screen" />
{
}
{
try
{
history.forward();
}
catch (e)
{
}
}
function validate(form1)
{
var a=form1.branch.value;
var b=form1.facname.value;
var c=form1.faccode.value;
55
Feedback System
if(a=="" || b=="" || c=="")

{
window.alert("Enter details");
return false;
}
else
form1.action="store_faculty.jsp";
}
function validate1(form2)
{
var b=form2.fname.value;
var c=form2.fcode.value;
if(b=="" || c=="")
{
window.alert("Enter details");
return false;
}
else
form2.action="update_faculty.jsp";
}
location = Url;
}
{
56
Feedback System

var putout = " ";
var c = 1;
if (looped > 10)
{
seed--;
}
{
for (c=0 ; c < seed ; c++)
{ putout+=" "; }
seed--;
}
else if (seed <= 0)
{
{
57
Feedback System
seed--;
}
else
{
window.status=" ";
looped += 1;
}
}
}
// -->

</script>
</head>
<div id="sitebg">
<div id="sitebg2">
<div id="content">
58
Feedback System
<div id="main">
<div id="header">
<div id="logo">
</div>
<div id="menu">
<ul>
<li id="button1"><a href="index.html" title="">HOME</a></li>
<li id="button4"><a href="view_subjects.jsp"
title="">SUBJECTS</a></li>
<li id="button5"><a href="admin_view2.jsp" title="">START
SESSION</a></li>
</ul>
</div>
</div>
<div id="right">
<div id="righttop">
<%
try
{
String button1=request.getParameter("new");
String button2=request.getParameter("update");
String button3=request.getParameter("delete");
59
Feedback System
ResultSet rs;
/*******************NEW FACULTY**********************/
if(button1!=null)
{
%>
<br><br><br><br><br><br><br>
<center>
<form name="form1" onsubmit="return validate(this)" method="post">
<table>
<tr>
<th><font color="#6d0202" size=3>Branch</font></th>
<th> </th>
<th><select name="branch"><option value="CSE">CSE</option>
<option value="BSE">BSE</option>\
</select>
</th>
</tr>
<tr>
<th> </th>
</tr>
60
Feedback System
<tr>
<th><font color="#6d0202" size=3>Faculty Name</font></th>
<th> </th>
<th><input type="text" name="facname" size=10></th>
</tr>
<tr>
<th> </th>
</tr>
<tr>
<th><font color="#6d0202" size=3>Faculty Code</font></th>
<th> </th>
<th><input type="text" name="faccode" size=10></th>
</tr>
<tr>
<th> </th>
</tr>
<tr>
<th colspan=3><input type="submit" value="Submit"></th>
</tr>
</table>
</form>
</center>
<%
}
/****************************UPDATE FACULTY*********************/
else if(button2!=null)
{
61
Feedback System
String select=request.getParameter("select");
String branch,facname;
int faccode;
if(select!=null)
{
rs=st.executeQuery("select branch,facname,code from faculty where
code="+select+"");
if(rs.next())
{
branch=rs.getString(1);
facname=rs.getString(2);
faccode=rs.getInt(3);
session.setAttribute("dept",branch);
session.setAttribute("facname1",facname);
session.setAttribute("faccode1",faccode);
%>
<br><br><br><br><br>
<center>
<form name="form2" onsubmit="return validate1(this)" method="post">
<table>
<tr>
<th><font color="#6d0202" size=3>Branch</font></th>
<th><select name="branch"><option value="CSE">CSE</option>
62
Feedback System
<option value="BSE">BSE</option>
</select>
</th>
</tr>
<tr>
<th> </th>
</tr>
<tr>
<th><font color="#6d0202" size=3>Faculty Name</font></th>
<th><input type="text" name="fname" size=10 value="<%=facname%>"></th>
</tr>
<tr>
<th> </th>
</tr>
<tr>
<th><font color="#6d0202" size=3>Faculty Code</font></th>
<th><input type="text" name="fcode" size=10 value="<%=faccode%>"></th>
</tr>
<tr>
<th> </th>
</tr>
<tr>
<th colspan=2><input type="submit" value="Submit"></th>
</table>
</form>
</center>
<%
}
63
Feedback System
}
else
{
%>
<center>
<font color="#6d0202" size=3>Select Faculty</font>
</center>
<%
}
}
/*******************************DELETE FACULTY***********************/
else if(button3!=null)
{
String select=request.getParameter("select");
if(select!=null)
{
st.executeUpdate("delete from faculty where code='"+select+"'");
response.sendRedirect("view_faculty.jsp");
}
else
{
%>
<br><br>
<a href="view_faculty.jsp"><font color="#6d0202" size=3>View Faculty</font></a>
<center>
64
Feedback System
<font color="#6d0202" size=3>Select Faculty</font>

</center>
<%
}
}
}
catch(Exception e)
{
out.println(e);
}
%>
</div>
<div id="post">
</div>
</div>
<div id="left">
src="images/feedback.jpg" alt="testing"/></div>
</div><div id="footer">
<p><font size=6 type="callibri" color="white"><i>ADITYA ENGINEERING
COLLEGES</i></font></p>
</div>
</div></body></html>
65
Feedback System
5. TEST CASES
Test Input Description Expected Result Pass/Fail

Case Id
1 Admin Id While login, admin If id is not matched Pass
entered must enter his id and with the password, it
password must show a warning.
2 Faculty The admin can view The code of faculty Pass
details the faculty details. must be unique,
otherwise it must
show an error
3 Subject The admin can view The code of subject Pass

details the subjects’ details. must be unique,
otherwise it must
show an error
4 Map subjects The admin maps the The system must show Pass
and faculty subjects and faculty a warning if any
for respective sections required subject or
faculty is not matched
5 Trying to map The admin may try to It must display a Pass
for the map the subjects and message as the
existing ones faculty for already mapping already exists
mapped ones
66
Feedback System
6 Submit The feedback form is The student must not Pass

Feedback displayed for the leave any feedback
student form empty. If he/she
tries to do it, it gives a
warning
7 Submitting The student may try to It must show an error Pass

feedback form access the feedback message and the
again form again feedback form should
not be displayed again
8 Mgmt Id While login, If id is not matched Pass
entered management must with the password, it
enter his id and must show a warning
password
9 Admin After login, the admin The student should not Pass
activites has some activities to be able to view the
do activities of admin
10 Reports The management The student should not Pass
views the feedback be able to view the
reports reports
11 Reports The reports should be The admin has no Pass
viewed only by access to view the
management reports
67
Feedback System
6.SCREENS AND REPORTS
Screen for admin login
Fig. 6.1 admin login
68
Feedback System
Screen For Viewing Faculty
Fig. 6.2 Faculty Details
Screen for Inserting new faculty
69
Feedback System
Fig. 6.3 Inserting New Faculty
70
Feedback System
Screen for exception if a faculty already exists
Fig. 6.4 Exception
71
Feedback System
Screen For Viewing Subject Details
Fig. 6.5 Subject Details
72
Feedback System
Screen For Viewing Question Details
Fig.6.6 Question Details
73
Feedback System
Screen For Selecting Branch Details
Fig.6.7 Branch Selection
74
Feedback System
Screen For Mapping Subjects and Faculty
Fig.6.8 Mapping Subjects and Faculty
75
Feedback System
Screen For Feedback Form
Fig.6.9 Feedback Form1
76
Feedback System
77
Feedback System
78
Feedback System
Screen for trying to access feedback from again
Fig.6.12 Trying to access the form again
79
Feedback System
Screen for Management login
Fig. 6.13 Management login
80
Feedback System
Screen For Selecting Branch For Reports
Fig.6.14 Selecting Branch
81
Feedback System
Screen For Viewing Reports
Fig.6.15 Reports
82
Feedback System
Screen For Viewing Reports
Fig.6.16 Reports
83
Feedback System
7. CONCLUSION AND FUTURE SCOPE
7.1 Conclusion :
This computerized feedback system reduced the paper work and complexity of
computation. This system is reliable as it is giving exact reports. This is more secure as the
students ids are not revealed. As this system is portable, it can be implemented in any
college.
7.2 Future Scope :
 We can extend this project to be more configurable like the administrator of the
college can define number of branches, sections, subjects and so on.
 We can also generate different kinds of reports like date-wise reports, year-wise
reports etc.
 We can expand this system for any number of branches and colleges.
84
Feedback System
8.BIBLIOGRAPHY
8.1 Books Referred :
SNO Author Book Publisher VolNo. Year

1 Jim Keogh J2EE:The Complete Tata 19th edition 2007
Reference McGraw-
Hill
2 The unified Grady booch - Pearson 2nd edition 2008
Modeling James Education
language : Ivar Jacobson
user guide
3 Software Roger.S.Pressman TMH ltd 6th edition 2006
Engineering
4 Internet and Dietle and Nieto Pearson 2nd edition 2005
world wide education
- web
8.2 Web Sites Visited :
http://www.javaworld.com/javaworld/jw-04-2006/jw-0417-push.html
http://www.google.com
www.wikipedia.com
85

Feedback

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Feedback

Uploaded by

Copyright:

Available Formats

Feedback System

1.1 Existing System

Disadvantages of Existing System

1.2 Proposed System

1.2.1 Key Features of Proposed System

1.2.2 Scope and Purpose of the System

1.2.3 System Description

1.2.3.1 Administrator Module

 View the Faculty Details

 View Subjects Details

 View the Questions Details

 Map Subjects and Faculty

 Delete Existed Mapping

 Delete Existed Feedback

1.2.3.2 Student Module

1.2.3.3 Management Module

1.2.4 Advantages of Proposed System

2.1 Hardware And Software Requirements

2.1.1 Hardware Requirements :

2.1.2 Software Requirements :

2.1.3 Functional Requirements:

2.2 Software Requirement Specification (SRS)

The FeedBack System is a computerised system that makes the management to be

Student Any student of a college or University

2.2.3 System Functions

SNO SYSTEM Feed Back Administration

2.2.4 Detailed Software Requirements

2.2.4.1 Use case model

Actor Name Administrator

Actor Name Student

Actor Name Management

Frequency of Use High

2.2.4.2 List of Use Cases

Use Case Name Conducting feedback

S6. To map the subjects and

2. User selects one of the 2.1 The selected option (sub

S2: Update the details of subjects and faculty

S3: Delete the details of subjects and faculty

1.User selects S3. 1.1 System prompts the user

S4: Inserting new questions

S5: Delete the existed questions

S6: Map subjects and faculty

S7: Delete Mapping

S8: Start a feedback for students

S9: Delete Existed Feedback

the existed feedback and

Exception E1. If any subject or faculty name is not properly inserted, it

section, not the student.

System 1 : s e le c ts b ra n c h ,ye a r ,s e m e s te r a n d s e c tio n o f s tu d n e ts

Fig. 2.2.4.2.1 Conducting Feedback

Use Case Submit feedback

Sub Flows No subflows

1: submits the feedback

student provide feedback

Fig. 2.2.4.2.1 Submit Feedback

Use Case Name View feedback

Sub Flows S1: Generate reports

S2: Export Report to Excel

view feedback report

Fig. 2.2.4.2.1 View Feedback

2.2.5 Functional Capabilities

 The feedback providers' identities should not be known.