A model-driven approach to industrializing discovery processes in pharmaceutical research

Bhattacharya, Kamal; Guthman, R.; Lyman, K.; Heath, Fenno F.; Kumaran, Santhosh; Nandi, Prabir; Wu, Frederick Y.; Athma, P.; Freiberg, C.; Johannsen, L.; Staudt, A.

doi:10.1147/sj.441.0145

Cited by 69 publications

(55 citation statements)

References 7 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…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%

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%

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

“…Business artifacts (or simply "artifacts") model key business-relevant entities, which are updated by a set of services that implement business process tasks. This modeling approach has been successfully deployed in practice [4,3,9,14,39]. In particular, the Guard-Stage-Milestone (GSM) approach [12,23] to artifact specification uses declarative services with pre-and post-conditions, parallelism, and hierarchy.…”

Section: Introductionmentioning

confidence: 99%

Process-centric views of data-driven business artifacts

Koutsos

Vianu

2017

Journal of Computer and System Sciences

View full text Add to dashboard Cite

Declarative, data-aware workflow models are becoming increasingly pervasive. While these have numerous benefits, classical process-centric specifications retain certain advantages. Workflow designers are used to development tools such as BPMN or UML diagrams, that focus on control flow. Views describing valid sequences of tasks are also useful to provide stake-holders with highlevel descriptions of the workflow, stripped of the accompanying data. In this paper we study the problem of recovering process-centric views from declarative, data-aware workflow specifications in a variant of IBM's business artifact model. We focus on the simplest and most natural processcentric views, specified by finite-state transition systems, and describing regular languages. The results characterize when process-centric views of artifact systems are regular, using both linear and branching-time semantics. We also study the impact of data dependencies on regularity of the views.

show abstract

“…tasks) are invoked on them. This "artifact-centric" approach provides a simple and robust structure for workflow, and has been demonstrated in practice to permit efficiencies in business transformation [2,3]. In the artifact-centric approach obviously the process is of interest, but differently from process-centric workflows the data play a key role.…”

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

A model-driven approach to industrializing discovery processes in pharmaceutical research

Cited by 69 publications

References 7 publications

A Data-Centric Design Methodology for Business Processes

A Data-Centric Design Methodology for Business Processes

Process-centric views of data-driven business artifacts

Artifact-Centric Workflow Dominance

Contact Info

Product

Resources

About