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.

Automotive companies increasingly include proven agile methods in their plan-driven system development. The adoption of agile methods impacts not only the way individuals collaborate, but also the management of artifacts like requirements, test cases, safety documentation, and models. While practitioners aim to reduce unnecessary documentation, there is a lack of guidance for automotive companies with respect to what artifacts are needed and how to manage them. To close this knowledge gap and create practical guidelines, we conducted a design-science study together with 53 practitioners from six automotive companies. Using interviews, surveys, and focus groups, we analyzed categories of artifacts and practical challenges to create applicable guidelines to collaboratively manage artifacts in agile automotive contexts. Our findings indicate that different practices are required to manage artifacts that are shared among different teams within the company (boundary objects) and those that are relevant within a specific team (locally relevant artifacts). CCS CONCEPTS• Software and its engineering → Software development methods; Agile software development; Documentation; Collaboration in software development; KEYWORDSAgile systems engineering, empirical software engineering, largescale agile, documentation ACM Reference Format: Rebekka Wohlrab, Patrizio Pelliccione, Eric Knauss, and Mats Larsson. 2018.

Design tables for broadband terminations are presented. The termination circuits consist of one or two x/4 transmission lines in cascade loaded with a resistance in series with an open circuit stub. Since no holes in the substrate or metallic connections with the groundplanes are needed the design is suitable for printed circuits. Measurements have been made on a termination which had a total length of A/2. The bandwidth was designed to be 85 percent. The experimental result is close to the theoretical predictions. Broadband terminations of this kind may be used in a number of ways.

No abstract

No abstract