The 2005 Enterprise Architecture, Process Modeling & Simulation

Total Page:16

File Type:pdf, Size:1020Kb

The 2005 Enterprise Architecture, Process Modeling & Simulation BUSINESS PROCESS TRENDS A BPT Report The 2005 Enterprise Architecture, Process Modeling & Simulation Tools Report Version 1.0 April 28, 2005 Curtis Hall Paul Harmon www.bptrends.com BPTrends The 2005 EA, Process Modeling & Simulation Tools Report Contents Foreword by Celia Wolf …………………………………...………………..……………….. 1 Introduction ………………………………………………………………….………………… 4 A Detailed Analysis of EA, Process Modeling & Simulation Tools …………………13 CACI’s SIMPROCESS ………………………………………………………………………. 25 Holocentric’s Holocentric Modeler ....……………………………………….……… ……… 41 IDS Scheer’s ARIS ………......………………………………………….…………………… 57 iGrafx’s iGrafx ……………....…………………………………………......………………… 72 MEGA’s MEGA Suite ……………………………………..…..……………………………… 87 Popkin Software’s System Architect ……….……..................…………...……………… 104 Process Wizard Ltd.’s ProcessWizard ……………………………..…………..........…… 118 Proforma Corporation’s ProVision ………………………………………………………… 133 ProModel Solutions’ Process Simulator ………………………...………………...……… 147 xBML Innovations’ xBML Modeling Suite ……………………………….…..……….…… 158 EA, Process Modeling & Simulation Tools Matrix ……………………...…………… 174 Author’s Bios ………………………………………………………………………………… 182 Copyright (c) 2005 Business Process Trends. www.bptrends.com BPTrends The 2005 EA, Process Modeling & Simulation Tools Report Celia Wolf Foreword Foreword This is the second in a series of reports that BPTrends plans to produce and publish on business process software products. We are producing these reports to provide our members with an overview of the various types of business process software products available today. In each report we will define the specific market, describe the features important in tools designed for that market, provide detailed reviews of the leading players and their products, and provide a comparison of the key features of the products. Figure 1 provides an overview of the business process software products market as BPTrends currently defines it. We use circles to represent the major product groupings and have overlapped circles to suggest key relationships. The olive area in the center of Figure 1 represents the product groupings we focused on in the BPTrends 2005 Enterprise Architecture, Process Modeling, and Simulation Tools Report. Drawing Tools Process Organization Modeling Simulation and Enterprise Tools Tools Modeling Tools BP Business Rule Languages Management Tools Workflow Business Process BPM Tools Management Suites Applications EAI Tools Business Process Software Monitoring Tools Modeling & Development Tools Figure 1. The Business Modeling Software Product Market. What Are Enterprise Architecture, Process Modeling, and Simulation Tools? This report focuses on tools that companies use to analyze and modify business processes. The core tool for this task is a tool that lets business managers or analysts create a diagram or model of a business process and then change that diagram to explore how the process could be improved or redesigned. Some business process change teams prefer process modeling tools that are simple and easy to use. Others prefer more sophisticated tools that can support additional tasks. Many organizations use the same process modeling tool to analyze many different processes. Some create Copyright (c) 2005 Business Process Trends. www.bptrends.com 1 BPTrends The 2005 EA, Process Modeling & Simulation Tools Report Celia Wolf Foreword diagrams of entire value chains and then subdivide the chain into separate processes and subprocesses to understand how everything works together. Similarly, many companies analyze their organizations as a whole to define how all the processes or value chains work together. At the same time they extend the process models to show how resources flow into the processes and how employees and software systems support processes. Others use their process modeling tools to gather cost data on processes. Some use process simulation tools to explore how a process will function before they make physical changes in actual processes. Tools that provide support for organization analysis and modeling are, today, usually termed Enterprise Architecture tools. Tools that focus entirely on simulation are termed Simulation Tools. Increasingly, however, companies are using business process modeling tools that also incorporate support for enterprise modeling and simulation. Thus, we decided to include all the tools that can be used for Enterprise Architecture, Business Process Modeling, and Process Simulation in the same report. To simplify the language of the report, we will use the term modeling tool as a generic phrase whenever we want to refer all the tools being considered in this report. We will use the terms enterprise architecture tool, process modeling tool, or process simulation tool only when we wish to refer to tools that provide these specific functions. We have consciously excluded three other types of tools from this report. We do not consider the simpler graphical drawing or diagramming tools. These tools are widely used for creating simple process diagrams, but they cannot support sustained modeling and redesign efforts. The key to discriminating between the drawing tools and serious process modeling tools is whether they store data about the models in a database or repository. Serious modeling tools create data entries in a database. Thus, a box drawn in a process modeling tool is not simply an image of a box; it is an object in a database. Once you give the box a name you can begin to record information about that process or activity. You can record costs and associated business rules. You can indicate where inputs come from and where outputs go, and you can name the software applications that support that activity. More important, you can create a new diagram and create a new box with the same name and immediately inherit all the data you have already entered to describe that activity. In other words, a serious process modeling tool is the interface for a database that allows you to organize and save information about your business processes. All of the process modeling tools considered in this report store data about processes and can be used to create and manage a database of information about your organization’s processes. Second, we do not consider either BPM Suites or Software Modeling Tools in this report. The BPM Suites are considered in a separate report, The BPTrends 2005 BPM Suites Report, which we published and posted to BPTrends in March, 2005 BPM Suites include process modeling tools, but they are primarily used to manage the day-to-day execution of business processes. They also provide other capabilities used by those managing processes, including business rule execution engines and real-time process monitoring. Similarly, we have not included the various Software Modeling Tools in this report. Those tools are used by software developers to capture business requirements and to design software applications. A glance at marketing data reveals that vendors in the Process Modeling, BPM Suites, and Software Modeling markets are not competing with each other. In essence, there are three separate market niches. The leading Process Modeling vendors are all flourishing and Process Modeling tools are being used by business managers and analysts who want to create or improve their business processes. Our objective in this report is to describe the various options available from Enterprise Architecture, Process Modeling, and Process Simulation vendors. Different companies are using these tools for very different purposes. It does not make sense to argue that there is, or should be, a “best” tool with a specific configuration that would be best for all. Thus, we have avoided any comparison that suggests that some tools are the “winners” while others are “less desirable.” Instead, we analyze each Copyright (c) 2005 Business Process Trends. www.bptrends.com 2 BPTrends The 2005 EA, Process Modeling & Simulation Tools Report Celia Wolf Foreword product, explain what specific markets the vendor is pursuing, consider how the tool is adapted for that market, and identify what is special or unique about each product. To make comparisons as easy as possible, we have explored the capabilities of modeling tools in several ways. These are discussed in the section entitled, “A Detailed Analysis of Enterprise, Process Modeling and Simulation Tools.” Some vendors only implement a subset of the features we describe. That does not necessarily detract from their offering. It could mean that the vendor does not think the feature is required for its target market. Or it could mean that the vendor thinks it is more efficient to partner with another vendor who provides that specific feature. For example, we asked each vendor how it supports simulation. Some have built their own simulation engine into their tool. Others provide links to another simulation tool developed by a third party. Still others do not provide a simulation engine, allowing users to select their own. No one of these solutions makes the underlying Process Modeling tool better or worse, although it may make it more or less popular with a particular user. Users that already have a simulation tool may prefer a business modeling product without an embedded simulation system. Users at companies that do not currently have a standard simulation tool may prefer a modeling tool with its own simulation engine. As we said, it is impossible to say exactly what the ideal business modeling tool should have or not have. We have sought to provide a
Recommended publications
  • Business Process Model and Notation—BPMN
    Business Process Model and Notation—BPMN Mark von Rosing, Stephen White, Fred Cummins, Henk de Man INTRODUCTION This chapter is intended to provide an overview and introduction to the Busi- ness Process Model and Notation (BPMN). We will describe BPMN and its his- toric development. In addition, we will provide the general context and usage of BPMN, layered upon the technical details defined in the BPMN 2.0 Specification. The basics of the BPMN notation will be described—that is, the types of graphical shapes, their purpose, and how they work together as part of a Business Process Model/Diagram. Also discussed will be the different uses of BPMN diagram types, including how levels of precision affect what a modeler will include in a diagram. Finally, the value in using BPMN as a standard notation will be defined. It is vital to note that because both main authors and the additional four authors all officially work with the Object Management Group (OMG) to develop standards, this chapter and its content be based on the official OMG BPMN specification.1 WHAT IS BPMN? Business Process Model and Notation (BPMN) is a standard for business process modeling that provides graphical notation for specifying business processes in a Business Process Diagram (BPD),2 based on traditional flowcharting techniques. The objective of BPMN is to support business process modeling for both technical users and business users, by providing notation that is intuitive to business users, yet able to represent complex process semantics. The BPMN 2.0 specification also pro- vides execution semantics as well as mapping between the graphics of the notation and other execution languages, particularly Business Process Execution Language (BPEL).3 BPMN is designed to be readily understandable by all business stakeholders.
    [Show full text]
  • BPMN and Business Process Management
    BPMN and Business Process Management Introduction to the New Business Process Modeling Standard By Martin Owen and Jog Raj, Popkin Software BPMN and Business Process Management Executive Summary ....................................................................................... 3 Introducing BPMN .......................................................................................... 4 BPMN Enables Business Process Management (BPM)......................................... 4 BPMI.ORG Created to Establish BPM Standards ............................................. 4 Rigor of the BPMI.ORG Standards ............................................................... 5 BPMN Enables Modeling of B2B and B2C ......................................................... 5 BPMN Maps to Business Execution Languages.................................................. 5 BPMI.ORG Works with OASIS for e-Business Standards.................................. 5 BPMN Models Web Services .......................................................................... 6 A First Look at BPMN ...................................................................................... 7 Modeling Business Events............................................................................. 8 More Complex Events -- Specifying Trigger Types ......................................... 8 Business Processes, Sub-Processes, and Tasks ...............................................10 Decomposing Your Processes Into Hierarchies..............................................10 Easily Viewing
    [Show full text]
  • Business Process Modeling and Execution. Tools and Technologies Report for Soames Project Soames for Report Technologies and Tools Execution
    ESPOO 2007 VTT RESEARCH NOTES 2407 VTT Tiedotteita – Research Notes project NOTES 2407 Business Process Modeling and Execution. Tools and technologies report for SOAMeS VTT RESEARCH 2385 Löfman, Jari, Keto, Vesa & Mészáros, Ferenc. FEFTRATM. Verification. 2007. 103 p. + app. 4 p. 2386 Loikkanen, Torsti, Hyytinen, Kirsi & Koivusalo, Salla. Yhteiskuntavastuu ja kilpailu- kyky suomalaisyrityksissä. Nykytila ja kehitysnäkymät. 2007. 118 s. 2387 Henttonen, Katja. Stylebase for Eclipse. An open source tool to support the modeling of quality-driven software architecture. 2007. 61 p. + app. 15 p. 2388 Lanne, Marinka & Kupi, Eija. Miten hahmottaa security-alaa? Teoreettinen malli Suomen security-liiketoiminta-alueista. 2007. 52 s. + liitt. 1 s. 2389 Leikas, Jaana & Lehtonen, Lauri. Ikääntyvien idealiike. Käyttäjälähtöisellä innovoinnilla elämänmakuisia mobiilipalveluja. 2007. 34 s. 2390 Tuominen, Anu, Ahlqvist, Toni, Rämä, Pirkko, Rosenberg, Marja & Räsänen, Jukka. Liikennejärjestelmän teknologiapalvelujen vaikutusarvioinnit tulevaisuudessa. 2007. 64 s. + liitt. 5 s. 2391 Mikkola, Markku & Pirttimäki, Antti. Tuotekehitys Kiinassa. Uhka, mahdollisuus vai yhdentekevää? 2007. 31 s. 2392 Kettunen, Jari, Rakshit, Krishanu & Uoti, Mikko. Electronic India. Market trends and industry practices in IT services, telecoms and online media. 2007. 98 p. + app. 2 p. 2394 Herrala, Maila. The value of transport information. 2007. 87 p. + app. 5 p. 2395 Aarnisalo, Kaarina, Heiskanen, Seppo, Jaakkola, Kaarle, Landor, Eva & Raaska, Laura. Traceability of foods and foodborne hazards. 2007. 46 p. + app. 2 p. 2396 Nylund, Nils-Olof, Erkkilä, Kimmo, Clark, Nigel & Rideout, Greg. Evaluation of duty cycles for heavy-duty urban vehicles. Final report of IEA AMF Annex XXIX. 2007. 81 p. + app. 10 p. 2397 Helynen, Satu, Flyktman, Martti, Asikainen, Antti & Laitila, Juha. Metsätalouteen ja Mika Koskela & Jyrki Haajanen metsäteollisuuteen perustuvan energialiiketoiminnan mahdollisuudet.
    [Show full text]
  • OMG Unified Modeling Language Specification
    OMG Unified Modeling Language Specification Version 1.4 September 2001 Copyright © 1997-2001 Computer Associates International Inc. Copyright © 1997-2001 Electronic Data Systems Corporation Copyright © 1997-2001 Hewlett-Packard Company Copyright © 1997-2001 IBM Corporation Copyright © 1997-2001, I-Logix Copyright © 1997-2001 IntelliCorp Copyright © 1997-2001 Microsoft Corporation Copyright © 1997-2001 Object Management Group Copyright © 1997-2001 Oracle Corporation Copyright © 1997-2001 Ptech Inc. Copyright © 1997-2001 Rational Software Corporation Copyright © 1997-2001 Reich Technologies Copyright © 1997-2001 Softeam Copyright © 1997-2001 Taskon A/S Copyright © 1997-2001 Unisys Corporation PATENT The attention of adopters is directed to the possibility that compliance with or adoption of OMG specifications may require use of an invention covered by patent rights. OMG shall not be responsible for identifying patents for which a license may be required by any OMG specification, or for conducting legal inquiries into the legal validity or scope of those patents that are brought to its attention. OMG specifications are prospective and advisory only. Prospective users are responsible for protecting themselves against liability for infringement of patents. NOTICE The information contained in this document is subject to change without notice. The material in this document details an Object Management Group, Inc. specification. This document does not represent a commitment to implement any portion of this specification in any companies' products.
    [Show full text]
  • Business Modeling Techniques
    Enterprise Architect User Guide Series Business Modeling Techniques What are the best Business Modeling techniques? Here are fifty valuable business modeling techniques using Sparx Systems Enterprise Architect's Business modeling capabilities for Business Analysts, managers, architects, designers, testers and more. Author: Sparx Systems & Stephen Maguire Date: 16/01/2019 Version: 1.0 CREATED WITH Table of Contents Business Modeling Techniques 4 Strategy 6 Balanced Scorecard 7 Benchmarking and Market Analysis 9 Business Capability Analysis 11 Business Cases 13 Business Model Canvas 16 Organizational Modeling 18 SWOT Analysis 20 Collaboration 22 Brainstorming 23 Collaborative Games 25 Focus Groups 27 Interviews 29 Mind Mapping 31 Workshops 33 Analysis 37 Acceptance and Evaluation Criteria 38 Business Rules Analysis 39 Data Mining 41 Decision Analysis 42 Document Analysis 45 Financial Analysis 47 Interface Analysis 48 Non-Functional Requirements Analysis 50 Observation 53 Process Analysis 55 Root Cause Analysis 57 Modeling 58 Concept Modeling 59 Data Dictionary 62 Data Flow Diagrams 64 Data Modeling 65 Decision Modeling 67 Functional Decomposition 68 Glossary 71 Process Modeling 72 Prototyping 75 Sequence Diagrams 77 State Modeling 78 Use Cases and Scenarios 80 User Stories 82 Project Management 84 Backlog Management 85 Estimation 87 Item Tracking 88 Lessons Learned 90 Metrics and Key Performance Indicators (KPIs) 92 Prioritization 93 Reviews 95 Risk Analysis and Management 96 Roles and Permissions Matrix 98 Scope Modeling 99 Stakeholder List, Map, or Personas 101 Survey or Questionnaire 109 Vendor Assessment 111 Business Modeling Techniques - Business Modeling Techniques 16 January, 2019 Business Modeling Techniques Enterprise Architect provides a sophisticated and flexible Business Analysis modeling platform that can be used by the analyst and others from strategic planning through to product support.
    [Show full text]
  • Integration of Business Process Modeling and Web Services: a Survey
    Service Oriented Computing and Applications (SOCA) 2013 The final publication is available at link.springer.com: http://link.springer.com/article/10.1007%2Fs11761-013-0138-2 DOI 10.1007/s11761-013-0138-2 Integration of Business Process Modeling and Web Services: A Survey 1 Katarina Grolinger, Miriam A. M. Capretz Department of Electrical and Computer Engineering, Faculty of Engineering Western University London ON Canada N6A 5B9 Phone: 1-519-661-2111 ext. 85478 Fax: 1-519-850-2436 [email protected], [email protected] Americo Cunha Faculty of Business, Sheridan Institute of Technology & Advanced Learning Mississauga ON Canada L5B0G5 [email protected] Said Tazi CNRS, LAAS 7 Avenue du Colonel Roche, F-31400 Toulouse, France Université de Toulouse UT1 Capitole, LAAS, F-31000 Toulouse, France Abstract: A significant challenge in business process automation involves bridging the gap between business process representations and Web service technologies that implement business activities. We are interested in business process representations such as BPMN (Business Process Modeling Notation) and EPCs (Event-Driven Process Chains). Web Service technologies include protocols such as SOAP (Simple Object Access Protocol), architectures such as RESTful (REpresentational State Transfer) or semantic description languages and formalisms such as OWL-S (Web Ontology Language for Services) and WSMO (Web Service Modeling Ontology). This paper reviews previous work on the integration of business process representations and Web service technologies. It provides a perspective on the field by summarizing, organizing, and classifying the proposed approaches. Consequently, this study has identified opportunities for future research in the field, including the need for a generic transformation approach among arbitrary models, the need to represent mappings in a formalized way, and the necessity of a common execution framework.
    [Show full text]