Feedback Doc

8/8/2019 Feedback Doc

1/85

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


2/85

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


3/85

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


4/85

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


5/85

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


6/85

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


7/85


8/85

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


9/85

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 students 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

FUNCTION

Feed Back Administration

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


10/85

Feedback System

2.2.4 Detailed Software Requirements

2.2.4.1 Use case model

Actor Name Administrator

Actor Id ACT-01

DescriptionThe administrator of the college conducts the feedback

process

Main Activities

Selection of branch ,year, semester and section for

which course the feedback is to be provided.

Providing feedback form to the students

Frequency of Use High

Work Environment /

LocationBrowser

Number of Users 1

Actor Name Student

Actor Id ACT-02

Description The students of a college

Main ActivitiesGives the feedback for all the subjects and labs of a

particular branch,year,semester and section


Work Environment /

LocationBrowser

Number of Users Any number

Actor Name Management

Actor Id ACT-03

DescriptionThe college management which checks the feedback

report

Main Activities Views the reports for each faculty

10


11/85

Feedback System


Work Environment /

LocationBrowser

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 feedbackform to the students.

Preconditions Admin must have a login id and password

Main Flow 1. The administrator login to

the page.

1.1 The administrator gives

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


12/85

Feedback System

2. User selects one of the

options: for S1 to S9. For all

these, the branch, year,

semester and section should

be selected

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.1 The selected option (sub

flow) is executed.

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 subjectsand 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


13/85

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


Input fields to the user tomap 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


14/85

Feedback System

the existed feedback and

conduct new feedback.

Exception

Flows

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

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.

System

Sequence

Diagram

A d m i n i s t r a t or

S t u d e n

1 : s e l e c ts b r a n c h ,y e a r ,s e m e s t e r a n d s e c t i o n o f s t u

2 : P ro v id e s fe e d b a c k f o rm

14


15/85

Feedback System

login

administrator

initialise feedback

Fig. 2.2.4.2.1 Conducting Feedback

Use Case

Name

Submit feedback

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 thereMain Flow 1. The student will be given a

feedback form.

1.1 The student fills the

feedback form

Sub Flows No subflows

Exception

Flows

E1. If the user donot give the feedback properly, it will not be

submitted.

Post

Conditions

The feedback form is submitted

Cross

References

-

Assumptions The feedback is filled properly by the student

Business

Rules

Only the students can view the feedback form.

Only the student should give the feedback.

15


16/85

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


17/85

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 Flow1.The management

login to the page

1.1 The management views the

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 thefeedback in the form ofreports.

S2: Export Report to Excel

1.User selects S2. 1.1 The report isexported to excel.

Exception

Flows

E1. If there is no feedback for any faculty, the message should

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.

Fig. 2.2.4.2.1 View Feedback

17

view feedback report

Management

generate report


18/85

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


19/85

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

19

SNo ATTRIBUTE

NAME

DATA TYPE CONSTRAINTS DESCRIPTION

1 ADMINID VARCHAR2 (30) PRIMARY KEY Admin Login Id

2 ADMINPWD VARCHAR2 (30) PRIMARY KEY Admin Password


20/85

Feedback System

TABLE NAME : FACULTY

TABLE NAME : SUBJECTS

TABLE NAME : QUESTIONS

20

SNO

ATTRIBU

TE


1 BRANCH VARCHAR2 (30) PRIMARY KEY Branch of a Particular

Faculty

2 FACNAM

E

VARCHAR2 (100) PRIMARY KEY Name of Faculty

3 CODE NUMBER (10) PRIMARY KEY Unique code of

Faculty

SNO

ATTRIBUT

E

DATA TYPE CONSTRAINT

S

DESCRIPTION

1 BRANCH VARCHAR2 (30) PRIMARY KEY The branch related to

a particular subject2 FACNAME VARCHAR2 (100) PRIMARY KEY Name of Subject

3 CODE VARCHAR2(30) PRIMARY KEY Unique code of

Subject

SNO

ATTRIBU

TE


1 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


21/85

Feedback System

TABLE NAME : GRADES

TABLE NAME : IDENTIFY

Table Name: MAP_FACULTY

21

SNO

ATTRIBU

TE


1 GRADE NUMBER(10) PRIMARY KEY The grades given to

each option

2 EXPL VARCHAR2 (30) NOT NULL The explanation of

the grade

SNOATTRIBUTENAME


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

particular branch,

year, semester and

2 BRANCH VARCHAR2 (30) NOT NULL Branch

3 YEAR NUMBER (10) NOT NULL Year

4 SEM NUMBER(10) NOT NULL Semester

5 SEC NUMBER(10) NOT NULL Section


22/85

Feedback System

TABLE NAME : IPS

Table Name: MAP_SUBJECTS

22

SN

ATTRIBUTE

NAME


S

DESCRIPTION

1 BID NUMBER (30) PRIMARY KEY Id of a particular

branch, year,

semester and section2 FAC1 VARCHAR2 (100) NOT NULL Faculty1

3 FAC2 VARCHAR2 (100) NOT NULL Faculty2











SNOATTRIBUTE


1 IP VARCHAR2(30) PRIMARY KEY It stores the ip

addresses of clients


23/85

Feedback System

23

SN

ATTRIBUTE

NAME


S

DESCRIPTION

1 BID NUMBER (30) PRIMARY KEY Id of a particular

branch, year,

semester and section2 SUB1 VARCHAR2 (100) NOT NULL Subject1

3 SUB2 VARCHAR2 (100) NOT NULL Subject2












24/85

Feedback System

TABLE NAME : FEEDBACK

TABLE NAME : SUGGESTION

TABLE NAME : MGMT

24

SNO

ATTRIBUT

E


1 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

SNo ATTRIBU

TE

DATA TYPE CONSTRA

INTS

DESCRIPTION

1 BID NUMBER(10) PRIMARY

KEY

Id of a particular

branch, year, semester

2 COMM VARCHAR2 (3000) Suggestions

SNo ATTRIBUTENAME

DATA TYPE CONSTRAINTS

DESCRIPTION

1 MGMID VARCHAR2(30) PRIMARY

KEY

Login Id of

Management

2 MGMPWD VARCHAR2 (30) PRIMARY

KEY

Password of

Management


25/85

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.

View Rep orts

Map Subjects and Fa culty

administrator

Initialise Feedback

StudentsSubmit Feedback

Management

25


26/85

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.

Managementmgmt_id()

mgmt_pwd()

View reports()

Student

Submit Feedback()

Administratoradmin_id

admin_pwd

Insert faculty details()

Insert subject details()

Insert questions details()

Map subjects and faculty()

Start Feedback()

Provides feedback form

Submits feedback form

Fig. 3.3.2 Class Diagram

26


27/85

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.

Administrator

Student

1: Provides Feedback Form

2: Submits Feedback Form

Fig. 3.3.3 Sequence Diagram

3.3.4 Collaboration Diagram

27


28/85

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.

Administrator

Student

1: Provides Feedback Form

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


29/85

Feedback System

FeedbackStarted

FeedbackSubmitted

ReportsGenerated

Fig. 3.3.5 State chart Diagram

3.3.6 Activity Diagram

29


30/85

Feedback System

login

Enter FacultyDetails

Enter SubjectDetails

Enter Question

Details

Selectbranch,year,sem,sect

If Mappingexists

Do Mapping ofsubjects and faculty

StartFeedback

Students SubmitFeedback

Selectbranch

ViewReports

Admin

Mgmt

Yes No

Fig. 3.3.6 Activity Diagram

4. SYSTEM IMPLEMENTATION

30


31/85

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 (). We utilized the following tags in our project.

..

The text that appears between the opening and closing tags is displayed in the size

specified in the size attribute of the font tag.

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.

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.

31


32/85

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.

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.

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.

This tag creates checkboxes which are grouped into sets. A user can select multiple

check boxes within the same group.

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.

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.

A reset button resets fields to their values when the form was originally displayed on the

web page.

This tag creates a table. The TR tag defines a row. The TH tag defines cell header. The

TD tag defines data cell.

32


33/85

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

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 FunctionsA 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


34/85

Feedback System

is used to check the visitors 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 combinations of

two. There are 3 types of JSP elements:

1. Directives

2. Scripting Elements

3. Actions

34


35/85

Feedback System

4.1.3.1 Directives

Directives are instructions to the JSP container that describes what code should be

generated.

Page Directive

This directive is used to specify the attributes for JSP page as a whole.

Include Directive

This directive merges the content of another file as translation time into the .jsp

sources input stream.

Taglib Directive

This directive makes the custom actions available in the current page to the use of a

tag library.

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.

Scriplets

Scriptlets is a set of one or more java language statements is intended to be use

process on HTTP request.

Declarations

Declaration section can be used to declare class or instance variables or methods, or

inner classes.

35


36/85

Feedback System

4.1.3.3Actions

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.

action_body

4.1.4Database

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


37/85

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 wont

work with another manufacuturers 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


38/85

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


39/85

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


40/85

Feedback System

4.2 Sample Code

admin_view2.jsp

ADITYA INSTITUTIONS..

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


41/85

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=""; }

else if (seed > 100)

{

seed--;

var cmd="infoscroll(" + seed + "," + looped + ")";

timerTwo=window.setTimeout(cmd,100);

}

else if (seed 0)

{

for (c=0 ; c < seed ; c++)

{ putout+=" "; }

putout+=msg.substring(0,100-seed);

seed--;


window.status=putout;


}

41


42/85

Feedback System

else if (seed

42


43/85

Feedback System

Welcome To FeedBack System

ADITYA

ENLIGHTENS THE NESCIENCE

HOME

REPORTS

FACULTY

SUBJECTS

QUESTIONS

43


44/85

Feedback System

Branch

[select]

CSE

IT

ECE

EEE

MECH

CIVIL

BSE

Year

[select]

44


45/85

Feedback System

1

2

3

4

Semester

[select]

1

2

Section

[select]

1

2

45


46/85

Feedback System

46


47/85

Feedback System

ADITYA ENGINEERING

COLLEGES

mapping.jsp



{


}


{

try

{

47


48/85

Feedback System

history.forward();

}

catch (e)

{

}


}




location = Url;

}


{





var putout = " ";

var c = 1;

if (looped > 10)



{

seed--;



}

48


49/85

Feedback System

else if (seed 0)

{

for (c=0 ; c < seed ; c++)

{ putout+=" "; }


seed--;




}

else if (seed


50/85

Feedback System

}

// -->


ADITYA


Home

REPORTS

DELETE

MAP

50


51/85

Feedback System

FEEDBACK

FACULTY


52/85

Feedback System

String sub3=request.getParameter("sub3");










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


53/85

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+"')");

%>

Subjects and Faculty are

Mapped

53


54/85

Feedback System

Subjects and Faculty are

Mapped

Details Already Exist

action_faculty.jsp

54


55/85

Feedback System



{


}


{

try

{

history.forward();

}

catch (e)

{

}


}

function validate(form1)

{

var a=form1.branch.value;

var b=form1.facname.value;

var c=form1.faccode.value;

55


56/85

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


57/85

Feedback System





var putout = " ";

var c = 1;

if (looped > 10)



{

seed--;



}

else if (seed 0)

{

for (c=0 ; c < seed ; c++)

{ putout+=" "; }


seed--;




}

else if (seed


58/85


59/85

Feedback System


ADITYA


HOME

REPORTS

FACULTY

SUBJECTS

START

SESSION


60/85

Feedback System

Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");

Connection con=DriverManager.getConnection("jdbc:odbc:feed","system","intel123");

Statement st=con.createStatement();

ResultSet rs;

/*******************NEW FACULTY**********************/

if(button1!=null)

{

%>

Branch

CSE

IT

ECE

EEE

MECH

CIVIL

BSE\

60


61/85

Feedback System

Faculty Name

Faculty Code


62/85

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);

%>

Branch

CSE

IT

ECE

EEE

MECH

CIVIL

62


63/85

Feedback System

BSE

Faculty Name

Faculty Code


64/85

Feedback System

}

else

{

%>

Select Faculty

View Faculty

64


65/85

Feedback System

Select Faculty

ADITYA ENGINEERING

COLLEGES

65


66/85

Feedback System

5. TEST CASES

Test

Case Id

Input Description Expected Result Pass/Fail

1 Admin Id

entered

While login, admin

must enter his id and

password

If id is not matched

with the password, it

must show a warning.

Pass

2 Faculty

details

The admin can view

the faculty details.

The code of faculty

must be unique,

otherwise it must

show an error

Pass

3 Subject

details

The admin can view

the subjects details.

The code of subject

must be unique,

otherwise it must

show an error

Pass

4 Map subjects

and faculty

The admin maps the

subjects and faculty

for respective sections

The system must show

a warning if any

required subject or

faculty is not matched

Pass

5 Trying to map

for the

existing ones

The admin may try to

map the subjects and

faculty for already

mapped ones

It must display a

message as the

mapping already exists

Pass

66


67/85

Feedback System

6 Submit

Feedback

The feedback form is

displayed for the

student

The student must not

leave any feedback

form empty. If he/she

tries to do it, it gives a

warning

Pass

7 Submitting

feedback form

again

The student may try to

access the feedback

form again

It must show an error

message and the

feedback form should

not be displayed again

Pass

8 Mgmt Id

entered

While login,

management must

enter his id and

password

If id is not matched

with the password, it

must show a warning

Pass

9 Admin

activites

After login, the admin

has some activities to

do

The student should not

be able to view the

activities of admin

Pass

10 Reports The management

views the feedback

reports

The student should not

be able to view the

reports

Pass

11 Reports The reports should be

viewed only by

management

The admin has no

access to view the

reports

Pass

67


68/85

Feedback System

6.SCREENS AND REPORTS

Screen for admin login

Fig. 6.1 admin login

68


69/85

Feedback System

Screen For Viewing Faculty

Fig. 6.2 Faculty Details

Screen for Inserting new faculty

69


70/85

Feedback System

Fig. 6.3 Inserting New Faculty

70


71/85

Feedback System

Screen for exception if a faculty already exists

Fig. 6.4 Exception

71


72/85

Feedback System

Screen For Viewing Subject Details

Fig. 6.5 Subject Details

72


73/85

Feedback System

Screen For Viewing Question Details

Fig.6.6 Question Details

73


74/85

Feedback System

Screen For Selecting Branch Details

Fig.6.7 Branch Selection

74


75/85

Feedback System

Screen For Mapping Subjects and Faculty

Fig.6.8 Mapping Subjects and Faculty

75


76/85

Feedback System

Screen For Feedback Form

Fig.6.9 Feedback Form1

76


77/85

Feedback System



77


78/85

Feedback System



78


79/85

Feedback System

Screen for trying to access feedback from again

Fig.6.12 Trying to access the form again

79


80/85

Feedback System

Screen for Management login

Fig. 6.13 Management login

80


81/85

Feedback System

Screen For Selecting Branch For Reports

Fig.6.14 Selecting Branch

81


82/85

Feedback System

Screen For Viewing Reports

Fig.6.15 Reports

82


83/85

Feedback System

Screen For Viewing Reports

Fig.6.16 Reports

83


84/85

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


85/85

Feedback System

8.BIBLIOGRAPHY

8.1 Books Referred :

SNO Author Book Publisher VolNo. Year

1 Jim Keogh J2EE:The Complete

Reference

Tata

McGraw-

Hill

19th edition 2007

2 The unified

Modeling

language :

user guide

Grady booch -

James

Ivar Jacobson

Pearson

Education

2nd edition 2008

3 Software

Engineering

Roger.S.Pressman TMH ltd 6th edition 2006

4 Internet and

world wide

- web

Dietle and Nieto Pearson

education

2nd edition 2005

8.2 Web Sites Visited :

http://www.javaworld.com/javaworld/jw-04-2006/jw-0417-push.html

http://www.google.com

www wikipedia com
http://www.javaworld.com/javaworld/jw-04-2006/jw-0417-push.htmlhttp://www.google.com/http://www.wikipedia.com/http://www.javaworld.com/javaworld/jw-04-2006/jw-0417-push.htmlhttp://www.google.com/http://www.wikipedia.com/

Feedback Doc

Documents

Transcript of Feedback Doc