Collaborative resolution of requirements mismatches when adopting open source components

  • Authors:

  • Nguyen Duc Anh;Daniela S. Cruzes;Reidar Conradi;Martin Höst;Xavier Franch;Claudia Ayala

  • Affiliations:

  • Department of Computer and Information Science, Norwegian University of Science and Technology, Trondheim, Norway;Department of Computer and Information Science, Norwegian University of Science and Technology, Trondheim, Norway;Department of Computer and Information Science, Norwegian University of Science and Technology, Trondheim, Norway;Department of Computer Science, Lund University, Lund, Sweden;Department of Service Engineering and Information Systems, Technical University of Catalunya, Barcelona, Spain;Department of Service Engineering and Information Systems, Technical University of Catalunya, Barcelona, Spain

  • Venue:
  • REFSQ'12 Proceedings of the 18th international conference on Requirements Engineering: foundation for software quality
  • Year:
  • 2012

Quantified Score

Hi-index 0.00

Visualization

Abstract

[Context and motivation] There is considerable flexibility in requirements specifications (both functional and non-functional), as well as in the features of available OSS components. This allows a collaborative matching and negotiation process between stakeholders such as: customers, software contractors and OSS communities, regarding desired requirements versus available and thus reusable OSS components. [Problem] However, inconclusive research exists on such cooperative processes. Not much empirical data exists supporting the conduction of such research based on observation of industrial OSS adoption projects. This paper investigates how functional and non-functional requirement mismatches are handled in practice. [Results] We found two common approaches to handle functional mismatches. The main resolution approach is to get the components changed by the development team, OSS community or commercial vendor. The other resolution approach is to influence requirements, often by postponing requirements. Overall, non-functional requirements are satisfactorily achieved by using OSS components. Last but not least, we found that the customer involvement could enhance functional mismatch resolution while OSS community involvement could improve non-functional mismatch resolution. [Contribution] Our data suggests that the selecting components should be done iteratively with close collaboration with stakeholders. Improvement in requirement mismatch resolution to requirements could be achieved by careful consideration of mismatches size, requirements flexibility and components quality.