Behavioral Types for Component-Based Development of Cyber-Physical Systems

Blech, Jan Olaf; Herrmann, Peter

doi:10.1007/978-3-662-49224-6_5

Cited by 3 publications

(4 citation statements)

References 36 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Behavioral types have been used for the specification of real-time systems (Lee and Xiong, 2004). Furthermore, behavioral types are a formal description method that have been applied for software components (Blech et al, 2012), industrial automation systems (Blech et al, 2014) and cyber-physical systems (Blech and Herrmann, 2015). The idea is to have descriptions that allow for automatic checks of interactions between entities in very much the same way as type compatibility and compliance checking works in higher programming languages.…”

Section: Related Workmentioning

confidence: 99%

Collaborative Model-based Development of a Remote Train Monitoring System

Herrmann

Svae

Svendsen

et al. 2016

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

Self Cite

View full text Add to dashboard Cite

The model-based engineering technique Reactive Blocks supports the development of reactive systems by UML-based graphic modeling of control and data flows, model checker supported analysis, and automated code generation. Moreover, it facilitates the cooperation of teams of engineers by enabling the definition of formally precise behavioral interfaces that make the separation of the modelling process into various work packages easy. In this paper, we illustrate the use of Reactive Blocks for a joint student project that realized the monitoring and control of Lego Mindstorms-based trains in Norway through a control center in Australia. In particular, we explain how the Reactive Blocks interfaces and the applied communication protocols were used to split the project into work packages separately handled by the students involved.

show abstract

Section: Related Workmentioning

confidence: 99%

Collaborative Model-based Development of a Remote Train Monitoring System

Herrmann

Svae

Svendsen

et al. 2016

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

Self Cite

View full text Add to dashboard Cite

show abstract

“…Similarly, in [44][45][46], behavioral types, represented by FSMs, are used to describe the behavior of component types and their interaction protocols. The latter is constrained by the fact that behavioral types strictly describe method calls and thus, cannot describe n-ary synchronizations among components.…”

Section: Related Workmentioning

confidence: 99%

“…Behavioral types can be used for runtime verification through automatic generation of monitors that are executed in parallel with a system implementation. Runtime monitors, in [44], are connected to components using AspectJ. Similarly to the JavaBIP approach, this requires the developers to be aware of the APIs of the underlying components.…”

Section: Related Workmentioning

confidence: 99%

“…Similarly to the JavaBIP approach, this requires the developers to be aware of the APIs of the underlying components. With respect to JavaBIP, the advantage of [44] could be that components need not specifically provide spontaneous ports in their interfaces. Instead a developer could set up notifications for spontaneous transitions, as long as a sufficiently close pointcut can be defined.…”

Section: Related Workmentioning

confidence: 99%

See 1 more Smart Citation

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