CROWDSOURCING FOR

REQUIREMENT ENGINEERING

Presented by : Ranjan Dhar1

2

MORE HEADS ARE BETTER THAN ONE

3

EXAMPLES

4

EXAMPLES

5

What is Crowd Sourcing ????

6

Crowd sourcing Online, Distributed, Problem solving

production model. Problems are usually solved by involving

a large number of people/users.

Crowdsourcing

Crowd Crowdsourcers

7

Goal / Motivation ?

Explore the relationship between features and the quality of requirements elicited using Crowdsourcing.

Systematically develop crowd sourcing platforms for Requirement Engineering and maximize efficiency.

8

Why Crowdsourcing ? Technology Trends Wide and Diverse audience

9

Eliciting Requirements This can be done at 2 levels. Design level Runtime (Feedbacks, Problems, Outdated features)

“Could be used throughout the lifecycle of software development”

Crowdsourcing increases the qualityas well as the economic feasibility ofRequirement Engineering.

10

Bloom of Crowdsourcing Traditional approaches were costly and

inaccurate. Example: Surveys and Interviews. Platform diversion from traditional

software systems towards mobile and cloud.

11

Studies which utilized “CROWD” Requirement-Driven Social Adaptation Acquiring and analyzing the actual users perception on the role

of the system in achieving their requirements and its quality. They propose to utilize that to make adaptation decisions.

Feedback Based Requirement Engineering Users feedback on software could help developers to better

understand the requirements of the next release of the system. This feedback could be explicit or implicit.

Stakeholder’s discovery In complex and dynamic systems, it is hard to identify the set

of stakeholders and their roles and expertise and also their requirements. Crowdsourcing here would help identifying a comprehensive set of stakeholders from an initial set of stakeholders specified by the analysts.

12

Studies which utilized “CROWD” Requirements Identification In software paradigms like Cloud Computing and Mobile Apps,

the users set is highly diverse and unpredictable. This means relying on an elite group of users to understand what functionality and quality attributes to meet in the software is limited and also costly.

Empirical Validation users might not maintain the same opinion when time passes

due to the emergence of competitive solutions and the use of software in contexts which were not thought of at the engineering stage. Example: Scaling performance of an application.

13

Features of Crowdsourcing

14

A bit of stat !!

15

Negatives

16