2016
DOI: 10.1109/mc.2016.377
|View full text |Cite
|
Sign up to set email alerts
|

Software Abstractions for Component Interaction in the Internet of Things

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
24
0

Year Published

2018
2018
2020
2020

Publication Types

Select...
4
2
1

Relationship

1
6

Authors

Journals

citations
Cited by 32 publications
(24 citation statements)
references
References 7 publications
0
24
0
Order By: Relevance
“…attr.Set("send_try", false) }) 7 }} Process T deals with try-messages ("try", y, z, tid) as mentioned before. If the current round equals the round attached in the message z, then the received message has been originated by another component performing the same round of the algorithm and we have two cases (Lines [12][13][14][15][16][17][18][19]. The first case is executed when the id of the vertex is greater than the id of the message tid, i.e.…”
Section: Case Study: a Distributed Graph Colouringmentioning
confidence: 99%
See 1 more Smart Citation
“…attr.Set("send_try", false) }) 7 }} Process T deals with try-messages ("try", y, z, tid) as mentioned before. If the current round equals the round attached in the message z, then the received message has been originated by another component performing the same round of the algorithm and we have two cases (Lines [12][13][14][15][16][17][18][19]. The first case is executed when the id of the vertex is greater than the id of the message tid, i.e.…”
Section: Case Study: a Distributed Graph Colouringmentioning
confidence: 99%
“…DEECo [14] and Helena [25] adopt an architecture-based approach to specify ensembles. In general, they impose logical conditions on the membership of ensembles that components have to satisfy.…”
Section: Related Workmentioning
confidence: 99%
“…From the software design and development perspective, such cooperation needs to take place at the syntactic level (e.g., API matching, language interoperability), at the semantic level (e.g., common vocabulary, contracts for assume-guarantee reasoning), and at the strategic level (such as sharing of goals performed by highlevel tasks). In this work, we focus on cooperation of software components at the strategic level in the first place-assum-ing that they form dynamic groups, also known as component ensembles [1,2]. Specifically, we presume that:…”
Section: Introductionmentioning
confidence: 99%
“…Moreover, ensembles have been suggested to hoist the component cooperation and knowledge distribution concerns in a dynamically changing CPS at the level of software architecture 1 [1]. This has been done in the context of specialized component models and languages such as SCEL [6], DEECo [1], and Helena [7]. By a logical condition upon the ensemble and component actual states, an ensemble's description determines its member components and which particular roles in the ensemble they play.…”
Section: Introductionmentioning
confidence: 99%
See 1 more Smart Citation