SAVITRIBAI PHULE PUNE UNIVERSITY

A PRILIMINARY PROJECT REPORT ON

Analyzing Sentiments in One Go

SUBMITTED TOWARDS THE

PARTIAL FULFILLMENT OF THE REQUIREMENTS OF

BACHELOR OF ENGINEERING (Computer

Engineering)
BY
Srushti Jare B150484223
Aditi Adawade B150484201
Komal Balkawade B150484205
Shweta Parge B150484259

Under The Guidance of

Prof. P. M. Gore

DEPARTMENT OF COMPUTER ENGINEERING

Padmabhooshan Vasantdada Patil Institute of
Technology, Bavdhan, Pune-21
 Padmabhooshan Vasantdada Patil Institute of Technology
DEPARTMENT OF COMPUTER ENGINEERING
CERTIFICATE

This is to certify that the Project Entitled

Analyzing Sentiments in One Go .
Submitted by
Srushti Jare B150484223
Aditi Adawade B150484201
Komal Balkawade B150484205
Shweta Parge B150484259

is a bonafide work carried out by these students under the supervision of

Prof. P. M. Gore and it is submitted towards the partial fulfillment of the
requirement of Bachelor of Engineering (Computer Engineering).

Prof. P. M. Gore Dr. B. K.Sarkar

Internal Guide H.O.D
Dept. of Computer Engg. Dept. of Computer Engg.
 Abstract

Propose system tend to concentrate on modeling user-generated review and

overall rating pairs and aim to spot linguistics aspects and aspect-level sen-
timents from review knowledge similarly on predict overall sentiments of
reviews. We tend to propose a completely unique probabilistic supervised
joint side and sentiment model (SJASM) to upset the issues in one go under-
neath a unified framework. SJASM represents every review document within
the style of opinion pairs, and might at the same time model side terms and
corresponding opinion words of the review for hidden side and sentiment de-
tection. It conjointly leverages sentimental overall ratings, which regularly
comes with on-line reviews, as superintendence knowledge, and might infer
the linguistics aspects and aspect-level sentiments that aren’t solely pur-
poseful however conjointly prognosticative of overall sentiments of reviews.
Moreover, we tend to conjointly develop economical illation methodology
for parameter estimation of SJASM supported folded Gibbs sampling. We
tend to judge SJASM extensively on real-world review knowledge, and ex-
perimental results demonstrate that the planned model outperforms seven
well-established baseline strategies for sentiment analysis tasks.
We are building a social network web site on that user post with attaching
files, thereon file topic name match with product name then suggest to user
on e-commerce web site.

PVPIT ,Department of Computer Engineering 2018-19. I

 Acknowledgments

This gives us great pleasure in presenting the preliminary project report on

”Analyzing Sentiments in One Go”.

We would like to take this opportunity to thank my project internal guide

Prof. P. M. Gore for giving me all the help and guidance I needed. I
am really grateful to them for their kind support. Their valuable suggestions
were very helpful.

We are also grateful to Dr. B. K.Sarkar, Head of Computer Engineering

Department, Padmabhooshan Vasantdada Patil Institute of Technology for
his indispensable support, suggestions.

Srushti Jare
Aditi Adawade
Komal Balkawade
Shweta Parge
(B.E. Computer Engg.)
Contents

1 Synopsis 2
1.1 Project Title . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.2 Project Option . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.3 Internal Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.4 Sponsorship and External Guide . . . . . . . . . . . . . . . . 3
1.5 Technical Keywords (As per ACM Keywords) . . . . . . . . . 3
1.6 Problem Statement . . . . . . . . . . . . . . . . . . . . . . . . 3
1.7 Abstract . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.8 Goals and Objectives . . . . . . . . . . . . . . . . . . . . . . . 4
1.9 Relevant mathematics associated with the Project . . . . . . . 5
1.10 Names of Conferences / Journals where papers can be published 5
1.11 Review of Conference/Journal Papers supporting Project idea 6
1.12 Plan of Project Execution . . . . . . . . . . . . . . . . . . . . 6

2 Technical Keywords 7
2.1 Area of Project . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.2 Technical Keywords . . . . . . . . . . . . . . . . . . . . . . . . 8

3 Introduction 9
3.1 Project Idea . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
3.2 Motivation of the Project . . . . . . . . . . . . . . . . . . . . 10
3.3 Literature Survey . . . . . . . . . . . . . . . . . . . . . . . . . 10

4 Problem Definition and scope 12

4.1 Problem Statement . . . . . . . . . . . . . . . . . . . . . . . . 13
4.1.1 Goals and objectives . . . . . . . . . . . . . . . . . . . 13
4.1.2 Statement of scope . . . . . . . . . . . . . . . . . . . . 13
4.2 Software context . . . . . . . . . . . . . . . . . . . . . . . . . 13
4.3 Major Constraints . . . . . . . . . . . . . . . . . . . . . . . . 13
4.4 Methodologies of Problem solving and efficiency issues . . . . 14
4.5 Outcome . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
4.6 Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

PVPIT ,Department of Computer Engineering 2018-19. III

 4.7 System Requirements: . . . . . . . . . . . . . . . . . . . . . . 15
4.7.1 Hardware Resources Required . . . . . . . . . . . . . . 15
4.7.2 Software Resources Required . . . . . . . . . . . . . . . 16

5 Project Plan 17
5.1 Project Estimates . . . . . . . . . . . . . . . . . . . . . . . . . 18
5.1.1 Reconciled Estimates . . . . . . . . . . . . . . . . . . . 19
5.1.2 Project Resources . . . . . . . . . . . . . . . . . . . . . 21
5.2 Risk Management w.r.t. NP Hard analysis . . . . . . . . . . . 21
5.2.1 Risk Analysis . . . . . . . . . . . . . . . . . . . . . . . 21
5.2.2 Risk probability definitions: . . . . . . . . . . . . . . . 21
5.2.3 Risk Impact definitions: . . . . . . . . . . . . . . . . . 22
5.2.4 Overview of risk mitigation, monitoring and management 22
5.3 Project Schedule . . . . . . . . . . . . . . . . . . . . . . . . . 24
5.3.1 Project task set . . . . . . . . . . . . . . . . . . . . . . 24
5.3.2 Task network . . . . . . . . . . . . . . . . . . . . . . . 24
5.3.3 Timeline Chart . . . . . . . . . . . . . . . . . . . . . . 24
5.4 Team Organization . . . . . . . . . . . . . . . . . . . . . . . . 26
5.4.1 Team structure . . . . . . . . . . . . . . . . . . . . . . 26
5.4.2 Management reporting and communication . . . . . . . 26

6 Software requirement specification 27

6.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
6.1.1 Purpose and Scope of Document . . . . . . . . . . . . 28
6.1.2 Overview of responsibilities of Developer . . . . . . . . 28
6.2 Usage Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . 28
6.2.1 Use-case . . . . . . . . . . . . . . . . . . . . . . . . . . 28
6.2.2 Use Case View . . . . . . . . . . . . . . . . . . . . . . 29
6.3 Data Model and Description . . . . . . . . . . . . . . . . . . . 29
6.3.1 Data Description . . . . . . . . . . . . . . . . . . . . . 29
6.3.2 Data objects and Relationships . . . . . . . . . . . . . 30
6.4 Functional Model and Description . . . . . . . . . . . . . . . . 30
6.5 Non-functional Requirement . . . . . . . . . . . . . . . . . . . 30
6.5.1 Performance Requirement : . . . . . . . . . . . . . . . 30
6.5.2 Safety & Security Requirement : . . . . . . . . . . . . . 30
6.6 UML Diagrams: . . . . . . . . . . . . . . . . . . . . . . . . . . 30
6.6.1 Data Flow Diagram . . . . . . . . . . . . . . . . . . . . 30
6.6.2 Activity Diagram: . . . . . . . . . . . . . . . . . . . . . 33
6.6.3 State Diagram: . . . . . . . . . . . . . . . . . . . . . . 34
6.6.4 Design Constraints . . . . . . . . . . . . . . . . . . . . 36
6.6.5 Software Interface Description . . . . . . . . . . . . . . 36

PVPIT ,Department of Computer Engineering 2018-19. IV

7 Detailed Design Document using Appendix A and B 37
7.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
7.2 Architectural Design . . . . . . . . . . . . . . . . . . . . . . . 38
7.3 Data design . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
7.3.1 Internal software data structure . . . . . . . . . . . . . 38
7.3.2 Global data structure . . . . . . . . . . . . . . . . . . . 38
7.3.3 Temporary data structure . . . . . . . . . . . . . . . . 38
7.3.4 Database description . . . . . . . . . . . . . . . . . . . 38
7.4 Component Design . . . . . . . . . . . . . . . . . . . . . . . . 38
7.4.1 Class Diagram . . . . . . . . . . . . . . . . . . . . . . . 40

8 Summary and Conclusion 41

9 References 43

10 Project Planner 45
List of Figures

5.1 Waterfall Model . . . . . . . . . . . . . . . . . . . . . . . . . . 18

5.2 NP Hard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
5.3 Task network . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
5.4 Timeline Chart . . . . . . . . . . . . . . . . . . . . . . . . . . 25

6.1 Use case diagram . . . . . . . . . . . . . . . . . . . . . . . . . 29

6.2 DFD0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
6.3 DFD1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
6.4 DFD2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
6.5 Activity diagram . . . . . . . . . . . . . . . . . . . . . . . . . 33
6.6 State transition diagram . . . . . . . . . . . . . . . . . . . . . 35

7.1 Architecture diagram . . . . . . . . . . . . . . . . . . . . . . . 39

7.2 Class Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
List of Tables

5.1 Cost Estimation . . . . . . . . . . . . . . . . . . . . . . . . . . 20

5.2 Risk Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
5.3 Risk Probability definitions . . . . . . . . . . . . . . . . . . . 22
5.4 Risk Impact definitions . . . . . . . . . . . . . . . . . . . . . 22

PVPIT ,Department of Computer Engineering 2018-19. 1

CHAPTER 1
SYNOPSIS
1.1 Project Title
Analyzing Sentiments in One Go: A Supervised Joint Topic Modeling Ap-
proach

1.2 Project Option

Internal Project

1.3 Internal Guide

Prof. P. M. Gore

1.4 Sponsorship and External Guide

No

1.5 Technical Keywords (As per ACM Key-

words)
1. Sentiment analysis

2. Aspect-based sentiment analysis

3. Probabilistic topic model

4. Supervised joint topic model.

1.6 Problem Statement

To generate report on product review system on E-commerce using Senti-
mental analysis on user reviews linked with social media.

PVPIT ,Department of Computer Engineering 2018-19. 3

1.7 Abstract
• Propose system tend to concentrate on modeling user-generated review
and overall rating pairs and aim to spot linguistics aspects and aspect-
level sentiments from review knowledge similarly on predict overall sen-
timents of reviews. We tend to propose a completely unique probabilis-
tic supervised joint side and sentiment model (SJASM) to upset the
issues in one go underneath a unified framework. SJASM represents
every review document within the style of opinion pairs, and might at
the same time model side terms and corresponding opinion words of the
review for hidden side and sentiment detection. It conjointly leverages
sentimental overall ratings, which regularly comes with on-line reviews,
as superintendence knowledge, and might infer the linguistics aspects
and aspect-level sentiments that aren’t solely purposeful however con-
jointly prognosticative of overall sentiments of reviews. Moreover, we
tend to conjointly develop economical illation methodology for parame-
ter estimation of SJASM supported folded Gibbs sampling. We tend to
judge SJASM extensively on real-world review knowledge, and experi-
mental results demonstrate that the planned model outperforms seven
well-established baseline strategies for sentiment analysis tasks.
We are building a social network web site on that user post with at-
taching files, thereon file topic name match with product name then
suggest to user on e-commerce web site.

1.8 Goals and Objectives

• Aggregation and contradiction analysis

• To produce Efficient and reliable system interaction

• Make proper identification of Product review

• To provide trusted review in E-commerce

• To help produce more accurate results of Sentimental Analysis

PVPIT ,Department of Computer Engineering 2018-19. 4

1.9 Relevant mathematics associated with the
Project
Let S be the Whole system S= {I,P,O}
I-input
P-procedure
O-output
Input( I)
I={No of user ,reviews, likes, dislikes , total ,trusted reviews}
Where,
Users −→ upload +ve, - ve review,
Trusted review 7−→ Friend circles recommended review
Procedure (P),
P={I , LDA algorithm, Sentiment Analysis Algorithm, suggestion ,total re-
view count} For LDA Algorithm :
Input: words w documents d Where,
- w be the corpus of words.
- d is the set of documents.
- n be the number of words.
- k be the number of words in the document.
- α and β are LDA constants.
Output: topic assignments z and counts n(d,k) , n(k,w) and nk .
Where,
n(d,k) the number of words assigned to topic k in document d.
n(k,w) the number of times word w is assigned to topic k.

Output(O)-
O={effective reviews ,total count, Search history}

1.10 Names of Conferences / Journals where

papers can be published
• International Journal of Advance Engineering and Research Develop-
ment (IJAERD)
• International Journal of Advance Research in Engineering, Science Tech-
nology (IJAREST)
• International Journal of Engineering Research and Technology (IJERT)

PVPIT ,Department of Computer Engineering 2018-19. 5

 • Indian Journal of Computer Science and Engineering (IJCSE)

1.11 Review of Conference/Journal Papers sup-

porting Project idea
Not Applied.

1.12 Plan of Project Execution

NO TASK DURATION START END

(Days) DATE DATE
1 Group Formation 4 21-6-18 26-6-18
2 Decide Area 4 26-6-18 28-6-18
Of Interest
3 Search Topic 5 28-6-18 6-7-18
4 Topic Selection 5 6-7-18 16-7-18
5 Topic Selection 5 16-7-18 22-7-18
6 Search Related 12 22-7-18 12-8-18
Information
7 Understanding 7 12-8-18 20-8-18
Concept
8 Search Essential 6 20-8-18 31-8-18
Document(IEEE and
White Paper,)
Software)
9 Problem Definition 2 31-8-18 8-9-18
10 Literature Survey 5 8-9-18 18-9-18
11 SRS 14 18-9-18 20-9-18
12 Project Planning 2 20-9-18 30-9-18
13 Modeling and design 10 30-9-18 2-10-18
14 Technical Specification 2 30-9-18 2-10-18
15 PPT 6 2-10-18 5-10-18
 CHAPTER 2
TECHNICAL KEYWORDS
2.1 Area of Project
Data mining

2.2 Technical Keywords

1. Sentiment analysis

2. Aspect-based sentiment analysis

3. Probabilistic topic model

4. Supervised joint topic model.

 CHAPTER 3
INTRODUCTION
3.1 Project Idea
Previously all the reviews and ratings which is generated by the user and
main purpose is to analyze semantic aspects and aspect level sentiments
from review data as well as to predict overall sentiments of reviews.All the
time it is necessary to analyze and identify review. Sometime it become more
fuzzy. To overcome by this issue we introduce SJASM.by using that Trusted
review given by users social media friend and recommend user according to
users search topic modeling, with According to user post topic name matched
with product name then recommend to user.

3.2 Motivation of the Project

Our motivation is whatever the drawbacks of existing system , we need to
overcome with problem . Combine The producers perspective, the societies
perspective and collect the reviews from that to help user bye product. Ex-
isting system does not provide the trusted review (friend circle)which is con-
nected by social media. Propose system provide trusted review and count
for recommended review for the product.

3.3 Literature Survey

PVPIT ,Department of Computer Engineering 2018-19. 11
 CHAPTER 4
PROBLEM DEFINITION AND
SCOPE
4.1 Problem Statement
To generate report on product review system on E-commerce using Senti-
mental analysis on user reviews linked with social media.

4.1.1 Goals and objectives

• To help produce more accurate results of Sentimental Analysis

• aggregation and contradiction analysis

• To produce Efficient and reliable system interaction

• Make proper identification of Product review

• To provide trusted review in E-commerce

4.1.2 Statement of scope

• System Can be used in current E-commerce system to provide better
guidelines for online consumers and Byers

4.2 Software context

• We require software’s like Eclipse, Xamp along with which we use the
MySQL database for storage and used web browsers for that we used
Apache tomcat Servers

4.3 Major Constraints

• Apache server

• Java jdk 1.8

• Mysql

PVPIT ,Department of Computer Engineering 2018-19. 13

4.4 Methodologies of Problem solving and ef-
ficiency issues
1. Requirement gathering and analysis: In this step of waterfall we iden-
tify what are various requirements are need for our project such are
software and hardware required, database, and interfaces.

2. In this system design phase we design the system which is easily under-
stood for end user i.e. user friendly. We design some UML diagrams
and data flow diagram to understand the system flow and system mod-
ule and sequence of execution.

3. Implementation: In implementation phase of our project we have im-

plemented various module required of successfully getting expected out-
come at the different module levels. With inputs from system design,
the system is first developed in small programs called units, which are
integrated in the next phase. Each unit is developed and tested for its
functionality which is referred to as Unit Testing.

4. Testing: The different test cases are performed to test whether the
project module are giving expected outcome in assumed time. All
the units developed in the implementation phase are integrated into a
system after testing of each unit. Post integration the entire system is
tested for any faults and failures.

5. Deployment of System: Once the functional and non-functional testing

is done, the product is deployed in the customer environment or released
into the market.

6. Maintenance: There are some issues which come up in the client en-
vironment. To fix those issues patches are released. Also to enhance
the product some better versions are released. Maintenance is done to
deliver these changes in the customer environment. All these phases
are cascaded to each other in which progress is seen as flowing steadily
downwards like a waterfall through the phases. The next phase is
started only after the defined set of goals are achieved for previous
phase and it is signed off, so the name ”Waterfall Model”. In this
model phases do not overlap.

PVPIT ,Department of Computer Engineering 2018-19. 14

4.5 Outcome
• On social network web site user post with attaching file by mistreat-
ment file topic modeling set. If topic name match with product name.
Then system advocate to user on e-commerce web site. Or if user post
while not attaching files then thereon post through word embedding
topic get match and advocate to user on E-commerce.

• Sentiment analysis is assessed into positive, negative, all, sure compo-

nents, even review outline like:- positive review with count, negative
review with count, all with count, sure with count. In sure review is
given by users social media friend.

4.6 Applications
• The main applications and challenges of one of the hottest research
areas in computer science.

• The most common application of sentiment analysis is in the area of

reviews of consumer products and services.

• There are many websites that provide automated summaries of reviews

about products and about their specific aspects

4.7 System Requirements:

4.7.1 Hardware Resources Required
1. Hardware : Intel core

2. Speed : 2.80 GHz

3. RAM : 1GB

4. Hard Disk : 20 GB

5. Key Board : Standard Windows Keyboard

6. Mouse : Two or Three Button Mouse

7. Monitor : 15 VGA color

PVPIT ,Department of Computer Engineering 2018-19. 15

4.7.2 Software Resources Required
1. Operating System : Windows 7

2. Technology : Java and J2EE

3. Web Technologies : JSP, JavaScript, CSS

4. IDE : Eclipse

5. Web Server : Tomcat

6. Database : My SQL

7. Java Version : J2SDK1.7

 CHAPTER 5
PROJECT PLAN
5.1 Project Estimates

Figure 5.1: Waterfall Model

1. Requirement gathering and analysis:

In this step of waterfall we identify what are various requirements are need
for our project such are software and hardware required, database, and in-
terfaces.

2. System Design:
In this system design phase we design the system which is easily understood
for end user i.e. user friendly. We design some UML diagrams and data flow
diagram to understand the system flow and system module and sequence of
execution.

3. Implementation:

PVPIT ,Department of Computer Engineering 2018-19. 18

In implementation phase of our project we have implemented various mod-
ule required of successfully getting expected outcome at the different module
levels. With inputs from system design, the system is first developed in small
programs called units, which are integrated in the next phase. Each unit is
developed and tested for its functionality which is referred to as Unit Testing.

4. Testing:
The different test cases are performed to test whether the project module
are giving expected outcome in assumed time. All the units developed in the
implementation phase are integrated into a system after testing of each unit.
Post integration the entire system is tested for any faults and failures.

5. Deployment of System:
Once the functional and nonfunctional testing is done, the product is de-
ployed in the customer environment or released into the market.

6. Maintenance:
There are some issues which come up in the client environment. To fix those
issues patches are released. Also to enhance the product some better versions
are released. Maintenance is done to deliver these changes in the customer
environment.
All these phases are cascaded to each other in which progress is seen as flow-
ing steadily downwards like a waterfall through the phases. The next phase
is started only after the defined set of goals are achieved for previous phase
and it is signed off, so the name ”Waterfall Model”. In this model phases do
not overlap.

5.1.1 Reconciled Estimates

5.1.1.1 Cost Estimate
COCOMO MODEL
The project cost can be found using any one of the model.

• COCOMO-1 Model

• COCOMO-2 Model

1. Model -1: The basic COCOMO model computes software development

efforts as a function of program size expressed in estimated lines of
code.

PVPIT ,Department of Computer Engineering 2018-19. 19

 Software A(b) B(b) C(b) D(b)
Project
Organic 2.4 1.05 2.5 0.38
Semi-detached 3.0 1.22 2.5 0.35
Embedded 3.6 1.20 2.5 0.32

Table 5.1: Cost Estimation

2. Model-2: The intermediate COCOMO model computes software devel-

opment efforts as a function of program size and a set of cost drivers
that include subjective assessment of the product, hardware, personnel,
project attributes

3. Model-3: The advanced COCOMO model incorporates all character-

istics of the intermediate version with a assessment of the cost drivers
impact on each step of the software engineering process. Following is
the basic COCOMO -2 model.

The basic COCOMO -2 model equations take form:

E=A(b)KLOCB(b)
D=C(b)ED(b)
Where E is the effort applied in person months. D is development time
in chronological month. KLOC is estimated number of delivered lines of
code for the project. This project can be classified as Semidetached software
project. The rough estimate of number of lines of this project is 9.072k.
Applying the above formula E=3.0*(9.072)1.22 = 44.20 person- months
D=2.5* 44.35 = 9.40 months
Hence according COCOMO -2 model the time required for completion of the
project is 9 ( 9.40) months.

Cost of Project: Equation for calculation of cost of project using

COCOMO - 2 model is:
C = D * Cp
Where,
C = Cost of project
D = Duration in month
Cp= Cost incurred per person-month, Cp=Rs.5000/- (per person-month)
(approx.)
C = 9 * 5000 = 45000/-
Hence according COCOMO - 2 model the cost of project is 45000/-(approx.)

PVPIT ,Department of Computer Engineering 2018-19. 20

5.1.1.2 Time Estimates
Approximately 9 months.

5.1.2 Project Resources

Windows , eclipse IDE, 2.93 GHZ CPU speed, 8 GB RAM, High speed
internet connection.

5.2 Risk Management w.r.t. NP Hard anal-

ysis
Np Hard:
We propose to exploit semantic attributes for image search re-ranking. Based
on the classifiers for all the predefined attributes, each image is represented
by an attribute feature consisting of the responses from these classifiers.
A hyper-graph is then used to model the relationship between images by
integrating low-level visual features and attribute features.
Since here P = NP so in initial stage our project is in Np-hard state

Figure 5.2: NP Hard

5.2.1 Risk Analysis

The risks for the Project can be analyzed within the constraints of time and
quality.

5.2.2 Risk probability definitions:

PVPIT ,Department of Computer Engineering 2018-19. 21

 Impact
ID Risk Description Probability
Schedule Quality Overall
1 Correctness Low Low High Low
2 Availability High Low High High

Table 5.2: Risk Table

Probability Value Description

High Probability of occurrence is > 75%
Medium Probability of occurrence is 26 − 75%
Low Probability of occurrence is < 25%

Table 5.3: Risk Probability definitions

5.2.3 Risk Impact definitions:

Impact Value Description

Very high > 10% Schedule impact or Unacceptable quality
High 5 − 10% Schedule impact or Some parts of the project have
low quality
Medium < 5% Schedule impact or Barely noticeable degradation
in quality Low Impact on schedule or Quality can
be incorporated

Table 5.4: Risk Impact definitions

5.2.4 Overview of risk mitigation, monitoring and man-

agement
Following are the details for each risk.

PVPIT ,Department of Computer Engineering 2018-19. 22

Risk ID 1
Risk Description Third party access
Category Networking Environment
Source Internet.
Probability High
Impact High
Response Mitigate
Strategy Break security
Risk Status Occurred

Risk ID 2
Risk Description User can make fake profle
Category Requirements
Source Software Design Specification documentation review.
Probability Low
Impact High
Response Mitigate
Strategy Better testing will resolve this issue.
Risk Status Identified

PVPIT ,Department of Computer Engineering 2018-19. 23

 Risk ID 3
Risk Description Server crash
Category Technology
Source This was identified during early development and
testing.
Probability Low
Impact Very High
Response Accept
Strategy Example Running Service Registry behind proxy
balancer
Risk Status Identified

5.3 Project Schedule

5.3.1 Project task set
Major Tasks in the Project stages are:
• Task 1: Correctness.

• Task 2: Availability.

• Task 3: Integrity.

5.3.2 Task network

Project tasks and their dependencies are noted in this diagrammatic form.

5.3.3 Timeline Chart

A project timeline chart is presented. This may include a time line for the
entire project. Above points should be covered in Project Planner as Annex
C and you can mention here Please refer Annex C for the planner

PVPIT ,Department of Computer Engineering 2018-19. 24

 Figure 5.3: Task network

Figure 5.4: Timeline Chart

PVPIT ,Department of Computer Engineering 2018-19. 25

5.4 Team Organization
Team consists of only one member and proper planning mechanism is used
and roles are defined.

5.4.1 Team structure

The team structure for the project is identified. Roles are defined.

Sr. No. Member Responsibilities

1 Srushti Jare Project analysis,development and design
2 Aditi Adawade Requirement gathering And Development
3 Komal Balkawade Testing and design
4 Shweta Parge Testing and requirement gathering

5.4.2 Management reporting and communication

Well planning mechanisms are used for progress reporting and inter/intra
team communication are identified as per requirements of the project.
 CHAPTER 6
SOFTWARE REQUIREMENT
SPECIFICATION
6.1 Introduction
6.1.1 Purpose and Scope of Document
System can be used in current E-commerce system to provide better guide-
lines for online consumers and Buyers.

6.1.2 Overview of responsibilities of Developer

1. To have understanding of the problem statement.

2. To know what are the hardware and software requirements of proposed

system.

3. To have understanding of proposed system.

4. To do planing various activities with the help of planner.

5. Designing,programming,testing etc

6.2 Usage Scenario

6.2.1 Use-case
All use-cases for the software are presented. Description of all main use cases
using use case template is to be provided.

PVPIT ,Department of Computer Engineering 2018-19. 28

6.2.2 Use Case View
Use Case Diagram. Example is given below

Figure 6.1: Use case diagram

6.3 Data Model and Description

6.3.1 Data Description
Data streams will be processed and analyzed by framework and Apache . The
real time queue is used internally by Apache. Processing items are internally
generated and processed By regretting two modules.

PVPIT ,Department of Computer Engineering 2018-19. 29

6.3.2 Data objects and Relationships
Data streams are given to framework which will classify that data and then
this data is given to Apache storm for processing an analysis purpose, so this
is how this two modules are connected.

6.4 Functional Model and Description

Data streams will be processed and analyzed by framework and Apache . The
real time queue is used internally by Apache. Processing items are internally
generated and processed By regretting two modules.

6.5 Non-functional Requirement

6.5.1 Performance Requirement :
• Every module of the system should work efficiently.

• The system should perform fast in all weather conditions.

6.5.2 Safety & Security Requirement :

The java application will not affect other applications on user’s system.

6.6 UML Diagrams:

6.6.1 Data Flow Diagram
6.6.1.1 Level 0 Data Flow Diagram

Figure 6.2: DFD0

PVPIT ,Department of Computer Engineering 2018-19. 30

6.6.1.2 Level 1 Data Flow Diagram

Figure 6.3: DFD1

PVPIT ,Department of Computer Engineering 2018-19. 31

6.6.1.3 Level 2 Data Flow Diagram

Figure 6.4: DFD2

PVPIT ,Department of Computer Engineering 2018-19. 32

6.6.2 Activity Diagram:
• The Activity diagram represents the steps taken.

Figure 6.5: Activity diagram

PVPIT ,Department of Computer Engineering 2018-19. 33

6.6.3 State Diagram:
State transition diagrams have been used right from the beginning in object-
oriented modeling. The basic idea is to define a machine that has a number
of states (hence the term finite state machine). The machine receives events
from the outside world, and each event can cause the machine to transition
from one state to another. For an example, take a look at given figure5. Here
the machine is a bottle in a bottling plant. It begins in the empty state. In
that state it can receive squirt events. If the squirt event causes the bottle
to become full, then it transitions to the full state, otherwise it stays in the
empty state (indicated by the transition back to its own state). When in the
full state the cap event will cause it to transition to the sealed state. The
diagram indicates that a full bottle does not receive squirt events, and that
an empty bottle does not receive cap events. Thus you can get a good sense
of what events should occur, and what effect they can have on the object.

PVPIT ,Department of Computer Engineering 2018-19. 34

 Figure 6.6: State transition diagram

PVPIT ,Department of Computer Engineering 2018-19. 35

6.6.4 Design Constraints
Apache tomcat and database connectivity.

6.6.5 Software Interface Description

The software interface to the outside world is very good and user friendly
for analyzed Data The requirements for interfaces are Windows XP/7,8 GB
RAM etc.
 CHAPTER 7
DETAILED DESIGN DOCUMENT
USING APPENDIX A AND B
7.1 Introduction
This document specifies the design that is used to solve the problem of Prod-
uct.

7.2 Architectural Design

A description of the program architecture is presented. Subsystem design or
Block diagram,Package Diagram,Deployment diagram with description is to
be presented.

7.3 Data design

A description of all data structures including internal, global, and temporary
data structures, database design (tables), file formats.

7.3.1 Internal software data structure

Data structures that are passed among components the software are de-
scribed.

7.3.2 Global data structure

Data structured that are available to major portions of the architecture are
described.

7.3.3 Temporary data structure

Files created for interim use are described.

7.3.4 Database description

Database(s) / Files created/used as part of the application is(are) described.

7.4 Component Design

Class diagrams, Interaction Diagrams, Algorithms. Description of each com-
ponent description required.

PVPIT ,Department of Computer Engineering 2018-19. 38

 Figure 7.1: Architecture diagram

PVPIT ,Department of Computer Engineering 2018-19. 39

7.4.1 Class Diagram

Figure 7.2: Class Diagram

 CHAPTER 8
SUMMARY AND CONCLUSION
The Web has dramatically changed the way that people express their views
and opinions. They can now post reviews of products at merchant sites
and express their views on almost anything in Internet forums, discussion
groups, and blogs, which are collectively called the user-generated content.
This online word of-mouth behavior represents new and measurable sources
of information with many practical applications. We develop supervised joint
side and sentiment model(SJASM) to investigate overall and aspect-level sen-
timents for sentiments that aren’t solely meaty however conjointly prognos-
ticative of overall sentiments of the review documents. We tend to conducted
experiments exploitation in public obtainable real-world review knowledge,
and extensively compared SJASM with seven well-established representative
baseline ways. For linguistics side detection and aspect-level sentiment iden-
tification issues we tend to conclude that in our system we tend to square
measure connecting social media and e-commerce website then advocate to
user in line with their topic modeling. By matching topic name and mer-
chandise name. Topic fetch by users attaching file or users post. Admin
add post then advocate on e-commerce website. Sentiment analysis classi-
fied as positive , negative, all, trustworthy review. Count of review conjointly
outlines.
CHAPTER 9
REFERENCES
[ 1 ] B. Liu, Sentiment analysis and opinion mining, Synthesis Lectures on
Human Language Technologies, vol. 5, no. 1, pp. 1167, May 2012.

[ 2 ] B. Pang, L. Lee, and S. Vaithyanathan, Thumbs up?: sentiment classi-

fication using machine learning techniques, in Proceedings of the ACL-
02 conference on Empirical methods in natural language processing -
Volume 10, ser. EMNLP02. Stroudsburg, PA, USA: Association for
Computational Linguistics, 2002, pp. 7986.

[ 3 ] V. Ng, S. Das gupta, and S. M. N. Arifin, Examining the role of

linguistic knowledge sources in the automatic identification and clas-
sification of reviews, in Proceedings of the COLING/ACL on Main
Conference Poster Sessions, ser. COLING-ACL 06. Stroudsburg,PA,
USA: Association for Computational Linguistics, 2006,pp. 611618.

[ 4 ] J. Zhao, K. Liu, and G. Wang, Adding redundant features for crfs-

based sentence sentiment classification, in Proceedings of the Confer-
ence on Empirical Methods in Natural Language Processing, ser.EMNLP
08. Stroudsburg, PA, USA: Association for Computational Linguistics,
2008, pp. 117126.

[ 5 ] P. Melville, W. Gryc, and R. D. Lawrence, Sentiment analysis ofblogs

by combining lexical knowledge with text classification, in Proceedings
of the 15th ACM SIGKDD International Conference on Knowledge
Discovery and Data Mining, ser. KDD09. New York,NY, USA: ACM,
2009, pp. 12751284.

[ 6 ] A. L. Maas, R. E. Daly, P. T. Pham, D. Huang, A. Y. Ng, and C. Potts,

Learning word vectors for sentiment analysis, in Proceedings of the
49th Annual Meeting of the Association for Computational Linguistics:
Human Language Technologies - Volume 1, ser. HLT11.Stroudsburg,
PA, USA: Association for Computational Linguistics,2011, pp. 142150.
 CHAPTER 10
PROJECT PLANNER
NO TASK DURATION START END
(Days) DATE DATE
1 Group Formation 4 21-6-18 26-6-18
2 Decide Area 4 26-6-18 28-6-18
Of Interest
3 Search Topic 5 28-6-18 6-7-18
4 Topic Selection 5 6-7-18 16-7-18
5 Topic Selection 5 16-7-18 22-7-18
6 Search Related 12 22-7-18 12-8-18
Information
7 Understanding 7 12-8-18 20-8-18
Concept
8 Search Essential 6 20-8-18 31-8-18
Document(IEEE and
White Paper,)
Software)
9 Problem Definition 2 31-8-18 8-9-18
10 Literature Survey 5 8-9-18 18-9-18
11 SRS 14 18-9-18 20-9-18
12 Project Planning 2 20-9-18 30-9-18
13 Modeling and design 10 30-9-18 2-10-18
14 Technical Specification 2 30-9-18 2-10-18
15 PPT 6 2-10-18 5-10-18

PVPIT ,Department of Computer Engineering 2018-19. 46