Business Process Management (BPM)

Slides:



Advertisements
Similar presentations
Understanding Student Learning Objectives (S.L.O.s)
Advertisements

Software Requirements
1 Senn, Information Technology, 3 rd Edition © 2004 Pearson Prentice Hall James A. Senns Information Technology, 3 rd Edition Chapter 7 Enterprise Databases.
Semantic Business Management November 5, 2009 Paul Haley Automata, Inc. (412)
The 4 T’s of Test Automation:
Chapter 7 System Models.
Requirements Engineering Process
Introduction to Product Family Engineering. 11 Oct 2002 Ver 2.0 ©Copyright 2002 Vortex System Concepts 2 Product Family Engineering Overview Project Engineering.
Relational Database and Data Modeling
Jeff Mischkinsky Nickolas Kavantzas Goran Olsson Web Services Choreography.
18 Copyright © 2005, Oracle. All rights reserved. Distributing Modular Applications: Introduction to Web Services.
Copyright © 2006 Data Access Technologies, Inc. Open Source eGovernment Reference Architecture Approach to Semantic Interoperability Cory Casanave, President.
Page 1 Copyright © 2010 Data Access Technologies, Inc. Model Driven Solutions May 2009 Cory Casanave Architecture of Services SOA for E-Government Conference.
Presented to: By: Date: Federal Aviation Administration Registry/Repository in a SOA Environment SOA Brown Bag #5 SWIM Team March 9, 2011.
Leading for High Performance. PKR, Inc., for Cedar Rapids 10/04 2 Everythings Up-to-Date in Cedar Rapids! Working at classroom, building, and district.
Gaining Senior Leadership Support for Continuity of Operations
Introduction Lesson 1 Microsoft Office 2010 and the Internet
© 2009 IBM Corporation iEA16 Defining and Aligning Requirements using System Architect and DOORs Paul W. Johnson CEO / President Pragmatica Innovations.
Week 2 The Object-Oriented Approach to Requirements
Intro to LPA Feb 11©2011 EDAC All Rights ReservedSlide 1 The Executive Development Assessment Centre Introduction to the LPA February 2011.
Configuration management
Software change management
Chapter 5 – Enterprise Analysis
Leadership and Strategic Planning
OOAD – Dr. A. Alghamdi Mastering Object-Oriented Analysis and Design with UML Module 3: Requirements Overview Module 3 - Requirements Overview.
Testing Workflow Purpose
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 31 Slide 1 Service-centric Software Engineering.
Chapter 19 – Service-oriented Architecture
© 2011 TIBCO Software Inc. All Rights Reserved. Confidential and Proprietary. Towards a Model-Based Characterization of Data and Services Integration Paul.
1 Web-Enabled Decision Support Systems Access Introduction: Touring Access Prof. Name Position (123) University Name.
1. 2 August Recommendation 9.1 of the Strategic Information Technology Advisory Committee (SITAC) report initiated the effort to create an Administrative.
Legacy Systems Older software systems that remain vital to an organisation.
IONA Technologies Position Paper Constraints and Capabilities for Web Services
Software Requirements
How to commence the IT Modernization Process?
31242/32549 Advanced Internet Programming Advanced Java Programming
Executional Architecture
25 seconds left…...
Copyright © Richard N. Taylor, Nenad Medvidovic, and Eric M. Dashofy. All rights reserved. Analysis of Software Architectures.
Copyright 2001 Advanced Strategies, Inc. 1 Data Bridging An Overview Prepared for DIGIT By Advanced Strategies, Inc.
Marketing Strategy and the Marketing Plan
Chapter 11 Component-Level Design
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 31 Slide 1 Service-centric Software Engineering 1.
Web Service Ahmed Gamal Ahmed Nile University Bioinformatics Group
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 13 Slide 1 Application architectures.
© 2014 Fair Isaac Corporation. Confidential. This presentation is provided for the recipient only and cannot be reproduced or shared without Fair Isaac.
From Model-based to Model-driven Design of User Interfaces.
1 XML Web Services Practical Implementations Bob Steemson Product Architect iSOFT plc.
Introduction to Control Flow Patterns and BizAgi
Creating Architectural Descriptions. Outline Standardizing architectural descriptions: The IEEE has published, “Recommended Practice for Architectural.
David Harrison Senior Consultant, Popkin Software 22 April 2004
Enterprise Workflow CPSC 476 Lightening Talk Brenda Griffith/Katie Soto.
Annual SERC Research Review - Student Presentation, October 5-6, Extending Model Based System Engineering to Utilize 3D Virtual Environments Peter.
Presented to: By: Date: Federal Aviation Administration Enterprise Information Management SOA Brown Bag #2 Sam Ceccola – SOA Architect November 17, 2010.
SOA, BPM, BPEL, jBPM.
Intelligent Workflow Management System(iWMS). Agenda Background Motivation Usage Potential application domains iWMS.
Database System Development Lifecycle © Pearson Education Limited 1995, 2005.
Overview of the Database Development Process
Copyright © 2004 by The Web Services Interoperability Organization (WS-I). All Rights Reserved 1 Interoperability: Ensuring the Success of Web Services.
SOFTWARE DESIGN AND ARCHITECTURE LECTURE 05. Review Software design methods Design Paradigms Typical Design Trade-offs.
Architecture View Models A model is a complete, simplified description of a system from a particular perspective or viewpoint. There is no single view.
BPEL
Course: COMS-E6125 Professor: Gail E. Kaiser Student: Shanghao Li (sl2967)
IBM Global Services © 2005 IBM Corporation SAP Legacy System Migration Workbench| March-2005 ALE (Application Link Enabling)
1 Seminar on SOA Seminar on Service Oriented Architecture BPEL Some notes selected from “Business Process Execution Language for Web Services” by Matjaz.
Business Process Execution Language (BPEL) Pınar Tekin.
Business process management (BPM)
Business process management (BPM)
Introduction to Control Flow Patterns and BizAgi
CSSSPEC6 SOFTWARE DEVELOPMENT WITH QUALITY ASSURANCE
Presentation transcript:

Business Process Management (BPM) What is BPM? Why should I care? SOA Brown Bag #4 SWIM Team February 9, 2011

Agenda Introduction – why should I care? Definitions The benefits of BPM Model-Driven Environment BPMN and its challenges DoD Primitives Adoption Challenges BPM and SOA BPEL Orchestration Key characteristics of BPM Suites Tools Getting Started

Business and IT are tightly connected; they either succeed or fail together Business Process: The required steps to accomplish a specific business function. “Representation of what an organization does -- its work -- in order to accomplish a specific purpose or objective” source: BPMN Modeling and Reference Guide Business processes that require automation are implemented and facilitated through IT. As business processes change, IT has to change. Business Processes IT implementation

Processes drive a “true” SOA Myth: If you’ve implemented web services, you’ve implemented SOA. Reality: An organization will reap the full benefits of SOA if it starts with its business process. The reward at the end of the journey

BPM, BPMN & BPEL defined BPM Business Process Management A management approach focused on aligning all aspects of an organization based on the wants and needs of clients. BPMN Business Process Modeling Notation A graphical representation for specifying business processes in a business process model. BPEL Business Process Execution Language A standard executable language for specifying actions within business processes with web services, created by the Organization for the Advancement of Structural Information Standards.

Business Process Execution Business Rules Processing Additional elements BPE Business Process Execution Supports web-service languages for process definition and execution. Supports BPEL. BRP Business Rules Processing Infers outcomes based on data and operation results from previous business process executions (Business Rules Engine).

How does it all fit together? BPM BPMN BPEL Services Layer

What is the benefit of BPM? To gain sight and control of the business process. To provide a service orchestration layer in SOA implementation. To enable business agility.

What is a model-driven environment (MDE)? Models created based on today’s problem and tomorrow’s solution environments. Models can be created with sufficient specificity to generate the necessary technical artifacts for execution, or can be executed directly in the appropriate run-time environment. Business Process Automation engine (see next slide) Business rules engine

How do we get to a model-driven environment? A BPMN model captures business processes transfers them to a Business Process Automation engine in a BPMN-executable serialization format. Depending on the tool, it may also be: Transferred as an XML Process Definition Language (XPDL) format. Translated into the BPEL specification. Captured in one of the business rules languages.

Process and rule models in an MDE Source: DoD Federation Strategy

BPMN: different conformance subclasses for different uses Descriptive Contains a limited vocabulary to facilitate model understanding by a broad group of stakeholders. Analytical Adds more refined modeling elements, such as different event types and exceptions. Common Executable Focuses mainly on the attributes of BPMN elements that need to be maintained to support the execution of a BPMN process.

BPMN 2.0 Conformance Class

Challenges There are too many options to accomplish the same results or to diagram the same processes. Using tools interchangeably is nearly impossible.

Project: DoD Primitives Using DoD Primitives is a way to establish standard format for diagrams and for data that represents the diagrams, and for data that moves within and between the reality that diagrams represent. The Object Management Group selects DoD primitives as a BPMN conformance class.

Primitives Ontology (PrOnto) Primitives Modeling Guide (PriMo) Provides basic definitions of the architecture model semantics. Provides elementary rules for the connectivity of primitive constructs. Provides foundation building blocks for constructing architecture products. Caveat: A common vocabulary by itself does not guarantee high quality products. A style guide provides subjective advice that will ensure the design of high quality products. A style guide advises on: Choice of words. Which constructs are appropriate in a given situation. Choice of grammar: How to combine constructs to maximum effect. Dictionary Source: DoD briefing

Adoption challenges Thinking “Process” – True, executable BPM requires a new level of rigor and attention to business processes. Managing cultural impact – Documenting processes with tools (as opposed to pictures) will illustrate issues with current processes. A socialization strategy is key. Many popular BPM suites are ‘heavyweight’ and present a non-trivial learning curve.

Coarse-Level Web Services BPM and SOA Process Flows Coarse-Level Web Services Best Case Scenario

A business-driven SOA, defined and the services that enable them.” * “SOA is a way of describing an environment in terms of shared mission and business functions and the services that enable them.” * *Source: DoD Net-Centric Data Strategy

BPM and SOA ESB BAM Trusted Enclave DMZ Internet Internal Systems BPEL UDDI External Systems ESB WS Security Internal Systems BPEL BAM Trusted Enclave DMZ Internet

BPEL orchestration A BPEL orchestration is considered a web service in the domain to which it belongs. All BPEL processes provide a set of WSDL and schema definition files within the namespace that identifies the domain. The BPEL WSDL file will provide the binding information and the endpoint of the location where it is deployed. The orchestration is represented in a WS-BPEL standard representation that should be portable across BPEL engines. BPEL orchestration service should follow web service invocation standards (WS-I).

BPEL orchestration, continued All orchestrations have one entry point and one response point. The invocation/entry to the orchestration is marked with the receive block and delivers the message identified as the input parameter in the operation. Response block must return a message identified as the output parameter in the operation. A BPEL process may be synchronous e.g., a client needs to receive response immediately, or asynchronous e.g., a client will continue its operation and receive a response at a later time.

BPEL orchestration elements A BPEL orchestration consists of scopes, sequence, partner-links, variables, activities and fault handling. Scope: Identifies the unit of operation within an orchestration. This helps to avoid variable collisions, fault handling and ensuring transaction integrity. Sequence: Identifies a sequence of activities. Partner Links: External services are represented as partner links and they specify the WSDL file of the external service. Partner Links/Adapters: Some BPEL tools provide technology and application adapters that extend basic technologies i.e., databases, queues or applications i.e., CRM, ERP as web services through wizards. Variables: Data stores that hold the operational data within the life of the orchestration. Variables can be localized to a scope or set in the global scope. Activities: Transformations allow copying whole or sub trees of data across variables. Assignments allow specifying values for leaf nodes of an XML tree. Fault handling: Scope errors can be managed using fault handling for a graceful exit as well as for ensuring transactional integrity. Errors with partner link invocations must be handled using fault handling.

Key characteristics of BPM suites A graphical modeling capability Ability to simulate business process Ability to create rules to drive flow and decisions Ability to capture, present, and analyze process metrics Standards-based

Getting started Prototype/Pilot – an area for improvements! Choose a small, but business-significant process. Engage the vendor for training, preferably focusing on the pilot problem. Identify business services required for process support. “Prototype” the socialization process. Engage stakeholders to assess feasibility of making candidate process changes illustrated by the modeling process.

For more information White Papers IBM Thought Leadership White Paper Lombardi Downloads Office of Information Technology – ATO BPMS Services Julie Flores-Kriegsfeld Jonathan Beams www.swim.gov Jim.Robb@faa.gov Paul.Jackson@faa.gov Dov.Levy@DovelTech.com

Discussion