Specifying Web Workflow Services for Finding Partners in the Context of Loose Inter-organizational Workflow

Andonoff, Eric; Bouzguenda, Lotfi; Hanachi, Chihab

doi:10.1007/11538394_9

Cited by 13 publications

(12 citation statements)

References 8 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Such an ontology could ease the sharing, the selection, the negotiation and possibly the enactment of protocols by different partners involved in a CIS. Derivation rules have already been specified to transform PNO into OWL-S in Andonoff et al (2005), this results could be exploited to produce web services behaving as OgPN.…”

Section: Resultsmentioning

confidence: 99%

Engineering deontic protocols by means of organizational Petri nets

Combettes¹,

Hanachi²,

Sibertin-Blanc³

2009

Engineering Applications of Artificial Intelligence

Self Cite

View full text Add to dashboard Cite

Section: Resultsmentioning

confidence: 99%

Engineering deontic protocols by means of organizational Petri nets

Combettes¹,

Hanachi²,

Sibertin-Blanc³

2009

Engineering Applications of Artificial Intelligence

Self Cite

View full text Add to dashboard Cite

“…Once defined, the process model can be simulated, checked and validated. Our case study has been implemented in a simulator called MatchFlow [12] whose objective is to connect workflow service requesters (for instance chairman in our case) to workflow service providers (for instance reviewer in our case). MatchFlow implements the three-workflow dimensions.…”

Section: Discussionmentioning

confidence: 99%

“…(iii) it supports coherent exchange because a role describes the constraints (obligations, requirements, skills) that an agent should satisfy to obtain a role. Moreover, our organizational model extends classical organizational models [11] by adding an original component called "Matchmaker" as it is presented in [12]. This component is very useful in the context of loose IOW since it helps to connect a requester (for instance chairman) to a provider one (for instance reviewer).…”

Section: The Organizational Modelmentioning

confidence: 99%

How to Design a Loose Inter-organizational Workflow? An Illustrative Case Study

Bouzguenda

2005

Lecture Notes in Computer Science

Self Cite

View full text Add to dashboard Cite

This work deals with the design of Loose Inter-Organizational Workflow (IOW). Loose IOW refers to occasional cooperation, free of structural constraints, where the partners involved and their number are not pre defined. We show that the design of Loose IOW application is very complex due to three factors: (i) the heterogeneity and distribution of the component processes, the organizations and the information (ii) the autonomy of each partner, which must be preserved (iii) the need to integrate in a coherent framework the three dimensions of a workflow: process, information and organization. One possible way to deal with this complexity, and to ease loose IOW applications design, is to use a well known software engineering principle: the separation of aspects, which aims at decomposing a system in communicating sub systems, each one coping with a relevant abstraction that requires a model to be structured and described. Following this practice, a loose IOW application must be though as three communicating models: an informational model, an organizational model and a process model. The first two models are represented with UML class's diagram, while the last model is described with Petri Nets with Objects (PNO), which are a formal language, have a very adequate expressive power and make the glue between the three workflow dimensions. We illustrate our solution through the well-known "reviewing papers" case study.

show abstract

“…The author gives semantics for model synthesis, which improves the reliability and maintainability of service process. In literature [18], an object Petri Nets (OPN) is used to services composition that each Web service is mapped to a PNO system in which different Petri Nets can be interacted via message delivery mechanism.…”

Section: Petri Nets Based Service Process Modeling Methodsmentioning

confidence: 99%