Reduction and Abstraction Techniques for BIP

Noureddine, Mohamad; Jaber, Mohamad; Bliudze, Simon; Zaraket, Fadi A.

doi:10.1007/978-3-319-15317-9_18

Cited by 9 publications

(7 citation statements)

References 20 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In that sense, our proposal, improves the current state of practice by reducing the number of properties that must be verified. Although additional techniques could be applied to better identify the source of an error, such as fault localisation [76] and reduction [61] techniques for BIP models, or analysis techniques similar to that used for the cone-of-influence reduction [26] 9 , we consider this direction as out of scope of the present paper and leave it for future research.…”

Section: Discussionmentioning

confidence: 99%

Early validation of system requirements and design through correctness-by-construction

Stachtiari

Mavridou

Katsaros

et al. 2018

Journal of Systems and Software

Self Cite

View full text Add to dashboard Cite

The early validation of requirements aims to reduce the need for the high-cost validation testing and corrective measures at late development stages. This work introduces a systematic process for the unambiguous specification of system requirements and the guided derivation of formal properties, which should be implied by the system 's structure and behavior in conjunction with its external stimuli. This rigorous design takes place through the incremental construction of a model using the BIP (Behavior-Interaction-Priorities) component framework. It allows building complex designs by composing simpler reusable designs enforcing given properties. If some properties are neither enforced nor verified, the model is refined or certain requirements are revised. A validated model provides evidence of requirements' consistency and design correctness. The process is semi-automated through a new tool and existing verification tools. Its effectiveness was evaluated on a set of requirements for the control software of the CubETH nanosatellite and an extract of software requirements for a Low Earth Orbit observation satellite. Our experience and obtained results helped in identifying open challenges for applying the method in industrial context. These challenges concern with the domain knowledge representation, the expressiveness of used specification languages, the library of reusable designs and scalability.

show abstract

Section: Discussionmentioning

confidence: 99%

Early validation of system requirements and design through correctness-by-construction

Stachtiari

Mavridou

Katsaros

et al. 2018

Journal of Systems and Software

Self Cite

View full text Add to dashboard Cite

show abstract

“…Behavior Interaction Priority (BIP) [5,42] allows to define systems as sets of atomic components with prioritized interactions. We present components, interactions, priorities, and their composition.…”

Section: Behavior Interaction Priority (Bip)mentioning

confidence: 99%

“…The global view is concerned with the architecture of the system, i.e., the interaction between components and their interfaces, the components are seen as black boxes. We formalize our approach by extending an existing formalism of CBSs: the Behavior Interaction Priority (BIP) framework [5,42]. The BIP component-based framework uses formal operational semantics.…”

Section: Introductionmentioning

confidence: 99%

Modularizing behavioral and architectural crosscutting concerns in formal component-based systems – Application to the Behavior Interaction Priority framework

El-Hokayem¹,

Falcone²,

Jaber³

2018

Journal of Logical and Algebraic Methods in Programming

Self Cite

View full text Add to dashboard Cite

We define a method to modularize crosscutting concerns in Component-Based Systems (CBSs) expressed using the Behavior Interaction Priority (BIP) framework. Our method is inspired from the Aspect Oriented Programming (AOP) paradigm which was initially conceived to support the separation of concerns during the development of monolithic systems. BIP has a formal operational semantics and makes a clear separation between architecture and behavior to allow for compositional and incremental design and analysis of systems. We distinguish local from global aspects. Local aspects model concerns at the component level and are used to refine the behavior of components. Global aspects model concerns at the architecture level, and hence refine communications (synchronization and data transfer) between components. We formalize local and global aspects as well as their composition and integration into a BIP system through rigorous transformation primitives. We present AOP-BIP, a tool for Aspect-Oriented Programming of BIP systems, demonstrate its use to modularize logging, security, and fault tolerance in a network protocol, and discuss its possible use in runtime verification of CBSs. represent different concerns. A concern is defined in [15] as a "domain used as a decomposition criterion for a system or another domain with that concern". Domains include logging, persistence, and system policies such as security. Concerns are often found in different parts of a system, or in some cases multiple concerns overlap one region. These are called crosscutting concerns. Aspect-Oriented Programming (AOP) [34,52] aims at modularizing crosscutting concerns by identifying a clear role for each of them in the system, implementing each concern in a separate module, and loosely coupling each module to only a limited number of other modules. Essentially, AOP defines mechanisms to determine the locations of the concerns in the system execution by introducing joinpoints and pointcuts. Then, it determines what to do at these locations by introducing advices. Finally, it provides a mechanism to coordinate all the advices happening at a location by introducing a process called weaving.Motivations and challenges. In Component Based Systems (CBSs), crosscutting concerns arise at the levels of components [19,37] (building blocks) and architectures (communications). Integrating crosscutting concerns in CBSs allows users to reason about crosscutting concerns in separation, and favors correct-by-construction design. Defining an AOP paradigm for CBSs poses multiple challenges. While the execution of a sequential program can be seen as a sequence of instructions, the semantics of a CBS is generally more complex and relies on a notion of architecture imposing several constraints on their execution. As a consequence of these constraints, AOP matching, instrumentation and modifications need to be extended to account for the architecture (i.e., data transfer and rendez-vous between components). Multiple approaches [44,11,19,37,16] have sought to apply AOP for...

show abstract

“…Behavior Interaction Priority (BIP) [2,20] allows to define systems as sets of atomic components with prioritized interactions. We present components, interactions, priorities, and their composition.…”

Section: Behavior Interaction Prioritymentioning

confidence: 99%

“…Approach. We use the Behavior Interaction Priority (BIP) component-based framework [2,20] with formal operational semantics. Coordination between components is achieved by using multiparty interactions and dynamic priorities for scheduling interactions.…”

Section: Introductionmentioning

confidence: 99%

Modularizing Crosscutting Concerns in Component-Based Systems

El-Hokayem

Falcone

Jaber

2016

Lecture Notes in Computer Science

Self Cite

View full text Add to dashboard Cite

We define a method to modularize crosscutting concerns in the Behavior Interaction Priority (BIP) component-based framework. Our method is inspired from the Aspect Oriented Programming (AOP) paradigm which was initially conceived to support the separation of concerns during the development of monolithic systems. BIP has a formal operational semantics and makes a clear separation between architecture and behavior to allow for compositional and incremental design and analysis of systems. We thus distinguish local from global aspects. Local aspects model concerns at the component level and are used to refine the behavior of components. Global aspects model concerns at the architecture level, and hence refine communications (synchronization and data transfer) between components. We formalize global aspects as well as their integration into a BIP system through rigorous transformation primitives and overview local aspects. We present AOP-BIP, a tool for Aspect-Oriented Programming of BIP systems, and demonstrate its use to modularize logging, security, and fault-tolerance in a network protocol.

show abstract

Reduction and Abstraction Techniques for BIP

Cited by 9 publications

References 20 publications

Early validation of system requirements and design through correctness-by-construction

Early validation of system requirements and design through correctness-by-construction

Modularizing behavioral and architectural crosscutting concerns in formal component-based systems – Application to the Behavior Interaction Priority framework

Modularizing Crosscutting Concerns in Component-Based Systems

Contact Info

Product

Resources

About