Verifying the correct composition of distributed components: Formalisation and Tool

Abstract

This article provides formal definitions characterizing well-formed composition of components in order to guarantee their safe deployment and execution. Our work focuses on the structural aspects of component composition; it puts together most of the concepts common to many component models, but never formalized as a whole. Our formalization characterizes correct component architectures made of functional and non-functional aspects, both structured as component assemblies. Interceptor chains can be used for a safe and controlled interaction between the two aspects. Our well-formed components guarantee a set of properties ensuring that the deployed component system has a correct architecture and can run safely. Finally, those definitions constitute the formal basis for our Eclipsebased environment for the development and specification of component-based applications.

Dealing with crosscutting and dynamic features in component software using aspect‐orientation: requirements and experiences

“…Following the symmetrical approach, SpringAOP aspects [53] are connections of two kinds of Java beans: pointcuts and interceptors: pointcut beans describe the interaction points and match intercepted calls at runtime; interceptor beans implement one or more aspect advices. In AOKell [63] and GCM [59], aspects are regular components associated with the container of functional components.…”

Monitoring as-a-service to drive more efficient future system design

“…These components can then be connected with other components within the same membrane or with non-functional interfaces of other components. This structure has been precisely and formally specified [48,49].…”

Integrated Environment for Verifying and Running Distributed Components

“…VerCors 4 is a software platform which aims at supporting the creation of safe distributed component-based applications. VerCors 5 includes a set of graphical designers based on UML where the user can specify the architecture and the business logic of his application, and check the static correctness of the component architecture [1]. The specification is then automatically transformed into a behavior graph that can be model-checked to prove its correctness.…”

“…Generated Java code of message1 B o o l e a n i s A c t i v e = n u l l ; 2 I n t e g e r l e f t = null , max = null , cnum = n u l l ; 3 S t a t e c u r S t a t e = S t a t e . I n i t i a l ;4 while ( true ) { 5 switch ( c u r S t a t e ) { 6. .…”