Specifying Workflow using CO- OPN Ang Chen SMV group 11 Mars, 2005.

Slides:



Advertisements
Similar presentations
Auto-Generation of Test Cases for Infinite States Reactive Systems Based on Symbolic Execution and Formula Rewriting Donghuo Chen School of Computer Science.
Advertisements

When is Orientated Programming NOT? Mike Fitzpatrick.
A university for the world real R © 2009, Chapter 3 Advanced Synchronization Moe Wynn Wil van der Aalst Arthur ter Hofstede.
Software and Systems Engineering Seminar Winter 2011 Domain-specific languages in model-driven software engineering 1 Speaker: Valentin ROBERT.
SATEL Semi Automatic TEsting Language University of Geneva Levi Lúcio, Didier Buchs M-TOOS, Portland 4/30/2015.
Towards Workflow Pattern Support of Event-Driven Process Chains (EPC) Jan Mendling, Gustaf Neumann Dept. of IS and New Media, WU Wien, Austria Markus Nüttgens.
Background information Formal verification methods based on theorem proving techniques and model­checking –to prove the absence of errors (in the formal.
® IBM Software Group © 2006 IBM Corporation Rational Software France Object-Oriented Analysis and Design with UML2 and Rational Software Modeler 04. Other.
1 Flexible Subtyping Relations for Component- Oriented Formalisms and their Verification David Hurzeler PhD Examination, 9/11/2004.
Object-Oriented Analysis and Design
Irina Rychkova. 9/20061 Systemic approach towards model definition Model transformation semantics.
Activity Diagrams [Arlow and Neustadt, 2005] CS 425 / 625 Seminar on Software Engineering University of Nevada, Reno Department of Computer Science & Engineering.
Architecture-driven Modeling and Analysis By David Garlan and Bradley Schmerl Presented by Charita Feldman.
1 CS 426 Senior Projects Chapter 14: Activity Diagrams [Arlow and Neustadt, 2005] February 17, 2009.
© Copyright Eliyahu Brutman Programming Techniques Course.
Visual Basic Introduction IDS 306 from Shelly, Cashman & Repede Microsoft Visual Basic 5: Complete Concepts and Techniques.
Business Process Modeling Workflow Patterns Ang Chen July 8, 2005.
Router modeling using Ptolemy Xuanming Dong and Amit Mahajan May 15, 2002 EE290N.
Principle of Functional Verification Chapter 1~3 Presenter : Fu-Ching Yang.
A university for the world real R © 2009, Chapter 23 Epilogue Wil van der Aalst Michael Adams Arthur ter Hofstede Nick Russell.
*Law and Coordination Rodrigo Paes. © LES/PUC-Rio Agenda Integration Coordination BPEL example Birth *Law and Coordination Further Steps.
程建群 博士(Dr. Jason Cheng) 年03月
Speaking Bluntly about SharpHDL: Some Old Stuff and Some Other Proposed Future Extensions Gordon J. Pace & Christine Vella Synchron’05 Malta, November.
Copyright 2001 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Appendix A Object-Oriented.
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 20 Object-Oriented.
Unified Modeling Language, Version 2.0
Programming in Java Unit 3. Learning outcome:  LO2:Be able to design Java solutions  LO3:Be able to implement Java solutions Assessment criteria: 
WSMX Execution Semantics Executable Software Specification Eyal Oren DERI
© DATAMAT S.p.A. – Giuseppe Avellino, Stefano Beco, Barbara Cantalupo, Andrea Cavallini A Semantic Workflow Authoring Tool for Programming Grids.
Web Service Composition workflow patterns in BPEL4WS Eyal Oren DERI 2004/06/02
Automatic Test Generation from here until the end (of my Phd.) University of Geneva Levi Lúcio SMV & Les Diablerets.
1 Levi Lúcio © A Test Selection Language for CO-OPN Specifications Levi Lúcio, Luis Pedro and Didier Buchs University of Geneva.
Paper written by Flavio Oquendo Presented by Ernesto Medina.
Procedures for managing workflow components Workflow components: A workflow can usually be described using formal or informal flow diagramming techniques,
An Ontological Framework for Web Service Processes By Claus Pahl and Ronan Barrett.
Object-Oriented Analysis and Design. Lesson 1: Introduction to Software Engineering.
Automata Based Method for Domain Specific Languages Definition Ulyana Tikhonova PhD student at St. Petersburg State Politechnical University, supervised.
Object-Oriented Modeling: Static Models. Object-Oriented Modeling Model the system as interacting objects Model the system as interacting objects Match.
Introduction to OOAD and the UML
BPEL Business Process Engineering Language A technology used to build programs in SOA architecture.
Object Oriented Analysis & Design & UML (Unified Modeling Language)1 Part VI: Design Continuous Activity Diagams State Diagrams.
1 Unified Modeling Language, Version 2.0 Chapter 2.
Chapter 14: Activity Diagrams November 2015 [Arlow and Neustadt, 2005] CS 425/625 Senior Projects University of Nevada, Reno Department of Computer Science.
Formal Verification. Background Information Formal verification methods based on theorem proving techniques and model­checking –To prove the absence of.
UML Course Instructor: Rizwana Noor. Overview  Modeling  What is UML?  Why UML?  UML Diagrams  Use Case  Components  Relationships  Notations.
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Appendix A Object-Oriented Analysis and Design A.1.
© 2009 Artisan Software Tools. All rights reserved. Testing Solutions with UML/SysML Andrew Stuart, Matthew Hause.
UML (Unified Modeling Language)
Process Mining – Concepts and Algorithms Review of literature on process mining techniques for event log data.
© Copyright 2010 Rockwell Collins, Inc. All rights reserved. Practical SysML Applications: A Method to Describe the Problem Space Ray Jorgensen David Lempia.
Slide 1 Unified Modeling Language, Version 2.0 Object-Oriented SAD.
CHAPTER
Cmpe 589 Spring 2006.
Main issues: • What do we want to build • How do we write this down
Object-Oriented Analysis and Design
Systems Analysis and Design With UML 2
Unified Modeling Language
About the Presentations
Anatomy of a Class & Method
UML Activity Diagrams & State Charts
Logical architecture refinement
Chapter 14: Activity Diagrams
Chapter 20 Object-Oriented Analysis and Design
Wil van der Aalst Eindhoven University of Technology
An Introduction to Software Architecture
Chapter 14: Activity Diagrams
Chapter 14: Activity Diagrams
Identifying & Creating Use Cases - Part 3
TYPES OF TESTING.
ERROR HANDLING AND DEBUGGING
Presentation transcript:

Specifying Workflow using CO- OPN Ang Chen SMV group 11 Mars, 2005

Plan Workflow patterns CO-OPN workflow building blocks Perspectives, patterns Abstract Data Type Reusability Verification, soundness Code generation and simulation Conclusion

Workflow patterns Van Der Aalst 20 patterns, control-flow oriented Perspectives Control: flow of cases (instances) Data: data and information processing Operation: interactions with human and external systems Resources

Elements of Workflow Elements Activities Cases: instances Actors (roles): human, machine Data, information Resources Processes How to define, deploy and execute processes?

Our approach: modeling workflow using algebraic Petri net Specify pre- and post- conditions Represent activities by means of classes Using building blocks to model control-flows By connecting activities and building blocks, we define and construct workflows. Advantages: reconfigurable, flexible, reusable.

CO-OPN building blocks for workflow Activity WorkflowCO-OPN CasesADT DataADT ActivityClass ProcessContext OperationMethod EventMethods/gate

CO-OPN building blocks for workflow cont. Top-down direction: Data, operation and event flow Left-right direction: control-flow

CO-OPN building blocks for workflow cont. Example: AND join Hierarchies

Perspectives We classify three stereotypes of methods and gates in our building blocks: instance flow, action/event flow and data flow Methods are input flows, gates are output flows Instance flows are always fireable. Action/event flows and data flows are not, they may synchronize with each other. We predefine an ADT “Case” to represent instance Naturally we obtain three perspectives: Control-flow: flow of instance Data: ADTs Operational: methods and gates represent input and output actions/events

Example Travel reservation Votation

Algebraic Abstract Data Type

Supported Workflow Patterns AND, OR Join/Split, choice, merge Multi-choice, synchronizing merge Multi-merge, discriminator, arbitrary cycles, implicit termination Multi-instance support …

Reusability Modularity Activity reusability Black box: coordinal composition, the context White box: class inheritance Patterns: building block We define the process by creating a context Process reusability A process can be a component of another process: composition of context Substitutability: depend on criteria…

Verification Behaviors are defined by axioms Possible to prove properties using formal techniques …

Code generation and simulation Generate workflow controller Prototype interpretable Simulation in CoopnBuilder

Conclusion CO-OPN provide a powerful way to represent business activities and processes Declarative activity definition: using pre- and post- conditions Three perspectives are modeled: contol-flow, data and operational ADT is an indispensable element