A formal notation and tool for the engineering of CORBA systems

Bastide, Rémi; Sy, Ousmane; Palanque, Philippe

doi:10.1002/1096-9128(20001210)12:14<1379::aid-cpe514>3.0.co;2-b

Cited by 13 publications

(3 citation statements)

References 18 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…It uses concepts borrowed from the object-oriented approach (dynamic instantiation, classification, encapsulation, inheritance, client/server relationship) to describe the structural or static aspects of interactive systems, and uses high-level Petri nets [7] to describe their dynamic or behavioural aspects. As an extension of the Cooperative Objects formalisms it has been designed to describe behavioural aspects of objects-based distributed systems [4]. The formalism is able to handle the specific aspects of interactive systems.…”

Section: Using Ico Formal Modeling To Design Interactive Cockpitsmentioning

confidence: 99%

Fault-Tolerant Interactive Cockpits for Critical Applications: Overall Approach

Fayollas¹,

Fabre²,

Navarre³

et al. 2012

Lecture Notes in Computer Science

Self Cite

View full text Add to dashboard Cite

The deployment of interactive facilities in avionic digital cockpits for critical applications is a challenge today. The dependability of the user interface and its related supporting software must be consistent with the criticality of the functions to be controlled. The approach proposed in this paper aims at describing how fault prevention and fault tolerance techniques can be combined to address this challenge. Following the ARINC 661 standard, a model-based development of interactive objects (namely widgets and layers) aims at providing zero-default software. Regarding remaining software faults in the underlying runtime support and also physical faults, the approach is based on fault tolerance design patterns, like self-checking components and replication techniques. The proposed solution relies on the space and time partitioning provided by the executive support following the ARINC 653 standard. Defining and designing resilient interactive cockpits is a necessity in the near future as these command and control systems provide a great opportunity to improve maintenance and evolutivity of avionic systems.

show abstract

Section: Using Ico Formal Modeling To Design Interactive Cockpitsmentioning

confidence: 99%

Fault-Tolerant Interactive Cockpits for Critical Applications: Overall Approach

Fayollas¹,

Fabre²,

Navarre³

et al. 2012

Lecture Notes in Computer Science

Self Cite

View full text Add to dashboard Cite

show abstract

“…Interaction design concepts have been studied in the area of reference models (such as ITU-T 1995ITU-T , 1999, design languages (such as Bastide et al 2000;ITU-T 2002;OMG 2003OMG , 2004Quartel et al 2002;van Sinderen et al 1992) and architectural description languages (such as Allan and Garlan 1997;Luckham and Vera 1995). The work presented in this paper is not meant to be another set of interaction design concepts.…”

Section: Related Workmentioning

confidence: 99%

The adequacy of languages for representing interaction mechanisms

2007

View full text Add to dashboard Cite

This paper presents criteria for the adequacy of languages to represent interaction mechanisms. It then uses these criteria to analyse the adequacy of UML. We focus on the interaction mechanisms provided by Web Services technology and by CORBA for request/response, callback, polling and (multicast) message passing. We argue that the criteria for adequacy of a design language are that the language should: (1) be expressive enough to represent the mechanisms; (2) be easy to use when expressing them; (3) be platform independent in the sense that it does not force implementation decisions for a mechanism; and (4) behave corresponding to the mechanisms that it represents. We show that these criteria follow logically from the use of a design language in the design process. For UML we evaluate the first three criteria in a qualitative manner. To evaluate the fourth criteria, we present Coloured Petri Nets that capture the behaviour of both the mechanisms precisely and the UML constructs that represent them. Subsequently, we check the correspondence of their behaviour.

show abstract

“…These tests expose the non-interoperability of some implementations which trace back, on one hand, to the original specification's incompleteness and, on the other hand, to mistakes in the implementation. The authors propose that the first cause be corrected by the use of a formalism suited to the needs of CORBA systems (like the Petri nets based Cooperative Objects formalism [2]), and the second by the provision of test cases with the original specification.…”

Section: Towards Components That Plug and Play (R Bastide O Sy)mentioning

confidence: 99%

New Issues in Object Interoperability

Vallecillo

Núñez

Troya

2000

Object-Oriented Technology

View full text Add to dashboard Cite

Abstract. This report summarizes the presentations, discussions, and outcomes of the ECOOP'2000 Workshop on Object Interoperability, held in Sophia Antipolis, France, on Monday, June 12, 2000. Divided into four main sessions, the workshop covered some of the most important issues related to object interoperability at different levels (such as protocols or semantics). This report has two main goals. First, it tries to provide a snapshot of some of the current research being carried out within the object-oriented community in these areas. And second, it summarizes some of the open questions and issues related to object interoperability, in order to set the basis for further research activities.

show abstract

A formal notation and tool for the engineering of CORBA systems

Cited by 13 publications

References 18 publications

Fault-Tolerant Interactive Cockpits for Critical Applications: Overall Approach

Fault-Tolerant Interactive Cockpits for Critical Applications: Overall Approach

The adequacy of languages for representing interaction mechanisms

New Issues in Object Interoperability

Contact Info

Product

Resources

About