FEEDBACK COLLECTION API

Under JAVA TECHNOLOGY

(By SIP. (2023))

Submitted By

Group ID: 83

NAME ROLL NO

ASHUTOSH TRIPATHI 5314

PARTH PARMAR 5318

Date of submission: 1st November,2023

Submitted To

K. S. School of Business Management

M.Sc. - Computer Applications and Information Technology.

 TABLE OF CONTENTS
1. INTRODUCTION
System Details
Existing System
Proposed System
Scope of System
Objectives

2. PROPOSED SYSTEM REQUIREMENT GATHERING

Stack-Holder of System
Requirement Gathering Technique Used
Consolidated List
Project Definition

3 SYSTEM MANAGEMENT AND PLANNING

Feasibility Study
Technical Study
Economical Study
Operational Study
Hardware-Software Requirement
System Planning
Work Breakdown Structure
Gantt Chart
Process Model

4 SYSTEM ANALYSIS AND PLANNING

UML (Unified Modeling Language)
System Flow Diagram
Data Dictionary
User Interface
System Navigation

5 INPUT-OUTPUT DESIGN

6 TESTING

7 SUMMARY
Assumption
Limitation
Future Scope
Conclusion
 1- INTRODUCTION

Basically, the desired project is about the Feedback Collection API. Purpose of making this project is to guide an
individual about virtual Feedback Collection. There are number of criteria which have been covered in this
project which was more time consuming. But real time implementation of this project can overcome the stated
problems.

System Details
The system is about the managing the Feedback Collection and formalities regarding to the users. In this system
the administrator will be the service provider itself. Admin is responsible for the all the services being provided
for Feedback Collection.

Existing System
There are number of virtual Feedback Collection systems existing in the market but scope of the system is just
encapsulated for the particular organizations only which includes just couple of features.
Proposed System
There are number of core features included into this system which is stated beneath.
• Student Management System
• Feedback Management System

Listed features will be moderated by the representative of particular organization.

Scope of the System

The desired web application is designed to cover up the basic necessity of the particular virtual Feedback
Collection System based on their own requirement. There are so many ways and situations where
implementation of this web-app can be very useful. The scope of this system is wider than whatever stated
above. Because implementation of this project will create a link to the users as well as the admin and the
duration of the solving problem regarding to the organization will be reduced because of the easy access service.
To implement this system user just require any device which comes with the normal web browser.
Objectives

The main objective to make this project is transparency between huge amount of the users and admin, in
order to provide basic services by system the main aim is to provide the feedback particular
organization. There are so many objectives covered up in this system which drives to develop this type
of system to overcome some of the factors stated following.

• Report Purpose
The user facility is included into this project for only one objective i.e., viewing their feedback

•Easy Access & Data Safety

As this system is much durable that it can easily access in any of the devices which has normal web
browser.so that each and every time users don’t have to contact the administration to complaint or users
can view as well as post their own problems to the respective organizations.
 2- Proposed System Requirement Gathering
The basic step to develop a system which fulfills the users’ requirement is to gather the basic
information about the desired system. This means what actually user/client expects from the system
on their point of view.

2.1 Stack holder of System

There are mainly 2 types of the stack-holders who will be the backbone of this system.

 Admin
 Users

2.2 Requirement Gathering Technique Used

Before developing the system, requirement of the user / client is quite essential. To gather the
requirement of the system the observation and document analysis approach was much effective to
scratch up the skeleton of the system. To gather technique the states approach was quite effective
because the main purpose of client was to provide a platform which facilitates the services to the
students and teachers. But in the real world, this type of systems is very less. So, there is a smaller
number of the reference where basic study of any specific system can be done. So, the requirement
gathering must be obviously depended on the client.

Requirement gathering was also done through some questions as well as some record review also.
Which clears up the remaining scrambled segment of the requirement of the system?

2.3 Consolidated List of Requirement

Consolidated stands for the skeleton or basic or core type of the requirement. So, in that segment
some of the basic requirement was stated by the client is shown as the following

• User data entry

The data entry system is more essential organizations include more users. It is
basic requirement for the users of an organizations to include feedback functionality into the
system so service provider (client) has demanded to include this feature.

• Uniqueness in Huge Similar Data

There is very essential need of uniqueness when there is huge amount of similar data. So that on the
admin side whenever any representative of an organization log-in to the system so there is no chance
of the data confliction
Prospective / Abstraction
There are two actors of this system. So, there will be so many prospective of the system then some of
the module must be private or abstract while some of the module must be exposed which is based on the
role of the user and the login priorities.

Project Definition
On the basis of the upward statements one thing is clear is that the system is about the virtual Feedback
Collection system but the system will not acquire only one particular organization but it will acquire all the
interested organization who will take services by the service provider. So, the development of this project will
be developed under the prospective of the service provider who will handle and manage all the organizations.
 3. System management and planning
Before making any huge project, which require a great effort and teamwork the management and the
planning must be a basic factor to measure a complexity and overall effort to accomplish any
particular project / System.

Feasibility Study
Before going through the planning, we should make sure that whether the system is feasible to the
circumstances or not.

Technical Feasibility

There are number of features which are included into this system the main technologies and the tools
which are connected with this system is:
• Java
• JSP/Spring MVC
• MySQL
• HTML
• CSS / JavaScript/Bootstrap Foundation

All these technologies are freely available and to manage the system using these technologies
requires development skills By implementing this system into the market the main devices are easily
available with every person to access this website. From these, it is clear that the system is
technically feasible to implement.

Economic Feasibility

Initially the website will be host on the free web hosting space. But for later implementation and to
maintain huge amount of data it will be hosted in a paid hosting space for getting more cloud storage to
store data. This protocol will require some minor amount. The amount of maintaining data will be paid
off through the charges being retrieved by the users / service taker. From these protocols it is clear that
the system is quite feasible on the basis of economic criteria.

Operational Feasibility

There are number of the users and the number of the representative to the particular organization. And
the number of the request and requirement will pass to the admin who manages the organization. So
practically it is kind of complex task to response and manage those all requests and database. So, it
requires some special skills to manage the databases and some high level of system mining to overcome
data confliction. On the basis of the above stated possibilities the system seems Operational feasible to
implement.
Hardware & Software Requirement
To access the website user must have the following hardware & software equipment.

Hardware Requirement:
• a device with the basic browser (Android / iOS / Windows)
• internet connection
• min. 2GB of RAM
• A processor with 2ghz of Frequency
• Webcam

Software Requirement:
• JDK environment for developing
• JDBC drivers (.jar execution file)
• Eclipse editor
• MySQL Yog GUI / MySQL workbench (iOS)
• Jsp / Spring MVC
Front End Technologies
 HTML
 CSS
 JavaScript
 Bootstrap / Foundation
System Planning
So, basically the whole process of development period will be followed as stated as below.

System Breakdown Structure

Gantt Chart
Process Model
 4. SYSTEM ANALYSIS & DESIGN
USE CASE DIAGRAM
a- Admin Use Case
b- User Use Case
Class Diagram
Activity Diagrams
a- Admin Activity Diagram
b- User Activity Diagram
Sequence Diagram
a- Admin Sequence Diagram
b- User Sequence Diagram
System Flow Diagram
Data Dictionary
Admin

SR NO Fields Size Constraint

1 Email 30 Not Null
2 Password 25 Not Null

Users

SR NO Fields Size Constraint

1 Name 30 Not Null
2 Email 25 Not Null
3 Password 40 Not Null

Feedback

SR NO Fields Size Constraint

1 Name 30 Not Null
2 Feedback 25 Not Null
User Interface
Home
Login
Registration
System Navigation
 5 INPUT/OUTPUT DESIGN
Homepage
User Registration
User Login
User Feedback
User View Feedback
Admin Login
Admin Home Page
Admin View Feedback
 6- TESTING
USERSIDE
Registration
Test_Id Description Expected Actual Successful/

Result Result Unsuccessful

1 Enter valid detail all Register is As Expected Sucessful

successful
field register Like a

password , phone

number & email

2 If Any Field is Please fill the empty As Expected Sucessful

empty field
Login
TEST ID DESCRIPTION EXPECTED ACTUAL SUCCESSFUL /
RESULT RESULT UNSUCESSFUL
1 Enter valid Email Successfully login As Expected Successful
Id & password
2 Enter Invalid Should not login As Expected Successful
Email ID &
password
3 If user email User should get As Expected Successful
format is validation error for
not valid enter valid email
address
4 If user email & User should get As Expected Successful
password is blank validation error for
Enter Email Id &
password
Feedback

Test ID Description Expected Actual Successful/

Result Result Unsuccessful

1 If Any Field is Please fill the empty As expected Successful

Empty
Field

2 When User Click on Redirected on User As expected Successful

View Feedback link view Feedback

When User enter Redirected on

3 Feedback As expected Successful
valid things
Confirmation Page
ADMINSIDE
LOGIN

TEST ID DESCRIPTION EXPECTED ACTUAL SUCCESSFUL /

RESULT RESULT UNSUCESSFUL
1 Enter valid Email Successfully As Expected Successful
Id & password login
2 Enter Should not login As Expected Successful
Invalid
Email ID
&
password
3 If admin email Admin should As Expected Successful
format is not get validation
valid error forenter
valid email
address
4 If admin email Admin should As Expected Successful
& password is get validation
blank error for Enter
Email Id &
Password

If admin click
5 Redirected to As Expected Successful
on view admin view
feedback page Feedback page

If admin click Redirected to As Expected Successful

delete feedback
6 on delete
page
button in view
feedback page
 7 SUMMARY
Assumption
• Users must have basic knowledge about common browsing and surfing.
• Users must be bit knowledgeable about English language.
• Admin must be smart enough to operate hardware devices as well as the system on which
he/she currently working on.
• In Short to gain up full advantages of this system user must be able to use the system properly.

Limitations
• This system requires bit extra knowledge about the hardware as well as English also therefore it
doesn’t cover mass users.

Future Scope
• All users will get knowledge of collecting feedback virtually
• The system will be a flexible to adopt any type of changes needed.

Conclusion
• The System has been developed with simple user interaction, efficient and less time consuming.
• This Project is based on the requirement specification of the user and the analysis of the existing
system, with flexibility for future enhancement.
• Our system will be tested with proper data and proper validations.
• Data storage and retrieval will become faster and easier to maintain.
• This project is developed as SIP