A reference model for interaction semantics
December 23, 2017 Β· Declared Dead Β· π arXiv.org
"No code URL or promise found in abstract"
Evidence collected by the PWNC Scanner
Authors
Johannes Reich, Tizian SchrΓΆder
arXiv ID
1801.04185
Category
cs.SE: Software Engineering
Cross-listed
cs.LO
Citations
3
Venue
arXiv.org
Last Checked
4 months ago
Abstract
In this article, we introduce a reference model for interaction semantics among communicating discrete systems to guide the discourse on interoperability. The necessary set of unifying concepts is small and comprises essentially the notion of discrete systems interacting by exchanging information. It is based on a simple, but nevertheless complete classification of system interactions with respect to information transport and processing. Information transport can only be uni- or bidirectional and information processing is subclassified along the binary dimensions of state, determinism and synchronicity. For interactions with bidirectional information flow we are able to define a criterion for a layered structure of systems: we name a bidirectional interaction "horizontal" if all interacting systems behave the same with respect to state, determinism and synchronicity and we name it "vertical" --- providing a semantic direction --- if there is a behavioral asymmetry between the interacting systems with respect to these properties. It is shown that horizontal interactions are essentially stateful, asynchronous and nondeterministic and are described by protocols. Vertical interactions are essentially top-down-usage, described by object models or operations, and bottom-up-observation, described by anonymous events. The reference model thereby helps us to understand the significant relationships that are created between interacting discrete systems by their interactions and guides us on how to talk about discrete system interoperability. To show its conceptual power, we apply the reference model to assess several other architectural models, communication technologies and so called software design or architectural styles like SOA and REST.
Community Contributions
Found the code? Know the venue? Think something is wrong? Let us know!
π Similar Papers
In the same crypt β Software Engineering
R.I.P.
π»
Ghosted
R.I.P.
π»
Ghosted
Microservices: yesterday, today, and tomorrow
π
π
The Cartographer
A Survey of Machine Learning for Big Code and Naturalness
R.I.P.
π»
Ghosted
An Overview on Smart Contracts: Challenges, Advances and Platforms
R.I.P.
π»
Ghosted
Slither: A Static Analysis Framework For Smart Contracts
R.I.P.
π»
Ghosted
ContractFuzzer: Fuzzing Smart Contracts for Vulnerability Detection
Died the same way β π» Ghosted
R.I.P.
π»
Ghosted
Federated Learning: Strategies for Improving Communication Efficiency
R.I.P.
π»
Ghosted
In-Datacenter Performance Analysis of a Tensor Processing Unit
R.I.P.
π»
Ghosted
Deep Convolutional Neural Networks for Computer-Aided Detection: CNN Architectures, Dataset Characteristics and Transfer Learning
R.I.P.
π»
Ghosted