Status Presentation on the
Workflow Evaluation Workgroup
December 4, 1997
Goals of the Workflow
• Provide feedback to submitters to
– improve the final submission(s) and
– encourage convergence of the separate initial submissions.
• Identify and help address architectural issues as early as possible
• Collect and identify evaluation criteria
– From RFP
– Other criteria from workgroup members
• Assess submission(s) against evaluation criteria
• Provide a forum to help BODTF members understand and assess
• Generate an Evaluation Report to accompany the Final
Schedule (Depends on Final Submission
• Identify and circulate scenarios (e-mail, ASAP)
• Evaluation Worksession (2/8, Salt Lake City)
• Evaulation Workgroup Meeting (2/9)
• Evaluation Report Document Outline & Writing Assignments
• Workflow Evaluation Report (Final Submission + 4 Weeks)
Proposed Agenda for
Salt Lake City Worksession
• Document Evaluation Criteria and Assessment Hueristics
• Review Final Submission(s)
• Conduct Scenario Walkthroughs to exercise proposed interfaces
• Work on Evaluation Document
• General Requirements
• General Evaluation Criteria
• Mandatory Workflow Requirements
• Optional Workflow Requirements
• Issues to be Discussed
• Relationships to other OMG Technologies
• Workflow Evaluation Criteria
• Additional Evaluation Criteria (from workgroup members)
– Provide a focus for understanding proposed interfaces in operation
– Demontrate interface consistency and completeness
– Explore Workflow from Domain Perspectives
– Document Scenario in Narrative form (steps)
– Represent Workflow Schema for Scenario
– Generate Dynamic Model for Interactions (human actions and operation
– Capture Issues for Clarification by Submitters
• Candidate Scenarios
– Trouble Ticket
– PDM, e.g., Change of product data
– OOPSLA Scenarios
Relationships to Consider
– Workflow interactions with Business Objects
– Workflows re. Process Business Objects
– MOF representation of Workflow Meta-Schema
– Mapping between workflow concepts and UML concepts
Workflow Discussion Issues
• Definition of Workflow Schemas
– Can we achieve a Workflow Specification Language?
– How do we get reuse of common processes?
– What is the relationship to WfMC WPDL?
• Ad-hoc Workflows
– How do we make dynamic runtime modification of the current workflow
• Workflow Interoperability
– How do we define interoperability for Workflow Management Facilities?
– How do we measure interoperability?
– Are there different levels of interoperability that we can define?
– How can we achieve loose coupling of workflows?
Workflow Discussion Issues 2
• Workflow Granularity
– Are there different sizes of workflows?
– Are there tiers of granularity?
– How do we achieve security for workflows, particularly with delegation
across separate implementations (chain of responsibility)?
• Workflow Quality of Service
– How do we ensure integrity of workflows?
• Nested Domains
– How do you represent the way a business domain might consist of other
(business) domains and how this impacts the workflow interfaces?
Workflow Discussion Issues 3
• Workflow Terminology
– Can we standardize the use of terms and achieve a common
understanding of their meaning across BODTF? OMG?
• See the current thread on the CBO exploder . . .
• Extended Transactions
– Can we extend transactions across multiple activities?
– What are the recoverability boundaries for workflows?
• Naming/Trading/Scoping dependencies
• Parallelism and Synchronization
• Notification of Workflow state changes