Boundary Objects and their Use in Agile Systems Engineering

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

Why and How Your Traceability Should Evolve: Insights from an Automotive Supplier

Traceability is a key enabler of various activities in automotive software and systems engineering and required by several standards. However, most existing traceability management approaches do not consider that traceability is situated in constantly changing development contexts involving multiple stakeholders. Together with an automotive supplier, we analyzed how technology, business, and organizational factors raise the need for flexible traceability. We present how traceability can be evolved in the development lifecycle, from early elicitation of traceability needs to the implementation of mature traceability strategies. Moreover, we shed light on how traceability can be managed flexibly within an agile team and more formally when crossing team borders and organizational borders. Based on these insights, we present requirements for flexible tool solutions, supporting varying levels of data quality, change propagation, versioning, and organizational traceability.Comment: 9 pages, 3 figures, accepted in IEEE Softwar

Living Boundary Objects to Support Agile Inter-Team Coordination at Scale

Context: In the last decades, large-scale agile development has received increasing attention, as also organizations with many stakeholders and large systems aim for higher development speed and focus on customer value. A recognized research challenge in large-scale agile development relates to inter-team coordination. To coordinate effectively, organizations need to identify what knowledge is required across team borders and how it can be managed over time. Knowledge is potentially manifested in boundary objects – artifacts that create a shared understanding between teams (e.g., requirements or architecture descriptions). Traceability between artifacts is a key necessity to manage change in agile contexts. Moreover, agile practitioners aim to reduce the documentation effort to absolutely crucial artifacts and trace links.Objective: This thesis aims to improve how practitioners can manage knowledge for inter-team coordination in large-scale agile development. We focus especially on how knowledge can be made explicit in artifacts and trace links that are evolved over time. Method: We empirically investigated problems and developed solutions using a research approach that was inspired by design science. Case studies, an in-depth design science study, a mixed methods study, and surveys were performed. Using this mix of research methods, we leveraged both qualitative and quantitative data. Results: We coined the concept of living boundary objects to manage knowledge for inter-team coordination. Living boundary objects are boundary objects that are traced to other artifacts, kept up to date, and serve for inter-team coordination. They should be established early in the lifecycle to create a common understanding of the product to be developed. We scrutinized architecture descriptions, interfaces, and requirements and traceability information models as examples of concrete boundary objects. We recommend establishing alignment using a common high-level structure, but also supporting diverse knowledge management practices to fulfill the individual needs of agile teams. Conclusions: Our contributions help to establish knowledge management practices that are considered beneficial by practitioners and focus on the crucial aspects to align agile teams on. We suggest concepts and requirements for knowledge management tools that take the distinct role of living boundary objects into consideration and can be adjusted as organizations\u27 needs evolve

Experimental determination of gap flow-conditioned forces at turbine stages and their effect on the running stability of simple rotors

Instabilities in turbine operation can be caused by forces which are produced in connection with motions involving the oil film in the bearings. An experimental investigation regarding the characteristics of such forces in the case of three typical steam turbine stages is conducted, taking into account the effect of various parameters. Supplementary kinetic tests are carried out to obtain an estimate of the flow forces which are proportional to the velocity. The measurements are based on the theoretical study of the damping characteristics of a vibrational model. A computational analysis of the effect of the measured fluid forces on the stability characteristics of simple rotor model is also conducted

Preliminary Findings and Outlook of the CASHSS “Multiple Secularities – Beyond the West, Beyond Modernities”

In its initial research project description, the Centre for Advanced Studies in Humanities and Social Sciences (CASHSS) took a position on the longstanding academic and public debates on secularism, secularisation, and secularity. In doing so, it referred to the concept of Multiple Secularities, which had been developed in a previous research project,1 and which Kleine had applied to pre-modern Japan.2 Against this backdrop, an idea arose for a multidisciplinary project combining sociology, history of religion and study of religions. ‘Secularity’ is an analytical concept, which seeks to avoid the ideological connotations of the term secularism. The term, which is conceived as an ideal-type, describes how conceptual distinctions and institutional differentiations are made between religious and non-religious spheres and practices. In this context, ‘differentiation’ is not a complete separation, but entails some form of relation between two conceptually distinguished spheres.:1 Introduction and Background ................................................................................. 3 1.1 History of the Research Project.......................................................................... 3 1.2 The Academic Debate.......................................................................................... 5 1.3 Current State of Research in Selected Research Areas..................................10 2 Research Findings from the First Funding Period (2016-2020)........................13 2.1 Further Developing and Refining the Concept..............................................13 2.2 Assumptions and Hypotheses..........................................................................15 2.2.1 Internal Social Differentiation − Social Structures.....................................15 2.2.2 Taxonomies, Classifications, Knowledge Systems: Epistemic Structures.. 18 2.2.3 Differentiation of Spheres of Activity.........................................................24 2.2.4 Reference Problems and Guiding Ideas.......................................................26 2.2.5 Cultural Interaction and Acquisition, Transfer, and Integration Processes...........................................................................................................29 3 The Centre for Advanced Studies’ Aims in the Second Funding Period (2020−2024)..............................................................................................................30 3.1 Regional Expansion and Intercultural Encounter.........................................30 3.2 Systematic Perspectives.....................................................................................37 3.2.1 Critical Junctures and Path Probabilities.....................................................37 3.2.2 Culturalisation of Religion, Materiality of the Secular...............................38 3.2.3 Art, Culture, and Architecture as Spheres of Activity................................42 4 Bibliography..............................................................................................................4

T-Reqs: Tool Support for Managing Requirements in Large-Scale Agile System Development

T-Reqs is a text-based requirements management solution based on the git version control system. It combines useful conventions, templates and helper scripts with powerful existing solutions from the git ecosystem and provides a working solution to address some known requirements engineering challenges in large-scale agile system development. Specifically, it allows agile cross-functional teams to be aware of requirements at system level and enables them to efficiently propose updates to those requirements. Based on our experience with T-Reqs, we i) relate known requirements challenges of large-scale agile system development to tool support; ii) list key requirements for tooling in such a context; and iii) propose concrete solutions for challenges.Comment: Accepted for publication in Proc. of 26th IEEE Int. Requirements Eng. Conf., Demo Track, Banff, Alberta, Canada, 201

Research Programme of the HCAS 'Multiple Secularities - Beyond the West, Beyond Modernities

The project seeks to explore the boundaries that distinguish between the religious and non-religious, in modern as well as pre-modern societies. In doing so, we are aligning ourselves with current debates but we are approaching the debated issues from a basic theoretical perspective. At present, a general distinction can be drawn between three narratives: The first claims the dwindling presence and relevance of religion (“secularisation”); the second regards religion to be returning globally, consequently irritating the self-perception of modern societies (“return of religions”, “post-secular society”). According to the third, religion has always been present and has simply changed shape, meaning secularisation assumptions are misleading (“invisible religion”). There is also a theoretical-methodological conflict to be taken into consideration. Where the secularisation hypothesis considers its theories and methods to be universally applicable, the critics of this theory not only increasingly challenge the transferability of Western development paths, but also the transferability of the concepts used. This applies right down to the challenge of the religious/secular dual, which is understood to be an expression of Western experience and power of interpretation that forces other cultures into Western schematisations. In contrast, we are formulating an alternative position, in which we are trying to explore the boundaries between the religious and non-religious beyond normative concepts. We are particularly seeking such boundaries in regions that differ greatly from the so-called “West” in the “Modern World” in terms of culture and history: In various Asian regions and – partly overlapping with these – in the so-called “Islamic World”, but also in different epochs. This is linked to a plea for comparability across multifaceted regions and cultural contexts, and for investigating their entangled history

Why and How to Balance Alignment and Diversity of Requirements Engineering Practices in Automotive

In large-scale automotive companies, various requirements engineering (RE) practices are used across teams. RE practices manifest in Requirements Information Models (RIM) that define what concepts and information should be captured for requirements. Collaboration of practitioners from different parts of an organization is required to define a suitable RIM that balances support for diverse practices in individual teams with the alignment needed for a shared view and team support on system level. There exists no guidance for this challenging task. This paper presents a mixed methods study to examine the role of RIMs in balancing alignment and diversity of RE practices in four automotive companies. Our analysis is based on data from systems engineering tools, 11 semi-structured interviews, and a survey to validate findings and suggestions. We found that balancing alignment and diversity of RE practices is important to consider when defining RIMs. We further investigated enablers for this balance and actions that practitioners take to achieve it. From these factors, we derived and evaluated recommendations for managing RIMs in practice that take into account the lifecycle of requirements and allow for diverse practices across sub-disciplines in early development, while enforcing alignment of requirements that are close to release.Comment: 19 page