Formalizing and reasoning about the requirements specifications of workflow systems

Goce Trajcevski, Chitta Baral, Jorge Lobo

Research output: Contribution to journalArticle

5 Citations (Scopus)

Abstract

This work addresses the problem of workflow requirements specifications considering the realistic assumptions that, it involves experts from different domains (i.e. representatives of different business policies); not all the possible execution scenarios are known beforehand, during the early stage of specification. In particular, since the main purpose of a workflow is to achieve a certain (bussiness) goal, we propose a formalism which enables the users to specify their requirements (and expectations) and test if the information that they have provided is, in a sense, sufficient for the workflow to behave "as desired", in terms of the goal. Our methodology allows domain experts to express not only their knowledge, but also the "ignorance" (the semantics allows for unknown values to reflect a realistic situation of agents dealing with incomplete information) and the possibility of occurrence of exceptional situations. As a basis for formalizing the process of requirements specifications, we are using the recent results on reasoning about actions. We propose a high level language AW which enables specifying the effects that activites have on the environment and how they should be coordinated. We also describe our prototype tool for process specification. Strictly speaking, in this work we go "one step" before actual analysis and design, and offer a formalism which enables the involved partners to see if the extent to which they have expressed their domain knowledge (which may sometimes be subject to a proprietary restricions) can satisfy the intended needs and behaviour of their product_to_be. We define an entailment relation which enables reasoning about the correctness of the specification, in terms of achieving a desired goal and, also testing about consequences of modifications in the workflow descriptions.

Original languageEnglish (US)
Pages (from-to)483-507
Number of pages25
JournalInternational Journal of Cooperative Information Systems
Volume10
Issue number4
DOIs
StatePublished - Dec 2001

Fingerprint

Specifications
High level languages
Semantics
Testing
Industry

Keywords

  • Business process modeling
  • Information management
  • Knowledge representation and reasoning
  • Process specification
  • Reasoning about actions
  • Worfklow systems

ASJC Scopus subject areas

  • Information Systems

Cite this

Formalizing and reasoning about the requirements specifications of workflow systems. / Trajcevski, Goce; Baral, Chitta; Lobo, Jorge.

In: International Journal of Cooperative Information Systems, Vol. 10, No. 4, 12.2001, p. 483-507.

Research output: Contribution to journalArticle

@article{63347d80712e480eba00645493c7acb5,
title = "Formalizing and reasoning about the requirements specifications of workflow systems",
abstract = "This work addresses the problem of workflow requirements specifications considering the realistic assumptions that, it involves experts from different domains (i.e. representatives of different business policies); not all the possible execution scenarios are known beforehand, during the early stage of specification. In particular, since the main purpose of a workflow is to achieve a certain (bussiness) goal, we propose a formalism which enables the users to specify their requirements (and expectations) and test if the information that they have provided is, in a sense, sufficient for the workflow to behave {"}as desired{"}, in terms of the goal. Our methodology allows domain experts to express not only their knowledge, but also the {"}ignorance{"} (the semantics allows for unknown values to reflect a realistic situation of agents dealing with incomplete information) and the possibility of occurrence of exceptional situations. As a basis for formalizing the process of requirements specifications, we are using the recent results on reasoning about actions. We propose a high level language AW which enables specifying the effects that activites have on the environment and how they should be coordinated. We also describe our prototype tool for process specification. Strictly speaking, in this work we go {"}one step{"} before actual analysis and design, and offer a formalism which enables the involved partners to see if the extent to which they have expressed their domain knowledge (which may sometimes be subject to a proprietary restricions) can satisfy the intended needs and behaviour of their product_to_be. We define an entailment relation which enables reasoning about the correctness of the specification, in terms of achieving a desired goal and, also testing about consequences of modifications in the workflow descriptions.",
keywords = "Business process modeling, Information management, Knowledge representation and reasoning, Process specification, Reasoning about actions, Worfklow systems",
author = "Goce Trajcevski and Chitta Baral and Jorge Lobo",
year = "2001",
month = "12",
doi = "10.1142/S021884300100045X",
language = "English (US)",
volume = "10",
pages = "483--507",
journal = "International Journal of Cooperative Information Systems",
issn = "0218-8430",
publisher = "World Scientific Publishing Co. Pte Ltd",
number = "4",

}

TY - JOUR

T1 - Formalizing and reasoning about the requirements specifications of workflow systems

AU - Trajcevski, Goce

AU - Baral, Chitta

AU - Lobo, Jorge

PY - 2001/12

Y1 - 2001/12

N2 - This work addresses the problem of workflow requirements specifications considering the realistic assumptions that, it involves experts from different domains (i.e. representatives of different business policies); not all the possible execution scenarios are known beforehand, during the early stage of specification. In particular, since the main purpose of a workflow is to achieve a certain (bussiness) goal, we propose a formalism which enables the users to specify their requirements (and expectations) and test if the information that they have provided is, in a sense, sufficient for the workflow to behave "as desired", in terms of the goal. Our methodology allows domain experts to express not only their knowledge, but also the "ignorance" (the semantics allows for unknown values to reflect a realistic situation of agents dealing with incomplete information) and the possibility of occurrence of exceptional situations. As a basis for formalizing the process of requirements specifications, we are using the recent results on reasoning about actions. We propose a high level language AW which enables specifying the effects that activites have on the environment and how they should be coordinated. We also describe our prototype tool for process specification. Strictly speaking, in this work we go "one step" before actual analysis and design, and offer a formalism which enables the involved partners to see if the extent to which they have expressed their domain knowledge (which may sometimes be subject to a proprietary restricions) can satisfy the intended needs and behaviour of their product_to_be. We define an entailment relation which enables reasoning about the correctness of the specification, in terms of achieving a desired goal and, also testing about consequences of modifications in the workflow descriptions.

AB - This work addresses the problem of workflow requirements specifications considering the realistic assumptions that, it involves experts from different domains (i.e. representatives of different business policies); not all the possible execution scenarios are known beforehand, during the early stage of specification. In particular, since the main purpose of a workflow is to achieve a certain (bussiness) goal, we propose a formalism which enables the users to specify their requirements (and expectations) and test if the information that they have provided is, in a sense, sufficient for the workflow to behave "as desired", in terms of the goal. Our methodology allows domain experts to express not only their knowledge, but also the "ignorance" (the semantics allows for unknown values to reflect a realistic situation of agents dealing with incomplete information) and the possibility of occurrence of exceptional situations. As a basis for formalizing the process of requirements specifications, we are using the recent results on reasoning about actions. We propose a high level language AW which enables specifying the effects that activites have on the environment and how they should be coordinated. We also describe our prototype tool for process specification. Strictly speaking, in this work we go "one step" before actual analysis and design, and offer a formalism which enables the involved partners to see if the extent to which they have expressed their domain knowledge (which may sometimes be subject to a proprietary restricions) can satisfy the intended needs and behaviour of their product_to_be. We define an entailment relation which enables reasoning about the correctness of the specification, in terms of achieving a desired goal and, also testing about consequences of modifications in the workflow descriptions.

KW - Business process modeling

KW - Information management

KW - Knowledge representation and reasoning

KW - Process specification

KW - Reasoning about actions

KW - Worfklow systems

UR - http://www.scopus.com/inward/record.url?scp=0035623452&partnerID=8YFLogxK

UR - http://www.scopus.com/inward/citedby.url?scp=0035623452&partnerID=8YFLogxK

U2 - 10.1142/S021884300100045X

DO - 10.1142/S021884300100045X

M3 - Article

AN - SCOPUS:0035623452

VL - 10

SP - 483

EP - 507

JO - International Journal of Cooperative Information Systems

JF - International Journal of Cooperative Information Systems

SN - 0218-8430

IS - 4

ER -