Requirements Bazaar: Social requirements engineering for community-driven innovation

Abstract

Abstract-The innovation potential of niche communities often remains inaccessible to service providers due to a lack of awareness and effective negotiation between these two groups. Requirements Bazaar, a browser-based social software for Social Requirements Engineering (SRE), aims at bringing together communities and service providers into such a negotiation process. Communities should be supported to express and trace their requirements and eventually receive a realization. Service providers should be supported in discovering relevant innovative requirements to maximize impact with a realization. In this paper we present Requirements Bazaar with focus on four aspects: requirements specification, a workflow for co-creation, workspace integration and personalizable requirements prioritization.

REfine: A gamified platform for participatory requirements engineering

“…The tool also recommends requirements and identifies conflicts, and is supported by the StakeRare method [8]. CrowdREquire [10] and Requirements Bazaar [21] are other solutions along the lines of StakeSource 2.0. These approaches, however, do not focus on the provision of (long-term) incentives.…”

Decentralized Learning Infrastructures for Community Knowledge Building

“…It then replicates the microservices of the application via the p2p network and starts them locally. For requirement analysis and feedback, we used the Requirements Bazaar [27] to also include end-users in improving the development of the application and underlying framework itself. Both application and framework are released as open source software 2 .…”

Smart Ambient Learning with Physical Artifacts UsingWearable Technologies

“…Furthermore, we coined the DevOpsUse term by integrating the notion of end users into the development process [29]. We created a feedback workflow in the continuous innovation platform Requirements Bazaar [30] that allows users of our exhibition system to get in touch with the other stakeholders in the process, namely researchers, developers and operators. The overall aim is to establish a continuous innovation life cycle where advancements in the software follow the real needs of the whole community.…”