Professional Documents
Culture Documents
Practical File: Amrit Kaur
Practical File: Amrit Kaur
Development of SRS
2.
document, Design document 06/01/23
for the Sentiment Analyzer
Introduction
Sentimental analysis is the act of calculating and classifying people's expressed opinions as either positive, negative,
or neutral regarding a certain event, issue, or product. Sentimental analysis' main goal is to support data-driven
choices by utilising information from social media comments, survey responses, and product evaluations. Words,
sentences, documents, traits or aspects, concepts, phrases, linkages, clauses, and implications can all be used in
sentiment analysis. Recently, sentiment analysis has received a lot of interest, particularly from text mining and
natural language processing academics. However, the accuracy of sentiment analysis has been hampered by the
severe lack of annotated datasets that are used to train models across a variety of domains. Various forms of study
have been conducted to address the problem.
Tools/Software Required: Sentiment Analysis, Machine Learning, Lexicon-based, Corpus-based, Hybrid and
Ontology
Processor:
A lot of tasks need to be accomplish and relevant skills required to successfully build this prediction system.
Various tasks are:
1. System design or architecture
2. Data sample needs to be collected via some online source or survey.
3. Data Pre-processing or cleaning
4. Building a model – implement using a specific programming language.
5. Testing
6. Report Generation
7. Front end development
8. Back end deve lopment
9. Deployment
Rule-based Systems: Involves the use of a set of manually defined rules for automated sentiment analysis.
Automatic Systems: Involves the use of machine learning techniques in order to learn from data.
Hybrid Systems: Involves a combination of rule-based and automated approaches.
Sequence Diagrams:
A sequence diagram is a Unified Modeling Language (UML) diagram that illustrates the sequence of
messages between objects in an interaction. A sequence diagram consists of a group of objects that are
represented by lifelines, and the messages that they exchange over time during the interaction .
High-level interactions between user of the system and the system, between the system and other systems,
or between subsystems (sometimes known as system sequence diagrams) .
• Used to model and visualise the logic behind a sophisticated function, operation or procedure.
• They are also used to show details of UML use case diagrams.
• Used to understand the detailed functionality of current or future systems.
• Visualise how messages and tasks move between objects or components in a system.