Show/Hide Menu
Hide/Show Apps
Logout
Türkçe
Türkçe
Search
Search
Login
Login
OpenMETU
OpenMETU
About
About
Open Science Policy
Open Science Policy
Open Access Guideline
Open Access Guideline
Postgraduate Thesis Guideline
Postgraduate Thesis Guideline
Communities & Collections
Communities & Collections
Help
Help
Frequently Asked Questions
Frequently Asked Questions
Guides
Guides
Thesis submission
Thesis submission
MS without thesis term project submission
MS without thesis term project submission
Publication submission with DOI
Publication submission with DOI
Publication submission
Publication submission
Supporting Information
Supporting Information
General Information
General Information
Copyright, Embargo and License
Copyright, Embargo and License
Contact us
Contact us
History management in workflow systems
Date
1998-10-28
Author
Koksal, P
Arpinar, S
Doğaç, Asuman
Metadata
Show full item record
This work is licensed under a
Creative Commons Attribution-NonCommercial-NoDerivatives 4.0 International License
.
Item Usage Stats
47
views
0
downloads
Cite This
A workflow history manager maintains the information essential for workflow monitoring and data mining as well as for recovery and authorization purposes.
Subject Keywords
History management
,
Workflow system
,
Information essential
,
Authorization purpose
URI
https://hdl.handle.net/11511/62831
Collections
Department of Computer Engineering, Conference / Seminar
Suggestions
OpenMETU
Core
Specification and scheduling of workflows under resource allocation constraints
Karagöz Şenkul, Pınar; Toroslu, İsmail Hakkı; Department of Computer Engineering (2003)
Workflow is a collection of tasks organized to accomplish some business process. It also defines the order of task invocation or conditions under which task must be invoked, task synchronization, and information flow. Before the execution of the workflow, a correct execution schema, in other words, the schedule of the workflow, must be determined. Workflow scheduling is finding an execution sequence of tasks that obeys the business logic of workflow. Research on specification and scheduling of workflows has...
Deriving User Requirements from Business Process Models for Automation: A Case Study
Aysolmaz, Banu; Demirrs, Onur (2014-08-25)
The knowledge captured in business process models is essential to identify user requirements of the process aware information system to execute the processes. Frequently, relations between the models and requirements are either not established or only partially available. This results in increased effort, broken traceability, completeness and consistency problems for user requirements. We proposed a unified business process modeling method, UPROM, to analyze and develop models for business processes and use...
Evaluation and selection of case tools: a methodology and a case study
Okşar, Koray; Okşar, Koray; Department of Information Systems (2010)
Today’s Computer Aided Software Engineering (CASE) technology covers nearly all activities in software development ranging from requirement analysis to deployment.Organizations are evaluating CASE tool solutions to automate or ease their processes. While reducing human errors, these tools also increase control, visibility and auditability of the processes. However, to achieve these benefits, the right tool or tools should be selected for usage in the intended processes. This is not an easy task when the vas...
Dflow workflow management system
Dengi, C; Neftci, S (1997-09-02)
Process specification, automatic recovery: concurrency control and heterogeneity among processing entities are known problems of workflow management systems. Dflow provides a workflow specification language which combines the expressive power of a structural programming language with the recovery capabilities of transaction systems. Dflow tries to solve the problems of automatic recovery in its model and the problems of concurrency control and heterogeneity in its architecture.
WSLA Extensions for Managing Composite Semantic Web Services
Elgedawy, Islam (2016-09-30)
Managing Service Level Agreement (SLA) for composite semantic web services is a very complex process, as it involves many complex tasks such as components discovery, provisioning, monitoring, recovery, and coordination. Indeed, managing all these tasks manually is a very cumbersome operation, nevertheless it is time consuming and prone to errors. To overcome such problems, automated SLA management for composite semantic web services is needed. This requires the SLA of the composite service to be described i...
Citation Formats
IEEE
ACM
APA
CHICAGO
MLA
BibTeX
P. Koksal, S. Arpinar, and A. Doğaç, “History management in workflow systems,” 1998, vol. 53, p. 254, Accessed: 00, 2020. [Online]. Available: https://hdl.handle.net/11511/62831.