Anila Mjeda

UTP Semantics for Shared-State, Concurrent, Context-Sensitive Process Models

Process Modelling Language (PML) is a notationfor describing software development and business processes. It takes the form of a shared-state concurrent imperative language describing tasks asactivities that require resources to startand provide resources when they complete. Its syntax covers sequential composition, parallelism, iteration and choice, but without explicit iteration and choice conditions. It is intended to support a range of context-sensitive interpretations, from a rough guide for intended behaviour, to being very prescriptive about the order in which tasks must occur. We are using Unifying Theories of Programming (UTP) to modelthis range of semantic interpretations, with formal links between them, typically of the nature of a refinement. We address a number of challenges that arise when trying to developa compositional semantics for PML and its shared-state concurrent underpinnings, most notably in how UTP observations need to distinguishbetween dynamic state-changes and static context parameters. The formal semantics are intended as the basis for tool support for process analysis, with applicationsin the healthcare domain, covering such areas as healthcare pathwaysand software development and certification processesfor medical device software.

Requirement-centric reactive testing for safety-related automotive software

We propose a test reactivity taxonomy for embedded automotive software that a tester can use to align the process of test design with the requirements specification and verification of the project at hand. The proposed test reactivity taxonomy can be used to explore, identify and design the right types of test reactivity which target a specific functional or non-functional requirement or an application-specific situation. The taxonomy can also be used to document software testing decisions and enable discussions between the relevant stakeholders. The ordering of information provided by the taxonomy could also be a starting point into identifying relationships, patterns and factors that influence the relevance of different reactivity dimensions.

Model-Based Testing Design for Embedded Automotive Software

The ever increasing complexity of embedded automotive software is not matched by the current development and test processes of automotive embedded software and the latter have become the limiting factor. A model-based software development and testing approach has the potential to reduce software development times, to produce executable specifications very early in the process as well as facilitate automatic code generation. Not surprisingly, the above are regarded as highly beneficial for the automotive industry. The automotive industry is increasingly using modelbased testing techniques. Despite this, model-based testing tends to be done in a bespoke and nonsystematic fashion [1] and easy to use, high quality, formalised, model-based testing methodologies that cater for the specific needs of in-vehicle software are hard to find. This paper proposes a systematic model-based testing design approach which builds on previous work on systematic model-based testing for embedded automotive software [2], [3], [4]. The testing design is based on the functional requirements for the system under test and the test data are generated via two different and independent routes.

Decision spaces in product lines, decision analysis, and design exploration: an interdisciplinary exploratory study

Context. From recent works on product properties resulting from configurations and the optimisation of these properties, one comes quickly to more complex challenges such as multi-objective optimisation, conflicting objectives, multiple stakeholders, and conflict resolution. The intuition is that Software Product Line Engineering (SPLE) can draw from other disciplines that deal with decision spaces and complex decision scenarios. Objectives. We aim to (1) explore links to such disciplines, (2) systematise and compare concepts, and (3) identify opportunities, where SPLE approaches can be enriched. Method. We undertake an exploratory study: Starting from common SPLE activities and artefacts, we identify aspects where we expect to find corresponding counterparts in other disciplines. We focus on Multiple Criteria Decision Analysis (MCDA), Multi-Objective Optimisation (MOO), and Design Space Exploration (DSE), and perform a comparison of the key concepts. Results. The resulting comparison relates SPLE activities and artefacts to concepts from MCDA, MOO, and DSE and identifies areas where SPLE approaches can be enriched. We also provide examples of existing work at the intersections of SPLE with the other fields. These findings are aimed to foster the conversation on research opportunities where SPLE can draw techniques from other disciplines dealing with complex decision scenarios.

Can Formal Methods Make Automotive Business Sense? A Classification of Formal Methods by Usefulness

Legislative bodies are directing that automotive products comply with stringent safety levels. The liability for the safety of passengers in an automobile has traditionally been quite complex. Other transport sectors are externally regulated, and liability lies with the manufacturer or the transport service provider. The automotive industry is self-regulated and the individual driver carries a significant liability. Software and electronics increasingly provide greater control of automotive safety, possibly reducing driver liability, and increasing the need for more formal software development methods. The automotive business model, however, also presents challenges to the effective use of formal methods. An automotive design change costing €600 per vehicle could consume 100% of gross margin. In aviation, this cost represents 0.01% of gross margin. [1] [2]. The automotive industry is responding to the increasing impact of automotive software with the development of standards such as AUTOSAR [3], and EU funded projects such as ATESST [4] and EASIS [5]. They propose architectures which might deliver the benefits of best software engineering practice to the industry. In terms of safety, they recommend existing accepted standards such as IEC61508 [6], which stipulates various formal methods for the development of safetycritical software. However, IEC61508 does not compare specific formal methods in terms of their suitability to industry. This paper discusses the suitability for industry of formal methods of specification and verification. It provides a classification which looks at categories such as commercialization; capacity to solve industry-scale problems; cost effectiveness, etc. The paper looks at the relevance of the classification in terms of the challenges and constraints of the automotive domain and discusses how it might facilitate the engineer to make design decisions which improve safety in a cost effective manner.

The AUTOSAR standard – the experience of applying Simulink according to its requirements

Software has become the driving force behind innovation in the automotive industry. According to a recent Frost & Sullivan market research report, “Strategic Analysis of the European Market for Software in Passenger Cars”, the software for passenger cars in Europe accounted for 5.8% of the cost of vehicles in 2004. The same report projects an annual growth rate (CAGR) of 15.5% until 2011, when software is expected to represent 11.0% of the cost of vehicles. This paper discusses the emerging AUTOSAR standard (AUTOSAR release 2.0), which aims to address the need for more efficient E/E (Embedded Electronic) automotive architecture solutions. The paper also provides a review of the mapping of a few key AUTOSAR concepts to their Simulink counterparts, which should help designers using Simulink deliver AUTOSAR compatible solutions. Finally the paper features a component of an experimental engine management system that has been remodeled in Simulink to conform to the AUTOSAR requirements.