The ROLE Requirements Bazaar

Uploaded on

A presentation on the ROLE Requirements Bazaar and the ROLE Social Requirements Engineering approach going in the direction of implementation.

A presentation on the ROLE Requirements Bazaar and the ROLE Social Requirements Engineering approach going in the direction of implementation.

More in: Technology , Education
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads


Total Views
On Slideshare
From Embeds
Number of Embeds



Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

    No notes for slide


  • 1. The ROLE Requirements Bazaar Dominik Renzel Chair of Computer Science 5 (Databases & Information Systems) RWTH Aachen University, Germany Chair of Computer Science 5, RWTH Aachen University, Germany Fraunhofer FIT – CAPLE Group Guerilla Meeting Mar 1, 2012 This work by Dominik Renzel is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported. ©
  • 2. Motivation Somebody What to listening to develop first my needs!? to create most impact? Negotiation of requirements between developers and users Challenges:  Massive amounts of requirements...  stated by lots of users...  organized in multiple heterogenous communities...  with different interests/practices/levels of technical literacy...  stating imprecise/informal requirements...Tool for social requirement engineering needed
  • 3. The ROLE SRE Approach – Support for the Long Tail  No Mainstream Web 2.0 RE!  “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
  • 4. ROLE Social Requirements Engineering (SRE) – i* SR
  • 5. ROLE Requirements Bazaar – Required Features
  • 6. Requirements Elicitation in the Bazaar
  • 7. Requirements Elicitation – Alternatives Comic-like annotations Web 2.0 feedback tools:on screenshots/Storytelling • •
  • 8. Requirements Dashboard - Weigthed Prioritization
  • 9. ROLE CoP Requirements Analysis Services User-to-Service Communication  CoP-aware Usage Statistics  Identification of successful CoP services  Identification of CoP service usage patterns User-to-User Communication  CoP-aware Social Network Analysis  Identification of influential CoP members  Identification of CoP member interaction patterns +
  • 10. What can we find with monitoring analysis? Context-Aware Usage Statistics  Frequency, Density, Patterns  Users, Communities  Location, Time, Technology Used Tool Quality  Performance, Stability, etc.  Error Occurency/Sources Tendencies for/against requirements Hints to non-functional requirements
  • 11. Monitoring User-to-User /Service Interaction: MobSOSX Monitoring of XMPP Protocol Activity (Chat, PubSub, IWC, etc.)
  • 12. Monitoring User-to-Service Interaction: MobSOSR Monitoring of RESTful Service Usage
  • 13. Creating Awareness – Monitoring Visualization
  • 14. What can you find with SNA measures? How well the position of a person is to receive and disseminate information – experts (centrality measures) [Wasserman & Faust, 1994] Do users communicate only within their groups or with some users from the other groups as well – innovation stars (boundary spanners, brokers, high betweenness centrality) [Burt, 2005] Who and what effects a user? – influence networks [Lewis, 2009] What are groups/communities a user belongs to? – community mining [Clauset et al., 2004]
  • 15. Integration with ROLE Widget Store
  • 16. Observations from first Bazaar Prototypes Users  …need intuitive means for requirements input  …need templates to support formal requirement specs  …are not acquainted with developer tools & jargon Developers  …use issue trackers for technical requirements, bugs, ideas, etc.  …use source code management systems for code maintenance  …do not use “island applications“ 2-step Approach  Use Requirements Bazaar to get users and developers into requirement negotiation process  Transfer to JIRA only if developers take up implementation of requirement
  • 17. Integration of the Bazaar with external services
  • 18. Future Work (ROLE Y4) Development  ROLE Requirements Store  ROLE RE Widgets & Interface Elements  Integration with ROLE Widget Store  Integration with ROLE Infrastructure Data Gathering for Requirements Analysis  User Ratings  Distributed Monitoring Approach  Formalized Ranking Model