2005
DOI: 10.1007/11575801_6
|View full text |Cite
|
Sign up to set email alerts
|

On the Notion of Coupling in Communication Middleware

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
18
0
1

Year Published

2007
2007
2010
2010

Publication Types

Select...
3
2
1

Relationship

2
4

Authors

Journals

citations
Cited by 23 publications
(19 citation statements)
references
References 11 publications
0
18
0
1
Order By: Relevance
“…coupling over time and space [4,12], guaranteed delivery, encryption). In this section we distill some of these specialised requirements.…”
Section: Motivating Requirementsmentioning
confidence: 99%
See 2 more Smart Citations
“…coupling over time and space [4,12], guaranteed delivery, encryption). In this section we distill some of these specialised requirements.…”
Section: Motivating Requirementsmentioning
confidence: 99%
“…Then the message engine attempts to lock every message in Ω. 4. If all messages were successfully locked, then for each message-id in Ω, that property tuple is deleted, and each corresponding message gets removed from the buffer and sent to the requestor in a callback.…”
Section: Resolving Contentionmentioning
confidence: 99%
See 1 more Smart Citation
“…A good overview can be found in [13]. For example: the formalization of the design of the so-called worklet service, which adds flexibility and exception handling capabilities to the YAWL workflow system [5]; formalizing the implementation of a healthcare process in a workflow management system [20]; presenting a model-based approach to requirements engineering for reactive systems [16]; expressing architectural requirements and assessing middleware support in terms of decoupling [6]; and formalizing the implementation of a patient record system by modeling task descriptions [19]. Related to this is [24], in which CP Nets are used for specifying the operational semantics of new YAWL, a business process modeling language founded on the well-known workflow patterns 4 .…”
Section: Related Workmentioning
confidence: 99%
“…Pode se observar nesta figura que as aplicações não estão conectadas diretamente, isto é, estão desacopladas. O desacoplamento entre as aplicações permite criar sistemas mais flexíveis (ALDRED et al, 2005;EUGSTER et al, 2003 …”
Section: Comunicação Publish/subscribe (P/s)unclassified