Vodak kernel data model

Duchene, H.; Kaul, M.; Turau, Volker

doi:10.1007/3-540-50345-5_21

Cited by 7 publications

(1 citation statement)

References 5 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The COACT concepts can be embedded into the object-oriented database programming language (both Data Definition Language and Data Manipulation Language) so that they become an integral part of the database system. An alternative is to utilize the openness of the VO-DAK Model Language VML [25] and to incorporate the COACT concepts by defining various meta classes covering the semantics of cooperative activities. These meta classes guide the composition of activities and control the execution, termination and interaction of user activities.…”

Section: Coact Modelmentioning

confidence: 99%

Workflow and Process Automation

Cichocki¹,

Helal²,

Rusinkiewicz³

et al. 1998

View full text Add to dashboard Cite

Workflow and process automation : concepts and technology I by AndrzejCichocki ... [et al.]. p. cm. --(Kluwer international series in engineering and computer science ; SECS 432) Includes bibliographical references and index. ISBN 978-1-4613-7599-9 ISBN 978-1-4615-5677-0 (eBook)This chapter is focused on the first phase of the workflow application life cycle (Figure 2.1) that is responsible for process modeling and investigation of its properties.The purpose of modeling is to produce an abstraction of a process (mode~ that serves as a basis for the workflow specification. The model of a process enables us to understand what activities, dependencies among activities, and roles (human or information system skills) are necessary to the process.Process modeling methodologies can be mainly divided into the following three categories: communication-based, artifact-based and activity-based. Communication-based ModelingThe communication-based methodologies are based on Winograd/Flores "Conversation for Action Model" [92]. This methodology type represents an action in a workflow based on communication between a customer and a performer. This communication consists of four phases that are defined as follows (Figure 2.2):1. Request -a customer requests an action to be performed CHAPTER 2 Analysis Administration Development Execution Figure 2.1 Life cycle of a workflow application [41] Request ~ \ B9 Offstlon Customer ~ow ~ Pertonner Acceptance Performance Figure 2.2 Conversation for action model 2. Negotiation -customer and performer agree on the action to be performed 3. Performance -the action is performed 4. Acceptance -the customer reports satisfaction with the action Process Technology Customer r::~ Equipment Proc't Office Proc't Office Verify ~ Accounts ~J~ Get~ Vendors k J ~~ V~dM Figure 2.3 Communication-based workflow of procure equipment process 7

show abstract

Section: Coact Modelmentioning

confidence: 99%