A MICRO-PROJECT REPORT

ON

“Online Feedback System”

In the partial fulfilment of the requirement for the Diploma

In

Computer Technology

Submitted By

Hase Purva Bhausaheb

Godse Sanika Anil
Mansuri Aribafatema Shahidkhan

Under the Guidance of Prof. Thitme. V. V

Amrutvahini Sheti and Shiksha Vikas Sanstha’s

Amrutvahini Polytechnic, Sangamner

 Amrutvahini Sheti and Shiksha Vikas Sanstha’s

Amrutvahini Polytechnic, Sangamner

Department of Computer Technology

CERTIFICATE

This is to Certify that

Hase Purva Bhausaheb

Godse Sanika Anil
Mansuri Aribafatema Shahidkhan

Has satisfactorily carried out and completed the

microproject entitled:

“Online Feedback System”

As prescribed by MSBTE, Mumbai, as part of syllabus for

the partial fulfilment of Diploma in Computer Technology

Software Testing (22518)

For the academic year 2023-24

Prof- Mr. Thitme V. V Prof- Mr. Kale. G. B

(Guide) (HOD)
 Index

Sr.no Name

1 Rationale

2 Aim/Benefits

3 Course Outcomes Achieved

4 Literature Review

5 Actual methodology followed

6 Actual Resource Used

7 Output of the Micro project

8 Skill Developed/Learning Outcomes

9 Applications
 Acknowledgement
It is our great pleasure to express our heartfelt gratitude to the numerous
individuals who have played a significant role in the development and presentation
of the "Online Feedback System" project.
With their unwavering support, including that of our dedicated staff, project
partners, and external resources, we have successfully completed this endeavour.
We extend our sincere appreciation to each and every one of them for their
invaluable contributions.

We would like to extend a special thank you to our project guide, Mr. Thitme V.
V., whose expert guidance and valuable insights have been instrumental in shaping
both our seminar and project work. We are deeply grateful to all the staff members
and anyone who has lent a helping hand throughout the course of this project.

Furthermore, we wish to express our gratitude to Mr. Kale G. B., Head of the
Computer Technology Department, for his unwavering support in terms of moral
encouragement, technical expertise, and relevant guidance. His contributions have
played a crucial role in ensuring the quality and effectiveness of the 'Online
Feedback System' project.

Once again, we extend our heartfelt thanks to all those who have been part of this
journey.
 Annexure II

M icro-Project Report

Online Feedback System

1.0 Rationale –

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

In this project the Online Feedback System will be tested using different parameters.
Firstly SRS (Software Requirement Specification) will be created i.e., it contains all the
functional and non-functional requirements. It will be easier using SRS to test the
application and find bugs. It will be easier using SRS to test the application and find bugs.
A Test Plan with standard format will be created for this application. Test Cases will be
prepared to test the functionality of the software. And at last, the Summary Report with a
conclusion.
 2.0Aim of Micro-Project –

The primary objective is to enhance user engagement and satisfaction by providing a

user-friendly platform for collecting feedback and suggestions from website visitors. This
system will allow users to easily submit their opinions, report issues, and share valuable
insights, which will be analysed and used to make data-driven improvements to our
website's content, design, and functionality

3.0 Course Outcomes Addressed –

Co. No. Course Outcome Statement

CI504.1 Describe various software testing methods

CI504.2 Use different types and levels of testing writing test cases

CI504.3 Prepare test plan for an application

CI504.4 Prepare defect report based on bugs identify for given application

CI504.5 Use automated testing tool to test software for performance measures

4.0 Literature Review –

Online Feedback System reveals a growing interest in harnessing digital platforms

to facilitate efficient and constructive feedback exchanges. In the educational
context, online feedback systems have been found to enhance student engagement,
foster self-regulated learning, and improve academic performance. Additionally, in
the realm of e-commerce and service industries, online feedback systems play a
pivotal role in shaping consumer decisions and improving business outcomes.

5.0 Actual Methodology Followed –

 Collect feedback requirements from stakeholders.
 Create an architecture and UI for the feedback system.
 Build the system using chosen technologies.
 Design and implement the database schema.
 Rigorously test the system for functionality and security.
 Roll out the system for actual use and gather user feedback.

6.0 Actual Resources Used –

Sr. No. Name of Resource/material Specifications Quantity Remarks
Computer System with broad 13 processor, 2GB 1
1 specifications RAM
2 Operating System Windows 7 (for
practical study)
 Google Chrome (for
3 Browser Support
data analysis)
7.0 Output of Micro-project –
6.0.1 - Functionality Requirement Specification
Student Module:
First, the student has to register. Only registered Student will log in by his username and
password. In the dashboard all the contents of the student's feedback forms will be
displayed. There would be option student feedback in this there would be questions
related to how students can make the teaching quality better. Student can tell his likes and
dislikes about the teachers by attending every questions.
Faculty Module:
Here faculty will first login in this section. The faculty will enter their user’s name and
password if the faculties do not have an account, they have to sign up in order to create
an account. As the details are filled the faculty dashboard appears in which they can fill
self-appraisal, peer appraisal. The faculty should firstly fill the self-appraisal in which
they have to rate themselves on some criteria. The peer faculty has to click onto the peer
appraisal in order to fill the form as they click onto peer appraisal.
Principal/H.O. D’s Module:
HOD user cannot sign up for the feedback system since she is the only one to access the
feature the login is pre-defined in code itself. Once the HOD logins into her portal she
can perform various tasks like Giving authority appraisals also reviewing form no one
which is duly filled by faculty after verifying that only then the HOD can further proceed
with the summary form. In summary, the total of all marks will be calculated and
according to it percentage is calculated also the grades are calculated on this percentage
basis also she can take print out of the summary list and keep a backup of it.

6.0.2- TEST PLAN

Prepare Test Plan for Online Feedback System
1 Introduction
The Test Plan is designed to prescribe the scope, approach, resources, and schedule of all
testing activities of the project Online Feedback System.
The plan identifies the items to be tested, the features to be tested, the types of testing to
be performed, the personnel responsible for testing, the resources and schedule required
to complete testing, and the risks associated with the plan.
1.1 Scope
1.1.1 In Scope
All the feature of Online Feedback System which were defined in software requirement
specs are need to bested
Module Name Applicable Roles Description
Registration Students, Students: A student can register into the college
Faculty, HOD, feedback system by entering his Name, then
Principal Password again confirm password field, as well
as Email ID and Mobile No. will be required
here. Either he/she can register or login if he/she
has an account already over the system
Login Students, Admin 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 allocated to
them. If He/she don't have account He/she can
register using 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.
Feedback Student Student: Here in this Feedback module, there are
number of Feedback partitions. Such as: -
1. Course Feedback, here a student can give
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.
4.College 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.
4. Canteen Feedback, here a student can give
feedback related in canteen, items sold in
canteen, item sold in canteen, their costing more
or less, etc.
Logout Student, Admin Students: Students can logout after giving his
feedback on the college online feedback system
using Logout option available there.
Admin: Admin can logout after he has collected
feedback of students.

1.1.2 Out of Scope

These features are not be tested because they are not included in the software requirement
specs
 User Interfaces
 Hardware Interfaces
 Software Interfaces
 Database logical
 Communications Interfaces
 Website Security and Performance
1.2 Quality Objective
The test objectives are to verify the functionality of the Online Feedback System the
project should focus on testing the Feedback operation to guarantee all these operations
can work normally in real business environments.
1.3 Roles and Responsibilities
The project should use outsourced members as the tester to save the project cost.
No. Member Tasks
1 Test Identifying and describing appropriate test techniques/tools/
automation architecture Verify and assess the Test Approach
Execute the tests, Log results, Report the defects. Outsourced
members
2 Developer in Developer in Test Implement the test cases, test program, test
Test suite etc
3 Test Builds up and ensures test environment and assets are
Administrator managed and maintained Support Tester to use the test
environment for test execution
4 SQA members Take in charge of quality assurance Check to confirm whether
the testing process is meeting specified requirements
2 Test Methodology
2.1 Test Levels
In the project line Feedback System, the 3 types of testing should be conducted.
  Integration Testing (Individual state modules are combined and tested as a
group).
 System Texting Conducted on a complete integrated system to evaluate the
system's compliance with in specified requirements.
 API testing Ted all the APIs creme for the software under tested.
2.2 Suspension Criteria and Resumption Requirements
If the team members report that there are 40% of test cases failed, suspend testing until
the development team is all the failed
2.3 Test Complete
 Specifies the criteria that denote a successful completion of a test phase
 Run rate is mandatory to be 100% unless a clear reason is given.
 The pass rate is 80%, and achieving the pass rate is mandatory
2.4 Project task and estimation and schedule
Task Members Estimate Effort

Create the test specification specification Test Designer 12man-hour

Perform Test Execution Tester, Test Administrator Designer 10man-hour

Test Report Tester Designer 6man-hour

Total Designer 28man-hour

3) Test Deliverables
Test deliverables are provided below
Before testing phase
 Test plans document.
 Test cases documents
 Test Design specifications.
4) Test Environment
It mentions the minimum hardware requirements that will be used to test the Application.
Following software's required in addition to client-specific software.
 Windows 8 and above
 Office 2013 and above
5) 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

6.0.3- 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 testcases can be built to produce 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, 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
testcase should also contain a place for the actual result.
These steps can be stored in a word processor document, spreadsheet, database or other
common repository.
In a database system, you may also be able to see past test results and who generated the
result sand the system configuration used to generate those results. These past results
would usually be stored in a separate table. Test suites often also contain
 Test summary
 Configuration.

6.0.4- Test Case

Test Test case Test Steps Test Data Expected Actual Status
case ID Description Result Result
FB001 Verify that a “Navigate to the Valid Feedback is Feedback is Pass
 user can feedback feedback submitted submitted
successfully submission text. successfully. successfully.
submit page.”
feedback
with valid “Enter valid
input. feedback text in
the feedback
field.”

“Click the
"Submit"
button.”
FB002 Verify that a “Navigate to the Empty User receives User Pass
user cannot feedback feedback an error receives an
submit submission text. message error
feedback page.” indicating message
without that feedback indicating
entering any “Leave the cannot be that
text. feedback field empty. feedback
empty.” cannot be
empty.
“Click the
"Submit"
button.”
FB003 Verify that “Navigate to the Test Data: Feedback Feedback Pass
the feedback feedback N/A submission submission
submission submission form is form is
form is page.” displayed displayed
displayed with the with the
correctly. required required
fields. fields.
FB004 Verify that a “Navigate to the Feedback User receives User Pass
user cannot feedback text an error receives an
submit submission exceeding message error
feedback page.” the indicating message
exceeding character that feedback indicating
the “Enter feedback limit. text is too that
maximum text exceeding long. feedback
character the character text is too
limit. limit.” long.

“Click the
"Submit"
button.”
FB005 Verify that “Submit valid Valid Submitted Submitted Pass
submitted feedback.” feedback feedback is feedback is
feedback is text. displayed in displayed in
displayed in “Navigate to the the user's the user's
 the user's user's feedback feedback feedback
feedback history.” history. history.
history
FB006 Verify that a “Submit valid Modified The edited The edited Pass
user can edit feedback.” feedback feedback is feedback is
their text. saved saved
submitted “Navigate to the successfully. successfully.
feedback. user's feedback
history.”

“Click the "Edit"

button for the
submitted
feedback.”

“Modify the
feedback text.”

“Click the
"Save" button.”
FB007 Verify that a “Submit valid N/A The feedback The Pass
user can feedback.” is deleted feedback is
delete their successfully. deleted
submitted “Navigate to the successfully.
feedback. user's feedback
history.”

“Click the
"Delete" button
for the
submitted
feedback.”

“Confirm the
deletion.”
FB008 Verify that “Log in as an Admin The admin The admin Pass
an admin can admin.” credentials. can view a can view a
view all list of all list of all
feedback “Navigate to the feedback feedback
submissions. admin submissions. submissions.
dashboard.”

“Access the
feedback
submissions
page.”
FB009 Verify that “Log in as an Admin The admin The admin Pass
an admin can admin.” credentials can view can view
 filter and date filtered filtered
feedback “Navigate to the filter feedback feedback
submissions admin criteria. submissions submissions
by date. dashboard.” based on the based on the
date criteria. date criteria.
“Access the
feedback
submissions
page.”

“Apply a date
filter.”
FB0010 Verify that “Log in as an Admin The selected The selected Pass
an admin can admin.” credentials feedback is feedback is
mark and marked as marked as
feedback as “Navigate to the feedback resolved. resolved.
resolved. admin to mark as
dashboard.” resolved.

“Access the
feedback
submissions
page.”

“Select a
feedback
submission.”

“Mark it as
resolved.”

6.0.5- TEST CASE Report

Application Test Scenario In our Online Feedback System there is a “Transport Feedback
Issue” Module. In that module user enters all details in that form which are required.
When 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.
Description:
Application crash on clicking the Submit button after filling Transport Feedback form.
Steps to reproduce:
1. Login to the application.
2. Click on Feedback Option.
3. Enter the Transport Feedback option.
4. Fill 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.

6.0.6- SUMMARY
In today’s world where education has become a basic necessity for every child/adult so to
ensure that proper education Is being delivered or not their lefts only one way „by taking
feedback‟ so as to reduce the manpower, the software is built which automatically takes
the feedback turn by turn so as to not skip any of the member.
  The number of test cases executed- 18
 The numbers of test cases pass – 17
 The numbers of test cases fail – 1
 Pass percentage – 94.45 %
 Fail percentage – 5.55%
 Comments - We have prepared defect report of one defect and assigned it to
developer so as to resolve it. Other modules are tested and they don’t have any
issue.
8.0 Skill Developed / learning out of this Micro-Project –
This Project is created for improving the testing knowledge of applications.
1. Studying of the different types of testing techniques.
2. Learned how to prepare Test Plan related to that specified application.
3. Learned how to prepare Test Cases to test if the application is working properly or not.
4. Learned about SRS (Software Required Specification) document.
5. Learned about Defect Report and its necessity.
6. Studied advantages and disadvantages of testing and how necessary it is to build a
defect free software and user friendly.
9.0 Applications –
o Agricultural Research: Gathering feedback from farmers and agricultural experts
to improve crop management and sustainable farming practices.
o Space Exploration: Collecting feedback from astronauts and scientists involved in
space missions to enhance spacecraft design and mission planning.
o Museums and Art Galleries: Implementing feedback systems to understand visitor
preferences and improve exhibit curation and engagement.
o Nonprofit Organizations: Using feedback to assess the impact of charitable
programs and fine-tune strategies for social and environmental causes.
o Online Marketplaces for Rare Items: Enabling feedback on authenticity and seller
credibility for unique or collectible items.
o Autonomous Vehicles: Gathering feedback from users of self-driving cars to
enhance safety and usability in emerging transportation technologies.