WEBSITE EVALUATION USING OPENION

MINING
By

Areeba Abbas 2021-GCUF-95299

Abiha Zanib 2021-GCUF-95286
BACHELOR OF SCIENCE
IN
COMPUTER SCIENCE

DEPARTMENT OF COMPUTER SCIENCE

Government College University Faisalabad

2025
Table of Contents
1. Introduction......................................................................................................................................3
1.1 Purpose...........................................................................................................................................3
1.2 Project Objective.............................................................................................................................3
1.3 Project Scope..................................................................................................................................3
2. Overall Description..........................................................................................................................3
2.1 User Classes and Characteristics.....................................................................................................4
2.2 Operating Environment...................................................................................................................4
2.3 Design and Implementation Constraints.........................................................................................4
2.4 Assumptions and Dependencies......................................................................................................4
3. External Interface Requirements....................................................................................................4
3.1 User Interfaces................................................................................................................................4
3.2 Hardware Interfaces........................................................................................................................4
3.3 Software Interfaces.........................................................................................................................5
3.4 Communications Interfaces.............................................................................................................5
4. Other Nonfunctional Requirements...............................................................................................5
4.1 Performance Requirements.............................................................................................................5
4.2 Safety Requirements.......................................................................................................................5
4.3 Security Requirements....................................................................................................................5
5. Tools & Technologies.......................................................................................................................5
5.1 Programming Languages................................................................................................................5
5.2 Databases/Data Storages.................................................................................................................5
5.3 Operating System............................................................................................................................5
6. WBS Project Diagram..................................................................................................................6
7. Analysis Model...............................................................................................................................7
7.1 Use Case Diagram..........................................................................................................................7
7.1.1Use Case Diagram to Login in System...........................................................................................8
7.3 Sequence Diagram..........................................................................................................................9
7.2 Class Diagram...............................................................................................................................10
7.4 Activity Diagram..........................................................................................................................11
7.4.1Activity Diagram for System Login.............................................................................................11
Appendix B: Check List.........................................................................................................................14
Appendix C: Supervisory Committee..................................................................................................13
Government College University Faisalabad page 3

1. Introduction
In the digital age, users frequently rely on online reviews and feedback to assess the quality of
websites, products, and services. The Website Evaluation Using Opinion Mining Web Project
leverages artificial intelligence and natural language processing (NLP) to analyze user opinions,
reviews, and ratings to provide insightful evaluations of websites. By collecting and processing
large volumes of user-generated content, this project helps in determining the overall sentiment
positive, negative, or neutral associated with a particular website.
Project Name: Website Evolution Using Opinion Mining Starting Date:

Controlling Agency: Final Date:

Prepared By: Areeba Abbas, Abiha Zanib Authorized by:

1.1 Purpose
The Website Evaluation Using Opinion Mining web project aims to analyze and assess user opinions,
feedback, and reviews to determine the overall quality, usability, and effectiveness of websites. With
the increasing reliance on digital platforms, user experience plays a crucial role in the success of
websites. This project leverages opinion mining (sentiment analysis) techniques to extract meaningful
insights from user-generated content such as reviews, comments, and ratings. The primary purpose of
this project is to help website owners, developers, and businesses understand user satisfaction and
identify areas for improvement.
1.2 Project Objective
The primary objective of the Website Evaluation Using Opinion Mining Web Project is to develop a
system that analyzes user opinions and feedback to assess website performance, usability, and overall
user satisfaction. This project leverages Natural Language Processing (NLP) and Sentiment Analysis
techniques to extract insights from user reviews, comments, and ratings across various online
platforms. It categorizes sentiments into positive, negative, or neutral, helping website owners and
developers understand user experiences and identify areas for improvement. Additionally, the project
seeks to detect key trends and patterns, such as frequent complaints or highly appreciated features, to
provide actionable insights for website optimization.
1.3 Project Scope
The Website Evaluation Using Opinion Mining Web Project aims to provide an automated and
intelligent system for analyzing user opinions and feedback to assess the quality and performance of
websites. The project leverages natural language processing (NLP) and machine learning techniques
to extract meaningful insights from user reviews, comments, and ratings. The primary scope of this
system is to collect, process, and analyze vast amounts of user-generated content from various
platforms, including social media, review sites, and feedback forms.
Government College University Faisalabad page 4

1.4 Project Limitations

While The Website Evaluation Using Opinion Mining Web Project is designed to analyze user
reviews and feedback to assess the quality of websites. However, despite its advantages, the project
has several limitations that may affect its accuracy and effectiveness. One of the primary challenges is
data accuracy and bias, as opinion mining relies on user-generated content, which can sometimes be
biased, fake, or manipulated through spam reviews.
1.5 Process Model
The Website Evaluation Using Opinion Mining Web Project is designed to analyze user feedback,
reviews, and sentiments to assess the quality and effectiveness of websites. This system utilizes
Natural Language Processing (NLP) and Machine Learning (ML) techniques to extract meaningful
insights from user opinions.

2. Overall Description
Here all the details of Overall Description
2.1 User Classes and Characteristics
The User of the proposed application is as follows.
 Admin
 User
2.2 Operating Environment
Windows and mobile operating system as well as a web server and web browser.
2.3 Design and Implementation Constraints
The application is designed using bootstrap and html/CSS and PHP.
2.4 Assumptions and Dependencies
The system cannot be run without server and sql database connectivity.

3. External Interface Requirements

EIR are types of functional requirement. They are defined below;
3.1 User Interfaces
The user interface is built with HTML/CSS and PHP. And all the web pages are user attractive and
responsive. The application can be executing of any latest google chrome as well as internet explorer.
3.2 Hardware Interfaces
The hardware requirements are as follows.
 Core 2 duo processor (at least)
 2-Gb of RAM
 150 GB of HDD.
 Government College University Faisalabad page 5
3.3 Software Interfaces
The tools used for development of the application are as follows.
 XAMPP server
 Visual Studio
 Google chrome
3.4Communications Interfaces
At the core of the app is a comprehensive dashboard, serving as a central hub where users can access an
overview of their activities and relevant information. This dashboard provides quick access to key
features and settings.

4. Other Nonfunctional Requirements

Nonfunctional Requirements (NFRs) define system attributes such as security, reliability, performance,
maintainability, scalability, and usability. They serve as constraints or restrictions on the design of
the system across the different backlogs. Also known as system qualities, nonfunctional requirements
are just as critical as functional Epics, Capabilities, Features, and Stories. They ensure the usability
and effectiveness of the entire system.
4.1 Performance Requirements
The application is tested under the controlled hardware requirements so it is found normal in and well
executed.
4.2 Safety Requirements
All the accounts are secured with Php sessions. And login accounts are provided to every client.
4.3 Security Requirements
Without login details no user can get access to the application.

5. Tools & Technologies

Tools and Technologies are defined below:
5.1 Programming Languages
 PHP (For the Development of back-end of the application)
 HTML (To Build the user interface of the application)
5.2 Databases/Data Storages
My SQL Server (To build and maintain the database for the proposed application.)
5.3 Operating System
The system is built on the workstation/ pc using the operating system Microsoft Windows.
Government College University Faisalabad page 6

6. WBS Project Diagram

In a WBS, the deliverable can be an object, a service, or an activity. By focusing on deliverables
rather than methods the what, not the how a work breakdown structure helps eliminate unnecessary
work to get the intended result.

Website Evaluation Using Opinion Mining

Admin User

Login
Login

Register

Add Data

View Data

Add User

Rate Data

View User
Comment

View Feedback
View Rating

Make Decision Send massage

Logout
Government College University Faisalabad page 7

7. Analysis Model
The analysis model for our web platform involves a comprehensive examination of user
requirements, system functionalities, and potential challenges. We begin by conducting a thorough
user analysis to understand the diverse needs and preferences of consumers and farmers who will
interact with the platform. This includes studying user behaviors, preferences, and expectations to
inform the design and functionality of the website. Simultaneously, we delve into a detailed system
analysis, identifying core features such as user authentication, product listings, secure payment
processing, and inventory management. This phase also involves assessing the scalability and
flexibility of the platform to accommodate potential future enhancements and technological
advancements. Furthermore, our analysis model considers potential challenges such as data security,
user privacy, and seamless integration with third-party services. By conducting a comprehensive
analysis, we aim to develop a web platform that not only meets the immediate needs of users but also
anticipates future trends and technological advancements, ensuring a robust and adaptive solution for
agricultural product buying and selling.

7.1 Use Case Diagram

A use case diagram is a graphical depiction of a user's possible interactions with a system. A use case
diagram shows various use cases and different types of users the system has and will often be
accompanied by other types of diagrams as well. The use cases are represented by either circles or
ellipses. A use case is a description of how a person who actually uses that process or system will
accomplish a goal. It's typically associated with software systems, but can be used in reference to any
process. For example, imagine you're a cook who has a goal of preparing a grilled cheese sandwich.
The use case would describe through a series of written steps how the cook would go about preparing
that sandwich. A use case helps you understand where errors could occur in the process and design
features to resolve those errors. Three elements that a use case must contain.
Actor: which is the user, which can be a single person or a group of people, interacting with a process
System: which is the process that's required to reach the final outcome
Goal: which is the successful user outcome.
Government College University Faisalabad page 8

7.1.1 Use Case Diagram to Login in System

Manage
Database
Register

Update

Account
Admin Setting
View
Feedback

Ratting User

Login

m m
Write
Co m
Co
nt e
me nt

View
View User

View Data
Government College University Faisalabad page 9

7.3 Sequence Diagram

A sequence diagram is a type of interaction diagram because it describes how—and in what order a
group of objects works together. These diagrams are used by software developers and business
professionals to understand requirements for a new system or to document an existing process.
Here is the proposed sequence diagram for the system login.

System User

User

Add Details

confirmation

Check

Ratting

[Accepted]

[exists]

[else] [invalid]
Government College University Faisalabad page 10

7.2 Class Diagram

A class diagram is a diagram used in designing and modeling software to describe classes and their
relationships. The diagram shows the names and attributes of the classes, connections between the
classes, and sometimes also the methods of the classes.
Here is the proposed class diagram for the system.
Admin Login
User login
User-Verification
+admin: String +User: String
:
+Admin Id: String +User Id :String
+Password: String + Password :String
+ Admin Verification + User Verification

Classes

+User
Relationships
+ admin

+User + Ratting

+Inventory +Website Evaluation

+Website Evaluation Using Opinion
Using Opinion Mining
Mining

Attributes
+User: name, Id, email,
+ Password
+Products: Id, Price,
+Descript
+supplier: id, user-id,
Government College University Faisalabad page 11

7.4 Activity Diagram

An activity diagram shows business and software processes as a progression of actions. These
actions can be carried out by people, software components or computers. Activity diagrams are used
to describe business processes and use cases as well as to document the implementation of system
processes.
7.4.1 Activity Diagram for System Login

Search
Admin

Browse

Item found item not found

View Ratting User

Details

Feedback
Government College University Faisalabad page 12

7.5 ERD
An entity relationship diagram (ERD), also known as an entity relationship model, is a graphical
representation that depicts relationships among people, objects, places, concepts or events within
an information technology (IT) system. The ERD for the proposed system is as follows.

3.6.1 ER Diagram

A-ID
Email
Name

Password
Admin

View
DB
Manage
User

System

Copy
Manage Give URL
Acc Feed
Back

Browser
Password User

Domain
Email Name Name
Enter
URL
U-id
Government College University Faisalabad page 13

7.6 Object Diagram

Web User User
0.. 1
Login_id :String
User
(id)Password
:String :String
1
User Id
:String

1
Request
Eid:Integer
Jid:Integer
Email:String
location
:String

Ratting
Rid
:Integer Result
Jid
:Integer User:
Ratting:
Loc Comment:
Government College University Faisalabad page 14
Appendix B: Check List

Check List Yes No

I. Starting/Ending Dates

II. Project Scope

III. Product modules (covering all aspects of scope)

IV. System Features (covering scope)

V. Interface Requirements

VI. Non-Functional Requirements

VII. WBS

VIII. Tools and Technologies Detail (for implementation)

IX. Plagiarism Report

Government College University Faisalabad page 15

Appendix C: Supervisory Committee

For Approval of any two Consultant Teachers

Teacher Consulted Teacher Consulted

Name: _ _. Name: _ _.

Designation: _ . Designation: _ .

Comments:_ Comments:_

_ _

_ _

_ _

_ _

Signature: _ Signature: _

---------------------------------------------------------------------
Government College University Faisalabad page 16

(For office use only)

Date:

□ Approved Group ID:

Meeting Required: Date: Time: Place:

□ Rejected

Remarks:

Project Title (if Revised):

Project Coordinator