A Process View Framework for Artifact-Centric Business Processes Sira Yongchareon Chengfei Liu 2010 1.

Slides:



Advertisements
Similar presentations
Chapter 10 THINKING IN OBJECTS 1 Object Oriented programming Instructor: Dr. Essam H. Houssein.
Advertisements

Chapter 4.
SYSTEM ANALYSIS & DESIGN (DCT 2013)
Systems Analysis and Design 9th Edition
Introduction To System Analysis and Design
Fall 2007CS 225 Introduction to Software Design Chapter 1.
Introduction to Software Design Chapter 1. Chapter 1: Introduction to Software Design2 Chapter Objectives To become familiar with the software challenge.
Software Factory Assembling Applications with Models, Patterns, Frameworks and Tools Anna Liu Senior Architect Advisor Microsoft Australia.
Model Driven Architecture (MDA) Partha Kuchana. Agenda What is MDA Modeling Approaches MDA in a NutShell MDA Models SDLC MDA Models (an Example) MDA -
Viewpoint-oriented requirements methods. Objectives To explain the notion of viewpoints in RE To explain the notion of viewpoints in structured analysis.
Chapter 2: IS Building Blocks Objectives
Systems Analysis and Design in a Changing World, 6th Edition
Chapter 4.
Spring 2009CS 225 Introduction to Software Design Chapter 1.
The Software Product Life Cycle. Views of the Software Product Life Cycle  Management  Software engineering  Engineering design  Architectural design.
Process Modelling Using Data Flow Diagrams - Building and Levelling Them; Process Modelling Using Function Decomposition CSE Information Systems.
Lesson-21Process Modeling Define systems modeling and differentiate between logical and physical system models. Define process modeling and explain its.
ITIS 3200: Introduction to Information Security and Privacy Dr. Weichao Wang.
Introduction to Software Design Chapter 1. Chapter 1: Introduction to Software Design2 Chapter Objectives To become familiar with the software challenge.
Chapter 7 Structuring System Process Requirements
PROCESS MODELING Chapter 8 - Process Modeling
Chapter 1: Data Flow Diagram Structuring System Process Requirements
Sage CRM Developers Course
VirtualWorks.
Aurora: A Conceptual Model for Web-content Adaptation to Support the Universal Accessibility of Web-based Services Anita W. Huang, Neel Sundaresan Presented.
Chapter 6 System Engineering - Computer-based system - System engineering process - “Business process” engineering - Product engineering (Source: Pressman,
 Introduction Introduction  Purpose of Database SystemsPurpose of Database Systems  Levels of Abstraction Levels of Abstraction  Instances and Schemas.
Introduction CS 3358 Data Structures. What is Computer Science? Computer Science is the study of algorithms, including their  Formal and mathematical.
Agent Model for Interaction with Semantic Web Services Ivo Mihailovic.
Formal Analysis of Problem Domain Workflows Uldis Donins Riga Technical University Baltic DB & IS 2012, July 8-11, Vilnius, Lithuania This work.
Introduction to Software Design Chapter 1. Chapter Objectives  To become familiar with the software challenge and the software life cycle  To understand.
Systems Analysis and Design in a Changing World, Fifth Edition
Introduction To System Analysis and Design
Database Systems: Design, Implementation, and Management Tenth Edition
Chapter 1 : Introduction §Purpose of Database Systems §View of Data §Data Models §Data Definition Language §Data Manipulation Language §Transaction Management.
©Silberschatz, Korth and Sudarshan1.1Database System Concepts Chapter 1: Introduction Purpose of Database Systems View of Data Data Models Data Definition.
Introduction CS 3358 Data Structures. What is Computer Science? Computer Science is the study of algorithms, including their  Formal and mathematical.
1 Introduction to Software Engineering Lecture 1.
Requirements as Usecases Capturing the REQUIREMENT ANALYSIS DESIGN IMPLEMENTATION TEST.
7 Systems Analysis and Design in a Changing World, Fifth Edition.
Search Engine Optimization © HiTech Institute. All rights reserved. Slide 1 What is Solution Assessment & Validation?
Towards a Pattern Language for User Interface Design
CHAPTER 5 1 DATA AND PROCESS ANALYSIS. Chapter Objectives Describe data and process modeling concepts and tools, including data flow diagrams, a data.
Systems Analysis and Design in a Changing World, Fourth Edition
Mr.Prasad Sawant, MIT Pune India Introduction to DBMS.
Systems Analysis and Design 8th Edition
Search Engine Optimization © HiTech Institute. All rights reserved. Slide 1 Click to edit Master title style What is Business Analysis Body of Knowledge?
Lecture 4: Logical Database Design and the Relational Model 1.
Normalization. Overview Earliest  formalized database design technique and at one time was the starting point for logical database design. Today  is.
1 7 Systems Analysis and Design in a Changing World, 2 nd Edition, Satzinger, Jackson, & Burd Chapter 7 The Object-Oriented Approach to Requirements.
1 8.1 Requirements Analysis Rules of Thumb Rules of Thumb Models should focus on requirements that are visible within the problem or business domain. The.
© 2012 Cengage Learning. All Rights Reserved. This edition is intended for use outside of the U.S. only, with content that may be different from the U.S.
Introduction to DBMS Purpose of Database Systems View of Data
Software Project Configuration Management
The Components of Information Systems
Business System Development
Chapter 1: Introduction
Web Ontology Language for Service (OWL-S)
Chapter 1: Data Flow Diagram Structuring System Process Requirements
The Components of Information Systems
Chapter 3 The Relational Database Model
Introduction to Database Systems
Introduction to DBMS Purpose of Database Systems View of Data
Introduction to Systems Analysis and Design Stefano Moshi Memorial University College System Analysis & Design BIT
CHAPTER 9 (part a) BASIC INFORMATION SYSTEMS CONCEPTS
Chapter 7: Data Flow Diagram Structuring System Process Requirements
Metadata The metadata contains
Chapter 1: Introduction
Chapter 1: Introduction
Presentation transcript:

A Process View Framework for Artifact-Centric Business Processes Sira Yongchareon Chengfei Liu

 Process Modelling Process centric modelling *Artifact Centric Process (ACP) modelling – The focus is on describing how business data are changed / updated by a particular action or task.(Wikipedia)  The difference between these process modelling approaches: Artifact CentricProcess Centric Process LogicBusiness rules and servicesControl flows AbstractionObject based abstractionTask based abstraction Introduction 2

Components of ACP Atrifacts  An artifact is a business entity or an object involved in a business process which contains a set of attributes and states ( including: creation- completion- achieving) Services  A task /service is a task that requires input data from artifact or user and produces the output by updating the state of artifact Business rules  Determine the association between artifact and service in a condition-action style. Each rule determine which service is invoked and which state of the artifact needs to be updated under a pre-condition. 3

Motivation to process views 4 Concerns: Different levels of privacy, authority, access, etc. Different levels of detail/ interest for different roles (stakeholders) Solution: A framework that enables a customization of views for artifact centric business processes to support different levels of details based on role, authority control, or privacy requirements.

Operational view vs. Abstract views 5 Order Sale = {created: {init, open_for_item}, ready_for_shipping, in_processing :{delivering : {in_shipping, shipped}, billed}, closed}

Problem definitions/ Approach How to define, construct and validate constructed views for ACP? View Construction – State composition – State hiding View Validation – Rules for state tree preservation  Rule1. State ordering relation preserve – Rules for state transition preservation  Rule2. Hierarchy preservation  Rule3. Atomicity of composite state preservation  Rule4. business rule- Transitions of multiple artifacts preservation – Rules for attribute condition preservation  Rule5. Attribute condition preservation 6

View Construction View transformation by – State composition: nesting states at the same level under the new defined composite state – State hiding: only applicable for the nested states 7

Consistency Rule 1 State ordering relation preservation  This rule ensures that the transition corresponding to business rules of two views are consistent  If S x < S y in ACP view respecting role1 then S x < S y in ACP view respecting role2  If S x || S y in ACP view respecting role1 then S x || S y in ACP view respecting role2 (|| denotes independency) 8

Consistency Rule 2 Hierarchy preservation 9 Example: state ‘Shipped’ preserves the hierarchy consistency between the sale’s view and its underlying original view.

Consistency Rules: modification of business rules  State conditioning modification of business rule Hiding any states of an artifact will break up the transition 1 relation between such hidden state and other state. Transition rearrangement is required. (consistency rule 3) 10  Attribute conditioning modification of business rule Attempt to maintain the condition of each business rule that corresponds to the rearranged transition as most specific as possible. (consistency rule 5: the new attribute is the disjunction of every attribute proposition ) 1 A transition means that the state of the artifact changes from source state to target state if the precondition of the related business rule holds

Consistency Rule 3 Atomicity of composite state preservation To preserve the existence of transition between hidden state and non hidden state and the nonexistence between hidden state and hidden state If any state under the composite state is hidden then – An entry transition (from non-hidden state to hidden state) must be rearranged to composite state. – An exit transition (from non-hidden state to hidden state) must be rearranged to the composite state. – An inner transition (from hidden state to hidden state) must be removed. 11

Example Entry transition (delivering)={ready-for-shipping, r4, in-shipping} Exit transition(delivering) ={shipped, r7, billed} r3 and r11 are exit transitions to be rearranged. For composite state created r1 and r2 are inner transitions (as they don’t exist in the entry or exit functions) that need to be hidden. 12

Consistency Rule 4 Business rule- Transitions of multiple artifacts preservation – Ensures the integrity of a business rule of a hidden transition where the rule is used in multiple artifacts. – If a business rule induces transitions of multiple artifacts and any of these transitions in one artifact is hidden in ACP (l2) then such rule and its induced transitions in other artifacts must be hidden in ACP (l2) 13

Contribution/Conclusion A novel artifact centric process view framework respecting roles – an artifact-centric business process model – a process view model with the construction approach – a comprehensive set of view consistency rules to preserve the structural and behavioural consistency between process views 14