2006
DOI: 10.1016/j.entcs.2006.07.003
|View full text |Cite
|
Sign up to set email alerts
|

A Component Model for Separation of Control Flow from Computation in Component-Based Systems

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

0
5
0

Year Published

2006
2006
2020
2020

Publication Types

Select...
3
3
1

Relationship

3
4

Authors

Journals

citations
Cited by 8 publications
(5 citation statements)
references
References 12 publications
0
5
0
Order By: Relevance
“…Their purpose is similar to that of connector elements that can be found in architecture description languages, e.g. [17]. The example of a component composed in series is shown in Fig.…”
Section: Specifying Serial Composition Of Componentsmentioning
confidence: 98%
“…Their purpose is similar to that of connector elements that can be found in architecture description languages, e.g. [17]. The example of a component composed in series is shown in Fig.…”
Section: Specifying Serial Composition Of Componentsmentioning
confidence: 98%
“…Their purpose is similar to that of connector elements that can be found in many architecture description languages, e.g. [8].…”
Section: B Specifying Composition Of Componentsmentioning
confidence: 98%
“…To enable flexible service composition in such heterogeneous environments, control flow, data flow and computation should be orthogonal [35,36,38,76,144,201,202]. This would enable separate reasoning of concerns so system developers can focus on IoT service composition, while service developers focus on efficient service functionality [37,74,76].…”
Section: Separation Of Control Data and Computationmentioning
confidence: 99%