Requirements Traceability across Organizational Boundaries - A Survey and Taxonomy

Abstract

Abstract. [Context and motivation]Outsourcing of software development is an attractive business model. Companies expect cost reduction, enhanced efficiency, and exploited external resources. However, this paradigmatic shift also introduces challenges as stakeholders are spread across distinct organizations. [Question/problem] Requirements traceability supports stakeholders in satisfying information needs about developments and could be a viable way of addressing the challenges of interorganizational development. While requirements traceability has been the subject of significant research efforts, its application across organizational boundaries is a largely unexplored area. [Principal ideas/results] We followed a qualitative research approach. First, we developed a taxonomy identifying the needs of inter-organizational traceability. Second, we conducted semi-structured interviews with informants from 17 companies. Eventually, we applied qualitative content analysis to extract findings that supported and evolved our taxonomy. [Contribution] Practitioners planning and managing inter-organizational relationships can use our findings as a conceptual baseline to effectively leverage traceability in those settings. Effective traceability supports projects in accomplishing their primary goal of maximizing business value.

Software Engineering Applications Enabled by Blockchain Technology: A Systematic Mapping Study

“…Collaboration practices in interorganizational software projects may be complicated, as well. It has been reported that there is an underlying conflict between the common project goal and independent organizational goals, for instance, one organizational goal could be to not disclose functional knowledge [17]. This implies restricted access to artifacts at the partner's side, which in turn impedes complete and reliable requirements traceability and hinders the assessment of whether quality gates have been passed [17].…”

Smart and Agile Manufacturing Framework, A Case Study for Automotive Industry

“…Experts from different geographical locations are available to provide their expertise and suggestions in the construction and innovation of a system [45]. In such a developmental environment, the traceability needs to be globally updated [46]. Model-based traceability is replacing the conventional development approach nowadays.…”

Mind the gap: assessing the conformance of software traceability to relevant guidelines

“…Organizations struggle to establish and maintain accurate and complete sets of traceability links [5,38,49,48,39]. A prior analysis of the traceability information submitted by various organizations to the US Food and Drug Administration (FDA) as part of the medical device approval process, showed a significant traceability gap between the traceability expectations as laid out in the FDA's "Guidance for the Content of Premarket Submissions for Software Contained in Medical Devices" [21], and the traceability data documented in the submissions [39].…”