1 Review Topics 1.Basic understanding of a business process 2.The relationship of a business process with a work flow 3.The different types aspects and.

Slides:



Advertisements
Similar presentations
Design by Contract.
Advertisements

Beta Testing: The Contractor’s Perspective Trns·port User Group Meeting October 2005.
BUSINESS DRIVEN TECHNOLOGY Enhancing Collaborative Partnerships
ARCH-01: Introduction to the OpenEdge™ Reference Architecture Don Sorcinelli Applied Technology Group.
LOTUS to SharePoint Migration Services. © 2010 Star Knowledge Technology Team Alliance 2 Key Discussion Points Star Knowledge Value Proposition Microsoft.
©2002, Pearson Education Canada 1.1 c h a p t e r 1 1 MANAGING THE DIGITAL FIRM: CANADA AND BEYOND CANADA AND BEYOND.
Chapter 15 Design, Coding, and Testing. Copyright © 2005 Pearson Addison-Wesley. All rights reserved Design Document The next step in the Software.
Pervasive Enablement of Business Process 徐天送 2004/11/2.
Copyright 2002 Prentice-Hall, Inc. Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer.
1 Review Topics The 3 Major Components of Workflow Management Systems 1.Buildtime 2.Metamodel 3.Runtime.
Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design Third Edition.
Nov. 14, 2007 Systems Engineering ä System ä A set or arrangement of things so related as to form a unity or organic whole. ä A set of facts, principles,
Chapter 1: Overview of Workflow Management Dr. Shiyong Lu Department of Computer Science Wayne State University.
The Architecture of Transaction Processing Systems
Lecture Nine Database Planning, Design, and Administration
Copyright 2002 Prentice-Hall, Inc. Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer.
Examine Quality Assurance/Quality Control Documentation
Chapter 10: Architectural Design
Workflow Description Language and Workflow Patterns Yi Wang.
1 Lab Beginning Analysis and Design 4 Completion of first version of use case diagram initiates the processes of analysis and design. 4 UML provides.
Introduction to Computer Technology
Enterprise Architecture
Documenting Network Design
WORKFLOW IN MOBILE ENVIRONMENT. WHAT IS WORKFLOW ?  WORKFLOW IS A COLLECTION OF TASKS ORGANIZED TO ACCOMPLISH SOME BUSINESS PROCESS.  EXAMPLE: Patient.
BUSINESS DRIVEN TECHNOLOGY Chapter Fourteen: Enhancing Collaborative Partnerships.
Workflow Management Kap. 1. Organizing Workflows
Chapter 10 Architectural Design
Introduction to Software Quality Assurance (SQA)
 Cloud computing  Workflow  Workflow lifecycle  Workflow design  Workflow tools : xcp, eucalyptus, open nebula.
Information System.
Test Organization and Management
Copyright © 2002 by The McGraw-Hill Companies, Inc. Information Technology & Management 2 nd Edition, Thompson Cats-Baril Chapter 8 I/S and Organizational.
Copyright 2002 Prentice-Hall, Inc. Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design.
Copyright 2002 Prentice-Hall, Inc. Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer.
CONTENTS Arrival Characters Definition Merits Chararterstics Workflows Wfms Workflow engine Workflows levels & categories.
Computer Science and Engineering 1 Service-Oriented Architecture Security 2.
OHT 11.1 © Marketing Insights Limited 2004 Chapter 9 Analysis and Design EC Security.
EMI INFSO-RI SA2 - Quality Assurance Alberto Aimar (CERN) SA2 Leader EMI First EC Review 22 June 2011, Brussels.
Event Management & ITIL V3
What is a Business Analyst? A Business Analyst is someone who works as a liaison among stakeholders in order to elicit, analyze, communicate and validate.
Chapter 1: Overview of Workflow Management Dr. Shiyong Lu Department of Computer Science Wayne State University.
ISM 5316 Week 3 Learning Objectives You should be able to: u Define and list issues and steps in Project Integration u List and describe the components.
Copyright 2002 Prentice-Hall, Inc. 1.1 Modern Systems Analysis and Design Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 1 The Systems Development.
PPA 502 – Program Evaluation Lecture 2c – Process Evaluation.
1 Analysis of workflows : Verification, validation, and performance analysis. Wil van der Aalst Eindhoven University of Technology Faculty of Technology.
Software Engineering Prof. Ing. Ivo Vondrak, CSc. Dept. of Computer Science Technical University of Ostrava
© 2006 Cisco Systems, Inc. All rights reserved.Cisco Public 1 Version 4.0 Gathering Network Requirements Designing and Supporting Computer Networks – Chapter.
Developing Component- Based Systems X LIU, School of Computing, Napier University TIP This chapter discusses the techniques to develop component-based.
Software Testing Process By: M. Muzaffar Hameed.
IT and Network Organization Ecommerce. IT and Network Organization OPTIMIZING INTERNAL COLLABORATIONS IN NETWORK ORGANIZATIONS.
JRA1.4 Models for implementing Attribute Providers and Token Translation Services Andrea Biancini.
Chapter 16 Quality Assurance Through Software Engineering Systems Analysis and Design Kendall & Kendall Sixth Edition.
Department of Computer Science 1 CSS 496 Business Process Re-engineering for BS(CS) Chapter 2: Workflow Management Khurram Shahzad
State of Georgia Release Management Training
Comparison of The Workflow Management Systems Bizagi, ProcessMaker, and Joget Mohamed Zeinelabdeen Abdelgader [1], Omer Salih Dawood [2], Mohamed Elhafiz.
John R Durrett1 Client/Server Computing Byte April 1995 & The Martian C/S book.
Business Process Execution Language (BPEL) Pınar Tekin.
CIS 375 Bruce R. Maxim UM-Dearborn
Chapter 1 The Systems Development Environment
Chapter 1 The Systems Development Environment
Chapter 1 The Systems Development Environment
Chapter 1 The Systems Development Environment
Chapter 1 The Systems Development Environment
Enterprise Integration: Workflow
WS Standards – WS-* Specifications
Chapter 1 The Systems Development Environment
Workflow and the WfMC Standards
Project Management Method and PMI ® PMBOK ® Roles
Presentation transcript:

1 Review Topics 1.Basic understanding of a business process 2.The relationship of a business process with a work flow 3.The different types aspects and types of workflows 4.Characteristics of applications built on a workflow 5.Advanced applications of workflows 6.Requirements of a production work flow 7.Relationship between workflow and other information processing technologies 8.Process engineering 9.Business logic models

2 What is a Business Process? “ A set of one or more linked procedures or activities which collectively realize a business objective or policy goal, normally within the context of an organizational structure defining function roles and relationships” (WfMC, 2003). WfMC is the Workflow Management Coalition

3 What is a Workflow? “The automation of a business process, in whole or part, during which documents, information, or tasks are passed from one participant to another for action, according to a set of procedural rules” (WfMC, 2003).

4 The Three Dimensions of Workflows Business processes and workflows have 3 dimensions 1.Process 2.Organization 3.Technology The three dimensions are also known as 3 Ws 1.What 2.Who 3.Technology Some call it 3Rs 1.Routes 2.Rules 3.Roles

5 Types of Users of Workflows End user – performs the individual tasks System administrator – has the overall responsibility for the workflow system Operation administrator – has the technical responsibility of the workflow system Process administrator – monitors the expected processing of the individual business process

6 Categories of Workflows Collaborative Ad Hoc Production Administrative Repetition Business Value low high

7 Application Structure of Workflows Systems A1A2 A3 A4A4 A5 C1 C2 C3

8 Application Structure of Workflows Systems A1A2 A3 A4A4 A5 C1 C2 C3 m1m2 m3m4

9 Operating Systems and Application OS An operating system is a fundamental systems software the enables application to run in their local environments A WFMS serves as a virtually mutual operating system, thus relieving applications from OS compatibility problems across multiple platform. It does that by invoking applications in their respective OS platform using mechanisms, such as, message queuing

10 Transactional Workflows The ACID properties of a transaction are: –Atomicity- A transaction is executed as a whole or it is aborted –Consistency – A transaction lead to a valid state of the system –Isolation – Data is isolated from other transaction until the transaction is completed –Durability – The changes are not lost under any circumstances In highly automated workflows, activities are often carried out as transactions. Such a transaction are called Global Transaction in Workflows The set of activates that are part of the global transaction are called atomic sphere

11 Workflows and Groupware Groupware is classified into: –Communication –Collaboration –Coordination This classification suggests four groupings of applications: –Communication systems –Shared data spaces –Workgroup computing

12 Business Engineering Business engineering is the analysis, specification, and modeling of business processes with their associated resources The key objective of business engineering are to: –Reduce time for the execution of the process –Eliminate unnecessary tasks –Perform parallel tasks Business engineering is triggered by the changing business environment The nature of processes have changed enormously in the last decade.

13 Business Modeling The objective is to show the current and intended process model of a business. The typical deliverables of business modeling are: –Process goals – customer sat., profitability, growth –Business processes – initially high level processes, roles, and activities are modeled –Organizational structures – structure of an organization –Business objects – not necessarily technology objects –Critical success factors – set of criteria to be met to declare success

14 Business Logic Collect Credit Information Assess Risk Accept Risk Request Approval Reject Risk Control Flow

15 Business Modeling Control Connector – the arrow that defines the flow of control from one activity to another activity. Fork – the activity that is the source of parallel work Join – the activity that is the target of the parallel work Join Condition – whether the activity can be performed Activation condition – when the activity can be carried out Exit condition – when the activity has successfully completed

16 Business Logic Collect Credit Information Assess Risk Accept Risk Request Approval Reject Risk Data Flow Name Address Risk Amount Name Address Risk Amount Amount > 1000 Risk is low Accept = Yes