1992
DOI: 10.1007/3-540-55599-4_92
|View full text |Cite
|
Sign up to set email alerts
|

A model to design reusable parallel software components

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1

Citation Types

0
3
0

Publication Types

Select...
3

Relationship

0
3

Authors

Journals

citations
Cited by 3 publications
(3 citation statements)
references
References 8 publications
0
3
0
Order By: Relevance
“…In the absence of any specialized interaction behavior specifications, the put and get events of ml and m2 inherit the universal interaction behavior from class Sa f eBuf. 4 (ml.X.put, k ) @ (m2.X.get, k ) with respect to the reusability of both concurrent class and interaction behavior specifications.…”
Section: Decomposition Of Interaction Behaviormentioning
confidence: 99%
See 2 more Smart Citations
“…In the absence of any specialized interaction behavior specifications, the put and get events of ml and m2 inherit the universal interaction behavior from class Sa f eBuf. 4 (ml.X.put, k ) @ (m2.X.get, k ) with respect to the reusability of both concurrent class and interaction behavior specifications.…”
Section: Decomposition Of Interaction Behaviormentioning
confidence: 99%
“…PCM [4] identifies two kinds of synchronization expressions of an object: the first, called concurrency constraints, do not depend on the state of the object, whereas the second, called state constraints, do. Concurrency constraints are defined separately in abstract classes, whereas state constraints are defined in classes.…”
Section: Relatedworkmentioning
confidence: 99%
See 1 more Smart Citation