Logic–Based Detection of Conflicts in Appel Policies

Montangero, Carlo; Reiff-Marganiec, Stephan; Semini, Laura

doi:10.1007/978-3-540-75698-9_17

Cited by 11 publications

(12 citation statements)

References 17 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…business managers, operators and clients, StPowla has a precise semantics, which we presented in natural language. Future work include the definition of a formal semantics, in the form of a mapping to logical theories, extending the work in [14]. This will be the basis for performing some analysis on the process models, e.g.…”

Section: Discussionmentioning

confidence: 99%

“…Conflicts can be detected with a supporting tool [14], and their resolution can be manual or automatic. Manual resolution can include re-formulation of policies.…”

Section: Pragmatics Of the Customizationmentioning

confidence: 99%

“…For instance, P3 and P1 overlap, as well as P3 and P2, while P1 and P2 don't. To help the user avoiding conflicts and undesired overriding when defining priorities, the policy wizard can be extended to integrate the analysis techniques defined in a previous work [14]. Now assume that P4 is added.…”

Section: P3 Seq P2 Seq P1 Seq Defaultmentioning

confidence: 99%

See 2 more Smart Citations

StPowla: SOA, Policies and Workflows

Gorton

Montangero

Reiff-Marganiec

et al. 2009

Service-Oriented Computing – ICSOC 2007

View full text Add to dashboard Cite

Abstract. We introduce StPowla, a workflow based approach to business process modelling that integrates a simple graphical notation, to ease the presentation of the core business process, a natural policy language, Appel, to provide the necessary adaptation to the varied expectations of the various business stakeholders, and the Service Oriented Architecture, to assemble and orchestrate available services in the business process. We illustrate the approach with a loan approval process.

show abstract

Section: Discussionmentioning

confidence: 99%

“…Conflicts can be detected with a supporting tool [14], and their resolution can be manual or automatic. Manual resolution can include re-formulation of policies.…”

Section: Pragmatics Of the Customizationmentioning

confidence: 99%

See 1 more Smart Citation

StPowla: SOA, Policies and Workflows

Gorton

Montangero

Reiff-Marganiec

et al. 2009

Service-Oriented Computing – ICSOC 2007

View full text Add to dashboard Cite

show abstract

“…The purpose of policies is to express system variability. Policies are written in APPEL [RMTB05], a policy description language with formal semantics via a mapping to ∆DST L [MRMS07,MRMSon]. They are written by the end (business) user and are combined with the workflow at execution time.…”

Section: Overviewmentioning

confidence: 99%

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

“…Besides, it has two characteristics that support its use by non technical users: it has a friendly interface to define policies in tabular form, and has been given formal semantics via a mapping to DSTL [32]. This way, it was possible to devise a technique to detect policy conflicts [31] when policies are deployed, providing a first, early, form of dependability.…”

Section: An Approach To Business Flexibilitymentioning

confidence: 99%

Dynamically Evolvable Dependable Software: From Oxymoron to Reality

Ghezzi

Inverardi

Montangero

2008

Concurrency, Graphs and Models

Self Cite

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

Logic–Based Detection of Conflicts in Appel Policies

Cited by 11 publications

References 17 publications

StPowla: SOA, Policies and Workflows

StPowla: SOA, Policies and Workflows

From StPowla processes to SRML models

Dynamically Evolvable Dependable Software: From Oxymoron to Reality

Contact Info

Product

Resources

About