CONTENTS

1. INTRODUCTION 5
1.1Introduction 6
2 .PROBLEM DEFINITION AND METHODOLOGY 7
2.1Problem definition 8
2.2Objectives 8
2.4Methodolog 10
3. REQUIREMENT ANALYSIS AND SPECIFICATION 14
3.1System analysis 15
3.1.1 Requirement Analysis 15
3.1.2Existing system 15
3.1.3 Proposed System 16
3.1.4 Feasibility Study 19
3.1.4.1 Technical Feasibility 20
3.1.4.2economic Feasibility 20
3.1.4.3 Behavioural Feasibility 21
3.1.5Cost Benefit Analysis 21
3.1.5.1Hardware Cost 21
3.1.5.2Software Cost 22
3.1.5.3 Personnel Cost 22
3.2Requirement specification 22
 PRODREV

3.2.1Functionalrequirements 22
3.2.2Non functional requirements 23
3.2.3Environmental requirements 24
4. SYSTEM DESIGN 26
4.1SystemDesign 27
4.1.1. Architecture Diagrams 27
4.1.1.1 Data Flow Diagrams 27
4.2 Database Design 30
4.2.1 Normalization 31
4.2.2 ERdiagram 32
4.3 Table design 34
5.IMPLEMENTATION 38
5.1 System implementation 39
6.SYSTEM TESTING 41
6.1System testing 42
6.1.1Unit testing 42
6.1.2Integration testing 43
6.1.2.1TopDown integration 43
6.1.2.2Bottomup integration 43
6.2Future enhancement 44
 PRODREV

7. CONCLUSION 46
7.1 Conclusion 47
8.BIBLIOGRAPHY 48
8.1Bibliography 49
9.APPENDIX 50
9.1Screenshorts 51

3
 PRODREV

ABSTRACT

4
 PRODREV

PROJECT ABSTRACT
E shopping is an integral aspect in the current day to day human
lifestyle. In the IT world we have numerous e-commerce platforms to
meet the shopping needs. Each ecommerce platform allows users to
update the product review for the purchase. Every e-commerce user
today has the luxury to view the review of the same product in different
shopping sites. Generally these are termed as product ratings. Product
ratings are nothing but a scale of values from 1 to 5. Higher the rating
means better the quality of the product. Apart from the rating the buyers
also express their views on the product. Each user review has three main
aspects feeling, experience and sentiment. These factors vary from
individual to individual. Any user before the purchase of a specific
product has to invest a good amount of time in different websites to
understand the review. Many users will loose their interest too for
purchasing the product. To overcome this we have some core objectives
which serves as the fundamentals for the proposed model. users will
loose their interest too for purchasing the product.
To overcome this we have some core objectives which serves as the
fundamentals for the proposed model.
They are as follows:
• Understanding the sentiments expressed in the product reviews
• An automated system which collects reviews from different sources.
• Reducing the manual intervention.
With these core objectives will enable the buyer to make fast and
reliable decisions while shopping.

5
 PRODREV

LIST OF FIGURES
Fig2.4 12
Fig4.1.1.1a 29
Fig4.1.1.1b 29
Fig4.1.1.1c 30

6
 PRODREV

LIST OF TABLES
Table4.3 35
Table4.3a 35
Table4.3b 36
Table4.3c 36
Table4.3d 37
Table4.3e 37
Table4.3f 38

7
 PRODREV

1.INTRODUCTION

8
 PRODREV

1. 1 INTRODUCTION
E shopping is an integral aspect in the current day to day human
lifestyle. In the IT world we have numerous e-commerce platforms to
meet the shopping needs. Each ecommerce platform allows users to
update the product review for the purchase. Every e-commerce user
today has the luxury to view the review of the same product in different
shopping sites. Generally these are termed as product ratings. Product
ratings are nothing but a scale of values from 1 to 5. Higher the rating
means better the quality of the product. Apart from the rating the buyers
also express their views on the product. Each user review has three main
aspects feeling, experience and sentiment. These factors vary from
individual to individual. Any user before the purchase of a specific
product has to invest a good amount of time in different websites to
understand the review. Many users will loose their interest too for
purchasing the product.

9
 PRODREV

2.PROBLEM DEFINITION AND METHODOLOGY

10
 PRODREV

2.1 PROBLEM DEFINITION

Each ecommerce platform allows users to update the product
review for the purchase. Every e-commerce user today has the luxury to
view the review of the same product in different shopping sites.
Generally these are termed as product ratings. Product ratings are
nothing but a scale of values from 1 to 5. Higher the rating means better
the quality of the product. Apart from the rating the buyers also express
their views on the product. Each user review has three main aspects
feeling, experience and sentiment. These factors vary from individual to
individual. Any user before the purchase of a specific product has to
invest a good amount of time in different websites to understand the
review. Many users will loose their interest too for purchasing the
product.
To overcome this we have some core objectives which serves as the
fundamentals for the proposed model.
They are as follows:
• Understanding the sentiments expressed in the product reviews
• An automated system which collects reviews from different sources.
• Reducing the manual intervention.
With these core objectives will enable the buyer to make fast and
reliable decisions while shopping.

2.2 OBJECTIVES
Our objective is to build an intelligent decision-making system by
implementing sentiment analysis techniques, thus helping the buyers to

11
 PRODREV

have a smooth online shopping experience. Sentiment analysis basically

derives the subjective information from text and classifies them as
positive, negative or neutral. Sentiment analysis is generally related with
opinion mining. It is an approach in Natural Language Processing
(NLP).From opinions the system evaluates the expression attributes
known as:
• Polarity: it basically relates to what is the speakers opinion: Positive or
Negative
• Subject: The matter being talked about.
• Opinion Holder: who is expressing the opinion the entity or person.
The topic sentiment analysis currently is of greater interest as it is
related with many practical applications. Many com use sentiment
analysis to automatically analyse the responses from the survey, product
reviews and social media to have valuable insights about their brand and
services. Scope can be applied to the levels mentioned below:
• Document Level : The analysis obtained from a complete set of
document or a block of paragraph.
• Sentence level: Analysis obtained from a single sentence .
• Sub-Sentence level: Analysis obtained from a set of sub expressions
with in the sentence .
It has been estimated that 75 percent of the whole data is
unstructured. This directly means we are dealing with a set of data
which is not organized in a pre-defined manner. Sentiment analysis
system gathers such huge amount of unstructured text and allows
companies to make sense by automating business process, reducing
12
 PRODREV

hours of manual data processing there by making more efficient work

outcomes. Some of the other advantages of Sentiment analysis are
scalability with respect to data, real time analysis of data, reduced errors
and increased consistency.

2.4 METHODOLOGY
In earlier days Iterative Waterfall model was very popular to
complete a project. But nowadays developers face various problems
while using it to develop a software. The main difficulties included
handling change requests from customers during project development
and the high cost and time required to incorporate these changes. To
overcome these drawbacks of Waterfall model, in the mid-1990s the
Agile Software Development model was proposed.
The Agile model was primarily designed to help a project to adapt
to change requests quickly. So, the main aim of the Agile model is to
facilitate quick project completion.To accomplish this task agility is
required. Agility is achieved by fitting the process to the project,
removing activities that may not be essential for a specific project.
Also,anything that is wastage of time and effort is avoided.
Actually Agile model refers to a group of development processes.
These processes share some basic characteristics but do have certain
subtle differences among themselves. A few Agile SDLC models are
given below. Agile model is the combination of iterative and
incremental process models.
Steps involve in agile SDLC models are:
• Requirement gathering
• Requirement Analysis
13
 PRODREV

• Design
• Coding
• Unit testing
• Acceptance testing
The time to complete an iteration is known as a Time Box. Time-
box refers to the maximum amount of time needed to deliver an iteration
to customers. So, the end date for an iteration does not change. Though
the development team can decide to reduce the delivered functionality
during a Time-box if necessary, to deliver it on time. The central
principle of the Agile model is the delivery of an increment to the
customer after each Time-box.

Fig:2.4

PYTHON
14
 PRODREV

Python is an interpreter, object-oriented, high-level programming

language with dynamic semantics. Its high-level built in data structure,
combined with dynamic typing and dynamic binding, makes it very
attractive for Rapid Application Development, as well as for use as a
scripting or glue language to connect existing components together.
Python’s simple, easy to learn syntax emphasizes readability and
therefore reduces the cost of program maintenance.Python supports
modules and packages, which encourages program modularity and code
reuse.The Python interpreter and the extensive standard library are
available in source or binary form without charge for all major platform,
and can be freely distributed.

MySQL
MySQL database has become the world's most popular Open
source database because of its consistency, fast performance, high
reliability and ease of use. It has also become the database of choice for
a new generation of applications built on the XAMPP stack (Linux,
Apache, MySQL, PHP / Perl / Python). MySQL runs on more than 20
platforms including Linux, Windows. MySQL offers a comprehensive
range of certified software, support, training and consulting. My SQL is
a multithreaded, multi-user SQL Database Management System.
MySQL's implementation of a relational database is an abstraction on
top of a computer’s file system. The relational database abstraction
allows collection of data items to be organized as a set of formally
described tables. Data can be accessed or reassembled from these tables
in many different ways, which do not require any reorganization of the
database tables themselves.
MySQL Features:
15
 PRODREV

1. Very fast and much reliable for any type of application.

2. Very light weight application.
3. Command line tool is very powerful and can be used to run SQL
queries against data base.
4. Supports indexing and binary objects.
5. Allows changing the structure of table while server is running.
6. It is a very fast thread-based memory allocation system

16
 PRODREV

3.REQUIREMENT ANALYSIS
AND SPECIFICATION

17
 PRODREV

3.1 SYSTEM ANALYSIS

System analysis is the process of collecting and interpreting facts,
understanding problems and using the information to suggest
improvements on the system. This will help to understand the existing
system and determine how computers make its operation more effective.
The aim of this analysis is to collect the detailed information on the
system and the feasibility study of the proposed system. This analysis
focuses on the flow of the system module by module and the efficiency
of each. To design the proposed system we need the exact processing
logic as well as the extended features of the existing system such as
reliability, consistency, storage capacity etc. This report will discuss the
advantages and drawbacks/disadvantages of the existing system and the
modifications and enhancements can be done. This analysis will
concentrate on the information gathering for the efficient, user friendly
and reliable system, which will carry forward the features of the existing
system.

3.1.1 1 REQUIREMENT ANALYSIS

Requirements analysis results in the specification of
software’s operational characteristics, indicates software’s
interface with other system elements, and establishes constraints
that software must meet. Requirements analysis allows you to
elaborate on basic requirements established during the inception,
elicitation, and negotiation tasks that are part of Requirements
engineering.
3.1.2 EXISTING SYSTEM

18
 PRODREV

The existing system include veriety of online shopping

websites,if we buy through the online platforms in now current
online future are great value aroint us. And depend for all
product even every simple products.to know the quality of
procuts we read all reviews and ratings in each sites.and we
calculatete in mind by compare all values of rating and review
3.1.3 PROPOSED SYATEM
A rule based system is used to formulate decisions based on certain
pre existnig assertions. As we mentioned earlier, there are many
challenges in sentiment analysis. Some of those challenges include the
following. During preprocessing symbols might be lost. It is quite
possible that models may not understand emoji’s and words like ’don’t’,
’shouldn’t’ in the correct sense. After pre-processing these words might
become ‘do’ and ’should’ which completely change the polarity of
thesentence that may severely affect the end results. These days people
are using short forms while commenting or writing reviews. For
example, ’gud’ instead of good, ’luv’ instead of love, ’alr8’ for alright
etc. Our rule based system is designed to overcome such challenges.
Dictionaries are created with enough knowledge within them.
Dictionaries include words, emoji’s, booster words, negating words,
short forms etc. Our model collects reviews automatically for a given
product by scraping and then pre-processes the collected data byre
moving stop words and breaking the strings into tokenized arrays of
single words. These words are analysed against text files that contain
emotion words with ratings, emoticons with ratings, booster words with
ratings and possible polarity changers.. Lev- enshtein algorithm is used
to find any phrase matches as it will be more accurate, meaningful, fast
19
 PRODREV

and easy to give sentiment score for a phrase. All the sentiment scores of
each review is taken into account and the average of those scores
represent the quality of the product acquired from the experiences of the
previous customers.
A. Scraping
To gather data for the proposed model, websites, for example,
amazon.in, having product reviews are crawled and the data is saved in
the local computer.
B. Pre processing
Quite often, it is observed that the data obtained from scraping may
not be ready for feeding into an algorithm. The scraped data might
consist of data with spelling errors, data that may not be useful for the
algorithm, data having a different data type, stop words etc. One of the
practices of Pre processing involves tokenization and removal of stop
words. Tokens can be words in a sentence or even sentences from a
document can act as tokens. For example, a given sentence like ’Natural
language processing is one branch of computer science, will be
tokenized into ’Natural, ’language’, ’processing, ’is, etc. Sometimes,
some extremely common words which would appear to be of little value
in helping select documents which match a user requirement are
excluded from the vocabulary entirely. These words are called stop
words. One of the major forms of pre-processing is to filter out data that
does not conform to the parameters of the algorithm. Stop words are
words that occur too frequently in a given document or a paragraph, for
example, words like ’a’, ’the’ etc. Crawlers in some search engines
ignore these words, to reduce the amount of memory consumed by data.
Hence such stop words are removed from the text data by comparing
20
 PRODREV

them with a pre existing set of stop words. The text data obtained after
cleaning it of stop words is used for evaluation.
C. Phrase matching
After the processing of data is complete, a phrase matching process
is undertaken. We have a dataset that is analysed. This phase of the
proposed model is for comparison of the current phrase with that of the
existing dataset. Levenshtein distance is utilised to compare the different
phrases. This means that the more phrases we have analysed previously
improves the entire dataset and allows phrases to be more accurately
scored against historical data. A block diagram of the proposed model is
given .The user just needs to enter the ASIN(Amazon Standard
Identification number) code which is a code that is unique for all
amazon products. The algorithm gathers all the web data of that amazon
product. All the unwanted strip tags and irrelevant data (the data other
than reviews) is removed and the data is sent for pre-processing. After
pre processing:
• Phrases are split up into lengths of n grams
• The phrase array is sorted in such a way that the word length from 10,
9 etc are sorted (descending order)
• There are three categories into which the phrases are compared with,
positive, negative and neutral
• Only matches that meet the minimum Levenshtein minimum distance
and similarity minimum distance are kept
D. Levenshtein Distance

21
 PRODREV

In Natural Language Processing, it is often a requirement that

strings be compared with each other. Levenshtein distance is a method
to observe the difference between two strings. It looks at the number of
characters which needs to be changed for one string to resemble the
other. Primarily it looks at single characters that can be can inserted,
substituted or deleted for one word or string to change to another. For
example, the Levenshtein distance between ”similar” and ”silver” is 4,
since it takes 4 edits for the words to change from one to another there is
no way to do it with fewer than three edits. A few further examples are
given below
• silver and similar - Levenshtein distance is 4
• property and properly - Levenshtein distance is 1
• congruent and congruous - Levenshtein distance is 3
There are upper and lower bounds of Levenshtein distance,
• It is at least the difference of the sizes of the two strings
• It is at most the length of the longer string.
• It is zero if and only if the strings are equal

3.1.4 4 FEASIBILITY STUDY

Feasibility study is made to see if the project on completion will
serve the purpose of the organization for the amount of work, effort and
the time that is spent on it. Feasibility study lets the developer foresee
the future of the project and the usefulness. Feasibility study is a test of
the system proposed regarding its workability, impact on the
organization, ability to meet the needs and effective use of resources.
Thus when a new project has proposed, it normally goes through a
22
 PRODREV

feasibility study before the development. The system proposed has

tested to check whether it is feasible by conducting the following:
1. Technical feasibility
2. Economic feasibility
3. Behavioral feasibility
3.1.4.1 TECHNICAL FEASIBILITY
It is considered in terms of technical requirements and their
availability in the markets. It determines whether the current level
of technology supports the proposed system or not. The technical
possibility of proposed system is as follows:
• The proposed system does not require much technical details.
• The current manual working is not so much sufficient.
• It just requires Windows operating system.
• The organization has already purchase all the enough devices
for latest technology. Hence, the proposed system is technically
feasible.
3.1.4.2 ECONOMIC FEASIBILITY
• The economic feasibility is considered in terms of
money/price value .The organization measure the cost effectiveness
of the project . The economic feasibility of the proposed system
is as under:
• The organization is ready to invest in proposed system for latest
technology and best result.

23
 PRODREV

• As the personnel and the manager know the computer

operating, the unit need not have to appoint any computer operator.
• The units has not be spend much amount for the computer
hardware and prodrev application.
3.1.4.3 BEHAVIORAL FEASIBILITY
The system is designed in user friendly manner and we need not to
provide any special training for the persons using this mobile website

3.1.5 5 COST BENEFIT ANALYSIS

The cost benefit analysis is a systematic process for calculating and
comparing benefits and costs of a project. In developing cost estimate of
the system, we consider the following elements.
• Hardware Cost
• Software Cost
• Personal Cost
• Operating Cost
3.1.5.1 HARDWARE COST
Hardware costs are related to the expenses incurred in buying the
required hardware. When considering the hardware cost which is
concerned with the cost of personal computer required by the developer
to code the application and also cost of personal computer required for
the server to store details of customers which are uploaded from stores.
The hardware that is required by the customer is an android phone.
Nowadays, personal computers and android phones are easily available
in the market at an affordable cost.
24
 PRODREV

3.1.5.2 SOFTWARE COST

Software cost includes all the cost related to the software tools
required to develop and run the system. All the tools necessary are open-
source and so the software .cost required to develop the system is very
less.
3.1.5.3 PERSONNEL COST
The users and admin are sufficient for the system to run. It requires
only simple training for admin to monitor and control the activities
because it is easy to understand.
3.1.5.4 OPERATING COST
It includes all cost with the day to day operation of the system.
General cost to run the system includes electricity charges, Internet
charges etc.

3.2 REQUIREMENT SPECIFICATION

3.2.1 FUNCTIONALREQUIREMENTS
Functional requirements of a system can relate to hardware,
software or both in terms of calculations, technical details, data
manipulation and processing or other specific functionality that defines
what a system is supposed to accomplish. A functional requirement can
be in the form of a document explaining the expected types of outputs
when the device (system) is placed in a certain kind of environment. A
functional requirement is said to be a later form of a system design
because a design is the outcome of overcoming a certain kind of a
problem

25
 PRODREV

(technical/non-technical) being faced .The Functional Requirements

Specification documents the operations and activities that a system must
be able to perform.
Functional Requirements should include:

each screen
-flows performed by the system

3.2.2 ON FUNCTIONALREQUIREMENT
A non-functional requirement is a requirement that specifies
criteria that can be used to judge the operation of a system, rather than
specific behaviours.
a. Need Internet connection.
b. Usability
The system’s interface is user-friendly and easy to get familiar with.
c. Reliability

26
 PRODREV

d. Performance
Response time for a transaction - maximum.
e. Security
The system shall protect itself and its sensitive data and communications
from accidental,malicious, or unauthorized access, use, modification, or
destruction.
f. Safety

The system shall prevent any possible threat to human lives.

DESIGN CONSTRAINTS
Software Constraints
The system should run on windows 7 and above operating system or on
linux operating system,VS code, PySQL client,python 3.7.4 Software.
Hardware Constraints
The system should run on CORE(TM) and above workstation with at
least 2GB RAM and 100MB hard Disk
Assumption
The person who is entering data into software is aware of the fact that
the proper values are entered as no validation done for that.

3.2.3 ENVIRONMENTAL REQUIREMENTS

Hardware Specifications
The selection of hardware is very important in the existence and
proper working of any software.
27
 PRODREV

Then selection hardware, the size and capacity requirements are also
important.
• Processor : Intel Pentium Core i3 and above
• Primary Memory : 4GB RAM and above
• Storage : 320 GB hard disk and above
• Display : VGA Color Monitor
• Key Board : Windows compatible
• Mouse : Windows compatible
Software Specifications
One of the most difficult task is selecting software for the system, once
the system requirements
is found out then we have to determine whether a particular software
package fits for those system
requirements. The application requirement:
OPERATING SYSTEM : WINDOWS 10
FRONT END :PYTHON
BACK END : Mysql
SOFTWARES USED : Jetbrains Pycharm,SQLyog

28
 PRODREV

4.SYSTEM DESIGN

29
 PRODREV

4.1 SYSTEM DESIGN

Design is a meaningful engineering representation of something
that is to be built. It is an iterative process through which requirements
are translated in to a blueprint for constructing the software. The goal of
the design phase is to plan a solution of the problem specified by the
requirements document.

4.1.1 ARCHITECTURAL DIAGRAMS

4.1.1.1DATA FLOW DIAGRAM
A data flow diagram is a graphical technique that depicts data flow
and transforms that are applied as data move from input to output. The
DFD is used to represent increasing information flow and functional
details. A Level 0 DFD also called a fundamental system model or
context model represents the entire software elements as a single bubble
with input and output indicated by incoming and outgoing arrows
respectively. Additional process and information flow parts are
represented in next level i.e., Level 1 DFD. Each of the processes
represented at level 1 are sub functions of overall system depicted in the
context model.
Data flow diagram symbol:

Source/Destination of Data

Data flow

30
 PRODREV

Process

Storage

LEVEL 0 DFD
As shown in the Fig. Two actors in this system are Admin and
user.The two actors can interact with the system.

Fig4.1.1.1a
LEVEL 1 FOR ADMIN

31
 PRODREV

Fig4.1.1.1b
EVEL 1 FOR USER

Fof4.1.1.1c

32
 PRODREV

4.2 DATABASE DESIGN

A database is collections of inter related data stored with
minimum redundancy to serve many users quickly and efficiently. In
database design data independence, accuracy, privacy, and security are
given higher priority. Database design is an integrated approach to file
design. This activity deals with the design of the physical database. All
entries and attributes have been identified while creating the database.
The database design deals with the grouping of data into number of
tables so as to reduce the duplication of data, minimize storage space,
and retrieve the data efficiently.
Guidelines for designing a database:

Design a relational schema so that it is easy to explain its meaning.

Do not combine attributed from multiple entity and relationship types
into a single relation.

Design the database schema so that no insertion, deletion or

modification anomalies are present in the relation.

As far as possible, avoid placing attributes in a base relation whose

values may frequently be null.
Advantages

Ease of use

Data independence

Accuracy and
integrity

Avoiding inordinate delays

 PRODREV
Recovery from failure
33
 PRODREV

Privacy and security.

4.2.1 1 NORMALIZATION
Normalization theory is built around the concept of normal form.
Normalization reduces necessary redundancies of data in database.
Redundancy can cause problem with storage and retrieval of data in
database. During the process of normalization, dependencies can be
identified which can cause problem during deletion and updating
database.
Normalization theory is based on the fundamental for fundamental
dependency. Normalization helps in simplifying structure of tables.
FIRST NORMAL FORM
Moving data into separate table when the data in each table is of
similar type and giving each table a primary key to this. This eliminates
repeating groups of data.
SECOND NORMAL FORM
First normal form table can be converted into second normal
form by taking out data that is only depend on part of the key.
THIRD NORMAL FORM
This means getting rid of anything in the table that does not depend to
primary key. Any time the data is in third normal form, is already
automatically in second normal form. There must be no indirect
relationship between attributes.

34
 PRODREV

In the database all the information are stored in the form of tables. A
table is simply a way storing data in rows and columns. In the system
data is stored in many tables.

4.2.2 2 ER DIAGRAM
An entity-relationship diagram is a data modeling technique that
creates a graphical representation of the entities, and relationship
between entities, within an information system.
There are three basic elements in ER models:
• Entities are the “things” about which we seek information
• Attributes are the data we collect about entities.
• Relationships provided the structure needed to draw information
from multiple entities.
ER Diagram Symbols:

Entity

Attribute

35
 PRODREV

Relation

36
 PRODREV

4.33TABLE DESIGN
In the database all the information are stored in the form of
tables. A table is simply a way storing data in rows and columns. In the
system data is stored in many tables.

Table name Description

Feedback Store feedback

37
 PRODREV

Login Store username and password

Product Store products

Product_rate Store product rating

Review Store feedback

Usertb Store user deteils

Table4.3
1.Table name:feedback
Field Datatype Description Constraits

Feedback_id Int Feedback id Primary key

User_id Int User id Not null
feedback Varchar() Feedback Not null

Date Date Date Not null

Table4.3a
2.Table name:login
Field Datatype Description Constraits

Login_id int Login id Primary key

Username Varchar() Username Not null

38
 PRODREV

Password Varchar() password Not null

Type Varchar() Type(admin/user) Not null

Table4.3b
3.Table name:product
Field Data type Description Constraints

Product_id Int Product id Primary key

Product_name Varchar() Product name Null

Price Varchar() Price Null

Image Varchar() image Null

Quantity Varchar() quantity Null

Table4.3c

Table name:product_rate
Field Data type Description Constraints

Rat_id Int Rate id Primary key

P_id Int Product id Foreign key

39
 PRODREV

Rate Double Rate Null

Table4.3d
Table name:review
Field Datatype Description Constraints

Review_id Int Review id Primary key

User_id Int User id Null

Product_id Int Product id Null

Review Varchar() Review Null

Date Date Date Null

Table4.3e
Table name:usertb
Field Data type Description Constraints

User id Int User id Primary key

Login Int Login id Null

Id
40
 PRODREV

F_name Varchar() First name Null

L_name Varchar() Last name Null

Gender Varchar() Gender Null

Dob Varchar() Date of birth Null

Place Varchar() Place Null

Post Varchar() Post office Null

Pin Varchar() Pin code Null

Phonenumber Int Phone number Null

email Varchar() Email address Null

Table4.3f

41
 PRODREV

5.IMPLEMENTATION

42
 PRODREV

5.1 SYSTEM IMPLEMENTATION

The SDLC has different phases to develop the product. The phases are
followed in a particular sequence. All the phases are interlinked and
each phase produces deliverable required by the next phase. Software
Development Services in India having a life cycle that can be broadly
classified into six phases:
· Requirement capture and Analysis
· Design
· Development(Coding)
· Testing
· Maintenance
Let us see what process is carried out in each of this phase.
1. Requirement Capture and Analysis – This is the first step of the
software development cycle.In this, the requirements are collected from
the clients. People involved in this phase are managers, stakeholders and
the user of course. All the requirements area ambiguously taken and
various parameters pertaining the requirements area greed.
2. Design – The prerequisite for this phase is the requirement
specification document. In this phase, the system and software design
are prepared based on the given requirements. The system design helps
in specifying hardware and software requirements and overall defines
the system architecture. In the STLC this phase is used by the testers to
create the test strategy and they confirm what and how to test.

43
 PRODREV

3.Development or coding – For this phase, the pre-requisite is the

system design document. In this phase, the work is divided into modules
and units and the actual coding is started. This is the longest phase of the
software development life cycle and requires hard-work and dedication
by the developers.
4. Testing – In this phase, the developed code is tested against all the
requirements. It is made sure that the product is in line with the
requirements and works exactly the way it is supposed to and bugs if
any are reported to the developer. This phase uses all types of functional
testing like unit testing, integration testing, system testing, acceptance
testing and also the non-functional testing.
5. Maintenance –Problems arises once the customers start using the
product. These problems need to be fixed from time to time. This is
what is covered in the maintenance phase. The service engineers oblige
the customers by solving the issue.

44
 PRODREV

6.SYSTEM TESTING

45
 PRODREV

6.1 SYSTEM TESTING

System testing is an investigation conducted to provide stakeholders
with information about the quality of the software product or service
under test. Software testing can also provide an objective, independent
view of the software to allow the business to appreciate and understand
the risks of software implementation. Test techniques include the
process of executing a program or application with the intent of finding
software bugs (errors or other defects), and verifying that the software
product is fit for use.
Software testing involves the execution of a software component or
system component to evaluate one or more properties of interest. In
general, these properties indicate the extent to which the component or
system under test:
• meets the requirements that guided its design and development,
• responds correctly to all kinds of inputs,
• performs its functions within an acceptable time,
• it is sufficiently usable,
• can be installed and run in its intended environments ,and
• Achieves the general result its stakeholder’sdesire.
6.1.1 UNIT TESTING
Unit testing is a level of software testing where individual units/
components of a software are tested. The purpose is to validate that each
unit of the software performs as designed. A unit is the smallest testable
part of any software. It usually has one or a few inputs and usually a
single output. In procedural programming, a unit may be an individual
program, function, procedure, etc. In object-oriented programming, the
46
 PRODREV

smallest unit is a method, which may belong to a base/

superclass,abstractderived/childclass.(Sometreatamoduleofanapplication
asa unit. This is to be discouraged as there will probably be many
individual units within that module.) Unit testing frameworks, drivers,
stubs, and mock/ fake objects are used to assist in unit testing.
6.1.2 INTEGRATION TESTING
Here all the units are integrated into a single module. So in our
system there are three module of the system. They are admin, employee
and user. So we integrated all the units related to admin as a module
likewise the other two modules too. Then these each module is tested. I
tested all the functions of the modules. There were several errors while
testing these modules when combined together and corrected later. Now
the entire module works properly as per the functions. The following are
the type integration testing:
6.1.2.1 TOP DOWN INTEGRATION
This method is an incremental approach to the construction of
program structure. Modules are integrated by moving downward
through the control hierarchy, beginning with the main program module.
The module subordinates to the main program module are incorporated
into the structure in either a depth first or breadth first manner.
6.1.2.2 BOTTOM UP INTEGRATION
This method begins the construction and testing with the modules
at the lowest level in the program structure. Since the modules are
integrated from the bottom up, processing required for modules
subordinate to a given level is always available and the need for stubs is
eliminated. The

47
 PRODREV

bottom up integration strategy may be implemented with the following

steps:
➢ The low-level modules are combined into clusters into clusters that
perform a specific software sub-function.
➢ A driver (i.e.) the control program for testing is written to coordinate
test case input and output.
➢ The cluster is tested.
➢ Drivers are removed and clusters are combined moving upward in the
program structure.
6.2 FUTURE ENHANCEMENT
Emotions that people have to certain objects or situations around
them are of much importance in fields of advertising and media. An
analysis of the emotions of people are evaluated through the sentiment
analysis. Now a days, everything is digitalised, so sentiment analysis
engines play a huge role in the coming future. The proposed
systemseeks to categorise the sentiment and score of the given data. Our
model mainly focuses on Amazon products but also is generalised for all
the other data too. The engine requires ASIN code as an input. It
automatically collects the review data of the product with the given
ASIN code (ASIN is unique code for each amazon product). The
collected data is then preprocessed and sent for sentiment analysis. The
system computes the sentiment scores using rule set and scoring
algorithms. The final sentiment score of the product reviews determines
the quality of the product. Our model considered the challenges that
sentiment analysis faced in the previous models like negation, emoji´s,
sentiment enhancers etc. Being a web-based-application it is easy for the

48
 PRODREV

users to interface and understand. Knowledge of the model depends on

the content available in the dictionary. So the accuracy can be enhanced
by increasing the number of words that conveys sentiment The more the
content in dictionary, the more the knowledge, the higher the accuracy.
Considering the future scope of the project we can increase the accuracy
of the model using hybrid systems. That is take the best out of two
approaches, rule based and machine learning, so that the model performs
much better. Also current model only works for English language. In
future, we can work on multilingual basis.

49
 PRODREV

7.CONCLUSION

50
 PRODREV

7.1 C0NCLUTION
The project was successfully completed within the time span
allotted. Every effort has been made to present the system in more user-
friendly manner. All the activities provide a feeling like an easy walk
over to the user who is interfacing with the system .The system model
important purposes collecting all reviews of same product from
different online shopping sites and conclude all reviews from all sites to
a single review instead of simple product rating value. This system can
be further improved to consider the above fact and update server
database accordingly.

51
 PRODREV

8.BIBLIOGRAPHY

52
 PRODREV

8.1BIBLIOGRAPHY
[1] Shriya Se et al. “AMRITA-CEN@ SAIL2015: sentiment analysis in
Indian languages”. In: International Conference on Mining Intelligence
and Knowledge Exploration. Springer. 2015, pp. 703–710.
[2] Theresa Wilson, Janyce Wiebe, and Paul Hoffmann. “Recognizing
contextual polarity in phraselevel sentiment analysis”. In: Proceedings
of human language technology conference and conference on empirical
methods in natural language processing. 2005, pp. 347–354.
[3] Rui Xia et al. “Polarity shift detection, elimination and ensemble: A
three-stage model for documentlevel sentiment analysis”. In:
Information Processing & Management 52.1 (2016), pp. 36–45.
[4] Cäcilia Zirn et al. “Fine-grained sentiment analysis with structural
features”. In: Proceedings of 5th International Joint Conference on
Natural Language Processing. 2011, pp. 336–344.
[5] KS Krishnaveni, Rohit R Pai, and Vignesh Iyer. “Faculty rating
system based on student feedbacks using sentimental analysis”. In: 2017
International Conference on Advances in Computing, Communications
and Informatics (ICACCI). IEEE. 2017, pp. 1648–1653.

53
 PRODREV

9.APPENDIX

54
 PRODREV

9.1SCREENSHORTS

55
 PRODREV

ProdRev.

Welcome to ProdRev
( ,A perfect platform to'know whats bestlo choose.....

*!::'dh!.*

r
I'

ProdRev.

Welcome to ProdRev

--
A perfec}plalform to know whals bes!10 choosa.....
1

,. '"Jh!i.*

56