Specifying embedded systems with statecharts and Z: an agenda for cyclic software components

Grieskamp, Wolfgang; Heisel, Maritta; Dörr, Heiko

doi:10.1016/s0167-6423(00)00024-1

Cited by 14 publications

(6 citation statements)

References 32 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…We propose a method for the development of mixed systems, that helps the specifier providing means to structure the system in terms of communicating subcomponents and to give the sequential components using a semi-automatic concurrent automata generation with associated algebraic data types. A previous version of our method [21] is described in terms of the agenda 2 concept [12,14]. The method presented here is refined and accompanied with the use of visual diagrams.…”

Section: A Methods For the Specification Of Mixed Componentsmentioning

confidence: 99%

Specification of Mixed Systems in Korrigan with the Support of a UML-Inspired Graphical Notation

Choppy

Poizat

Royer

2001

Fundamental Approaches to Software Engineering

View full text Add to dashboard Cite

Our Korrigan formalism is devoted to the structured formal specification of mixed systems through a model based on a hierarchy of views [4,20]. In our unifying approach, views are used to describe the different aspects of a component (both internal and external structuring). We propose a semi-formal method with guidelines for the development of mixed systems, that helps the specifier providing means to structure the system in terms of communicating subcomponents and to describe the sequential components. While there is growing interest for having both textual and graphical notations for a given formalism, we introduce composition diagrams, a UML-inspired graphical notation for Korrigan, associated with the various steps of our method. We shall show how our method is applied to develop a Korrigan specification (both in textual and graphical notation) and illustrate this approach on a case study. 125 ing well-accepted semi-formal notations and use them as a graphical means to improve the readability of formal languages and concepts. In order to be close to the UML, we select a subset of UML that is relevant to illustrate concepts of our approach. We also extend/modify it when needed. For instance (Fig. 8), we use a simple class diagram together with informations related to the possible communications (its interface) of the component. The interface symbols 3 we use are described in Figure 7. synchronous communication asynchronous communication communication TO a T component T communication FROM a T component T communication with a T component

show abstract

Section: A Methods For the Specification Of Mixed Componentsmentioning

confidence: 99%

Specification of Mixed Systems in Korrigan with the Support of a UML-Inspired Graphical Notation

Choppy

Poizat

Royer

2001

Fundamental Approaches to Software Engineering

View full text Add to dashboard Cite

show abstract

“…This class is referred to as cyclic software components (cf. [GHD98], [MK99]). In the world of automotive controls it is very common for a software function to be based on an initialization and step function.…”

Section: Cyclic Software Componentsmentioning

confidence: 99%

Evolutionary Safety Testing of Embedded Control Software by Automatically Generating Compact Test Data Sequences

Pohlheim

Conrad

Griep

2005

SAE Technical Paper Series

View full text Add to dashboard Cite

Whereas the verification of non-safety-related, embedded software typically focuses on demonstrating that the implementation fulfills its functional requirements, this is not sufficient for safety-relevant systems. In this case, the control software must also meet application-specific safety requirements.Safety requirements typically arise from the application of hazard and/or safety analysis techniques, e.g. FMEA, FTA or SHARD. During the downstream development process it must be shown that these requirements cannot be violated. This can be achieved utilizing different techniques. One way of providing evidence that violations of the safety properties identified cannot occur is to thoroughly test each of the safety requirements. This paper introduces Evolutionary Safety Testing (EST), a fully automated procedure for the safety testing of embedded control software. EST employs extended evolutionary algorithms in an optimization process which aggressively tries to find test data sequences that cause the test object to violate a given safety requirement.A compact description formalism for input sequences for safety testing is presented, which is compatible with description techniques used during other test process stages. This compact description allows 1) an efficient application of evolutionary algorithms (and other optimization techniques) and 2) the description of long test sequences necessary for the adequate stimulation of real-world systems. The objective function is designed in such a way that optimal values represent test data sequences which violate a given safety requirement. By means of repeated input sequence generation, software execution and the subsequent evaluation of the objective function each safety requirement is extensively tested.The use of EST for the safety testing of automotive control software is demonstrated using safety requirements of an adaptive cruise control (ACC) system.The EST approach can easily be integrated into an overall software test strategy which combines different test design techniques with specific test objectives.

show abstract

“…Agendas [Hei97] are a possible way of realising the explicit, fine-grained representation of methodical knowledge in the form of sequences of steps listed in a table. Each step can be characterised in more detail by means of application-independent validation conditions [GHD98]. Furthermore, the steps can also be supplemented with references to guidance, for instance in the form of templates.…”

Section: Figure 5 Instantiation Of the Interdisciplinary Information mentioning

confidence: 99%

8.3.1 Towards an Integrated Methodology for the Model‐based Development of Embedded Automotive Control Software

Buhr

Conrad

Dörr

et al. 2005

INCOSE International Symp

Self Cite

View full text Add to dashboard Cite

The complexity of developing automotive control unit software can generally not be mastered without an efficient development methodology. The development discipline activities requirements, modelling / implementation and quality assurance are, for this reason, supported by individual methods. In order to optimally coordinate the methods with one another during their deployment, a structured integration of these individual specialised methods is, however, essential. The following paper, using the model‐based development approach as an example, outlines the content and structure of an integrated methodology that provides such integration. Its use shortens development time and increases product quality by coordinating the deployment of individual methods over the course of the entire developmental process. The main components of this kind of integrated methodology are an interdisciplinary information model, process models with integrated procedures for the realisation of single development activities as well as guidance such as checklists, templates, and examples, among other things. In this paper, we present the experiences that we have gained at DaimlerChrylser Research in developing and applying such an integrated methodology1.

show abstract

Specifying embedded systems with statecharts and Z: an agenda for cyclic software components

Cited by 14 publications

References 32 publications

Specification of Mixed Systems in Korrigan with the Support of a UML-Inspired Graphical Notation

Specification of Mixed Systems in Korrigan with the Support of a UML-Inspired Graphical Notation

Evolutionary Safety Testing of Embedded Control Software by Automatically Generating Compact Test Data Sequences

8.3.1 Towards an Integrated Methodology for the Model‐based Development of Embedded Automotive Control Software

Contact Info

Product

Resources

About