2006
DOI: 10.1007/11914853_12
|View full text |Cite
|
Sign up to set email alerts
|

Aspect-Oriented Workflow Languages

Abstract: Erklärung: Hiermit erkläre ich, daß ich die vorliegende Arbeit selbstständig und unter ausschließlicher Verwendung der angegebenen Quellen und Hilfsmittel angefertigt habe. Darmstadt, den 12. Dezember 2006To my parents,To my wife, To my brother and my sister AcknowledgmentsFirstly, I would like to thank sincerely my advisor Prof. Dr. Mira Mezini for giving me the chance to work in her team, for her support and guidance during the three years of my PhD work, and for providing valuable feedback on early drafts o… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
29
0
1

Year Published

2008
2008
2018
2018

Publication Types

Select...
5
3
1

Relationship

0
9

Authors

Journals

citations
Cited by 36 publications
(30 citation statements)
references
References 74 publications
(215 reference statements)
0
29
0
1
Order By: Relevance
“…A different approach, based on a middleware that supports reliable Web Services built on active replication has been proposed in [40]. Similarly, Erradi et al [41] propose a lightweight service-oriented middleware for transparently enacting recovery action in service-based processes; and Charfi et al [42] use an aspect-based container to provide middleware support for BPEL that plugs in support for non-functional requirements. Chen et al [43] construct composite services resilient to various failure types using inherent redundancy and diversity of Web Service components jointly with mediator approach.…”
Section: Related Workmentioning
confidence: 99%
“…A different approach, based on a middleware that supports reliable Web Services built on active replication has been proposed in [40]. Similarly, Erradi et al [41] propose a lightweight service-oriented middleware for transparently enacting recovery action in service-based processes; and Charfi et al [42] use an aspect-based container to provide middleware support for BPEL that plugs in support for non-functional requirements. Chen et al [43] construct composite services resilient to various failure types using inherent redundancy and diversity of Web Service components jointly with mediator approach.…”
Section: Related Workmentioning
confidence: 99%
“…It addresses the issue of business process adaptation. For SAR we enhanced aspect-oriented business process management [17] with event-driven capabilities for discovering situations requiring adaptations. To this end, we developed an aspect-oriented extension to BPMN2.0 similar to AO4BPMN [18].…”
Section: Esr and Sar Recommendersmentioning
confidence: 99%
“…This approach is inspired by aspectoriented programming and defines extensions to workflow languages in general [23], BPEL [24] and BPMN [22], to represent non-functional aspects of a business process such as security and logging, as separate, reusable modules. The notions of joint point, pointcut and advice used in aspect oriented programming, are adopted in this context.…”
Section: Metricsmentioning
confidence: 99%