O SlideShare utiliza cookies para otimizar a funcionalidade e o desempenho do site, assim como para apresentar publicidade mais relevante aos nossos usuários. Se você continuar a navegar o site, você aceita o uso de cookies. Leia nosso Contrato do Usuário e nossa Política de Privacidade.
O SlideShare utiliza cookies para otimizar a funcionalidade e o desempenho do site, assim como para apresentar publicidade mais relevante aos nossos usuários. Se você continuar a utilizar o site, você aceita o uso de cookies. Leia nossa Política de Privacidade e nosso Contrato do Usuário para obter mais detalhes.
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
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
ROLE Social Requirements Engineering (SRE) – i* SR
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 +
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
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]
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
Integration of the Bazaar with external services
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