Model-driven synthesis of SOA solutions

Strosnider, J.K.; Nandi, Prabir; Kumaran, Santhosh; Ghosh, Sourobh; Arsanjani, Ali

doi:10.1147/sj.473.0415

Cited by 46 publications

(21 citation statements)

References 13 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…This paper formed the basis of a substantial effort at IBM Research, which resulted in the "ModelDriven Business Transformation (MDBT)" method and toolkit [15]. This was subsequently incorporated as the "Business Entity Lifecycle Analysis (BELA)" [24] capability pattern into IBM's Service-Oriented Method and Architecture (SOMA) [1]. The meta-models of [22] and of MDBT [15,24] can be viewed as lying within the BALSA framework.…”

Section: Suggested Additional Readingmentioning

confidence: 99%

“…This was subsequently incorporated as the "Business Entity Lifecycle Analysis (BELA)" [24] capability pattern into IBM's Service-Oriented Method and Architecture (SOMA) [1]. The meta-models of [22] and of MDBT [15,24] can be viewed as lying within the BALSA framework. Reference [22] uses an information model based on (possibly nested) attribute-value pairs, while [15,24] use ER diagrams for the artifact information model.…”

Section: Suggested Additional Readingmentioning

confidence: 99%

“…The meta-models of [22] and of MDBT [15,24] can be viewed as lying within the BALSA framework. Reference [22] uses an information model based on (possibly nested) attribute-value pairs, while [15,24] use ER diagrams for the artifact information model. Both meta-models use detailed finite state machines for the artifact lifecycles.…”

Section: Suggested Additional Readingmentioning

confidence: 99%

“…Experiences from some of these efforts are reported in [4,6,24]. The business managers and subject matter experts involved in these transformations said that the use of artifacts as the basic modeling primitive gave them a kind of "bird's eye" of their operations that they were not obtaining from the traditional activity-flow based approaches, and that it enabled substantially improved communication between the various stakeholders.…”

Section: Suggested Additional Readingmentioning

confidence: 99%

See 3 more Smart Citations

A Data-Centric Design Methodology for Business Processes

Bhattacharya¹,

Hull²,

Su³

Handbook of Research on Business Process Modeling

View full text Add to dashboard Cite

This chapter describes a design methodology for business processes and workflows that focuses first on "business artifacts", which represent key (real or conceptual) business entities, including both the business-relevant data about them and their macro-level lifecycles. Individual workflow services (a.k.a. tasks) are then incorporated, by specifying how they operate on the artifacts and fit into their lifecycles. The resulting workflow is specified in a particular artifact-centric workflow model, which is introduced using an extended example. At the logical level this workflow model is largely declarative, in contrast with most traditional workflow models which are procedural and/or graph-based. The chapter includes a discussion of how the declarative, artifact-centric workflow specification can be mapped into an optimized physical realization.

show abstract

Section: Suggested Additional Readingmentioning

confidence: 99%

Section: Suggested Additional Readingmentioning

confidence: 99%

Section: Suggested Additional Readingmentioning

confidence: 99%

Section: Suggested Additional Readingmentioning

confidence: 99%

See 2 more Smart Citations

A Data-Centric Design Methodology for Business Processes

Bhattacharya¹,

Hull²,

Su³

Handbook of Research on Business Process Modeling

View full text Add to dashboard Cite

show abstract

“…In the past several years a data-centric approach to modeling workflows has emerged, in which both data and process are tightly coupled in the basic building blocks of workflows. One class of datacentric workflow models is centered around "business artifacts" [12,16], which are augmented data records that correspond to key business-relevant entities, their lifecycles, and how/when services (a.k.a. tasks) are invoked on them.…”

Section: Introductionmentioning

confidence: 99%

Artifact-Centric Workflow Dominance

Calvanese

Giacomo

Hull³

et al. 2009

Service-Oriented Computing – ICSOC 2007

View full text Add to dashboard Cite

Abstract. In this paper we initiate a study on comparing artifactcentric workflow schemas, in terms of the ability of one schema to emulate the possible behaviors of another schema. Artifact-centric workflows are centered around "business artifacts", which contain both a data schema, which can hold all of the data about a key business entity as it passes through a workflow, along with a lifecycle schema, which specifies the possible ways that the entity can evolve through the workflow. In this paper, the data schemas for artifact types are finite sets of attribute-value pairs, and the lifecycle schemas are specified as sets of condition-action rules, where the condition is evaluated against the current snapshot of the artifact, and where the actions are external services (or "tasks"), which read a subset of the attributes of an artifact, which write onto a subset of the attributes, and which are performed by an entity outside of the workflow system (often a human). The services are also characterized by pre-and post-conditions, in the spirit of semantic web services. To compare artifact-centric workflows, we introduce the notion of "dominance", which intuitively captures the fact that all executions of a workflow can be emulated by a second workflow. (In the current paper, the emulation is focused only on the starting and ending snapshots of the possible enactments of the two workflows.) In fact, dominance is a parametric notion that depends on the characterization of the policies that govern the execution of the services invoked by the workflows. In this paper, we study in detail the case of "absolute dominance", in which this policy places no constraints on the possible service executions. We provide decidability and complexity results for bounded and unbounded workflow executions in the cases where the values in an artifact range over an infinite structure, such as the integers, the rationals, or the reals, possibly with order, addition, or multiplication.

show abstract