Formal Service-Oriented Development of Fault Tolerant Communicating Systems

Laibinis, Linas; Troubitsynå, Elena; Leppänen, Sari; Lilius, Johan; Malik, Qaisar A.

doi:10.1007/11916246_14

Cited by 6 publications

(2 citation statements)

References 9 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Use of refinement and decomposition rules in the development of telecommunications systems is outlined in [11]. The refinement approach of Event-B has also been used for the formal development of fault-tolerant communication systems [24] and fault-tolerant agent systems [23]. Other important work carried out using the refinement approach include verification of the IEEE 1394 tree protocol distributed algorithm [5], development of a secure communication system [13], development of a train system [2], verification of one copy equivalence criterion in a distributed database system [38].…”

Section: Related Workmentioning

confidence: 99%

Formal Development of a Total Order Broadcast for Distributed Transactions Using Event-B

Yadav

Butler

2009

Methods, Models and Tools for Fault Tolerance

View full text Add to dashboard Cite

Abstract. In a replicated database system, copies of the database are kept across several sites for fault-tolerance and availability. Data access in such systems is usually done within a transactional framework. A readonly transaction accesses data locally and an update transaction modifies the database at all sites. Total order broadcast primitives have been proposed to support transactions and allow fault-tolerant cooperation between the sites in a distributed system. In this paper, we identify and analyze the problem of formation of deadlocks among conflicting update transactions due to race conditions and outline how a system of total order broadcast prevents deadlocks and transaction failures. Later we outline how a refinement based approach with Event-B can be used for formal development of the models of total order broadcast. In this approach we begin with the abstract model of a total order broadcast and verify that the required ordering properties are preserved by the system. Subsequently, in a series of refinement steps we outline how an abstract total order can correctly be implemented by using a notion of sequence number. This technique requires us to discharge proof obligations due to consistency and refinement checking. To discharge the proof obligations we are required to discover invariants that describes the relationship between the abstract total order and the underlying mechanism.

show abstract

Section: Related Workmentioning

confidence: 99%

Formal Development of a Total Order Broadcast for Distributed Transactions Using Event-B

Yadav

Butler

2009

Methods, Models and Tools for Fault Tolerance

View full text Add to dashboard Cite

show abstract

“…Some, but not all of the consistency rules for the modeling concepts and for their relationships are checked by the wizards. In future, the work done for formalizing and implementing the correct-by-construction paradigm for Lyra (see for example (Ilic et al, 2006) (Leppänen et al, 2005) (Laibinis et al, 2005a) (Laibinis et al, 2005b) (Laibinis et al, 2006)) will be implemented as a part of the automation approach. This increases significantly the coverage of consistency checking, and enhances the approach with automated generation of fault tolerance properties to the system models.…”

Section: Experiencesmentioning

confidence: 99%

Workflow Automation for System Architecting

Turunen

Leppänen

2008

Proceedings of the Third International Conference on Evaluation of Novel Approaches to Software Engineering

View full text Add to dashboard Cite

Managing the ever-growing complexity of even mass-market products, such as mobile phones, is becoming increasingly hard without the adoption of improved system development methods, such as model-based development. To allow industrial use of such methods, tools that are able automate development tasks as far as possible are needed. In this paper, we present a partly automated system design flow based on the Lyra method with UML 2.0 language and Telelogic Tau G2 modeling tool. We discuss how the tool was extended to support automation of some central tasks in Lyra and show a running example of the design flow. In the example, a telephony functionality of a mobile device is modeled producing an executable specification for the system. The efficiency gains from the automation are promising.

show abstract