Boundary objects and their use in agile systems engineering. Issue 5 (22nd April 2019)

• Record Type: Journal Article
• Authors: Wohlrab, Rebekka; Pelliccione, Patrizio; Knauss, Eric; Larsson, Mats
• Other Names: O'Connor Rory V. guestEditor.; Houston Dan guestEditor.; Hebig Regina guestEditor.; Kuhrmann Marco guestEditor.
• Is Part Of: Journal of software. Volume 31:Issue 5(2019)
• Page Start: n/a
• Page End: n/a
• Publication Date: 2019-04-22
• Subjects: agile systems engineering -- boundary objects -- design science -- documentation; Software engineering -- Periodicals; Computer software -- Development -- Periodicals; Software maintenance -- Periodicals; 005.1
• DOI: 10.1002/smr.2166
• Languages: English
• ISSNs: 2047-7473

Abstract

Summary: Agile methods are increasingly introduced in automotive companies in the attempt to become more efficient and flexible in the system development. The adoption of agile practices influences communication between stakeholders and makes companies rethink the management of artifacts and documentation like requirements, safety compliance documents, and architecture models. Practitioners aim to reduce irrelevant documentation but face a lack of guidance to determine what artifacts are needed and how they should be managed. This paper presents artifacts, challenges, guidelines, and practices for the continuous management of systems engineering artifacts in automotive based on a theoretical and empirical understanding of the topic. In collaboration with 53 practitioners from six automotive companies, we conducted a design‐science study involving interviews, a questionnaire, focus groups, and practical data analysis of a systems engineering tool. The guidelines suggest the distinction between artifacts that are shared among different actors in a company (boundary objects) and those that are used within a team (locally relevant artifacts). We propose an analysis approach to identify boundary objects and three practices to manage systems engineering artifacts in industry. Abstract : The adoption of agile practices not only influences communication between stakeholders but also makes companies rethink the management of artifacts and documentation like requirements and architecture models. The paper presents a design‐science study with 53 practitioners from six automotive companies, involving qualitative methods and analysis of industrial systems engineering data. It provides an analysis of practices, challenges, recommended guidelines, and tool practices to manage artifacts that are shared among different actors in a company (boundary objects) and those that are used within a team (locally relevant artifacts).