# Boundary Objects and their Use in Agile Systems Engineering

arXiv: https://arxiv.org/abs/1904.12131 · HTML: https://mlsanity.com/paper/1904.12131/

## Key facts

- Cited by 3 papers in the map (data through 14 Oct 2026).
- First posted on arXiv 27 Apr 2019.

## Built on by (most cited first, 3 of 3)

- [Requirement Engineering Challenges for AI-intense Systems Development](https://mlsanity.com/paper/2103.10270/) (2021)
- [CausalOps -- Towards an Industrial Lifecycle for Causal Probabilistic Graphical Models](https://mlsanity.com/paper/2308.01375/) (2023)
- [Designing a Boundary Negotiating Artifact for Collaborative Socio-Technical Sense-Making in AI Regulatory Sandboxes](https://mlsanity.com/paper/2609.37109/) (2026)

## Abstract (arXiv)

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, but also 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.