|
|
|
# Overview
|
|
|
|
|
|
|
|
Dynamic Condition Response (DCR) Choreographies [^1] extend the concept of DCR graphs [REF] to specify the behaviour of communicating parties, providing a declarative, event-based, and stateful approach to modeling workflows in a (implicitly) decentralized context.
|
|
|
|
Dynamic Condition Response (DCR) Choreographies extend the concept of DCR graphs [REF] to specify the behaviour of communicating parties, providing a declarative, event-based, and stateful approach to modeling workflows in a (implicitly) decentralized context.
|
|
|
|
|
|
|
|
A DCR choreography defines messages, and data, exchanged between different actors as well as control-flow constraints, beyond basic data dependencies, that represent the system’s business logic. In addition, it enables the representation of both events and constraints in a visual and intuitive manner, providing a high-level abstraction that is both human-readable and machine-executable.
|
|
|
|
|
|
|
|
DCR Choreographies enable the modeling of complex behaviour, going beyond simple state machines, allowing for an expressive, flexible and extendable programming language that can be used to design the application layer of swarms in decentralised and dynamic environments.
|
|
|
|
|
|
|
|
[^1]: https://doi.org/10.1007/978-3-031-41623-1_5
|
|
|
|
|
|
|
|
# Examples
|
|
|
|
[EDP Use Case](DCR Choreographies/EDP Use Case)
|
|
|
|
|
|
|
|
[Actyx Use Case](DCR Choreographies/Actyx Use Case) |
|
|
\ No newline at end of file |
|
|
|
[Actyx Use Case](DCR Choreographies/Actyx Use Case)
|
|
|
|
|
|
|
|
--- |
|
|
\ No newline at end of file |
