CROWDSOURCING

Project Submitted to
KAVAYITRI BAHINABAI CHAUDHARI NORTH MAHARASHTRA
UNIVERSITY,JALGAON
In fulfillment of requirement for the award of degree of
BACHELOR OF ENGINEERING
Under the
Faculty of Engineering and Technology
In the discipline
Computer Engineering

By
Nayan S. Patil
Puja M. Badhe
Shubham D. Mahale
Monika V. More
Narendra P. Marathe
B.E. Computer
Guide
Mr. Rahul Gaikwad
Assistant Professor

Department of Computer Engineering

Godavari Foundation’s
Godavari College of Engineering, Jalgaon
(NAAC Accredited)
(An affiliated to Kavayitri Bahinabai Chaudhari North Maharashtra University,
Jalgaon)
Year 2019-2020
 Godavari Foundation’s
Godavari College of Engineering, Jalgaon
(An affiliated to Kavayitri Bahinabai Chaudhari North Maharashtra University,
Jalgaon)

CERTIFICATE

This is to certify that the Project titled, " CrowdSourcing" submitted by Nayan S.
Patil, Puja M. Badhe, Shubham D. Mahale, Monika V. More, Narendra P. Marathe.
In fulfillment of the degree of BACHELORS OF ENGINEERING in Department of
Computer Engineering, Godavari College of Engineering, Kavayitri Bahinabai Chaud-
hari North Maharashtra University, Jalgaon is a bonafide record of work carried out
by his/her in the Department of Computer Engineering, Kavayitri Bahinabai Chaud-
hari North Maharashtra University, Jalgaon under my guidance and supervision. In my
opinion this work has attained the standard fulfilling the requirements of the regulations
of the University.

Date:
Place:Jalgaon

Mr. Rahul Gaikwad Mr. Pramodgiri B. Gosavi

GUIDE H.O.D.

Dr. V. H. PATIL
PRINCIPAL
Godavari Foundation’s
Godavari College of Engineering, Jalgaon
 DECLARATION / UNDERTAKING

We hereby declare that the work presented in this Project "CrowdSourcing" was carried
out by us under the supervision of guide from July-2019 to May-2020.
This Work or any part of this work is based on original research and has not been sub-
mitted by us to any University/Institution for the award of any degree.

Date:
Place: Jalgaon

Nayan S. Patil (Roll No.13)

Puja M. Badhe (Roll No.01)
Shubham D. Mahale (Roll No.09)
Monika V. More (Roll No.10)
Narendra P. Marathe (Roll No.22)
 ACKNOWLEDGEMENT

We consider ourself to be fortunate to get this opportunity to be part of a Project

Report on in CrowdSourcing We are sincerely grateful to Mr. Rahul Gaikwad (Guide)
for his invaluable guidance, motivation and support at all stages and creating a flexible
and enjoyable environment to work in.

Special thanks to Mr. PRAMODGIRI B. GOSAVI (Head of Computer Engineer-

ing) for the support and help us in completing this Project successfully.

Last but not least; we are thankful to the God, my dearly beloved Parents, all Faculty
Members, my Friends and all who directly or indirectly supported for completion.̇..

Nayan S. Patil (Roll No.13)

Puja M. Badhe (Roll No.01)
Shubham D. Mahale (Roll No.09)
Monika V. More (Roll No. 10)
Nrendra P. Marathe (Roll No. 22)
Contents

List of Figures iv

Abstract 1

1 INTRODUCTION 2
1.1 Motivation of Project . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

2 PROBLEM IDENTIFICATION AND PROJECT OBJECTIVE 4

2.1 Problem Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.2 Scope of the Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.3 Project Objective . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

3 LITERATURE REVIEW 6
3.1 Existing System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
3.2 Proposed System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
3.3 Feasibility Study . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

4 ANALYSIS 9
4.1 Software requirement specification . . . . . . . . . . . . . . . . . . . . 9
4.1.1 Purpose and Scope of Document . . . . . . . . . . . . . . . . . 9
4.1.2 Overview of responsibilities of Developer . . . . . . . . . . . . 9
4.2 System requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
4.2.1 Hardware Requirment . . . . . . . . . . . . . . . . . . . . . . 10
4.2.2 Software Requirements . . . . . . . . . . . . . . . . . . . . . . 10
4.3 Functional Requirement . . . . . . . . . . . . . . . . . . . . . . . . . . 10

i
 4.3.1 Performance Requirement . . . . . . . . . . . . . . . . . . . . 10
4.3.2 Safety Requirement . . . . . . . . . . . . . . . . . . . . . . . . 10
4.3.3 Security Requirement . . . . . . . . . . . . . . . . . . . . . . . 11
4.4 Non-Functional Requirement . . . . . . . . . . . . . . . . . . . . . . . 11
4.4.1 Performance Requirement . . . . . . . . . . . . . . . . . . . . 11
4.4.2 Safety Requirement . . . . . . . . . . . . . . . . . . . . . . . . 11
4.4.3 Security Requirement . . . . . . . . . . . . . . . . . . . . . . . 11
4.4.4 Software Quality Attributes . . . . . . . . . . . . . . . . . . . . 11
4.5 Software Interface Description . . . . . . . . . . . . . . . . . . . . . . 12
4.5.1 What is Java . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

5 DESIGN 16
5.1 System Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
5.1.1 Project Idea . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
5.1.2 Project Concept . . . . . . . . . . . . . . . . . . . . . . . . . . 17
5.2 System Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
5.3 Data Flow Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
5.4 UML Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
5.4.1 Activity Diagram . . . . . . . . . . . . . . . . . . . . . . . . . 19
5.4.2 Use Case Diagram . . . . . . . . . . . . . . . . . . . . . . . . 20
5.4.3 Package Diagram . . . . . . . . . . . . . . . . . . . . . . . . . 21
5.4.4 Class Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . 22
5.4.5 Sequence Diagram . . . . . . . . . . . . . . . . . . . . . . . . 23

6 CODING 24
6.1 Front-End Languages . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
6.1.1 Java . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
6.1.2 HTML . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
6.1.3 CSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
6.1.4 Apache Tomcat . . . . . . . . . . . . . . . . . . . . . . . . . . 25

ii
7 TESTING 26
7.1 Type of Testing Used . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
7.2 Test Cases and Test Results . . . . . . . . . . . . . . . . . . . . . . . . 29

8 CONCLUSION AND FUTURE WORK 32

8.1 Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
8.2 Future Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
bibliography . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

iii
List of Figures

4.1 Features of Java . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

5.1 System Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

5.2 Level 0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
5.3 Level 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
5.4 Level 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
5.5 Activity Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
5.6 Use Case Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
5.7 Package Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
5.8 Class Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
5.9 Sequence Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

7.1 Test Case :1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

7.2 Test Case :2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
7.3 Test Case :3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
7.4 Test Case :4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

iv
 Abstract

CrowdSourcing is a platform which may contain opinions, thoughts, facts and other in-
formation. Within it, many and various communities are originated by users with com-
mon interests, or with similar ways to feel part of the community. This paper presents
a possible combined approach between Social Network Analysis and Sentiment Anal-
ysis. In particular, we have tried to associate a sentiment to the nodes of the graphs
showing the social connec- tions, and this may highlight the potential correlations. The
idea behind it is that, on the one hand, the network topology can contextualize and then,
in part, unmask some incorrect results of the Sentiment Analysis; on the other hand, the
polarity of the feeling on the network can highlight the role of semantic connections
in the hierarchy of the communities that are present in the network. In this work, we
illustrate the approach to the issue, together with the system architecture and, then, we
discuss our first results.
Chapter 1

INTRODUCTION

Crowdsourcing is one of the most widely studied applications of Natural Language Pro-
cessing (NLP) and Machine Learning (ML). This field has grown tremendously with the
advent of the Web 2.0. The Internet has provided a platform for people to express their
views, emotions and senti- ments towards products, people and life in general. Thus, the
Internet is now a vast resource of opinion rich textual data. The goal of crowdsourcing
is to harness this data in order to obtain important information regarding public opinion,
that would help make smarter business decisions, political campaigns and better prod-
uct consumption. Sentiment Analysis focuses on identifying whether a given piece of
text is subjective or objective and if it is subjective, then whether it is negative or posi-
tive. Sentiment Analysis deals with the computational treatment of opinion, sentiment,
and subjectivity of texts. Sentiment Analysis starts with a small question: What other
people think?, and finally convert into billions of dollars of commercial deal. After the
great success of Web-2.0, Sentiment Analysis became a demanding and commercially
supported research field.

1.1 Motivation of Project

Crowdsourcing is when an entity whether an individual or an organization requests
specific resources from a group of people.

2
 CROWDSOURCING

Alert users from the emergency while getting the notification from the system
the project objective comprises of 3 parts
1.Performing crowdsource sentiment analysis on posts for 2019 indian election using
twitter public stream comparing two parties.
2.creating dummy account and then performing analysis on it which will enable us to
fetch the location of users.
3.hosting it through AWS Cloud platform.

CrowdSourcing 3
Chapter 2

PROBLEM IDENTIFICATION AND

PROJECT OBJECTIVE

2.1 Problem Statement

Given a status or acomments of that status, classify whether that is of posi- tive, nega-
tive, or neutral sentiment. For status or comments conveying both a positive and nega-
tive sentiment, whichever is the stronger sentiment should be chosen and average count
will be given at last.

2.2 Scope of the Project

Social media includes references to emergency events occurring at, or affecting specific
locations. To detect and describe the real time urban emergency event the 5W (What,
Where, When, Who, and Why) model is proposed. Propose system could be used in
real time for identification of user.

4
 CROWDSOURCING

2.3 Project Objective

1. Sentiment analysis is a useful tool for any organization or group for which public
sentiment or attitude towards them is important for their success - whichever way that
success is defined.
2. On social network, blogs, and online forums millions of people are busily dis-
cussing and reviewing businesses, companies, and organizations. And those opinions
are being listened to and analysed.
3. The results from sentiment analysis help businesses understand the conversa-
tions and discussions taking place about them, and helps them react and take action
accordingly.
4. They can quickly identify any negative sentiments being expressed, and turn poor
customer experiences into very good ones.
5. By listening to and analysing comments on social network, local government
departments can gauge public sentiment towards their department and the services they
provide, and use the results to improve services such as parking and leisure facilities,
local policing, and the condition of roads.
6. Universities can use sentiment analysis to analyze student feedback and com-
ments garnered either from their own surveys, or from online sources such as social
media. They can then use the results to identify and address any areas of student dis-
satisfaction, as well as identify and build on those areas where students are expressing
positive sentiments.

CrowdSourcing 5
Chapter 3

LITERATURE REVIEW

3.1 Existing System

Currently, During any event people just post on spcial media.
-The people do not have all the information about any emergency event.
-The information might be present on social media but the people do not have the tools
to check the post is positive, negative, good or bad.
-Also people do not get any real time information about any events.
-As most news agencies do not report local news people can not offer their help during
the event.

3.2 Proposed System

Crowdsourcing is evolving as a distributed problem solving and business production
model in recent years. In crowdsourcing paradigm, tasks are distributed to networked
people to complete such that a companys production cost can be greatly reduced.

6
 CROWDSOURCING

3.3 Feasibility Study

1) Sentiment Analysis and Opinion Mining AUTHOR: Bing Liu Pervasive real-life ap-
plications are solely a part of the rationale why sentiment analysis may be a well-liked
analysis downside. its conjointly extremely difficult as a IP analysis topic, and covers
several novel sub problems as we are going to see later. to boot, there was very little
analysis before the year 2000 in either IP or in linguistics. a part of the rationale is that
before then there was very little opinion text out there in digital forms. Since the year
2000, the sphere has mature chop-chop to become one in every of the foremost active
analysis areas in IP. Its conjointly wide researched in data processing, Web mining, and
knowledge retrieval. In fact, its unfold from computing to management sciences
2) Thumbs up? Sentiment Classification using Machine Learning Techniques AU-
THORS: Bo Pang and Lillian Lee, Shivakumar Vaithyanathan The prob- lem of clas-
sifying documents not by topic, however by overall sentiment, e.g., crucial whether
or not a review is positive or negative. Victimization film reviews as knowledge, we
discover that commonplace machine learning techniques definitively surpass human-
produced baselines. However, the 3 machine learning strategies we tend to utilized
(Naive Thomas Bayes, most entropy classification, and support vector machines) dont
perform in addi tion on sentiment classification as on ancient topic-based categoriza-
tion. We tend to conclude by examining factors that build the sentiment classification
drawback more difficult.
3). Adding Redundant Features for CRFs-based Sentence Sentiment Clas- sification
AUTHORS: Jun Zhao, Kang Liu, Gen Wang Author presents a completely unique
methodology supported CRFs in response to the 2 special characteristics of contex-
tual dependency and label redundancy in sen- tence sentiment classification. we have a
tendency to attempt to capture the discourse constraints on sentence sentiment victim-
ization CRFs. Through introducing redundant labels into the first sentimental label set
and organiz- ing all labels into a hierarchy, our methodology will add redundant options
into coaching for capturing the label redundancy. The experimental results prove that
our methodology outperforms the traditional ways like NB, SVM, MaxEnt and com-

CrowdSourcing 7
 CROWDSOURCING

monplace chain CRFs.

4) OpinionMiner: A Novel Machine Learning System for Web Opinion Min- ing and
Extraction AUTHORS: Wei Jin, Hung Hay Ho, Rohini K. Srihari Merchants merchan-
dising product on the net typically raise their customers to share their opinions and
active experiences on products they need pur- chased. sadly, reading through all client
reviews is tough, particularly for fashionable things, the number of reviews may be up
to tons of or maybe thousands. This makes it tough for a possible client to scan them to
make as- sociate degree educated call.
5) A Hierarchical Aspect-Sentiment Model for Online Reviews AUTHORS: Suin Kim,
Jianwen Zhang , Zheng Chen , Alice Oh , Shixia Liu To help users quickly perceive
the most important opinions from large online reviews, its necessary to mechanically
reveal the latent structure of the aspects, senti- ment polarities, and also the association
between them. However, theres very little work offered to do this effectively. during this
paper, we have a tendency to propose a gradable aspect sentiment model (HASM) to get
a gradable structure of aspect-based sentiments from unlabelled on-line re- views. In
HASM, the entire structure could be a tree. every node itself is a two-level tree, whose
root represents a facet and also the children repre- sent the sentiment polarities related
to it. Each side or sentiment polarity is sculptured as a distribution of words.

CrowdSourcing 8
Chapter 4

ANALYSIS

4.1 Software requirement specification

4.1.1 Purpose and Scope of Document

A software requirements specification (SRS) is a document that is created when a de-

tailed description of all aspects of the software to be built must be specified before the
project is to commence. It is important to note that a formal SRS is not always written.
In fact, there are many instances in which effort expended on a SRS might be better
spent in other software engineering activities.

4.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 planning various activities with the help of planner.
5. Designing, programming, testing etc.

9
 CROWDSOURCING

4.2 System requirements

4.2.1 Hardware Requirment

System : Pentium IV 2.4 GHz.

Hard Disk : 40 GB.
Monitor : 15 VGA Colour.
Ram : 512 Mb.

4.2.2 Software Requirements

Operating System: Windows 10

Technology: JAVA
Database: MySQL(back end)
Server: Apache Tomcat
Coding language: JSP, HTML, CSS And JAVA (front end).

4.3 Functional Requirement

4.3.1 Performance Requirement

Performance of the functions and every module must be well.

The overall performance of the software will enable the users to work efficiently.

4.3.2 Safety Requirement

The application is designed in modules where errors can be detected and fixed easily.
This makes it easier to install and update new functionality if required.

CrowdSourcing 10
 CROWDSOURCING

4.3.3 Security Requirement

Users all details are confidentiality. Data is modified by authorized person in authorized
manner. User need to go throw authentication process. Permissions to be assigned to
All Authenticated entities

4.4 Non-Functional Requirement

4.4.1 Performance Requirement

• The performance of the functions and every module must be well.

• The overall performance of the software will enable the users to work efficiently.
• Performance of encryption of data should be fast.
• Performance of the providing virtual environment should be fast.

4.4.2 Safety Requirement

The application is designed in modules where errors can be detected and fixed easily.
This makes it easier to install and update new functionality if required.

4.4.3 Security Requirement

All data will be encrypted using strong encryption algorithm and according to location
encryption is done.

4.4.4 Software Quality Attributes

Our software has many quality attribute that are given below:-

• Adaptability: This software is adaptable by all users.

• Availability: This software is freely available to all users. The availability of the
software is easy for everyone.

CrowdSourcing 11
 CROWDSOURCING

• Maintainability: After the deployment of the project if any error occurs then it can be
easily maintained by the software developer.

• Reliability: The performance of the software is better which will increase the reliabil-
ity of the Software.

• User Friendliness: Since, the software is a GUI application; the output generated is
much user friendly in its behavior.

4.5 Software Interface Description

4.5.1 What is Java

Java is a programming language and a platform. Java is a high level, robust, secured
and object-oriented programming language. Platform: Any hardware or software en-
vironment in which a program runs, is known as a platform. Since Java has its own
runtime environment (JRE) and API, it is called platform.

Where it is used? According to Sun, 3 billion devices run java. There are many devices
where java is currently used. Some of them are as follows:
1. Desktop Applications such as acrobat reader, media player, antivirus etc.
2. Web Applications such as irctc.co.in, javatpoint.com etc.
3. Enterprise Applications such as banking applications.
4. Mobile
5. Embedded System
6. Smart Card
7. Robotics
8. Games etc.

Types of Java Applications

There are mainly 4 type of applications that can be created using java programming:
1)Standalone Application

CrowdSourcing 12
 CROWDSOURCING

It is also known as desktop application or window-based application. An application

that we need to install on every machine such as media player, antivirus etc. AWT and
Swing are used in java for creating standalone applications.

2) Web Application
An application that runs on the server side and creates dynamic page, is called web
application. Currently, servlet, jsp, struts, jsf etc. technologies are used for creating
web applications in java.

3) Enterprise Application
An application that is distributed in nature, such as banking applications etc. It has
the advantage of high level security, load balancing and clustering. In java, EJB is used
for creating enterprise applications.

4) Mobile Application
An application that is created for mobile devices. Currently Android and Java ME
are use for creating mobile applications.
Features of Java
There is given many features of java. They are also known as java buzzwords. The
Java Features given below are simple and easy to understand.

Figure 4.1: Features of Java

Simple

CrowdSourcing 13
 CROWDSOURCING

According to Sun, Java language is simple because:

syntax is based on C++ (so easier for programmers to learn it after C++).removed
many confusing and/or rarely-used features e.g., explicit pointers, operator overloading
etc.No need to remove unreferenced objects because there is Automatic Garbage Col-
lection in java.
Object-oriented
Object-oriented means we organize our software as a combination of different types of
objects that incorporates both data and behaviour.
Object-oriented programming(OOPs) is a methodology that simplify software develop-
ment and maintenance by providing some rules.Basic concepts of OOPs are:

1. Object

2. Class

3. Inheritance

4. Polymorphism

5. Abstraction

6. Encapsulation
What does Java Development Kit (JDK) mean?
The Java Development Kit (JDK) is a software development environment used for
developing Java applications and applets. It includes the Java Runtime Environment
(JRE), an interpreter/loader (java), a compiler (javac), an archiver (jar), a documentation
generator (javadoc) and other tools needed in Java development. People new to Java
may be confused about whether to use the JRE or the JDK. To run Java applications and
applets, simply download the JRE. However, to develop Java applications and applets
as well as run them, the JDK is needed.
Java developers are initially presented with two JDK tools, java and javac. Both
are run from the command prompt. Java source files are simple text files saved with
an extension of .java. After writing and saving Java source code, the javac compiler is

CrowdSourcing 14
 CROWDSOURCING

invoked to create .class files. Once the .class files are created, the ’java’ command can
be used to run the java program.
For developers who wish to work in an integrated development environment (IDE),
a JDK bundled with Netbeans can be downloaded from the Oracle website. Such IDEs
speed up the development process by introducing point-and-click and drag-and-drop
features for creating an application.
There are different JDKs for various platforms. The supported platforms include
Windows, Linux and Solaris. Mac users need a different software development kit,
which includes adaptations of some tools found in the JDK
SQLite Database
SQLite is an embedded SQL database engine. Unlike most other SQL databases,
SQLite does not have a separate server process. SQLite reads and writes directly to
ordinary disk files. A complete SQL database with multiple tables, indices, triggers,
and views, is contained in a single disk file. The database file format is cross-platform
- you can freely copy a database between 32-bit and 64-bit systems or between big-
endian and little-endian architectures. These features make SQLite a popular choice as
an Application File Format. Think of SQLite not as a replacement for Oracle but as a
replacement for fopen()
SQLite is a compact library. With all features enabled, the library size can be less
than 500KiB, depending on the target platform and compiler optimization settings. (64-
bit code is larger. And some compiler optimizations such as aggressive function inlining
and loop unrolling can cause the object code to be much larger.) If optional features are
omitted, the size of the SQLite library can be reduced below 300KiB. SQLite can also
be made to run in minimal stack space (4KiB) and very little heap (100KiB), making
SQLite a popular database engine choice on memory constrained gadgets such as cell-
phones, PDAs, and MP3 players. There is a tradeoff between memory usage and speed.
SQLite generally runs faster the more memory you give it. Nevertheless, performance
is usually quite good even in low-memory environments.

CrowdSourcing 15
Chapter 5

DESIGN

5.1 System Design

Design is the first step in the development phase for any system. It may be defined as a
the of applying various techniques and principles for the purpose of defining a device, a
process, or a system insufficient detail to permit its physical realization System design
is the process of defining the elements of a supermarket system such as the architecture,
modules and components, the different interfaces of those components and the data
that goes through that system. Design will play a bigger role in every project; therefore
having a good design is needed to have enough information. In order to design a system,
the relational database must be designed first The design phase begins with an initial
three-step process:
• Project Idea
• Project Concept
• Appraisal

5.1.1 Project Idea

This stage is the preliminary, informal conceptualization and vetting of a project idea
among Colleagues within, and perhaps also outside.

16
 CROWDSOURCING

5.1.2 Project Concept

Once a project idea has been agreed upon, a project concept paper should be developed
in order to flesh out the idea, and enable those responsible for appraising the concept to
determine whether the proposed undertaking is viable, fits with perceived conservation
needs. A project concept paper is essentially a brief conceptualization of a project inter-
vention prepared prior to a Feasibility study and ultimately a full, participatory project
design undertaking. Developing a project concept involves the initial formulation of
project goals, targets, outputs,and activities in Summary form within the framework of
the WWF Global Priorities.

5.2 System Architecture

Figure 5.1: System Architecture

CrowdSourcing 17
 CROWDSOURCING

5.3 Data Flow Diagram

Figure 5.2: Level 0

Figure 5.3: Level 1

Figure 5.4: Level 2

CrowdSourcing 18
 CROWDSOURCING

5.4 UML Diagram

5.4.1 Activity Diagram

Figure 5.5: Activity Diagram

CrowdSourcing 19
 CROWDSOURCING

5.4.2 Use Case Diagram

Figure 5.6: Use Case Diagram

CrowdSourcing 20
 CROWDSOURCING

5.4.3 Package Diagram

Figure 5.7: Package Diagram

CrowdSourcing 21
 CROWDSOURCING

5.4.4 Class Diagram

Figure 5.8: Class Diagram

CrowdSourcing 22
 CROWDSOURCING

5.4.5 Sequence Diagram

Figure 5.9: Sequence Diagram

CrowdSourcing 23
Chapter 6

CODING

Front-End means a language that is used for user interface designing and coding. We
used our front end Java, HTML and CSS and use the Apache Tomcat server.par
Java is a programming language and a platform. Java is a high level, robust, secured
and object-oriented programming language. HTML (HyperText Markup Language) is
the most basic building block of the Web.
Cascading Style Sheets (CSS) is a simple mechanism for adding style (e.g., fonts,
colors, spacing) to Web documents. Apache Tomcat (sometimes simply "Tomcat") is
an open-source implementation of the Java Servlet, JavaServer Pages, Java Expression
Language and WebSocket technologies.

6.1 Front-End Languages

6.1.1 Java

Java is a programming language and a platform. Java is a high level, robust, secured
and object-oriented programming language. Platform: Any hardware or software en-
vironment in which a program runs, is known as a platform. Since Java has its own
runtime environment (JRE) and API, it is called platform.

24
 CROWDSOURCING

6.1.2 HTML

HTML (HyperText Markup Language) is the most basic building block of the Web. It
defines the meaning and structure of web content. Other technologies besides HTML
are generally used to describe a web page’s appearance/presentation (CSS) or function-
ality/behavior (JavaScript).

6.1.3 CSS

Cascading Style Sheets (CSS) is a simple mechanism for adding style (e.g., fonts, col-
ors, spacing) to Web documents.These pages contain information on how to learn and
use CSS and on available software. They also contain news from the CSS working
group.

6.1.4 Apache Tomcat

Apache Tomcat (sometimes simply "Tomcat") is an open-source implementation of the

Java Servlet, JavaServer Pages, Java Expression Language and WebSocket technolo-
gies.[3] Tomcat provides a "pure Java" HTTP web server environment in which Java
code can run.
Tomcat is developed and maintained by an open community of developers under
the auspices of the Apache Software Foundation, released under the Apache License
2.0 license.

6.2 Snapshots

6.2.1 Login form

A Login form is used to enter authentication credentials to access a restricted page or

form. This login form contains a field for the username and another for the password.
When the login form is submitted its underlying code checks that the credentials are

CrowdSourcing 25
 CROWDSOURCING

authentic, giving the user can access the restricted page. If a user is not able to provide
authentic credentials they will not be able to proceed past the login form.
**FIGURE***
After entering the correct user name and password we get a message of Login suc-
cessful, welcome admin and we can enter in the system. It is for security purpose.

6.2.2 Home/Main Page

The home page is the first page which shows what our system does and it shows 3
different choices such as Item Master in which we can add different items f different-
categories, Inventory that contains sales in which we can create a bill and add different
items for creating bill with GST and Exit option for exiting from the system.

6.2.3 Admin form

CrowdSourcing 26
Chapter 7

TESTING

7.1 Type of Testing Used

Purpose
Testing is an investigation conducted to provide stakeholders with informa- tion
about the quality of the product or service under test. Software testing also provides
an objective, independent view of the software to allow the business to appreciate and
understand the risks of software implementation. Test techniques include, but are not
limited to, the process of executing a program or application with the intent of finding
software bugs. Software testing can also be stated as the process of validating and veri-
fying that a software program or application or product:
1. Meets the business and technical requirements that guided its design and develop-
ment
2. Works as expected
3. Can be implemented with the same characteristics
Scope of Testing
Software testing, depending on the testing method employed, can be imple- mented
at any time in the development process. However, most of the test effort occurs after the
requirements have been defined and the coding process has been completed. As such,
the methodology of the test is governed by the software development methodology

27
 CROWDSOURCING

adopted. Different software development models will focus the test effort at different
points in the development process. Newer development models, such as Agile, often
employ test driven development and place an increased portion of the testing in the
hands of the developer, before it reaches a formal team of testers. In a more traditional
model, most of the test execution occurs after the requirements have been defined and
the coding process has been completed.
Test Plan
To test this application we are going with proper sequencing of testing like unit, inte-
gration, validation, GUI, Low level and High level test cases, major scenarios likewise.
We will go with the GUI testing first and then integration testing. After integration test-
ing performs the high level test cases and major scenarios which can affect the working
on the application. We will perform the testing on the data transmitted using the various
inputs and outputs and validate the results. It also intends to cover any deviations that
the project might take from the initially agreed Test Strategy in terms of scope, testing
methodology, tools, etc.. This test plan covers details of testing activities for this project
and scope.
GUI Testing :
Graphical User Interface (GUI) testing is the one of the mechanism in which user
interface developed System Under some graphical rules. GUI testing includes check-
ing various controls- menus, buttons, icons, dialog boxes and windows etc. Proposed
system is tested for user inputs against different mod- ules, validations are done. GUI
is tested for appearance of different controls, visibility graphs is tested. GUI testing
involves following actions:
1. Check all elements for size, position, width, length and acceptance of characters or
numbers. For instance, you must be able to provide inputs to the input fields.
2. Overall functionality related with performance of users graphical interface are checked.
3. Check Error Messages are displayed correctly
4. Check the font, layout details, style and display warning messages if it is false.
5. check the positioning of GUI elements.

CrowdSourcing 28
 CROWDSOURCING

Unit Testing :
It is the testing of individual software units of the application .it is done after the
complexion of an individual unit before integration. Unit testing involves the design
of test cases that validate that the internal program logic is functioning properly, and
that program inputs produce valid outputs. All decision branches and internal code
flow should be validated. This is a struc- tural testing, that relies on knowledge of its
construction and is invasive. Unit tests perform basic tests at component level and test
a specific business pro- cess,application, and/or system configuration. Unit tests ensure
that each unique path of a business process performs accurately to the documented
specifications and contains clearly defined inputs and expected results.
Integration Testing :
Integration tests are designed to test integrated software components to de- termine
if they actually run as one program. Testing is event driven and is more concerned with
the basic outcome of screens or fields. Integration tests demonstrate that although the
components were individually satisfaction, as shown by successfully unit testing, the
combination of components is cor- rect and consistent. Integration testing is specifically
aimed at exposing the problems that arise from the combination of components.
Testing Strategy
Software testing methods are traditionally divided into white- and black-box testing.
These two approaches are used to describe the point of view that a test engineer takes
when designing test cases.
White-box testing :
In white-box testing an internal perspective of the system, as well as pro- gramming
skills, are used to design test cases.
Black-box testing :
Black-box testing treats the software as a and quot;black box and quot;, examining
functionality without any knowledge of internal implementation. The testers are only
aware of what the software is supposed to do, not how it does it.
Grey-box testing

CrowdSourcing 29
 CROWDSOURCING

Grey-box testing involves having knowledge of internal data structures and algo-
rithms for purposes of designing tests, while executing those tests at the user, or black-
box level. The tester is not required to have full access to the software.

7.2 Test Cases and Test Results

Figure 7.1: Test Case :1

Figure 7.2: Test Case :2

CrowdSourcing 30
 CROWDSOURCING

Figure 7.3: Test Case :3

CrowdSourcing 31
 CROWDSOURCING

Figure 7.4: Test Case :4

CrowdSourcing 32
Chapter 8

CONCLUSION AND FUTURE

WORK

8.1 Conclusion
The rise of social network has fuelled interest in sentiment classification. Promptly and
correctly classifying sentiment from the text has become an important task for individ-
uals and companies. In the development of prediction models to classify the reviews,
more reliable approaches are expected to reduce the misclassifications. In this study,
the results of various hybrid methods are empirically evaluated on datasets of different
size for use in sentiment mining. Among the methods used, hybrid ensemble method
(HEM1) is highly robust in nature for balanced data models I, II and III, which is studied
through various quality parameters. The analysis also shows that the compound com-
bination of unigram, bigram and trigram performs better for almost all the prediction
methods. To handle imbalance data distribution in real time applications, it is observed
from the results that using SVMs for class prediction can be influenced by the data im-
balance, although SVMs can adjust itself well to some degree of data imbalance. To
cope with the problem, rebalancing the data is chosen as a promising direction, but both
under sampling and over sampling have limitations.
Through extensive experiments with benchmark and real application datasets, the

33
 CROWDSOURCING

proposed modified bagging method is shown to be effective and superior to several

other methods with different data sampling methods. The results also proved that the
PCA is a suitable dimension reduction method for hybrid methods for both balanced
and imbalanced datasets. In future, the effect of various other feature reduction tech-
niques like latent dirchlet allocation can be investigated. Further experiments should
be conducted in the future to evaluate the impact of various domain and region specific
parameters. Extending sentiment mining to other domains may lead to interesting new
results. In future, the use of more combination of n-grams and feature weighting that
gives a better accuracy level than this can be considered.

8.2 Future Scope

In this work, the focus is on finding features that appear explicitly as nouns or noun
phrases in the reviews. The finding of implicit features is left to future work. Future
opinion-mining systems need broader and deeper common and commonsense knowl-
edge bases. This will lead to a better understanding of natural language opinions and
will more efficiently bridge the gap between multimodal information and machine pro-
cessable data. Blending scientific theories of emotion with the practical engineering
goals of analyzing sentiments in natural language text will lead to more bio-inspired
approaches to the design of intelligent opinion-mining systems capable of handling se-
mantic knowledge, making analogies, learning new affective knowledge, and detecting,
perceiving, and feeling emotions. The work done in this research is only related to clas-
sification sentiment into two of the classes (binary classification) that is a positive class
and negative class. In the future development, a multiclass of sentiment classification
such as positive, negative, neutral and so on might be taken into consideration.

CrowdSourcing 34
 Bibliography

1 B. Liu, Sentiment analysis and opinion mining, Synthesis Lectures on Human Lan-
guage Technologies, vol. 5, no. 1, pp. 1-167, May 2012.

2 B. Pang, L. Lee, and S. Vaithyanathan,Thumbs up?: sentiment clas- sification using

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

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. 611-618.

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

5 P. Melville, W. Gryc, and R. D. Lawrence, Sentiment analysis ofblogs by combining

lexical knowledge with text classification Discovery and Data Mining, ser. KDD09.
New York,NY, USA: ACM,2009, pp. 1275-1284.

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 Proceed- ings of the 49th Annual Meeting of the As-
sociation for Computa- tional Linguistics: Human Language Technologies - Volume 1,
ser. HLT11.Stroudsburg, PA, USA: Association for Computational Lin- guistics,2011,
pp. 142-150.

35