Fault in the Future

Johnsen, Einar Broch; Lanese, Ivan; Zavattaro, Gianluigi

doi:10.1007/978-3-642-21464-6_1

Cited by 4 publications

(4 citation statements)

References 16 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…there is a unique compensation stack that is updated by each action. The above studies have been applied to provide formal support to standard technologies for web services [12,25,15,2] and to develop provably correct engines for transactional workflows [4,18,22,19].…”

Section: Discussionmentioning

confidence: 99%

LTS Semantics for Compensation-Based Processes

Bruni

Kauer

2013

Trustworthy Global Computing

View full text Add to dashboard Cite

Business processes design is an error-prone task often relying on long-running transactions with compensations. Unambiguous formal semantics and flexible verification tools should be used for early validation of processes. To this aim, we define a small-step semantics for the Sagas calculus according to the so-called "coordinated interruption" policy. We show that it can be tuned via small changes to deal with other compensation policies and discuss possible enhancements.

show abstract

Section: Discussionmentioning

confidence: 99%

LTS Semantics for Compensation-Based Processes

Bruni

Kauer

2013

Trustworthy Global Computing

View full text Add to dashboard Cite

show abstract

“…The exception would be raised only if later on a get on the future is performed. This approach requires to put the fault notification inside the future, and has been explored in the context of ABS in [18]. Indeed, this is also the approach of Java future library (asynchronous computation with futures has been standardized in a Java library since Java SE 5 [11]).…”

Section: How Do Faults Propagate?mentioning

confidence: 99%

“…If the execution already completed, one may do nothing or execute some code to compensate the terminated execution. This second option has been explored in [18]. The most interesting case is the one where the invoked process is running.…”

Section: How Do Faults Propagate?mentioning

confidence: 99%

Fault Model Design Space for Cooperative Concurrency

Lanese

Lienhardt

Bravetti

et al. 2014

Leveraging Applications of Formal Methods, Verification and Validation. Specialized Techniques and Applications

Self Cite

View full text Add to dashboard Cite

This paper critically discusses the different choices that have to be made when defining a fault model for an object-oriented programming language. We consider in particular the ABS language, and analyze the interplay between the fault model and the main features of ABS, namely the cooperative concurrency model, based on asynchronous method invocations whose return results via futures, and its emphasis on static analysis based on invariants.

show abstract

“…ABS objects conceptually have the same role as Erlang processes, once the well-known problems of distributed systems [WWWK96] can be addressed in ABS -work towards a distributed exception handling and recovery system is outlined in [JLZ11].…”

Section: Related Workmentioning

confidence: 99%

The ABS tool suite: modelling, executing and analysing distributed adaptable object-oriented systems

Wong¹,

Albert

Muschevici

et al. 2012

Int J Softw Tools Technol Transfer

View full text Add to dashboard Cite

Abstract. Modern software systems must support a high degree of variability to accommodate a wide range of requirements and operating conditions. This paper introduces the Abstract Behavioural Specification (ABS) language and tool suite, a comprehensive platform for developing and analysing highly adaptable distributed concurrent software systems. The ABS language has a hybrid functional and object-oriented core, and comes with extensions that support the development of systems that are adaptable to diversified requirements, yet capable to maintain a high level of trustworthiness. Using ABS, system variability is consistently traceable from the level of requirements engineering down to object behaviour. This facilitates temporal evolution, as changes to the required set of features of a system are automatically reflected by functional adaptation of the system's behaviour. The analysis capabilities of ABS stretch from debugging, observing and simulating to resource analysis of ABS models and help ensure that a system will remain dependable throughout its evolutionary lifetime. We report on the experience of using the ABS language and the ABS tool suite in an industrial case study.

show abstract

Fault in the Future

Cited by 4 publications

References 16 publications

LTS Semantics for Compensation-Based Processes

LTS Semantics for Compensation-Based Processes

Fault Model Design Space for Cooperative Concurrency

The ABS tool suite: modelling, executing and analysing distributed adaptable object-oriented systems

Contact Info

Product

Resources

About