the role sre approach - getting more concrete

19
© www.role- project.eu The ROLE SRE Approach – Getting More Concrete Dominik Renzel Chair of Computer Science 5, RWTH Aachen University, Germany WP1 Workshop May 14, 2010 - Leicester, UK

Upload: drenzel

Post on 27-May-2015

707 views

Category:

Documents


1 download

DESCRIPTION

Presentation in more concrete plans for Social Requirements Engineering on Personal Learning Environment Technology in the EU FP7 IP ROLE (

TRANSCRIPT

Page 1: The ROLE SRE Approach - Getting more concrete

© www.role-project.eu

The ROLE SRE Approach – Getting More Concrete

Dominik RenzelChair of Computer Science 5,

RWTH Aachen University, Germany

WP1 WorkshopMay 14, 2010 - Leicester, UK

Page 2: The ROLE SRE Approach - Getting more concrete

The ROLE SRE Approach – Support for the Long Tail

• No Mainstream Web 2.0 Requirements Engineering!• “Overall Top-N“: naive approach• Needs of specialized CoPs neglected• Innovation Killer (clones only)

• Rather Long-Tail Requirements Engineering• “Community-Aware Top-N“• Special support for niche CoPs• High specialization, but high innovation

Page 3: The ROLE SRE Approach - Getting more concrete

ROLE Social RE – i* Strategic Rationale

Satisfy CoP needs

Collaboration Medium

DD

Collaborative RE Medium

DD

Analyze CoP Generated

Content

Analyze Monitoring

Data

D

CoP Social Analysis Results

D

Monitoring Analysis Results

Decide on Realization of Requirements

Explicit Requirements

Analysis Results

D

Analyze Explicit Requirements

D

D

Express Individual Requirements

Identify Common CoP Requirements

Collaborate within CoP

Som

e +

Som

e +

UseInfrastructure

Provide CoP Services

Provide CoP Requirements Elicitation Services

Provide CoP Requirements Analysis Services

Provide Explicit Requirements

Generate Content Collaboratively

ROLE Infrastructure

DD

D

CoP Generated Content

D

D

D

D

ROLE CoP

Some

+

Provide CoP Monitoring Services

Provide CoP Requirements Decision Support Services

Decision Results

Communicate within CoP

Provide Decision on Requirements Realization

D D

Provide Decision Results

D

Collect Individual Decisions

D

Provide Communication Services

Communication Medium

D

D

Page 4: The ROLE SRE Approach - Getting more concrete

Explicit vs. Implicit Requirements

• Explicit Requirements• Actively stated by ROLE CoP members (usr, dev, res)• Requires communication between users & developers• Requires tools for active collection of requirements

• Implicit Requirements• Not directly stated by ROLE CoP members• Requires minable data (+technical means for acquisition)

• System usage monitoring

• User interaction monitoring

• Collaboratively generated content

• Requires requirements mining techniques

Page 5: The ROLE SRE Approach - Getting more concrete

ROLE CoP Communication Services & Media

Satisfy CoP needs

Collaboration Medium

DD

Collaborative RE Medium

DD

Analyze CoP Generated

Content

Analyze Monitoring

Data

D

CoP Social Analysis Results

D

Monitoring Analysis Results

Decide on Realization of Requirements

Explicit Requirements

Analysis Results

D

Analyze Explicit Requirements

D

D

Express Individual Requirements

Identify Common CoP Requirements

Collaborate within CoP

Som

e +

Som

e +

UseInfrastructure

Provide CoP Services

Provide CoP Requirements Elicitation Services

Provide CoP Requirements Analysis Services

Provide Explicit Requirements

Generate Content Collaboratively

ROLE Infrastructure

DD

DCoP Generated

Content

D

D

D

D

ROLE CoP

Some

+

Provide CoP Monitoring Services

Provide CoP Requirements Decision Support Services

Decision Results

Provide Decision on Requirements Realization

D D

Provide Decision Results

D

Collect Individual Decisions

D

D

D

Communicate within CoP

Provide Communication Services

Communication Medium

Page 6: The ROLE SRE Approach - Getting more concrete

ROLE CoP Communication Services & Media

• Important Prerequisites: • Contact between ROLE users & developers• “Hot Wire to the Developers“• Users to state what they need• Voices of users to be heard by developers (Exit/Voice)• But: Needs smart aggregation to prevent flooding

• Communication Services & Media• Developer mail• Developer IM• ROLE Developer Chat (ROLE XMPP Server)• ROLE SourceForge Web 2.0 Features (Wikis)• ROLE Google Groups

Page 7: The ROLE SRE Approach - Getting more concrete

Social RE in Android Market – Developer Contact

Page 8: The ROLE SRE Approach - Getting more concrete

ROLE CoP Requirements Elicitation Services

Satisfy CoP needs

Collaboration Medium

DD

Collaborative RE Medium

DD

Analyze CoP Generated

Content

Analyze Monitoring

Data

D

CoP Social Analysis Results

D

Monitoring Analysis Results

Decide on Realization of Requirements

Explicit Requirements

Analysis Results

D

Analyze Explicit Requirements

D

D

Express Individual Requirements

Identify Common CoP Requirements

Collaborate within CoP

Som

e +

Som

e +

UseInfrastructure

Provide CoP Services

Provide CoP Requirements Elicitation Services

Provide CoP Requirements Analysis Services

Provide Explicit Requirements

Generate Content Collaboratively

ROLE Infrastructure

DD

DCoP Generated

Content

D

D

D

D

ROLE CoP

Some

+

Provide CoP Monitoring Services

Provide CoP Requirements Decision Support Services

Decision Results

Communicate within CoP

Provide Decision on Requirements Realization

D D

Provide Decision Results

D

Collect Individual Decisions

DProvide Communication

Services

Communication Medium

D

D

Page 9: The ROLE SRE Approach - Getting more concrete

ROLE CoP Requirements Elicitation Services

• Dedicated Services• ROLE SourceForge Feature Tracker (Developers)• ROLE LinkedIn Group (Professionals)

• Integrated Services (End-Users)• Main Integration Point: Widget Store (IMC)• Inspiration from Android Market/iPhone Appstore• Collaborative Filtering for Widgets (rate, comments, etc.)• Dedicated Requirements Elicitation Widgets

• Explicit Feature Wishlists• Web 2.0 RE Widgets (BAT)• BILD Widget

Page 10: The ROLE SRE Approach - Getting more concrete

Web 2.0 RE Tool Example – Bubble Annotation Tool

Page 11: The ROLE SRE Approach - Getting more concrete

Social RE in Android Market – Recommendation Area

Explicit Requirementsin Comments

Ratings + Comments

Conditional Ratings(connected with Requirements)

Page 12: The ROLE SRE Approach - Getting more concrete

ROLE CoP Monitoring Services

Satisfy CoP needs

Collaboration Medium

DD

Collaborative RE Medium

DD

Analyze CoP Generated

Content

Analyze Monitoring

Data

D

CoP Social Analysis Results

D

Monitoring Analysis Results

Decide on Realization of Requirements

Explicit Requirements

Analysis Results

D

Analyze Explicit Requirements

D

D

Express Individual Requirements

Identify Common CoP Requirements

Som

e +

Som

e +

Provide CoP Services

Provide CoP Requirements Elicitation Services

Provide CoP Requirements Analysis Services

Provide Explicit Requirements

ROLE Infrastructure

DD

DCoP Generated

Content

D

D

ROLE CoP

Some

+

Provide CoP Requirements Decision Support Services

Decision Results

Provide Decision on Requirements Realization

D D

Provide Decision Results

D

Collect Individual Decisions

DProvide Communication

Services

Communication Medium

D

D

D

D

UseInfrastructure

Generate Content Collaboratively

Provide CoP Monitoring Services

Communicate within CoP

Collaborate within CoP

28.02.09

Page 13: The ROLE SRE Approach - Getting more concrete

ROLE CoP Monitoring Services

• User-to-Service Communication• Until now: Monitor Local Interwidget Communication • Planned: Extend to Remote Interwidget Communication (XMPP)

• User-to-User/Developer Communication• Chat Conversations• Message Boards• Web 2.0 Communication Media (e.g. Twitter)

28.02.09

Page 14: The ROLE SRE Approach - Getting more concrete

ROLE CoP Requirements Analysis Services

Satisfy CoP needs

Collaboration Medium

DD

Collaborative RE Medium

DD

D

D

Decide on Realization of Requirements D

D

D

Express Individual Requirements

Identify Common CoP Requirements

Collaborate within CoP

Som

e +

Som

e +

UseInfrastructure

Provide CoP Services

Provide CoP Requirements Elicitation Services

Generate Content Collaboratively

ROLE Infrastructure

DD

D

D

D

D

D

ROLE CoP

Some

+

Provide CoP Monitoring Services

Provide CoP Requirements Decision Support Services

Decision Results

Communicate within CoP

Provide Decision on Requirements Realization

D D

Provide Decision Results

D

Collect Individual Decisions

DProvide Communication

Services

Communication Medium

D

D

Analyze CoP Generated

Content

Analyze Monitoring

Data

CoP Social Analysis Results

Monitoring Analysis Results

Explicit Requirements

Analysis Results

Analyze Explicit Requirements

Provide CoP Requirements Analysis Services

Provide Explicit Requirements

CoP Generated Content

28.02.09

Page 15: The ROLE SRE Approach - Getting more concrete

Open Issues

• Analysis Targets• Explicit requirements• CoP-generated content• Monitoring data

28.02.09

Page 16: The ROLE SRE Approach - Getting more concrete

ROLE CoP Requirements Analysis Services

• User-to-Service Communication (Monitoring)• CoP-aware Usage Statistics• Identification of successful CoP services• Identification of CoP service usage patterns (cf. WP6)

• User-to-User Communication (Monitoring, Content)• CoP-aware Social Network Analysis• CoP-aware Sentiment Analysis• Identification of influential CoP members• Identification of CoP member interaction patterns (cf. WP7)

+

Page 17: The ROLE SRE Approach - Getting more concrete

ROLE CoP Requirements Decision Support Services

Satisfy CoP needs

Collaboration Medium

DD

Collaborative RE Medium

DD

Analyze CoP Generated

Content

Analyze Monitoring

Data

D

D

D

Analyze Explicit Requirements

D

D

Express Individual Requirements

Collaborate within CoP

Som

e +

Som

e +

UseInfrastructure

Provide CoP Services

Provide CoP Requirements Elicitation Services

Provide CoP Requirements Analysis Services

Provide Explicit Requirements

Generate Content Collaboratively

ROLE Infrastructure

DD

DCoP Generated

Content

D

D

D

D

ROLE CoP

Some

+

Provide CoP Monitoring Services

Communicate within CoP

D D

D

DProvide Communication

Services

Communication Medium

D

D

CoP Social Analysis Results

Monitoring Analysis Results

Decide on Realization of Requirements

Explicit Requirements

Analysis Results

Identify Common CoP Requirements

Provide CoP Requirements Decision Support Services

Decision Results

Provide Decision on Requirements Realization

Provide Decision Results

Collect Individual Decisions

28.02.09

Page 18: The ROLE SRE Approach - Getting more concrete

ROLE CoP Requirements Decision Support Services

• Analysis Outcome: • Requirements prioritization for developers• Compact overview (Requirements Dashboard)• Decision Support

• Model Construction Stakeholders• ROLE Test-beds• ROLE Alliance Programme

• End-User Communities• OS Developer Communities• Providers & Intermediaries• Learning Institutions• Policy Makers

• ...

28.02.09

Page 19: The ROLE SRE Approach - Getting more concrete

Open Issues

• Data Gathering for Requirements Analysis• ROLE Requirements Elicitation Tools

(Widgetstore Integration, Dedicated Widgets)• ROLE Infrastructure (upcoming in WP3)• Centralized vs. Decentralized• Privacy & Accessibility

• Requirements Mining Algorithms