238 research outputs found
Proceedings of the 2007 Workshop on Engineering Fault Tolerant Systems, EFTS 2007, Dubrovnik, Croatia, September 4, 2007
No full text
Proceedings of the 2008 RISE/EFTS Joint International Workshop on Software Engineering for Resilient Systems, Newcastle Upon Tyne — November 17 - 19, 2008
No full textFrameworks for designing and implementing dependable systems using Coordinated Atomic Actions: A comparative study
No full textpeer reviewedThis paper presents ways of implementing dependable distributed applications designed using the Coordinated Atomic Action (CAA) paradigm. CAAs provide a coherent set of concepts adapted to fault tolerant distributed system design that includes structured transactions, distribution, cooperation, competition, and forward and backward error recovery mechanisms triggered by exceptions. DRIP (Dependable Remote Interacting Processes) is an efficient Java implementation framework which provides support for implementing Dependable Multiparty Interactions (DMI). As DMIs have a softer exception handling semantics compared with the CAA semantics, a CAA design can be implemented using the DRIP framework. A new framework called CAA-DRIP allows programmers to exclusively implement the semantics of CAAs using the same terminology and concepts at the design and implementation levels. The new framework not only simplifies the implementation phase, but also reduces the final system size as it requires less number of instances for creating a CAA at runtime. The paper analyses both implementation frameworks in great detail, drawing a systematic comparison of the two. The CAAs behaviour is described in terms of Statecharts to better understand the differences between the two frameworks. Based on the results of the comparison, we use one of the frameworks to implement a case study belonging to the e-health domain
Resolving Architectural Mismatches of COTS Through Architectural Reconciliation
No full textThe integration of COTS components into a system under development entails architectural mismatches. These have been tackled, so far, at the component level, through component adaptation techniques, but they also must be tackled at an architectural level of abstraction. In this paper we propose an approach for resolving architectural mismatches, with the aid of architectural reconciliation. The approach consists of designing and subsequently reconciling two architectural models, one that is forward-engineered from the requirements and another that is reverse-engineered from the COTS-based implementation. The final reconciled model is optimally adapted both to the requirements and to the actual COTS-based implementation. The contribution of this paper lies in the application of architectural reconciliation in the context of COTS-based software development. Architectural modeling is based upon the UML 2.0 standard, while the reconciliation is performed by transforming the two models, with the help of architectural design decisions.
Hierarchical Algebraic Nets
No full textHierarchical Algebraic Nets (HANs ) presented here introduce a new algebraic net class which inherits from a five years experience on algebraic nets corresponding to the work done on the specification formalism CO-OPN [BG 91a]. These works has led to a complete specification formalim supported by a software environnement called SANDS [BFR 93] but who makes obsolete the initial theoretical work done in [BG 91a]. The hierarchical algebraic nets are defined : to answer to the major critics which can be made on CO-OPN and to introduce a specification formalism as a new structured algebraic net class. New features such as the recursive calls of methods or the local association of the data structures specification are some of the major new concepts. The paper essentially defines the syntax and the semantics of the hierarchical algebraic nets in a similar way as it is done for hierachical algebraic specifications which simplify the whole complexity of the formalism. The last part shows how HANs can be used in order to cover the lack of formal semantics to SANDS specifications and what can be the possible evolutions or use of such formalism. For example, HANs have shown their semantical utility through their use to give a formal semantics to a purely Object Oriented evolution of CO-OPN [BB 94a]. Keywords : Higher-level net models, specification, structured specification, semantics, algebraic abstract data types.LG
A Generic Framework for the Engineering of Self-Adaptive and Self-Organising Systems
No full textThis paper provides a unifying view for the engineering of
self-adaptive (SA) and self-organising (SO) systems. We first
identify requirements for designing and building trustworthy
self-adaptive and self-organising systems. Second, we propose a
generic framework combining design-time and run-time features,
which permit the definition and analysis at design-time of
mechanisms that both ensure and constrain the run-time behaviour of
an SA or SO system, thereby providing some assurance of its self-*
capabilities. We show how this framework applies to both an SA
and an SO system, and discuss several current proof-of-concept
studies on the enabling technologies
- …
