Shree Ambabai Talim Sanstha's

SANJAY BHOKARE GROUP OF INSTITUTES, MIRAJ

FACULTY OF POLYTECHNIC
Institute Code: 1552

Department Of Computer Engineering

Micro Project Report
On

ONLINE FEEDBACK SYSTEM

Prepared By

Roll no. Enrolment No. Name

3318 2215520030 Faika Farukh Shaikh
3305 2215520013 Sakshi Sunil Kamble
Komal Bhauso Gadade

Under the Guidance of

Mr. S .M .Patil
Submitted To

Maharashtra State Board of Technical Education, Mumbai

(Autonomous) (ISO-9001-2008) (ISO/IEC 27001:2013)
Academic Year 2020-2021

1
This is to certify that Mr. / Ms. ………………………………………………………
Roll No.….…., of ………... Semester of Diploma in………………….. Engineering ,
of Institute
(Code: ) has completed the Micro-Project work satisfactorily in course
Software Testing 22518 for the academic year 2024 to 2025 as prescribed in the
curriculum.

Place: Miraj Enrollment No:.……………

Date: …………… Exam. Seat No: ……………

2
 This is to certify that following students,

3318 2215520030 Faika Farukh Shaikh

3305 2215520013 Sakshi Sunil Kamble
Komal Bhauso Gadade

of 5Th Semester of Diploma in Computer Engineering , of Institute

(Code: ) are completed the Micro Project work satisfactorily in course

Software Testing 22518 for the academic year 2024 to 2025 as prescribed in the
curriculum.

Place: Miraj

Date:…………

3
First and the foremost I,
express my deep sense of
gratitude, sincere thanks
and deep
sense of application to
Project Guide Mr. K. P.
Jadhav, Department of
Computer Technology,
Sanjivani K.B.P.
Polytechnic, Kopargaon.
Your availability at any
time throughout the year,
valuable guidance, opinion,
view, comment, critics,
4
encouragement, and
support tremendously
boosted this project work.
Lots of thanks to Head of
Computer Technology
Department, Mr. G. N.
Jorvekar for
providing me the best
support I ever had. I like to
express my sincere
gratitude to Mr. A.R.
Mirikar, Principal,
Sanjivani K.B.P.
Polytechnic, Kopargaon
for providing great
platform to
5
complete the project within
the scheduled time. I am
also Thankful to all the
faculty members,
Computer Technology
Department, Sanjivani
K.B.P. Polytechnic,
Kopargaon for giving
comments for
improvement of work,
encouragement and help
during completion of the
project.
Last but not the least; We
should say thanks from our

6
bottom of heart to our
family and
friends for their never
ending love, help, and
support in so many ways
through all this time.
Thank you so much.
In today's software environment writing bug-free code is a challenging task, which makes
software testing an important tool to get quality software. Testing techniques include the process of
executing a program or application with the intent of finding software bugs and verifying that the
software product is fit for use. Students will learn the way to find bugs by applying types, levels, and
methods of software testing on applications with an effective test planning approach. It also covers
manual testing.

a) Apply various software testing methods.

b) Prepare test cases for different types and levels of testing.
c) Prepare test plans and defect bug reports.
d) Discipline knowledge: Apply computer engineering knowledge to solve broad-based
computer engineering-related problems.
e) Engineering tools: Apply appropriate computer engineering-related techniques/tools with
an understanding of the limitations.
f) Communication: Proper communication takes place between students and faculty.

a) Apply different software testing methods.

b) Prepare test cases for different types and levels of testing.

c) Prepare test plans and defect bug reports.

d) Discipline knowledge: Use computer engineering knowledge to solve broad-based computer

engineering-related problems.
7
e) Engineering tools: Apply appropriate computer engineering-related techniques/tools with an
understanding of the limitations.

f) Communication: Proper communication takes place between students and faculty.

g) Debugging and Optimization Abilities: Effectively identify and resolve issues in Java programs and
optimize code for better performance.

h) Hands-on Application: Gain practical experience by applying theoretical concepts to real-world Java
development tasks, preparing students for professional roles.

i) Software Development Lifecycle Understanding: Understand the development, testing, and

deployment processes in Java application development.

The main goal of Security Testing is to identify the threats in the system and measure its potential
vulnerabilities, so the threats can be encountered and the system does not stop functioning or can not be
exploited. It also helps in detecting all possible security risks in the system and helps developers to fix
the problems through coding.

a) Apply different software testing methods.

b) Prepare test cases for different types and levels of testing.
c) Prepare test plans and defect bug reports.
d) Discipline knowledge: Use computer engineering knowledge to solve broad-based computer
engineering-related problems.
e) Engineering tools: Apply appropriate computer engineering-related techniques/tools with an
understanding of the limitations.
f) Communication: Proper communication takes place between students and faculty.

(major resources like raw material, tools, software etc.)

1 Laptop/Computer 1
2 Internet

(Sequence and time required for major activities for 8 Weeks)

1 Searching the topic for micro-

project
2 collect information from the
internet and textbook
3 collect information from the
8
 STE Software testing 22518
reference book
4 Prepare a report on it using
MS word

9
In this project, we are going to test an Online Feedback System using Software Testing. The online
feedback system is a web-based system that provides a way for colleges to allow students to give
feedback to staff online to improve their teaching. Students are required to give feedback using one
standard feedback form. In our project, the security is also maintained by the result of feedback being
only visible to the authentic users. This project also includes a time portal. This system helps teachers
to improve their performance by analyzing the feedback given by students. The above features will
be tested using Software testing different techniques in this project. This system is not time-bound
due to which students will give monthly feedback.

In this project, the Online Feedback System will be tested by employing different parameters. Firstly
SRS( Software Requirement Specification) will be made i.e. it includes all the functional and non-
functional needs. It will be more effortless to use SRS to test the application and find bugs. A Test
Plan with a standard format will be created for this application. Test Cases will be designed to test the
functionality of the software. And at last the Summary Report with a conclusion.

10
There are mainly three modules in this application. The modules of this app are as follows:
• Faculty Module
• Student Module
• Admin Module

 Faculty Module: It contains users likes primary faculty, HOD’s. The primary users of the
Student Feedback System are members of faculty. When a faculty enters the faculty id and
password the database checks whether the faculty id and password are valid. If valid their
account will be opened and it contains the feedback report. The HOD users of the Student
Feedback System are members of faculty. When a HOD enters the HOD id and password the
database checks whether the HOD id and password are valid. If valid their account will be
opened and it contains modules like Add faculty, view faculty and view class. One HOD
cannot view the results of other Department faculty and cannot view the other department
classes. The super users of the Student Feedback System are members of faculty. When a super
user enters the super user id and password the database checks whether the super user id and
password are valid. If valid their account will be opened and it contains the modules like view
faculty and view class, LOGS. By using logs module he can view the operations performed by
the HOD’s and faculty.

 Student Module: Students will enter their roll number and section details. On the basis of
section, it will display the corresponding faculty name and faculty id. By clicking on the
faculty id we will get feedback form, it contains around 15 Questions, students will select the
corresponding answers in their point of view and data is stored in the server.

 Admin Module: The admin module will handle all the activities perform by the student and the
faculty. Admin can add or remove to the student or to the faculty.

11
 Applicable
Module Name Description
Roles

Students: A student can register into the college feedback system by

Students,
entering his Name, then Password again confirm password field, as well as
Registration Faculty, HOD,
Email ID and Mobile No. will be required here. Either he/she can register
Principal
or login if he/she has an account already over the system

Students: Only the students who are admitted in that college will be
provided with a specific username and password. he/she can login the
college online feedback system by entering correct username and password
Students, allocated to them. If he/she don‟t have account he/she can register using
Login
Admin registration process available in that feedback system and then login to the
system. Admin: Admin can login in the Feedback system to see whether
how many students have given their feedback and prepare a note on their
feedbacks.

Student: Here in this Feedback module there are number of Feedback

partitions. Such as :- 1. Course Feedback, here a student can give a
feedback for each subject. 2. Staff feedback, here a student can give
feedback on staff. 3. Event Feedback, here a student can give feedback
related to all events which are being carried out in the college. [Link]
Feedback Student
Feedback, here a student can give feedback related to college buildings,
water purifiers, washrooms, Office, etc.5. Transport Feedback, here a
student can give feedback related to transport system of students such as
Bus transport, etc. 6. Canteen Feedback, here a student can give feedback
related to canteen, items sold in canteen, their costing more or less, etc.

Students: Students can logout after giving his feedback on the college
Students,
Logout online feedback system using Logout option available there. Admin: Admin
Admin
can logout after he has collected feedback of students.

The Test Plan is prepared to define the scope, approach, resources, and schedule of all testing activities
of the project Online Feedback System. The plan identified the items to be tested, the features to be
tested, the kinds of testing to be performed, the personnel responsible for testing, the resources and
schedule needed to complete testing, and the risks associated with the plan.

1. [Link]
2. [Link]
3. MySQL Cook Book, Paul PHP and MySQL
4. development by Luke Welling.
5. PHP Reference: Beginner to Intermediate
6. PHP5 by Mario Lurig.

12
 Code/Program
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="viewport"
content="width=device-width,
initial-
scale=1.0">
<meta http-equiv="X-UA-
Compatible"
content="ie=edge">
<link rel="stylesheet"
href="[Link]">

13
<title>Word Length
Calcuator</title>
</head>
<body>
<h1>Type a word in the
box</h1>
<input type="text" id="str">
<div id="output"></div>
<button id="btn"><h2>Click to
calculate word
length</h2></button>
<script src="[Link]"></script>
</body>
</html>
body{
background-color:#f7240c;
14
text-align: center;
}
input{
margin: 100px auto 100px;
/* margin-left: 220px; */
width: 350px;
height: 40px;
display: block;
text-align: center;
}
#output{
TEST CASES

• Software testing is a critical element of software quality assurance and represents the ultimate reuse of
specification. Design and code testing represents interesting anomaly for the software during earlier
definition and development phase, it was attempted to build software from an abstract concept to
tangible implementation.

• The testing phase involves, testing of the development of the system using various techniques such as
White Box Testing, Control Structure Testing.

• A strategy for software testing must accommodate low level tests that are necessary to verify that a
small source code segment has been correctly implemented as well as high level against customer
requirements.

STRUCTURE OF PROJECT System Actors(Users)

15
• Admin
• Faculty
• Student

 Admin Features
1. Admin Login
2. Admin can add new faculty
3. Admin can View faculty list
4. Admin can Update faculty data
5. Admin can Delete faculty
6. Admin can Manage Student
7. Admin can Check feedback given by student
8. Admin can check average feedback for faculty
9. Admin can update the contact details dynamically
10. Admin can update password

 Faculty Features
1. Faculty can login
2. Faculty can update their profile
3. Faculty can update Password
4. Faculty can Check feedback given by students
5. Faculty can check average feedback given by students •
6. Logout

 Student Features
1. Student can Register
2. Student can Login
3. Student can view profile
4. Student can update profile
5. Student can update Password
6. Student can choose faculty and give feedback for every Questions

SECURITY TESTING OF THE PROJECT

The main goal of Security Testing is to identify the threats in the system and measure its potential
vulnerabilities, so the threats can be encountered and the system does not stop functioning or can not be
exploited. It also helps in detecting all possible security risks in the system and helps developers to fix
the problems through coding.
Black Box Testing
Black Box Testing is a software testing method in which the functionalities of software applications are
tested without having knowledge of internal code structure, implementation details and internal paths.
Black Box Testing mainly focuses on input and output of software applications and it is entirely based
on software requirements and specifications. It is also known as Behavioral Testing.
White Box Testing
White Box Testing is software testing technique in which internal structure, design and coding of
software are tested to verify flow of input-output and to improve design, usability and security. In white
box testing, code is visible to testers so it is also called Clear box testing, Open box testing, Transparent
box testing, Code-based testing and Glass box testing.

TEST CASE DESIGN

A test case is a specification of the inputs, execution conditions, testing procedure, and expected results
that define a single test to be executed to achieve a particular software testing objective, such as to
exercise a particular program path or to verify compliance with a specific requirement. Test cases
underlie testing that is methodical rather than haphazard. A battery of test cases can be built to produce
16
the desired coverage of the software being tested. Formally defined test cases allow the same tests to be
run repeatedly against successive versions of the software, allowing for effective and consistent
regression testing.

Typical Written Test Case Format:-

A test case is usually a single step, or occasionally a sequence of steps, to test the correct
behaviour/functionality, and features of an application. An expected result or expected outcome is
usually given.

Additional information that may be included:

 Test Scenario ID
 Test Scenario
 Test Case ID
 Test Case Description
 Test Steps
 Pre-Conditions
 Test Data
 Post Conditions
 Expected Result
 Actual Result
 Status
 Executed By
 Comments if Any

Larger test cases may also contain prerequisite states or steps, and descriptions. A written test case
should also contain a place for the actual result. These steps can be stored in a word processor
document, spreadsheet, database, or another common repository.
In a database system, you may also be able to see past test results and who generated the results, and the
system configuration used to generate those results. These past results would usually be stored in a
separate table.

Before testing phase

 Test plans document.
 Test cases documents
 Test Design specifications.

Terms/Acronyms
 Make a mention of any terms or acronyms used in the project

TERM/ACRONYM DEFINITION

API Application Program Interface

AUT Application Under Test

DEFECT REPORT

Application Test Scenario

In our Online Feedback System there is a “Transport Feedback Issue” Module. In that module, the user
enters all details in that form that are required. When a user clicks on submit button it displays a
message that the “Form should be filled completely”, even if the form is filled correctly. Now, we
17
should report this bug. Now here is how a bug is reported on the basis of the above scenario:

Mention the actual resources used)

1 Laptop/Computer 1
2 Internet

Test suites often also contain

 Test summary
 Configuration.

DEFECT REPORT
Application Test Scenario
In our Online Feedback System there is a “Transport Feedback Issue” Module. In that module,
the user enters all details in that form that are required. When a user clicks on submit button it
displays a message that the “Form should be filled completely”, even if the form is filled
correctly. Now, we should report this bug. Now here is how a bug is reported on the basis of the
above scenario:

Bug Name: The application crash on clicking the Submit button after filling the Transport
Feedback form.
Bug ID:BG_LMS_001
Area Path: Feedback Module.
Build Number: Version Number [Link].2
Severity: HIGH
Priority: HIGH (High/Medium/Low)
Assigned to: Kamble Sakshi Sunil
Created By: Gadade Komal Bhauso
Created On: 12th September 2024.
Reason: Defect
Status: Active
Environment: Windows 2003/SQL Server 2005.

18
 Application crash on clicking the Submit button after filling Transport Feedback form.
Steps to reproduce:
1. log in to the application.
2. Click on the Feedback Option.
3. Enter the Transport Feedback option.
4. Fill in the details correctly and click on Submit button.
5. Seen an error message.
6. See the attached logs for more information.
7. See the attached screenshots of error the error message for reference. Expected: On clicking
the “Submit” button user should be able to view the message “Transport Feedback Form
Registered Successfully.”

Excel export has not been developed for student.

 Faculty can see feedback.
 Faculty can not register themselves for login.

Further enhancements can be made in designing the screens. Some more forms can also be added so as
to better retrieve the feedback details. Various other options can also be added for the better usability of
project

19
 …………………………………………………………
……………………………………

……………………………………………………………
…

…………………………………………………………………………………………………….

……………………………………………………………………………………………………………………………………
…………..
……………………………………………………………………………………………………………………………………
……………
……………………………………………………………………………………………………………………………………
…………….

 (Please tick in appropriate cell for each characteristic)

Relate to very Related to Take care of Take care of

few LOs some Los at- least one more than
CO one
 ..
Not more At-least 5 At –least 7 About 10
than two relevant relevant relevant
sources sources, at sources, most sources, most
(primary least 2 latest latest latest
and
secondary),
very old
Completed Completed 50 Completed 60 Completed
less to to more
than 50% 60% 80% than 80 %

20
 Sample Size Sufficient and Sufficient and Enough data
small, data appropriate appropriate collected by
neither sample, sample, sufficient and
organized nor enough data enough data appropriate
presented well generated but generated sample size.
not organized which is Proper
and not organized and inferences
presented presented well drawn by
well. No or but poor organising and
poor inferences presenting
inferences drawn data through
drawn tables, charts
and graphs.

5 Incomplete Just Well Well

fabrication/ass assembled/fabri assembled/fabri assembled/fabri
embly. cated and parts cated with cated with
are not proper proper
functioning functioning functioning
well.
Not in proper parts. In proper parts. In proper
shape, shape, within shape, within
dimensions tolerance tolerance
beyond dimensions and dimensions and
tolerance
limit. good good
Appearance/ finish/ finish/
finis appearanc appearanc
h is shabby. e. But no e. Creativity in
creativity in design and use
design and use of material
of material

Very short, Nearly sufficient Detailed, correct Very detailed,

poor quality and correct and clear correct, clear
sketches, details about description of description of
Details about methods, methods, methods,
methods, material, materials, materials,
material, precautions and precautions and precautions and
precaution conclusion, but Conclusions. conclusions.
and
conclusions clarity is not Sufficient Enough tables,
omitted, some there in Graphic charts and
details are presentation. Description. sketches
But
wrong not enough
graphic
description.

Major Includes major Includes major Well organized,

information is information but information and includes major
not included, not well well organized information ,wel

21
 l
information is organized and but not presented
not well not presented presented well
organized . well
Any other
(depending
upon nature of
project: please
write
indicators
by pen)
Could not Replied to Replied Replied most of
reply properly
to considerable to considerable the questions
considerable
number of number of number of properly
question. questions but question.
not very
properly

Every course teacher is expected to assign marks for group evolution for each group of
students in first 3 columns as per rubrics & individual evaluation in 4TH column for each
group of students as per rubrics based on viva.

22
Signature:…………………………………………..

Date:……………………………………

23
24