Towards a Task-Oriented, Policy-Driven Business Requirements Specification for Web Services

Gorton, Stephen; Reiff-Marganiec, Stephan

doi:10.1007/11841760_40

Cited by 16 publications

(20 citation statements)

References 10 publications

(10 reference statements)

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Workflows specify core business processes, in which all task requirements are satisfied by services, that is a service (possibly human) can be invoked to complete the task. We model a workflow using a graphical notation presented in [GRM06c]. However, for the purpose of this paper we also adapt the more concise textual grammar presented in [BGR08] which shows how complex processes can be composed:…”

Section: Overviewmentioning

confidence: 99%

“…We have used the language of [GRM06c] for its simplicity, expressive power and our familiarity with it Policies have generally been used as an administration technique in system management (e.g. access control [Mos05] or Internet Telephony [RM03]).…”

Section: Related Workmentioning

confidence: 99%

“…Possibly AgentWork [MGR04], where ECA rules can be used to drop or add individual tasks to workflows, is closest to our initial discussions on linking policies with workflows [GRM06b,GRM06a]. However, there is no notion of tasks being linked to services in this work, and the policies are concerned with task replacement rather than task implementation, service selection or the more significant workflow restructuring discussed here.…”

Section: Related Workmentioning

confidence: 99%

“…It has three ingredients: workflows to express core processes, services to perform activities and policies to express variability. Workflows are expressed using a graphical notation, such as in [GRM06c] or UML activity diagrams 1 . Policies can make short-lived changes to a workflow instance, i.e.…”

Section: Introductionmentioning

confidence: 99%

See 3 more Smart Citations

From StPowla processes to SRML models

Bocchi

Gorton²,

Reiff-Marganiec

2010

Form. Asp. Comput.

Self Cite

View full text Add to dashboard Cite

Abstract. Service Oriented Computing is a paradigm for developing software systems as the composition of a number of services. Services are loosely coupled entities, that can be dynamically published, discovered and invoked over a network. The engineering of such systems presents novel challenges, mostly due to the dynamicity and distributed nature of service-based applications. In this paper, we focus on the modelling of service orchestrations. We discuss the relationship between two languages developed under the SENSORIA project: SRML as a high level modelling language for Service Oriented Architectures, and STPOWLA as a process-oriented orchestration approach that separates core business processes from system variability at the end-user's level, where the focus is towards achieving business goals. A fundamental challenge of software engineering is to correctly align business goals with IT strategy, and as such we present an encoding of STPOWLA to SRML. This provides a formal framework for STPOWLA and also a separated view of policies representing system variability that is not present in SRML.

show abstract

Section: Overviewmentioning

confidence: 99%

Section: Related Workmentioning

confidence: 99%

Section: Related Workmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

From StPowla processes to SRML models

Bocchi

Gorton²,

Reiff-Marganiec

2010

Form. Asp. Comput.

Self Cite

View full text Add to dashboard Cite

show abstract

“…To address its goals, StPowla integrates three main ingredients: a graphical workflow notation, a policy language, and SOA. Although intended to be independent of the workflow notation, some high level constructs to build processes out of tasks are presented in [15], and the related UML profile is under development [25]. Here, we can be satisfied with the simplest combinators: sequence, choice, and fork/join, as they are available, for instance in UML activity diagrams.…”

Section: An Approach To Business Flexibilitymentioning

confidence: 99%

Dynamically Evolvable Dependable Software: From Oxymoron to Reality

Ghezzi

Inverardi

Montangero

2008

Concurrency, Graphs and Models

View full text Add to dashboard Cite

Abstract. We analyze the main motivations that lead to the present need for supporting continuous software evolution, and discuss some of the reasons for change requirements. Achieving software that is both dynamically evolvable and dependable is our long-term research goal. We do not attempt here to propose a unified solution to dissolve the apparent oximoron, i.e. to reconcile these apparently conflicting goals. Rather, we enlighten different facets of the problem by distilling our experience through three research experience reports that act as case studies. We discuss the lessons learned from the state of the art and practice exemplified by our approaches and outline the directions of possible future research.

show abstract

Engineering Service Oriented Applications: From StPowla Processes to SRML Models

Bocchi

Gorton

Reiff-Marganiec

Fundamental Approaches to Software Engineering

Self Cite

View full text Add to dashboard Cite

Abstract. Service Oriented Computing is a paradigm for developing software systems as the composition of a number of services. Services are loosely coupled entities, can be dynamically published, discovered and invoked over a network. The engineering of such systems presents novel challenges, mostly due to the dynamicity and distributed nature of service-based applications. In this paper, we focus on the modelling of service orchestrations. We discuss the relationship between two languages developed under the SENSORIA project: SRML as a high level modelling language for Service Oriented Architectures, and STPOWLA as a process-oriented orchestration approach that separates core business processes from system variability at the end-user's level, where the focus is towards achieving business goals. We also extend the current status of STPOWLA to include workflow reconfigurations. A fundamental challenge of software engineering is to correctly align business goals with IT strategy, and as such we present an encoding of STPOWLA to SRML. This provides a formal framework for STPOWLA and also a separated view of policies representing system variability that is not present in SRML.

show abstract

Towards a Task-Oriented, Policy-Driven Business Requirements Specification for Web Services

Cited by 16 publications

References 10 publications

From StPowla processes to SRML models

From StPowla processes to SRML models

Dynamically Evolvable Dependable Software: From Oxymoron to Reality

Engineering Service Oriented Applications: From StPowla Processes to SRML Models

Contact Info

Product

Resources

About