Modeling Dynamic Architectures Using Dy-BIP

Bozga, Marius; Jaber, Mohamad; Maris, Nikolaos; Sifakis, Joseph

doi:10.1007/978-3-642-30564-1_1

Cited by 43 publications

(57 citation statements)

References 14 publications

(17 reference statements)

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Although this formalization is based on the previous work on BIP [4,8,11], it is adapted and extended to reflect the specificities of JavaBIP. Finally, we have designed new examples that we use to illustrate the JavaBIP modelling concepts and evaluate the overhead induced by the engine.…”

Section: Paper Contribution and Structurementioning

confidence: 99%

“…The following example was initially presented in [11]. Although it is inspired by a wireless audio protocol for peer-to-peer communication, it should be noted that this example does not implement any kind of message passing (see also the discussion in Remark 4.2).…”

Section: Trackers and Peers Examplementioning

confidence: 99%

“…However, their use requires the knowledge of all components (hence also all ports) in the system. In JavaBIP, we have opted for a macro notation similar to that introduced in [11]. This notation imposes synchronization constraints based on the component types, rather than on the component instances, allowing for a better separation between component and glue specification.…”

Section: Boolean Encoding Of the Connectors And Macro Notationmentioning

confidence: 99%

“…Table I provides the encodings of all the connectors shown in Figure 9. Similarly to [11], ¶ we use the macro p Require a 1 ; . .…”

Section: Namementioning

confidence: 99%

“…In the constraints (1), this translates by conjuncts of the form ¶ The notation used in [11] differs from JavaBIP in that it uses the additional Unique macro to specify cardinality exactly one, which in JavaBIP is expressed directly in the Require macro. Additionally, in [11] it is not possible to express exact cardinalities larger than one.…”

Section: Namementioning

confidence: 99%

See 4 more Smart Citations

Exogenous coordination of concurrent software components with JavaBIP

et al. 2017

View full text Add to dashboard Cite

SUMMARYA strong separation of concerns is necessary in order to make the design of domain-specific functional components independent from cross-cutting concerns, such as concurrent access to the shared resources of the execution platform. Native coordination mechanisms, such as locks and monitors, allow developers to address these issues. However, such solutions are not modular, they are complex to design, debug and maintain. We present the JavaBIP framework that allows developers to think on a higher level of abstraction and clearly separate the functional and coordination aspects of the system behavior. It implements the principles of the BIP component framework rooted in rigorous operational semantics. It allows the coordination of existing concurrent software components in an exogenous manner, relying exclusively on annotations, component APIs and external specification files. We introduce the annotation and specification syntax of JavaBIP and illustrate its use on realistic examples; present the architecture of our implementation, which is modular and easily extensible; provide and discuss performance evaluation results.

show abstract

Section: Paper Contribution and Structurementioning

confidence: 99%

Section: Trackers and Peers Examplementioning

confidence: 99%

Section: Boolean Encoding Of the Connectors And Macro Notationmentioning

confidence: 99%

“…Table I provides the encodings of all the connectors shown in Figure 9. Similarly to [11], ¶ we use the macro p Require a 1 ; . .…”

Section: Namementioning

confidence: 99%

Section: Namementioning

confidence: 99%

See 3 more Smart Citations

Exogenous coordination of concurrent software components with JavaBIP

et al. 2017

View full text Add to dashboard Cite

show abstract

Programming Dynamic Reconfigurable Systems

Ballouli

Bensalem

Bozga

et al. 2018

Formal Aspects of Component Software

Self Cite

View full text Add to dashboard Cite

DR-BIP is an extension of the BIP component framework intended for programming reconfigurable systems encompassing various aspects of dynamism. It relies on architectural motifs to structure the architecture of a system and to coordinate its reconfiguration at runtime. An architectural motif defines a set of interacting components that evolve according to reconfiguration rules. With DR-BIP, the dynamism can be captured as the interplay of dynamic changes in three independent directions 1) the organization of interactions between instances of components in a given configuration; 2) the reconfiguration mechanisms allowing creation/deletion of components and management of their interaction according to a given architectural motif; 3) the migration of components between predefined architectural motifs which characterizes dynamic execution environments. The paper lays down the formal foundation of DR-BIP, illustrates its expressiveness on few examples and discusses avenues for dynamic reconfigurable system design.

show abstract

DReAM: Dynamic Reconfigurable Architecture Modeling

Nicola

Maggi

Sifakis

2018

Leveraging Applications of Formal Methods, Verification and Validation. Distributed Systems

Self Cite

View full text Add to dashboard Cite

Modern systems evolve in unpredictable environments and have to continuously adapt their behavior to changing conditions. The "DReAM" (Dynamic Reconfigurable Architecture Modeling) framework, has been designed for modeling reconfigurable dynamic systems. It provides a rule-based language, inspired from Interaction Logic, which is expressive and easy to use encompassing all aspects of dynamicity including parametric multi-modal coordination with creation/deletion of components as well as mobility. Additionally, it allows the description of both endogenous/modular and exogenous/centralized coordination styles and sound transformations from one style to the other. The DReAM framework is implemented in the form of a Java API bundled with an execution engine. It allows to develop runnable systems combining the expressiveness of the rule-based notation together with the flexibility of this widespread programming language.

show abstract

Modeling Dynamic Architectures Using Dy-BIP

Cited by 43 publications

References 14 publications

Exogenous coordination of concurrent software components with JavaBIP

Exogenous coordination of concurrent software components with JavaBIP

Programming Dynamic Reconfigurable Systems

DReAM: Dynamic Reconfigurable Architecture Modeling

Contact Info

Product

Resources

About