Mobile Based Student Feedback Analysis MN-B04

CHAPTER 1
INTRODUCTION

Dept of CSE VMTW

 Mobile Based Student Feedback Analysis MN-B04

1. INTRODUCTION

This Student Feedback System project is to develop a mobile-based application

which is very useful to maintain feedback reports by the administrator. Provides a student
to give feedback for the teaching of a lecturer in a mobile-based system online. Evaluates
the answer given by the students based on the feedback which will be given. Delivers
feedback via student lecture interface which acts as a service provider. .Provides individual
rating of the faculty in a particular semester which will help the management in making
salary appraisal decisions.

1.1 Purpose of the project:

Application for Android devices that has been designed and developed to aid
students in giving their feedback on their mobile or tablet devices. The application has been
created with the aim to allow students to access their feedback sheet on the go in a simple
and easy to use fashion with a number of features to enhance the user experience.

1.2 Scope of the project:

The main concept of mobile based student feedback system is developing the feedback
process with all the educational institutions. It is an economical & less time consuming
process.

1.3 Aim/Goal of the project:

The aim of the project is to create an Android mobile application for feedback system
that can be used by all students or clients for their respective courses. This application
fetches the details of the employee or faculties allotted the respective faculty and the
students enrolled in the courses from the server using the internet connection and stores it
in the information.
1.4 Feature of the project:

 Authorize students can access.

 Easy to give feedback on respective subject.
 Time to time re-arrangement can be done.
 Facility to view their feedback.

Dept of CSE VMTW

Mobile Based Student Feedback Analysis MN-B04

CHAPTER 2
LITERATURE SURVEY

Dept of CSE VMTW

Mobile Based Student Feedback Analysis MN-B04

[Link] SURVEY

First introduced in the United States in the mid-1920s to provide feedback to

academics on their teaching, student evaluation surveys are now routinely conducted in
universities in many parts of the world and their results are used for both formative, to guide
teaching practice, and summative, to inform management decision making, purposes
(Algozzine et al., 2004; Richardson, 2005).
After almost three decades of working in the field, Marsh (2007) identified five main
purposes of the surveys. They are to provide: diagnostic feedback for academics about the
effectiveness of their teaching; a measure of teaching effectiveness for decisions regarding
appointment and promotion; information for students to use in the selection of units of study
and teachers; a component for use in quality assurance processes; and data for use in
research. Overall, Marsh concluded that when appropriately designed and used, such
surveys are multidimensional; reliable and stable; relatively valid and unaffected by
variables that may be seen as sources of potential bias; and demonstrably useful in
improving teacher effectiveness.
Since the 1980s a large body of literature on student feedback surveys has developed from
the early work of Marsh (1982, 1987) and other veterans such as Abrami (1985) and
Feldman (1978). Their focus has been on the dimensionality, reliability, validity and
usefulness of student evaluation surveys, dimensions of teaching and learning and
identification of exemplary teachers and teaching. Periodically, these authors and their
colleagues have reviewed the literature to determine the state of research in the field.
In the most recent reviews, they raise a number of issues of concern (Abrami et al., 2007;
Marsh, 2007; Theall & Feldman, 2007). These include the changing nature of learning and
teaching and the relevance of the dimensions being measured; the use made of student
ratings for promotional and other summative purposes; and the imperative for universities
to respond to results by implementing programmes to improve teaching effectiveness.
Marsh bemoaned the paucity of theory-based studies in the field and the fact that after
decades of extensive research into the science, analysis, interpretation and uses of such
surveys, no general or unified theory of college teaching has emerged. All authors agree
that student surveys should be just one element of more comprehensive systems aimed at
fair and equitable evaluation and professional and academic development.

Dept of CSE VMTW

Mobile Based Student Feedback Analysis MN-B04

CHAPTER 3
SYSTEM ANALYSIS

Dept of CSE VMTW

 Mobile Based Student Feedback Analysis MN-B04

3. SYSTEM ANALYSIS

3.1 Existing system:

• The present Student Feedback Project has no application to provide communication
between the student and lecturer through the mobile.
• So far, this as only taken place in online websites but there is no application developed for
communication by giving apps predefined methods.

3.1.1 Diadvantages of Existing system:

1) Time consuming process.
2) Inconsistency in data entry.
3) Lack of security.
4) Data may be lost.

3.2 Proposed system:

• In this student feedback system project, we are proposing the new form of technology to
get communication between student and lecturer.
• With this, the student can successfully submit feedback on lecturer’s teaching in a very
efficient and convenient manner.
• By using this technology we can provide fast feedback about the college lecturers by the
students on time at anywhere from any place by just log in from their valid account.

3.2.1 Advantages of Proposed system:

o Authorize students can access

o Easy to give feedback on respective subject.
o Time to time re-arrangement can be done.
o Facility to view their feedback.

Dept of CSE VMTW

 Mobile Based Student Feedback Analysis MN-B04

3.3 System requirements:

We use Java, JSP and Servlets as Programming language for writing the code for the
project. HTML, CSS and JavaScript for creating the web pages MYSQL server is used for
creating the local and global database (server). ECLIPSE IDE for writing the programs.
Operating system will be Windows XP.

3.3.1 Software Requirements:

 Java (JDK 1.6)
 Android SDK
 Eclipse indigo IDE
 Operating System Windows XP and Above.

3.3.2 Hardware Requirements:

 System Pentium IV 2.4 GHz.
 Hard Disk : 40 GB.
 Floppy Drive : 1.44 Mb.
 Monitor : 15 VGA Colour.
 Mouse : Logitech.
 Ram : 512 Mb.

Dept of CSE VMTW

Mobile Based Student Feedback Analysis MN-B04

CHAPTER 4
IMPLEMENTATION

Dept of CSE VMTW

 Mobile Based Student Feedback Analysis MN-B04

4. IMPLEMENTATION

4.1 MODULES:
 Admin Module
 Login Module
 Faculty Module
 Student Module
 Feedback Module

4.2 MODULE DESCRIPTION:

4.2.1 Admin Module:

Admin will have the permission to see the overall statistics prepared by the system, using
the feedback forms submitted by the students.

4.2.2 Login Module:

This module allows the three type of users faculty, student and admin. Admin will give
login ID and password for faculty and the student.
All type users will register into the system, once.

4.2.3 Faculty Module:

This module will create the list of the students who opted the course.
At the end of each month/semester, faculty will give the permission to students who are
regular, to give the feedback for that course during that month /semester.

4.2.4 Student Module:

Using this module student can register to the system. At the end of every month/semester,
when the student login, they get to know the list of courses for which they can provide
feedback. They complete the feedback and submit.

4.2.5 Feedback Module:

Loading feedback form to the student who is regular or valid students.

Collecting the feedback form from the student and store it in the database.
Providing the feedback information to faculty, coordinator and admin whenever
requested.

Dept of CSE VMTW

 Mobile Based Student Feedback Analysis MN-B04

4.3 INPUT DESIGN:

Considering the requirements, procedures to collect the necessary input data in most
efficiently designed. The input design has been done keeping in view that, the interaction
of the user with the system being the most effective and simplified way.
Also the measures are taken for the following
 Controlling the amount of input
 Avoid unauthorized access to the classroom.
 Eliminating extra steps
 Keeping the process simple
 At this stage the input forms and screens are designed.

4.4 OUTPUT DESIGN:

All the screens of the system are designed with a view to provide the user with easy
operations in simpler and efficient way, minimum key strokes possible. Instructions and
important information is emphasized on the screen. Almost every screen is provided with
no error and important messages and option selection facilitates. Emphasis is given for
speedy processing and speedy transaction between the screens. Each screen assigned to
make it as much user friendly as possible by using interactive procedures. So to say user
can operate the system without much help from the operating manual.

Dept of CSE VMTW

Mobile Based Student Feedback Analysis MN-B04

CHAPTER 5
SYSTEM ARCHITECTURE

Dept of CSE VMTW

Mobile Based Student Feedback Analysis MN-B04

CHAPTER 6
SYSTEM STUDY

Dept of CSE VMTW

 Mobile Based Student Feedback Analysis MN-B04

6. SYSTEM STUDY
The next step in analysis is to verify the feasibility of the proposed system. “All projects
are feasible given unlimited resources and infinite time“. But in reality both resources and
time are scarce. Project should confirm to time bounce and should be optimal in their
consumption of resources. This place a constant is approval of any project.
Feasibility they are 3 types:
 Technical feasibility
 Operational feasibility
 Economical feasibility

6.1 TECHNICAL FEASIBILITY:

To determine whether the proposed system is technically feasible, we should take into
consideration the technical issues involved behind the system. This Application uses the
web technologies, which is rampantly employed these days worldwide. The world without
the web is incomprehensible today. That goes to proposed system is technically feasible.
6.2 OPERATIONAL FEASIBILITY:
To determine the operational feasibility of the system we should take into consideration the
awareness level of the users. This system is operational feasible since the users are familiar
with the technologies and hence there is no need to gear up the personnel to use system.
Also the system is very friendly and to use.
6.3 ECONOMICAL FEASIBILITY:
To decide whether a project is economically feasible, we have to consider various factors
as:
 Cost benefit analysis
 Long-term returns
 Maintenance costs.
It requires average computing capabilities and access to internet, which are very basic
requirements and can be afforded by any organization hence it doesn’t incur additional
economic overheads, which renders the system economically feasible.

Dept of CSE VMTW

Mobile Based Student Feedback Analysis MN-B04

CHAPTER 7
SYSTEM DESIGN

Dept of CSE VMTW

 Mobile Based Student Feedback Analysis MN-B04

7. SYSTEM DESIGN
System design is transition from a user oriented document to programmers or data
base personnel. The design is a solution, how to approach to the creation of a new system.
This is composed of several steps. It provides the understanding and procedural details
necessary for implementing the system recommended in the feasibility study.
Designing goes through logical and physical stages of development, logical design
reviews the present physical system, prepare input and output specification, details of
implementation plan and prepare a logical design walkthrough.
The database tables are designed by analyzing functions involved in the system and
format of the fields is also designed. The fields in the database tables should define their
role in the system. The unnecessary fields should be avoided because it affects the storage
areas of the system. Then in the input and output screen design, the design should be made
user friendly. The menu should be precise and compact.
7.1 SOFTWARE DESIGN:
In designing the software following principles are followed:
 . Modularity and partitioning: software is designed such that, each system should consists
of hierarchy of modules and serve to partition into separate function.
 Coupling: modules should have little dependence on other modules of a system.
 Cohesion: modules should carry out in a single processing function.
 Shared use: avoid duplication by allowing a single module be called by other that need the
function it provides.
7.2 UML DIAGRAMS:
UML stands for Unified Modeling Language. UML is a standardized general-
purpose modeling language in the field of object-oriented software engineering. The
standard is managed, and was created by, the Object Management Group. The goal is for
UML to become a common language for creating models of object oriented computer
software. In its current form UML is comprised of two major components: a Meta-model
and a notation. In the future, some form of method or process may also be added to; or
associated with, UML.

Dept of CSE VMTW

Mobile Based Student Feedback Analysis MN-B04

The Unified Modeling Language is a standard language for specifying,

Visualization, Constructing and documenting the artifacts of software system, as well as for
business modeling and other non-software systems. The UML represents a collection of
best engineering practices that have proven successful in the modeling of large and complex
systems. The UML is a very important part of developing objects oriented software and the
software development process. The UML uses mostly graphical notations to express the
design of software projects. Goals: The Primary goals in the design of the UML are as
follows:
Provide users a ready-to-use, expressive visual modeling Language so that they can
develop and exchange meaningful models.
Provide extendibility and specialization mechanisms to extend the core concepts.
Be independent of particular programming languages and development process.
Provide a formal basis for understanding the modeling language.
Encourage the growth of OO tools market.
Support higher level development concepts such as collaborations, frameworks, patterns
and components.
Integrate best practices.
DEPOLYMENT DIAGRAM:

client data base

server

Dept of CSE VMTW

Mobile Based Student Feedback Analysis MN-B04

7.3 Use Case Diagram:

A use case diagram in the Unified Modeling Language (UML) is a type of behavioral
diagram defined by and created from a Use-case analysis. Its purpose is to present a
graphical overview of the functionality provided by a system in terms of actors, their goals
(represented as use cases), and any dependencies between those use cases. The main
purpose of a use case diagram is to show what system functions are performed for which
actor. Roles of the actors in the system can be depicted.

add professors

view time table

admin

view feedback

generate reports

registration

login
student

giving feedback

Fig 7.1 Use Case Diagram

Dept of CSE VMTW

Mobile Based Student Feedback Analysis MN-B04

7.4 CLASS DIAGRAM:

In software engineering, a class diagram in the Unified Modeling Language (UML)

is a type of static structure diagram that describes the structure of a system by showing the
system's classes, their attributes, operations (or methods), and the relationships among the
classes. It explains which class contains information.

Fig 7.2 Class Diagram

Dept of CSE VMTW

Mobile Based Student Feedback Analysis MN-B04

7.5 SEQUENCE DIAGRAM:

A sequence diagram in Unified Modeling Language (UML) is a kind of interaction diagram
that shows how processes operate with one another and in what order. It is a construct of a
Message Sequence Chart. Sequence diagrams are sometimes called event diagrams, event
scenarios, and timing diagrams.

STUDENT:

student login giving feedback database

go to login page
req sent

verify
success

giving feedback to facutly

storing details
verify

success

Fig 7.3 Student Sequence diagram

Dept of CSE VMTW

Mobile Based Student Feedback Analysis MN-B04

7.6 COLLABORATION DIAGRAM:

1: go to login page
login

student

4: success

5: giving feedback to facutly 2: req sent

3: verify
8: success 7: verify

6: storing details

giving databas
feedback e

Dept of CSE VMTW

Mobile Based Student Feedback Analysis MN-B04

7.7 ACTIVITY DIAGRAM:

STUDENT:

registration

fail

login

success

view timetable giving feedback

Dept of CSE VMTW

Mobile Based Student Feedback Analysis MN-B04

CHAPTER 8
SAMPLE CODE

Dept of CSE VMTW

Mobile Based Student Feedback Analysis MN-B04

8. SAMPLE CODE
8.1 Faculty list java.
package [Link];

import [Link];

import [Link];
import [Link];

import [Link];
import [Link];
import [Link];
import [Link];
import [Link];
import [Link];
import [Link];
import [Link];
import [Link];
import [Link];

public class FacultylistActivity extends Activity {

String ClassName, Day,Year,Sem,getsub;
String res = "";
String ss[];
int status;
ListView list;
ArrayList<String> array;
ArrayAdapter<String> adapter;

@SuppressLint("NewApi")
@Override

Dept of CSE VMTW

Mobile Based Student Feedback Analysis MN-B04

protected void onCreate(Bundle savedInstanceState) {

[Link](savedInstanceState);
setContentView([Link].activity_facultylist);
if ([Link].SDK_INT > 9) {
[Link] policy = new
[Link]()
.permitAll().build();
[Link](policy);
}
Bundle b = getIntent().getExtras();
ClassName = [Link]("sendBranch");
Year = [Link]("sendyear");
Sem = [Link]("sendsam");
array=new ArrayList<String>();
list=(ListView)findViewById([Link].Faculty_list);
try {
HttpClient client = new HttpClient();
GetMethod get = new
GetMethod("[Link]
Year="+Year+"&Sem="+Sem+"");
status = [Link](get);
if (status != 404) {
res = [Link]();
} else {
res = "ws_not_found";
}
ss = [Link]().split("<br>");
int i;
for(i=0; i<[Link];i++){
if(ss[i]!=null){
[Link](ss[i].trim());
adapter=new
ArrayAdapter<String>([Link], [Link].simple_list_item_1,
array);

Dept of CSE VMTW

Mobile Based Student Feedback Analysis MN-B04

}
}

} catch (Exception e) {
// TODO: handle exception
[Link]();
}
[Link](adapter);
[Link](new OnItemClickListener() {

@Override
public void onItemClick(AdapterView<?> arg0, View arg1, int
arg2,
long arg3) {
// TODO Auto-generated method stub
getsub=[Link](arg2).toString();
Intent in=new Intent([Link],
[Link]);
[Link]("sendBranch", ClassName);
[Link]("sendyear", Year);
[Link]("sendsam", Sem);
[Link]("ss", getsub);
startActivity(in);

});
}

Dept of CSE VMTW

Mobile Based Student Feedback Analysis MN-B04

8.2 Get Teacher Activity:

package [Link];

import [Link];

import [Link];
import [Link];

import [Link];
import [Link];
import [Link];
import [Link];
import [Link];
import [Link];

import [Link];
import [Link];

public class GetTeacherActivity extends Activity {

int status;
String res = "",getteacher,getday;
ListView list;
TeacherAdapter adapter;
String exe;
String[] exe1;
public GetTeacherActivity CustomListView = null;
public ArrayList<ListModelTeacher> CustomListViewValuesArr = new
ArrayList<ListModelTeacher>();

@SuppressLint("NewApi")
@Override
protected void onCreate(Bundle savedInstanceState) {

Dept of CSE VMTW

Mobile Based Student Feedback Analysis MN-B04

[Link](savedInstanceState);
setContentView([Link].activity_get_teacher);
if ([Link].SDK_INT > 9) {
[Link] policy = new
[Link]()
.permitAll().build();
[Link](policy);
}
CustomListView = this;
Resources res =getResources();
list=(ListView)findViewById([Link]);
Bundle b = getIntent().getExtras();
getteacher = [Link]("senttechar");
getday=[Link]("sentday");
try {
HttpClient client = new HttpClient();
GetMethod get = new
GetMethod("[Link]
Name="+getteacher+"");
status = [Link](get);
if (status != 404) {
exe = [Link]();
exe1=[Link]().split("<br>");
for(int i=0;i<[Link];i++){
if(exe1[i]!=" ")
{
setListData(exe1[i].split(","));

adapter=new TeacherAdapter(CustomListView,
CustomListViewValuesArr,res);
[Link](adapter);
}
}
} else {

Dept of CSE VMTW

Mobile Based Student Feedback Analysis MN-B04

exe = "ws_not_found";
}
}catch(Exception e){
[Link]();
}
}
public void setListData(String[] ss)
{
final ListModelTeacher sched = new ListModelTeacher();
[Link](ss[0].trim());
[Link](ss[1].trim());
[Link](ss[2].trim());
[Link](ss[3].trim());
[Link](ss[4].trim());
[Link](ss[5].trim());
[Link](sched);

}
}
8.3 Send Feedback Activity:
package [Link];

import [Link];

import [Link];
import [Link];
import [Link];

import [Link];
import [Link];
import [Link];
import [Link];
import [Link];

Dept of CSE VMTW

Mobile Based Student Feedback Analysis MN-B04

import [Link];
import [Link];
import [Link];

public class SendfeedbackActivity extends Activity {

RatingBar ratingBar;
String rate, getqury,
st,check_1,check_2,check_3,ClassName,Year,Sem,TeacherName;
EditText givequry;
CheckBox checkBox1, checkBox2, checkBox3;

@Override
protected void onCreate(Bundle savedInstanceState) {
[Link](savedInstanceState);
setContentView([Link].activity_sendfeedback);
Bundle b = getIntent().getExtras();
ClassName = [Link]("sendBranch");
Year = [Link]("sendyear");
Sem = [Link]("sendsam");
TeacherName = [Link]("ss");
givequry = (EditText) findViewById([Link]);
ratingBar = (RatingBar) findViewById([Link].ratingBar1);
rate = [Link]([Link]()).toString();
checkBox1 = (CheckBox) findViewById([Link].checkBox1);
checkBox2 = (CheckBox) findViewById([Link].checkBox2);
checkBox3 = (CheckBox) findViewById([Link].checkBox3);
[Link](new OnClickListener() {

@Override
public void onClick(View v) {
// TODO Auto-generated method stub
if (((CheckBox) v).isChecked()) {
check_3=[Link]().toString();
}else {

Dept of CSE VMTW

Mobile Based Student Feedback Analysis MN-B04

check_3="";
}
}
});
}

public void sendfeed(View v) {

getqury = [Link]().toString();
rate = [Link]([Link]()).toString();
if([Link]("")){
[Link]([Link],"NO",
Toast.LENGTH_LONG).show();
}else{
HttpClient client = new HttpClient();
GetMethod get = new
GetMethod("[Link]
ear="+Year+"&Sem="+Sem+"&TeacherName="+TeacherName+"&query1="+getqury+"
&query2="+rate+"&query3="+check_3+"");
int status = 0;
try {
status = [Link](get);
} catch (HttpException e) {
// TODO Auto-generated catch block
[Link]();
} catch (IOException e) {
// TODO Auto-generated catch block
[Link]();
}
[Link](get);
String output="";
String res="";

if(status!=404){
try {

Dept of CSE VMTW

Mobile Based Student Feedback Analysis MN-B04

res=[Link]();
} catch (IOException e) {
// TODO Auto-generated catch block
[Link]();
}
}else {
res="SORRY";
}

if([Link]("sucessfully inserted"))
{

[Link](getApplicationContext(), "succesfully submited

feedback",9000).show();
}
}
}
}
8.4 View Feedback Activity:
package [Link];

import [Link];

import [Link];
import [Link];

import [Link];
import [Link];
import [Link];
import [Link];
import [Link];
import [Link];

Dept of CSE VMTW

Mobile Based Student Feedback Analysis MN-B04

import [Link];
import [Link];
import [Link];
import [Link];

public class ViewTimeTableActivity extends Activity {

String ClassName, Day,Year,Sem,getsub;
String res = "";
String ss[];
int status;
ListView list;
ArrayList<String> array;
ArrayAdapter<String> adapter;

@SuppressLint("NewApi")
@Override
protected void onCreate(Bundle savedInstanceState) {
[Link](savedInstanceState);
setContentView([Link].activity_view_time_table);
if ([Link].SDK_INT > 9) {
[Link] policy = new
[Link]()
.permitAll().build();
[Link](policy);
}
Bundle b = getIntent().getExtras();
ClassName = [Link]("branch");
Day = [Link]("day");
Year = [Link]("year");
Sem = [Link]("sem");
array=new ArrayList<String>();
list=(ListView)findViewById([Link].listView1);
try {
HttpClient client = new HttpClient();

Dept of CSE VMTW

Mobile Based Student Feedback Analysis MN-B04

GetMethod get = new GetMethod(

"[Link]
+Day+"&Year="+Year+"&Sem="+Sem+"");
status = [Link](get);
if (status != 404) {
res = [Link]();
} else {
res = "ws_not_found";
}
ss = [Link]().split("<br>");
int i;
for(i=0; i<[Link];i++){
if(ss[i]!=null){
[Link](ss[i].trim());
}
}

} catch (Exception e) {
// TODO: handle exception
[Link]();
}
adapter=new ArrayAdapter<String>([Link],
[Link].simple_list_item_1, array);
[Link](adapter);
[Link](new OnItemClickListener() {

@Override
public void onItemClick(AdapterView<?> arg0, View arg1, int
arg2,
long arg3) {
// TODO Auto-generated method stub
getsub=[Link](arg2).toString();

Dept of CSE VMTW

Mobile Based Student Feedback Analysis MN-B04

Intent in=new Intent([Link],

[Link]);
[Link]("ss", getsub);
startActivity(in);

});
}

8.5 Read java code:

package [Link];
import [Link];
import [Link];
import [Link];
import [Link];
import [Link];
import [Link];
import [Link];
import [Link];
import [Link];

import [Link];
import [Link];
import [Link];
import [Link];

import [Link];
import [Link];
import [Link];
import [Link];

Dept of CSE VMTW

Mobile Based Student Feedback Analysis MN-B04

import [Link];
import [Link];
import [Link];

public class ReedXlV extends HttpServlet {

private static final long serialVersionUID = 1L;
private int maxFileSize = 5000 * 1024;
private int maxMemSize = 400 * 1024;
private File file;
public void doPost(HttpServletRequest request, HttpServletResponse response)
throws ServletException, [Link] {
[Link](request);
@SuppressWarnings("deprecation")
String filepath1 = [Link](getServletName());
Path path = [Link](filepath1);
Path respath = [Link]();
//[Link](respath + "222222222222222222");
String finalpath = respath + "SHEETS";
//[Link](finalpath + "333333333333333");
File f = new File(finalpath);
String zz = [Link]();
[Link]();
[Link]("text/html");
[Link] out = [Link]();
DiskFileItemFactory factory = new DiskFileItemFactory();
// maximum size that will be stored in memory
[Link](maxMemSize);
// Location to save data that is larger than maxMemSize.
[Link](new File("c:\\temp"));
// Create a new file upload handler
ServletFileUpload upload = new ServletFileUpload(factory);
// maximum file size to be uploaded.
[Link](maxFileSize);
try {

Dept of CSE VMTW

Mobile Based Student Feedback Analysis MN-B04

// Parse the request to get file items.

List<?> fileItems = [Link](request);
Iterator<?> i = [Link]();
while ([Link]()) {
FileItem fi = (FileItem) [Link]();
if (![Link]()) {
String fileName = [Link]();
// Write the file
file = new File(finalpath + '\\' +fileName);
String fpath=[Link]();
String zzz = [Link]('\\','/');
[Link](file);
[Link]("[Link]");
Connection con
=[Link]("jdbc:mysql://localhost/timetabledatabase","root","");
Con .setAutoCommit(false);
PreparedStatement ps = null ;
FileInputStream input = new FileInputStream(zzz);
POIFSFileSystem fs = new POIFSFileSystem( input );
HSSFWorkbook wb = new HSSFWorkbook(fs);
HSSFSheet sheet = [Link](0);
HSSFRow row;
for(int i1=1; i1<=[Link](); i1++){
row = [Link](i1);
String Classname=[Link](0).getStringCellValue();
String day=[Link](1).getStringCellValue();
String year=[Link](2).getStringCellValue();
String sem=[Link](3).getStringCellValue();
String stime=[Link](4).getStringCellValue();
String etime=[Link](5).getStringCellValue();
String Subject=[Link](6).getStringCellValue();
String teacher=[Link](7).getStringCellValue();
ps=[Link]("insert into timetable
values(?,?,?,?,?,?,?,?)");

Dept of CSE VMTW

Mobile Based Student Feedback Analysis MN-B04

[Link]("2");
[Link](1, Classname);
[Link](2, day);
[Link](3, year);
[Link](4, sem);
[Link](5, stime);
[Link](6, etime);
[Link](7, Subject);
[Link](8, teacher);
[Link]();
[Link]("Values are inserted into tabel");
}
}
[Link]("Success import excel to mysql table");
}
}
catch (Exception ex) {
[Link](ex);
[Link]();
}
}
}

Dept of CSE VMTW

Mobile Based Student Feedback Analysis MN-B04

CHAPTER 9
SYSTEM TESTING

Dept of CSE VMTW

 Mobile Based Student Feedback Analysis MN-B04

9. SYSTEM TESTING
9.1 SOFTWARE TESTING:
Software testing is a critical element of software quality assurance and represents the
ultimate review of specification, design and code generation.
9.1.1 TESTING OBJECTIVES:

 To ensure that during operation the system will perform as per specification.
 TO make sure that system meets the user requirements during operation
 To make sure that during the operation, incorrect input, processing and output will be
detected
 To see that when correct inputs are fed to the system the outputs are correct
 To verify that the controls incorporated in the same system as intended
 Testing is a process of executing a program with the intent of finding an error
 A good test case is one that has a high probability of finding an as yet undiscovered error.
The software developed has been tested successfully using the following testing
strategies and any errors that are encountered are corrected and again the part of the program
or the procedure or function is put to testing until all the errors are removed. A successful
test is one that uncovers an as yet undiscovered error.
Note that the result of the system testing will prove that the system is working
correctly. It will give confidence to system designer, users of the system, prevent frustration
during implementation process etc.

9.2 TEST CASE DESIGN:

9.2.1 White box testing:
White box testing is a testing case design method that uses the control structure of the
procedure design to derive test cases. All independents path in a module are exercised at
least once, all logical decisions are exercised at once, execute all loops at boundaries and
within their operational bounds exercise internal data structure to ensure their validity. Here
the customer is given three chances to enter a valid choice out of the given menu. After
which the control exits the current menu.

Dept of CSE VMTW

 Mobile Based Student Feedback Analysis MN-B04

9.2.2 Black Box Testing:

Black Box Testing attempts to find errors in following areas or categories, incorrect
or missing functions, interface error, errors in data structures, performance error and
initialization and termination error. Here all the input data must match the data type to
become a valid entry.
The following are the different tests at various levels:
9.2.3 Unit Testing:
Unit testing is essentially for the verification of the code produced during the coding
phase and the goal is test the internal logic of the module/program. In the Generic code
project, the unit testing is done during coding phase of data entry forms whether the
functions are working properly or not. In this phase all the drivers are tested they are rightly
connected or not.
9.2.4 Integration Testing:
All the tested modules are combined into sub systems, which are then tested. The
goal is to see if the modules are properly integrated, and the emphasis being on the testing
interfaces between the modules. In the generic code integration testing is done mainly on
table creation module and insertion module.
9.2.5 Validation Testing:
This testing concentrates on confirming that the software is error-free in all respects.
All the specified validations are verified and the software is subjected to hard-core testing.
It also aims at determining the degree of deviation that exists in the software designed from
the specification; they are listed out and are corrected.
9.2.6 System Testing:
This testing is a series of different tests whose primary is to fully exercise the
computer-based system. This involves:
 Implementing the system in a simulated production environment and testing it.
 Introducing errors and testing for error handling.

Dept of CSE VMTW

Mobile Based Student Feedback Analysis MN-B04

CHAPTER 10
RESULT SCREENSHOTS

Dept of CSE VMTW

Mobile Based Student Feedback Analysis MN-B04

10. RESULT SCREENSHOTS

10.1 LOGIN PAGE:

Fig 10.1 Admin Login Page

10.2 WELCOME TO ADMINISTRATOR:

Fig 10.2 Welcome to Administrator

Dept of CSE VMTW

Mobile Based Student Feedback Analysis MN-B04

10.3 STUDENT REGISTRATION:

Fig 10.3 Student Registration Page

Dept of CSE VMTW

Mobile Based Student Feedback Analysis MN-B04

10.4 STUDENT FEEDBACK:

Fig 10.4 Student feedback

10.5 FORGET PASSWORD

Fig 10.5 Forget password

Dept of CSE VMTW

Mobile Based Student Feedback Analysis MN-B04

10.6 TABLE DESIGN AND STRCTURE:

Dept of CSE VMTW

Mobile Based Student Feedback Analysis MN-B04

Dept of CSE VMTW

Mobile Based Student Feedback Analysis MN-B04

11. CONCLUSION
The Project “Student Feedback System” is designed in order to reduce the
burden of maintaining bulk of records of all students feedback details of who study in an
educational institutions. Inserting, retrieving and updating the feedback details of a student
are easy when it is compared to the manual feedback and storing. Maintaining the project
is also easy which can is easily understandable maintaining the details in the database is
manageable. At the time of feedback generation it apply formulae for generate a feedback
of particular subject. After that it will displayed the whole record sheet to the staff, when
the staff will login in the system. As the comparison with manual feedback or existing
feedback system the new system is easier way to manage whole things in a particular
manner. As per the existing system it is very easy process to save each and every record of
individual student by the use of database.

Dept of CSE VMTW

Mobile Based Student Feedback Analysis MN-B04

12. FUTURE ENHANCEMENTS

Due to the lack of time, the design part is not done so attractive Further enhancements can
be made in designing the screens. Some more forms can also be added so as better retrieve
the feedback details. Various other options can also be added for the better usability of
project.

Dept of CSE VMTW

Mobile Based Student Feedback Analysis MN-B04

BIBLIOGRAPHY

[1] Jayakumar, N., Singh, S., Patil, S.H. and Joshi, S.D., 2015. Evaluation Parameters of
Infrastructure Resources Required for Integrating Parallel Computing Algorithm and
Distributed File System. IJSTE-Int. J. Sci. Technol. Eng, 1(12), pp.251-254.
[2] Salunkhe, R., Kadam, A.D., Jayakumar, N. and Thakore, D., 2016, March. In search
of a scalable file system state-of-the-art file systems review and map view of new
Scalable File system. In Electrical, Electronics, and Optimization Techniques (ICEEOT),
International Conference on (pp. 364-371). IEEE.
[3] Naveenkumar, J., Makwana, R., Joshi, S.D. and Thakore, D.M., 2015. Offloading
Compression and Decompression Logic Closer to Video Files Using Remote Procedure
Call. Journal Impact Factor, 6(3), pp.37-45
[4] Jayakumar, N., 2014. Reducts and Discretization Concepts, tools for Predicting
Student’s Performance. Int. J. Eng. Sci. Innov. Technol, 3(2), pp.7-15.

Dept of CSE VMTW