Safety-Critical Systems and Agile Development: A Mapping Study

In the last decades, agile methods had a huge impact on how software is developed. In many cases, this has led to significant benefits, such as quality and speed of software deliveries to customers. However, safety-critical systems have widely been dismissed from benefiting from agile methods. Products that include safety critical aspects are therefore faced with a situation in which the development of safety-critical parts can significantly limit the potential speed-up through agile methods, for the full product, but also in the non-safety critical parts. For such products, the ability to develop safety-critical software in an agile way will generate a competitive advantage. In order to enable future research in this important area, we present in this paper a mapping of the current state of practice based on {a mixed method approach}. Starting from a workshop with experts from six large Swedish product development companies we develop a lens for our analysis. We then present a systematic mapping study on safety-critical systems and agile development through this lens in order to map potential benefits, challenges, and solution candidates for guiding future research.Comment: Accepted at Euromicro Conf. on Software Engineering and Advanced Applications 2018, Prague, Czech Republi

Towards a Formalism-Based Toolkit for Automotive Applications

The success of a number of projects has been shown to be significantly improved by the use of a formalism. However, there remains an open issue: to what extent can a development process based on a singular formal notation and method succeed. The majority of approaches demonstrate a low level of flexibility by attempting to use a single notation to express all of the different aspects encountered in software development. Often, these approaches leave a number of scalability issues open. We prefer a more eclectic approach. In our experience, the use of a formalism-based toolkit with adequate notations for each development phase is a viable solution. Following this principle, any specific notation is used only where and when it is really suitable and not necessarily over the entire software lifecycle. The approach explored in this article is perhaps slowly emerging in practice - we hope to accelerate its adoption. However, the major challenge is still finding the best way to instantiate it for each specific application scenario. In this work, we describe a development process and method for automotive applications which consists of five phases. The process recognizes the need for having adequate (and tailored) notations (Problem Frames, Requirements State Machine Language, and Event-B) for each development phase as well as direct traceability between the documents produced during each phase. This allows for a stepwise verification/validation of the system under development. The ideas for the formal development method have evolved over two significant case studies carried out in the DEPLOY project

Developing a distributed electronic health-record store for India

The DIGHT project is addressing the problem of building a scalable and highly available information store for the Electronic Health Records (EHRs) of the over one billion citizens of India

In-plant logistics systems modeling with SysML

Up till now Systems Modeling Language (SysML) has mostly been used to model physical systems of interest. This paper shows how SysML can also be used to represent an abstract model. In this application a mathematical cost model is represented using the SysML plugin for the software MagicDraw. ParaMagic, a plugin in MagicDraw supplementary to SysML, links to Mathematica to solve the model. SysML is a formal language and offers a very intuitive graphical representation. It is therefore a useful medium to create a domain specific language for a field of knowledge. The comprehensiveness of the language, which makes it possible to incorporate specification, analysis, design, verification, and validation of systems, makes it a very valuable tool for collaboration on large projects

Automated analysis of feature models: Quo vadis?

Feature models have been used since the 90's to describe software product lines as a way of reusing common parts in a family of software systems. In 2010, a systematic literature review was published summarizing the advances and settling the basis of the area of Automated Analysis of Feature Models (AAFM). From then on, different studies have applied the AAFM in different domains. In this paper, we provide an overview of the evolution of this field since 2010 by performing a systematic mapping study considering 423 primary sources. We found six different variability facets where the AAFM is being applied that define the tendencies: product configuration and derivation; testing and evolution; reverse engineering; multi-model variability-analysis; variability modelling and variability-intensive systems. We also confirmed that there is a lack of industrial evidence in most of the cases. Finally, we present where and when the papers have been published and who are the authors and institutions that are contributing to the field. We observed that the maturity is proven by the increment in the number of journals published along the years as well as the diversity of conferences and workshops where papers are published. We also suggest some synergies with other areas such as cloud or mobile computing among others that can motivate further research in the future.Ministerio de Economía y Competitividad TIN2015-70560-RJunta de Andalucía TIC-186

Transferring Collective Knowledge: Collective and Fragmented Teaching and Learning in the Chinese Auto Industry

Collective knowledge, consisting of tacit group-embedded knowledge, is a key element of organizational capabilities. This study undertakes a multiple-case study of the transfer of collective knowledge, guided by a set of tentative constructs and propositions derived from organizational learning theory. By focusing on the group-embeddedness dimension of collective knowledge, we direct our attention to the source and recipient communities. We identify two sets of strategic choices concerning the transfer of collective knowledge: collective vs. fragmented teaching, and collective vs. fragmented learning. The empirical context of this study is international R&D capability transfer in the Chinese auto industry. From the case evidence, we find the expected benefits of collective teaching and collective learning, and also discover additional benefits of these two strategies, including the creation of a bridge network communication infrastructure. The study disclosed other conditions underlying the choice of strategies of transferring collective knowledge, including transfer effort and the level of group-embeddedness of the knowledge to be taught or re-embedded. The paper provides a group-level perspective in understanding organizational capabilities, as well as a set of refined constructs and propositions concerning strategic choices of transferring collective knowledge. The study also provides a rich description of the best practices and lessons learned in transferring organizational capabilities.http://deepblue.lib.umich.edu/bitstream/2027.42/39804/3/wp420.pd

Lifecycle Management of Automotive Safety-Critical Over the Air Updates: A Systems Approach

With the increasing importance of Over The Air (OTA) updates in the automotive field, maintaining safety standards becomes more challenging as frequent incremental changes of embedded software are regularly integrated into a wide range of vehicle variants. This necessitates new processes and methodologies with a holistic view on the backend, where the updates are developed and released

Comparative study of design: application to Engineering Design

A recent exploratory study examines design processes across domains and compares them. This is achieved through a series of interdisciplinary, participative workshops. A systematic framework is used to collect data from expert witnesses who are practising designers across domains from engineering through architecture to product design and fashion, including film production, pharmaceutical drugs, food, packaging, graphics and multimedia and software. Similarities and differences across domains are described which indicate the types of comparative analysis we have been able to do from our data. The paper goes further and speculates on possible lessons for selected areas of engineering design which can be drawn from comparison with processes in other domains. As such this comparative design study offers the potential for improving engineering design processes. More generally it is a first step in creating a discipline of comparative design which aims to provide a new rich picture of design processes