Minor Project Presentation 4

Download as pptx, pdf, or txt
Download as pptx, pdf, or txt
You are on page 1of 12

EXPLORING CUSTOMER

SENTIMENT IN AMAZON
PRODUCT REVIEWS
System Analysis
Stakeholders: Identifying stakeholders is crucial in understanding who will
be impacted by the system and who has input into its design:
Project Managers: Oversee project timelines and deliverables.
Data Analysts: Interpret the sentiment analysis and generate insights.
Developers: Build and maintain the software application.
End-Users: Business analysts, marketing teams, or product managers who will
utilize the insights derived from the analysis.
Existing System Analysis

Research existing sentiment analysis solutions to identify:


• Current tools and technologies used for similar purposes.
• Limitations of these tools and potential areas for improvement.
• Best practices in sentiment analysis and data handling in eCommerce settings.
USE CASE
• Develop use cases to illustrate how users will interact with the system:
• Use Case 1: Data Collection
• Process: The system scrapes reviews from Amazon or retrieves them via an API.
• Outcome: A database of structured reviews ready for analysis.
• Use Case 2: Sentiment Analysis
• Process: Sentiment analysis algorithms process the collected reviews.
• Outcome: Reviews are classified and stored with sentiment scores.
• Use Case 3: Reporting and Visualization
• Process: Users generate reports and view sentiment trends through a
dashboard.
• Outcome: Accessible visual representations of sentiment data.
Requirements Gathering
• Functional Requirements: Specify what the system should do:
1.Data Extraction:
 The system must extract product reviews from Amazon using web scraping or API
integration.
 It should support multiple product categories and enable filtering by date or rating.
2.Sentiment Analysis:
 Implement NLP and machine learning techniques to classify reviews as positive,
negative, or neutral.
 Explore sentiment scoring (e.g., on a scale from -1 to 1).
3. Data Storage:
 The system must store the collected reviews, sentiment scores, and
metadata (like product ID, user date) in a database for further analysis.
4.Reporting and Visualization:
 Provide a reporting feature that enables users to generate insights on
demand.
 Design a user-friendly dashboard to visualize sentiment trends over time
and by product categories.
Non-Functional Requirements: Outline system attributes that affect performance
and usability
1.Performance:
 The system should be able to analyze sentiment for thousands of reviews in a
reasonable timeframe (e.g., under 5 seconds per batch of reviews).
2.Scalability:
 The architecture should support scaling to accommodate a growing volume of
product reviews without significant performance degradation.
3. Security:
 Ensure the system meets legal compliance regarding data collection (e.g., GDPR
or CCPA).
 Implement role-based access control for different user types.
4.Usability:
 The user interface should be intuitive and cater to users with varying levels of
technical expertise, enabling them to navigate easily and extract insights.
Technical Requirements
Data Sources
• Identify APIs from Amazon or tools for web scraping (like Scrapy).
• Consider libraries for text processing (like NLTK, SpaCy) and sentiment analysis
(like TextBlob).
Technologies
• Programming Languages: Python for back-end processing and data analysis.
• Database: Choose an appropriate database system (e.g., MySQL, PostgreSQL,
MongoDB) for storing data.
• Frameworks: Consider using web frameworks (like Flask or Django) for
developing the application interface.
• Visualization Libraries: Utilize libraries such as Matplotlib, Seaborn, or
Plotly for presenting data.
Thank You
PRESENTATION BY:
M.CHANAKYA VARMA
VU22CSCI0200029

You might also like