Business Process Redesign and Modelling
|
|
- Garey Mosley
- 7 years ago
- Views:
Transcription
1 Business Process Redesign and Modelling
2 The Business Process Redesign the Process Handbook
3 the key idea of the Process Handbook approach is that a richly structured online repository about business processes can significantly enhance the creativity of process designers by helping them systematically explore many alternatives combinations of processes elements Source J.Tidd, 2000
4 Generalize and then Specify Deep structure vs Surface structure to avoid analysis paralysis (1) Meaning vs (different) wording (Few) Goals and Constraints vs (Many possible) specif sequence of activities Selling cars vs Make to order or Make to inventory Generalization vs Specialization
5 following three basic steps Analyze Identify core activities Identify key dependencies Identify coordination mechanisms Generate Alternative specializations Alternative coord. Mechanisms Alternative sequencing Multicolumn table Distant analogies 2 1 Target Process Model! pick a similar process! look left! and then right! process rccombinator! trade-off matriz 3 Select Process attributes and values Bundles and trade of tables
6 and doing an exception analysis Exceptions are deviations to process goals Exceptions represents violations of goals/committments Undesired states vs Desidered states ex. A delay vs beign on time at a meeting so the first step of exception analysis is identifying the goals of a process looking to what is required to achieve the output of a process ex. Being on time at a meeting requires the plane to land on time, the plane to land on time requires no delay at departure, no delays at departure it means proper maintenance and being allocated correctly in the time slot and so on. All of that are committments
7 Exception analysis continued the second step is to identify exceptions that can occur with a given set of goals ex. of exceptions are communication failures or delays in accomplishing a task In the process handbook goals and exceptions types are linked and finally identify possible exceptions handlers for each of the most importantu exceptions identified before The handbook contains goals, exceptions and handlers
8 to sum up.. A given process is analysed to determine goals Those goals are then mapped to the ways they can be violated And from there to the ways those violations can be handled achieved by has exception goal process exception requires is handled by
9 example Refining transformation Specializing transformation Specialization & Inheritance
10 The classification framework A specific classification framework for organizing knowledge using these concepts; A verb rather than a conventional object-oriented noun taxonomy Groups processes with similar functions to enable cross-disciplinary fertilization of ideas
11 Repository of business process knowledge A representative set of generic business process templates and specific case examples to illustrate how the concepts and framework can be used;
12 A set of software tools to organize and manipulate large amounts of knowledge. Web-accessible repository viewer/editor Process query language Software tools
13 Business Process Modelling
14 Business Process Modelling In general Business Process Modelling is used to create an understanding of business processes and to assist the design and implementation of software systems. Business Modelling can take many forms. The choice to use business modelling, and the choice of the type of modelling to use, require a clear understanding of the objectives of the modelling exercise. Business modelling is an area where excessive effort and cost can be expended for little benefit if those objectives are not properly understood.
15 What is a Model? A model is an abstract view of something that exists in reality, but it is quite different from what it models because some details are left out, it depends on the level of abstraction that the model contains. In the business domain a model could describe a business or a company itself (or a part of it), it should allow to model business goals, business processes, stakeholders, departments, dependencies between processes and so on. A business model does not necessarily says anything about the software system used within a company, whenever may (and should) serve as a basis for the information system model, ensuring consistency and accurate requirements being passed on to the software design. Therefore it is also called a Computational Independent Model (CIM) [1]. A CIM is a software independent model used to describe a business system. Certain parts of a CIM may be supported by software systems, but the CIM itself remains software independent.
16 What is a Model? Many people talk often about structural models versus dynamic models. In UML, for example, the class diagram is called a structural model and the state diagram a dynamic model, while in reality the class diagram and state diagram are so dependent on each other that they must be regarded as part of the same model. Thus an important feature of models, even of business models, is that they may consist of several views. Finally, a model must have a purpose, for a business this may be understanding its structure, improving it or re-engineering it. The details of the model will depend on its objectives.
17 Why a Business Process Model? There are several reasons for using Business Process Models. Mainly they allow a reduction of complexity and a clear understanding of process features through the use of a graphical representation; they also provide a common and shared agreement between stakeholders; they give an unambiguous explanation of interactions between processes and description of interfaces. Business Process Models offer also the opportunity to reach the following goals: to state how value-creating activities are carried out; to create a common approach for work to be carried out; to improve incrementally processes; to analyse properties of a process. to support processes by workflow management systems;
18 Why a Business Process Model? More than a method to have a clear understanding of the process that allows to precisely assign task, to underline issues and further improvement, a business process model could be very useful to define requirements for the workflow management systems (as stated above). In the last years a big effort has been done by many companies and organizations to define a formal language (a meta-model) to describe business processes in order to achieve the automatic implementation of a business process management system. Results of such work could extremely speed up the building of the organizations information systems, provide a framework to easily and rapidly manage changes in the organization that impact on IT systems and allow a more efficient collaboration between partners. These formal languages are near to become mature standards that could revolutionise the business process management.
19 Type of Business Process Before analyse business process standards characteristics an important distinction has to be made when designing a process model; the modeller has to take into account that business processes can belong to two distinct domains [2]: Public processes are those that an enterprise shares with its customers, suppliers, or other partners (Business-to-Business integration (B2Bi) domain). Private processes are those that are internal to the enterprise (Enterprise Application Integration (EAI) domain). In any enterprise, public and private business processes combine to perform the overall business operations. This fact drives the demand for a single business process standard for modelling processes that encompasses both the B2B and EAI domains. However some important differences between the two domains have to be considered, in example security and legal aspects.
20 The need for Business Process Standards A business process standard should provide the following features [2]: 1) Collaboration-Based Process Models: Experience in both EAI and B2B process modelling has led to the increasing adoption of collaborationbased process models, usually based on UML. In collaboration-based process models, processes are described as a set of collaborations between various participants (including organizations, applications, employees, and other business processes) using different roles. The ability to recursively decompose process models is generally required. 2) Workflow: The workflow defines how the participants in a process work together to execute a process from the beginning to the end, and is also called choreography or orchestration. Workflow descriptions can be generated from collaboration models, or specified independently. There are two complementary parts to workflow: the control flow and the data flow. The control flow defines the sequencing of different activities in the process. The data flow defines how information flows between activities.
21 The need for Business Process Standards 3) Transaction Management: Transactions are crucial building blocks of any business process and a comprehensive business process standard must provide a means for specifying how transactions are managed. Longrunning transactions that may take hours or weeks to complete must be supported. If an enclosing transaction fails after an enclosed transaction is completed, some compensating actions may be needed. Time constraints for receiving responses or acknowledgements may also be required. 4)Exception Handling: If an exception is raised during the course of a business process, then it is important that the model allow appropriate recovery actions to be taken. 5)Service Interfaces: These Interfaces provide a way to describe the loosely coupled services exposed by participants and a basis for passing messages between participants in collaboration-based processes.
22 The need for Business Process Standards 6) Message Security and Reliability: For mission-critical processes, reliable and secure message delivery is required. Additionally, B2B messages may need to be digitally signed and authenticated. These quality-ofservice semantics may vary for different transactions. 7) Audit Trail: It is generally very important for legal purposes in B2B processes that an audit trail of certain business transactions is kept. This means that a trading partner is unable to claim that a transaction was not accepted when in fact it was; that is, it ensures non repudiation of the transaction by the partner. Digitally signed receipt acknowledgements of messages may be demanded. 8) Agreements: The notion of agreements is specifically for B2B processes. An agreement represents a contract between two or more partners to carry out specific functions (identified by roles) in a public business process.
23 The need for Business Process Standards 9) Execution: Public processes describe only how information should flow between organizations. In order to be able to fully automate the execution of the business process within an organization, the complete information flow within that organization as well as across its firewalls must be specified. This requires the process models to fully describe the private as well as the public activities of the organization.
24 Integrated Enterprise Modelling (IEM) Fraunhofer Integrated Enterprise Modelling (IEM) [3] is an object-oriented modelling technique, created by the Fraunhofer Institute for Production Systems and Design Technology of Berlin, for modelling business processes, related organizational structures and required information systems. It provides a model for planning and optimizing the processes and organizational structures within the enterprise. Models developed according to the IEM method give a transparent representation of planning information and are therefore the basis for discussion between project participants. In order to evaluate the variety of planning information and description requirements it allows different views on one consistent model. IEM models provide the means to precisely assign the value of planning goals, such as improvements in time, costs, or quality, to each business process and resource and, therefore, to optimise the process organization.
25 Integrated Enterprise Modelling (IEM) The core of the IEM comprises two main views: the objects describing data represent the Information Model View; the tasks, which are to be executed on objects, and the business processes are the focal point of the Process Model View. Therefore, the core of the enterprise model consists of the data and process representation of classes of objects. The views are interlinked by referring to the same objects and activities, although they represent them in different ways, levels of detail and context. Any view on the model can be derived from this standardized model core.
26 The Information Model The generic classes Product, Resource and Order are the basis of Integrated Enterprise Modeling for developing models from a user s point of view. Orders control the activities in the enterprise e.g. customer or production orders; Products are all objects which an enterprise sells e.g. machines, services or software and product components which may come into the final product; Resources are the agents that accomplish or support the actions in the process; to resource belong employees, organizational units, documents and software systems. These classes of information are represented in rectangular round boxes with different colours, each colour is related to the specific meaning of the class.
27 The Information Model They will be specified according to the specifications of an individual enterprise. Each generic class prescribes a specific generic attribute structure, thus defining a frame for describing the structure and behavior of objects of its subclasses. Real enterprise objects will be modeled as objects of these subclasses. Required enterprise data and the business processes, i.e. the tasks referring to objects, are structured in accordance with the object classes (see below). Furthermore, the relations between objects are determined. The result is a complete description of tasks, business processes, enterprise data, production equipment and information systems of the enterprise at any level of detail.
28 The Information Model The IEM expects that information related to the objects handled by activities in the business process is organized in a structured manner, creating a tree for each class of objects.
29 The Process Model Everything that happens in a manufacturing enterprise as part of the manufacturing process can be described by activities. In general, activities process and modify objects which were classified above as Products, Orders and Resources. The IEM method suggests three levels when describing the essentials of an activity. the Action is an object-independent description of any task or business, a verbal description of some task, process step or procedure; the Function describes the processing of objects (Orders, Products or Resources) as a transformation from one determined (beginning) state to another determined (ending) state; the Activity specifies the Order, which controls the execution of the function, and the Resource(s), which is (are) in charge of executing the function. Action Function Activity Action Action Action
30 The Process Model The beginning and ending states are connected with the action rectangle by arrows from left to right. The controlling of the activity is represented by an order state description and a dashed vertical arrow from the top; the required or actually assigned capability for executing the function is represented by a resource state description and a dashed vertical arrow from the bottom. Order State n State n+1 Order Product Resource Action Order Product Resource Resource
31 The Process Model Using special linking constructs (see Figure 3), actions, functions and activities can be combined to represent business processes. The decomposition and aggregation of processes is also supported.
32 The Process Model In general Business Process Modelling is used to create an understanding of business processes and to assist the design and implementation of software systems. An example of activity modelling is illustrated in the next slide. In this case the activity operates a transformation on order objects. The model highlights: the name of the action (Purchase components); resources exploited by the action, that is: who is responsible for the execution of the operation (Leader assembly), the documentation supporting the operation (procedure instructions) and the tool to be used (PPS); the order controlling the activity; units of information that represents the beginning (components needed) and the ending state (Components are in store). Each element in the model has its own attributes describing objects features.
33 The Process Model
34 The Process Model One of the most important feature of the IEM is the capability to provide different levels of description hiding/showing the details in the model. By exploiting this characteristics, you can have a global view of the business process of a SME and then go deeper in the description of the activities linking a more detailed model (with the same external input-output-orderresource information) to the more abstract one
35 IDEF0 The IDEF0 method is based on a notation for specifying ICOMs (Input, Control, Output, Mechanism), activities and arrows that represent "data" associated with the ICOMs. The position at which the arrow attaches to a box conveys the specific role of the interface. The controls enter the top of the box. Controls are the standards, policies, guidelines, etc., that guide the process. The inputs, the data or objects acted upon by the operation, enter the box from the left. Inputs are the typical things such as resources consumed or transformed by a process. The outputs of the operation leave the right-hand side of the box. Outputs are the typical things created by the transformations of the inputs by the process. Mechanism arrows that provide supporting means for performing the function join (point up to) the bottom of the box. Mechanisms are the agents (people, manual tools, automated tools, etc.) that accomplish the actions delineated within the process. Call arrows, a type of mechanism arrow which enables the sharing of detail between models or between portions of the same model, connect to the bottom of the box and point downward. Figure 6 is an abstract view of IDEF0 notation.
36 IDEF0 IDEF0 notations are combined into diagrams that describe activation of the activities, not flow. IDEF0 allows for Business Modelling to take many forms. The choice to use business modelling, and the choice of the type of modelling to use, require a clear understanding of the objectives of the modelling exercise. Business modelling is an area where excessive effort and cost can be expended for little benefit if those objectives are not properly understood. Business Process Modelling is used to create an understanding of business processes and to assist in their the design and implementation.
37 IDEF0
38 IDEF3 Process Flow IDEF3 Process Schematics are the primary means for capturing, managing, and displaying process-centred knowledge. These schematics provide a graphical medium that helps domain experts and analysts from different application areas communicate knowledge about processes. This includes knowledge about events and activities, the objects that participate in those occurrences, and the constraining relations that govern the behaviour of an occurrenc.
39 IDEF3 Process Flow The basic IDEF3 syntactic unit is an UOB (Unit of Behaviour). Depending on the surrounding structure, UOBs may become functions, activities, processes, etc. An UOB may be decomposed in other UOBs and may also be cross-referenced with IDEF0 activities. UOBs are correlated together by different types of link: IDEF3 semantic provides also junctions to connect process activities in parallel way:
40 UML: Eriksson-Penker Business extensions The Eriksson-Penker Business extensions are intended as a basic framework for business modelling. Using these extensions, the business architects may add stereotypes and/or properties to the UML in order to suit their particular situation. The Eriksson-Penker Business extensions actually merge the UML with process modelling, providing a much needed specialized UML extension able to handle business process modelling. The Eriksson-Penker extensions achieve process representation in UML by stereotyping an activity (from a UML activity diagram) to a process. In this approach, a process takes input resources from the left-hand side and outputs resources from the right-hand side.
41 UML: Eriksson-Penker Business extensions A business process model typically defines the following elements: The Goal or reason for the process; Specific inputs; Specific outputs; Resources consumed; Activities that are performed in some order; Events that drive the process. The business process: May affect more than one organizational unit. Have a horizontal organizational impact; Creates value of some kind for the customer. Customers may be internal or external
42 UML: Eriksson-Penker Business extensions
43 Business Process A business process is a set of activities designed to produce a specific output. It implies a strong emphasis on how the work is done within an organization. A process is thus a specific ordering of work activities across time and place, with a beginning, an end, and clearly defined inputs and outputs. The process notation implies a flow of activities from left to right. Typically an event element is placed to the left of the process and the output to the right. To specifically notate the internal activities, UML activity elements may be placed inside the process element.
44 Inputs, Resources and Information In general Business Process Modelling is used to create an understanding of business processes and to assist the design and implementation of software systems. Business processes use information to tailor or complete their activities. Information is used as part of the transformation process. Information may come from external sources, from customers, from internal organizational units and may even be the product of other processes. A resource is an input to a business process, and, unlike information, is typically consumed during the processing. For example, as each daily train service is run and actuals recorded, the service resource is 'used up' as far as the process of recording actual train times is concerned.
45 Inputs, Resources and Information linked to the process is not used up in the processing phase. For example, order templates may be used over and over to provide new orders of a certain style - the templates are not altered or exhausted as part of this activity. An input link indicates that the attached object or resource is consumed in the processing procedure. As an example, as customer orders are processed they are completed and signed off, and typically are used only once per unique resource (order).
46 Events In general Business Process Modelling is used to create an understanding of business processes and to assist the design and implementation of software systems. An event is the receipt of some object, a time or date reached, a notification or some other trigger that initiates the business process. The event may be consumed and transformed (for example a customer order) or simply act as a catalyst (e.g. nightly batch job).
47 Outputs A business process will typically produce one or more outputs of value to the business. An output may be a physical object (such as a report or invoice), a transformation of raw resources into a new arrangement (a daily schedule or roster) or an overall business result such as completing a customer order. An output of one business process may feed into another process, either as a requested item or a trigger to initiate new activities.
48 Goals A business process has some well defined goal. A goal is the business justification for performing the activity, it is the reason the organization does this work A goal link indicates the attached object to the business process describes the goal of the process.
49 Extensibility of BPMN and Vertical Domains BPMN is intended to be extensible by modelers and modeling tools. This extensibility allows modelers to add nonstandard elements or Artifacts to satisfy a specific need, such as the unique requirements of a vertical domain. While extensible, BPMN Diagrams should still have the basic lookand-feel so that a Diagram by any modeler should be easily understood by any viewer of the Diagram. footprint of the basic flow elements (Events, activities, and Gateways) should not be altered. Nor should any new flow elements be added to a BPD, since there is no specification as to how Sequence and Message Flow will connect to any new Flow Object. In addition, mappings to execution languages may be affected if new flow elements are added. To satisfy additional modeling concepts that are not part of the basic set of flow elements, BPMN provides the concept of Artifacts that can be linked to the existing Flow Objects through Associations.
50 BPMN Mapping Since BPMN covers such a wide range of usage, it will map to more than one lower-level specification language: BPEL4WS are the primary languages that BPMN will map to, but they only cover a single executable private business process. If a BPMN Diagram depicts more than one internal business process, then there will a separate mapping for each on the internal business processes. The abstract sections of a BPMN Diagram will be mapped to Web service interfaces specifications, such as the abstract processes of BPEL4WS. The Collaboration model sections of a BPMN may be mapped Collaboration models such as ebxml BPSS, Rosetta- Net, and the W3C Choreography Working Group Specification (when it is completed). This specification will only cover a mapping to BPEL4WS. Mappings to other specifications will have to be a separate effort, or perhaps a future direction of BPMN (beyond Version 1.0 of the BPMN specification).
51 Core Modelling Elements
52 Core Element Set
53 Core Element Set
The Business Process Model
The Business Process Model by Sparx Systems All material Sparx Systems 2007 Sparx Systems 2007 Page: 1 Table of Contents INTRODUCTION...3 BUSINESS PROCESS MODELING NOTATION (BPMN)...4 FLOW ELEMENTS...4
More informationIntroduction to BPMN
Stephen A. White, IBM Corporation Abstract This paper is intended to provide a high-level overview and introduction to the Business Process Modeling Notation (BPMN). The context and general uses for BPMN
More informationThe Business Process Model
An Introduction to UML The Business Process Model by Geoffrey Sparks All material (c) Geoffrey Sparks 2000 www.sparxsystems.com.au Geoffrey Sparks 2000 Page:1 Table of Contents THE BUSINESS PROCESS MODEL...3
More informationBusiness Process Standards and Modeling
Business Process Standards and Modeling Janne J. Korhonen Helsinki University of Technology STANDARDS Standards Organizations Object Management Group (www.omg.org) Business Process Modeling Notation (BPMN)
More informationBusiness Process Modeling Information Systems in Industry (372-1-4207 )
Business Process Modeling Information Systems in Industry (372-1-4207 ) Arnon Sturm The material of this presentation is adopted from various people including:, Pnina Soffer, Iris Reinhartz-Berger 1 Outline
More informationBPMN Fundamentals. BPMI Meeting #12. London, United Kingdom May 13-14, 2004. Stephen A. White, IBM Notation Working Group Chair
BPMN Fundamentals Stephen A. White, IBM Notation Working Group Chair BPMI Meeting #12 London, United Kingdom May 13-14, 2004 Topics Background Relationship to other BPM Notations/ Languages and to Standards
More informationBusiness Modeling with UML
Business Modeling with UML Hans-Erik Eriksson and Magnus Penker, Open Training Hans-Erik In order to keep up and be competitive, all companies Ericsson is and enterprises must assess the quality of their
More informationProcess Modelling Notations
Process Modelling Notations Event-driven Process Chains (EPC) Business Process Modelling Notation (BPMN) Workflow Management Agenda Motivation for BPM EPC BPMN Case Study 1 Why Business Process Modelling
More informationUsage of Business Process Choreography
Usage of Business Process Choreography Akira Tanaka, Hitachi, Ltd. tanakaak@soft.hitachi.co.jp Infrastructures and Standard 1 Agenda Introduction Lifecycle! Design phase! Usage phase! Managing phase Remarks
More informationQuick Guide Business Process Modeling Notation (BPMN)
Quick Guide Business Process Modeling Notation (BPMN) IDM Technical Team January 2007 Quick Guide: BPMN 2 of 14 The scope of this document is to provide a quick guide to the concepts and usage of the Business
More informationModeling Guidelines Manual
Modeling Guidelines Manual [Insert company name here] July 2014 Author: John Doe john.doe@johnydoe.com Page 1 of 22 Table of Contents 1. Introduction... 3 2. Business Process Management (BPM)... 4 2.1.
More informationUsing Use Cases for requirements capture. Pete McBreen. 1998 McBreen.Consulting
Using Use Cases for requirements capture Pete McBreen 1998 McBreen.Consulting petemcbreen@acm.org All rights reserved. You have permission to copy and distribute the document as long as you make no changes
More informationINTRODUCTION TO BUSINESS PROCESS MODELING NOTATION BPMN 1.2 AND BPMN 2.0
INTRODUCTION TO BUSINESS PROCESS MODELING NOTATION BPMN 1.2 AND BPMN 2.0 Email: {goliva,gerosa}@ime.usp.br / Twitter: @golivax Agenda 2 Introduction to Business Processes BPMN 1.2 Introduction Elements
More informationCollated Food Requirements. Received orders. Resolved orders. 4 Check for discrepancies * Unmatched orders
Introduction to Data Flow Diagrams What are Data Flow Diagrams? Data Flow Diagrams (DFDs) model that perspective of the system that is most readily understood by users the flow of information around the
More informationLEADing Practice: Artifact Description: Business, Information & Data Object Modelling. Relating Objects
LEADing Practice: Artifact Description: Business, Information & Data Object Modelling Relating Objects 1 Table of Contents 1.1 The Way of Thinking with Objects... 3 1.2 The Way of Working with Objects...
More information(Refer Slide Time 00:56)
Software Engineering Prof.N. L. Sarda Computer Science & Engineering Indian Institute of Technology, Bombay Lecture-12 Data Modelling- ER diagrams, Mapping to relational model (Part -II) We will continue
More informationSoftware Engineering. System Models. Based on Software Engineering, 7 th Edition by Ian Sommerville
Software Engineering System Models Based on Software Engineering, 7 th Edition by Ian Sommerville Objectives To explain why the context of a system should be modeled as part of the RE process To describe
More information6-1. Process Modeling
6-1 Process Modeling Key Definitions Process model A formal way of representing how a business system operates Illustrates the activities that are performed and how data moves among them Data flow diagramming
More informationBPMN and Business Process Management Introduction to the New Business Process Modeling Standard
BPMN and Business Process Management Introduction to the New Business Process Modeling Standard By Martin Owen and Jog Raj, Popkin Software Executive Summary... 3 Introducing BPMN... 4 BPMN Enables Business
More informationRequirements engineering
Learning Unit 2 Requirements engineering Contents Introduction............................................... 21 2.1 Important concepts........................................ 21 2.1.1 Stakeholders and
More informationBPMN and Business Process Management
BPMN and Business Process Management An Introduction to the New Business Process Modeling Standard By Martin Owen and Jog Raj Popkin Software www.popkin.com (c) 2003, Popkin Software www.bptrends.com Executive
More informationBusiness Process Modeling and Standardization
Business Modeling and Standardization Antoine Lonjon Chief Architect MEGA Content Introduction Business : One Word, Multiple Arenas of Application Criteria for a Business Modeling Standard State of the
More informationFrom Business World to Software World: Deriving Class Diagrams from Business Process Models
From Business World to Software World: Deriving Class Diagrams from Business Process Models WARARAT RUNGWORAWUT 1 AND TWITTIE SENIVONGSE 2 Department of Computer Engineering, Chulalongkorn University 254
More informationLECTURE 11: PROCESS MODELING
LECTURE 11: PROCESS MODELING Outline Logical modeling of processes Data Flow Diagram Elements Functional decomposition Data Flows Rules and Guidelines Structured Analysis with Use Cases Learning Objectives
More informationIn this Lecture you will Learn: Systems Development Methodologies. Why Methodology? Why Methodology?
In this Lecture you will Learn: Systems Development Methodologies What a systems development methodology is Why methodologies are used The need for different methodologies The main features of one methodology
More informationWebSphere Business Modeler
Discovering the Value of SOA WebSphere Process Integration WebSphere Business Modeler Workshop SOA on your terms and our expertise Soudabeh Javadi Consulting Technical Sales Support WebSphere Process Integration
More informationBusiness Process Modelling Languages
Agent and Object Technology Lab Dipartimento di Ingegneria dell Informazione Università degli Studi di Parma Business Process Modelling Languages Paola Turci AOT Lab - DII - Università di Parma Business
More informationHow To Develop Software
Software Engineering Prof. N.L. Sarda Computer Science & Engineering Indian Institute of Technology, Bombay Lecture-4 Overview of Phases (Part - II) We studied the problem definition phase, with which
More informationIntroduction to Systems Analysis and Design
Introduction to Systems Analysis and Design What is a System? A system is a set of interrelated components that function together to achieve a common goal. The components of a system are called subsystems.
More informationTest Case Design Using Classification Trees
STAR 94, 8-12 May 1994, Washington, D.C. Test Case Design Using Classification Trees Matthias Grochtmann Daimler-Benz AG Forschung und Technik Alt-Moabit 91b D-10559 Berlin, Germany Tel: +49 30 39 982-229
More informationFourth generation techniques (4GT)
Fourth generation techniques (4GT) The term fourth generation techniques (4GT) encompasses a broad array of software tools that have one thing in common. Each enables the software engineer to specify some
More informationContents. Introduction and System Engineering 1. Introduction 2. Software Process and Methodology 16. System Engineering 53
Preface xvi Part I Introduction and System Engineering 1 Chapter 1 Introduction 2 1.1 What Is Software Engineering? 2 1.2 Why Software Engineering? 3 1.3 Software Life-Cycle Activities 4 1.3.1 Software
More informationQueensland recordkeeping metadata standard and guideline
Queensland recordkeeping metadata standard and guideline June 2012 Version 1.1 Queensland State Archives Department of Science, Information Technology, Innovation and the Arts Document details Security
More informationIntroduction to Service Oriented Architectures (SOA)
Introduction to Service Oriented Architectures (SOA) Responsible Institutions: ETHZ (Concept) ETHZ (Overall) ETHZ (Revision) http://www.eu-orchestra.org - Version from: 26.10.2007 1 Content 1. Introduction
More informationLecture 9: Requirements Modelling
A little refresher: What are we modelling? Lecture 9: Requirements Modelling Requirements; Systems; Systems Thinking Role of Modelling in RE Why modelling is important Limitations of modelling Brief overview
More informationPopkin Software 2003 (www.popkin.com) 2
BPMN and Business Process Management, An Introduction to the New Business Process Modeling Standard by Martin Owen and Jog Raj, Popkin Software, 2003, www.popkin.com. Popkin Software Corporate Headquarters
More informationBusiness Process Modelling. CA4 Business Process Modelling 1
Business Process Modelling CA4 Business Process Modelling 1 Historical View of BP Modelling Work Process Flow (early to mid 1900s) + Frank Gilbreth & his 'Flow Process Charts' (= flowcharts) + First structured
More informationBPMN PATTERNS USED IN MANAGEMENT INFORMATION SYSTEMS
BPMN PATTERNS USED IN MANAGEMENT INFORMATION SYSTEMS Gabriel Cozgarea 1 Adrian Cozgarea 2 ABSTRACT: Business Process Modeling Notation (BPMN) is a graphical standard in which controls and activities can
More informationMalay A. Dalal Madhav Erraguntla Perakath Benjamin. Knowledge Based Systems, Inc. (KBSI) College Station, TX 77840, U.S.A.
AN INTRODUCTION TO USING PROSIM FOR BUSINESS PROCESS SIMULATION AND ANALYSIS Malay A. Dalal Madhav Erraguntla Perakath Benjamin Knowledge Based Systems, Inc. (KBSI) College Station, TX 77840, U.S.A. ABSTRACT
More informationChapter 3 Chapter 3 Service-Oriented Computing and SOA Lecture Note
Chapter 3 Chapter 3 Service-Oriented Computing and SOA Lecture Note Text book of CPET 545 Service-Oriented Architecture and Enterprise Application: SOA Principles of Service Design, by Thomas Erl, ISBN
More informationAdvanced Service Creation: Bridging the Gap Between Requirements Elicitation and Service Design
Advanced Service Creation: Bridging the Gap Between Requirements Elicitation and Service Design Dionisis X. Adamopoulos 1, Constantine A. Papandreou 2 1 University of Piraeus, Greece and Centre for Communication
More informationBPMN Business Process Modeling Notation
BPMN (BPMN) is a graphical notation that describes the logic of steps in a business process. This notation has been especially designed to coordinate the sequence of processes and messages that flow between
More information1. Process Modeling. Process Modeling (Cont.) Content. Chapter 7 Structuring System Process Requirements
Content Chapter 7 Structuring System Process Requirements Understand the logical (&physical) process modeling by using data flow diagrams (DFDs) Draw DFDs & Leveling Balance higher-level and lower-level
More informationRequirements Analysis Concepts & Principles. Instructor: Dr. Jerry Gao
Requirements Analysis Concepts & Principles Instructor: Dr. Jerry Gao Requirements Analysis Concepts and Principles - Requirements Analysis - Communication Techniques - Initiating the Process - Facilitated
More informationUsing UML Part One Structural Modeling Diagrams
UML Tutorials Using UML Part One Structural Modeling Diagrams by Sparx Systems All material Sparx Systems 2007 Sparx Systems 2007 Page 1 Trademarks Object Management Group, OMG, Unified Modeling Language,
More informationCase studies: Outline. Requirement Engineering. Case Study: Automated Banking System. UML and Case Studies ITNP090 - Object Oriented Software Design
I. Automated Banking System Case studies: Outline Requirements Engineering: OO and incremental software development 1. case study: withdraw money a. use cases b. identifying class/object (class diagram)
More informationAssuming the Role of Systems Analyst & Analysis Alternatives
Assuming the Role of Systems Analyst & Analysis Alternatives Nature of Analysis Systems analysis and design is a systematic approach to identifying problems, opportunities, and objectives; analyzing the
More informationMeta-Model specification V2 D602.012
PROPRIETARY RIGHTS STATEMENT THIS DOCUMENT CONTAINS INFORMATION, WHICH IS PROPRIETARY TO THE CRYSTAL CONSORTIUM. NEITHER THIS DOCUMENT NOR THE INFORMATION CONTAINED HEREIN SHALL BE USED, DUPLICATED OR
More informationQUALITY TOOLBOX. Understanding Processes with Hierarchical Process Mapping. Robert B. Pojasek. Why Process Mapping?
QUALITY TOOLBOX Understanding Processes with Hierarchical Process Mapping In my work, I spend a lot of time talking to people about hierarchical process mapping. It strikes me as funny that whenever I
More informationWhat is a life cycle model?
What is a life cycle model? Framework under which a software product is going to be developed. Defines the phases that the product under development will go through. Identifies activities involved in each
More informationMTAT.03.231 Business Process Management (BPM) (for Masters of IT) Lecture 2: Introduction to BPMN
MTAT.03.231 Business Process Management (BPM) (for Masters of IT) Lecture 2: Introduction to BPMN Marlon Dumas marlon.dumas ät ut. ee How to engage in BPM? 1. Opportunity assessment 2. Process modelling
More informationChap 1. Introduction to Software Architecture
Chap 1. Introduction to Software Architecture 1. Introduction 2. IEEE Recommended Practice for Architecture Modeling 3. Architecture Description Language: the UML 4. The Rational Unified Process (RUP)
More informationICT Business Function Analysis
Institutional and Sector Modernisation Facility ICT Standards ICT Business Function Analysis Document number: ISMF-ICT/3.04 Version: 3.0 Project Funded by the European Union 1 Document control 1.1 List
More informationChapter 4: Tools of Modern Systems Analysis
Just Enough Structured Analysis Chapter 4: Tools of Modern Systems Analysis Nature has... some sort of arithmetical-geometrical coordinate system, because nature has all kinds of models. What we experience
More informationQuestions? Assignment. Techniques for Gathering Requirements. Gathering and Analysing Requirements
Questions? Assignment Why is proper project management important? What is goal of domain analysis? What is the difference between functional and non- functional requirements? Why is it important for requirements
More informationBusiness-Driven Software Engineering Lecture 3 Foundations of Processes
Business-Driven Software Engineering Lecture 3 Foundations of Processes Jochen Küster jku@zurich.ibm.com Agenda Introduction and Background Process Modeling Foundations Activities and Process Models Summary
More informationDesigning a Semantic Repository
Designing a Semantic Repository Integrating architectures for reuse and integration Overview Cory Casanave Cory-c (at) modeldriven.org ModelDriven.org May 2007 The Semantic Metadata infrastructure will
More informationApplying 4+1 View Architecture with UML 2. White Paper
Applying 4+1 View Architecture with UML 2 White Paper Copyright 2007 FCGSS, all rights reserved. www.fcgss.com Introduction Unified Modeling Language (UML) has been available since 1997, and UML 2 was
More informationSequence Diagrams. Massimo Felici. Massimo Felici Sequence Diagrams c 2004 2011
Sequence Diagrams Massimo Felici What are Sequence Diagrams? Sequence Diagrams are interaction diagrams that detail how operations are carried out Interaction diagrams model important runtime interactions
More informationZen of VISIO 2008. Leona Rubin WebTechNY User Group Date: September, 2008
Zen of VISIO 2008 Leona Rubin WebTechNY User Group Date: September, 2008 About the speaker Leona Rubin from New York began her career as a Senior Technical Communicator, Information Designer and Management
More information3SL. Requirements Definition and Management Using Cradle
3SL Requirements Definition and Management Using Cradle November 2014 1 1 Introduction This white paper describes Requirements Definition and Management activities for system/product development and modification
More informationAn Introduction to. Metrics. used during. Software Development
An Introduction to Metrics used during Software Development Life Cycle www.softwaretestinggenius.com Page 1 of 10 Define the Metric Objectives You can t control what you can t measure. This is a quote
More informationObject Oriented Design
Object Oriented Design Kenneth M. Anderson Lecture 20 CSCI 5828: Foundations of Software Engineering OO Design 1 Object-Oriented Design Traditional procedural systems separate data and procedures, and
More informationThe Software Process. The Unified Process (Cont.) The Unified Process (Cont.)
The Software Process Xiaojun Qi 1 The Unified Process Until recently, three of the most successful object-oriented methodologies were Booch smethod Jacobson s Objectory Rumbaugh s OMT (Object Modeling
More informationBusiness Process Modeling
Business Process Modeling e-framework Workshop Balbir Barn 12 th February 2007 Agenda Why we construct Business Process Models A historical context Approaches to business process modelling Business Process
More informationBudapest University of Technology and Economics Department of Measurement and Information Systems. Business Process Modeling
Budapest University of Technology and Economics Department of Measurement and Information Systems Business Process Modeling Process, business process Workflow: sequence of given steps executed in order
More informationBPMN by example. Bizagi Suite. Copyright 2014 Bizagi
BPMN by example Bizagi Suite Recruitment and Selection 1 Table of Contents Scope... 2 BPMN 2.0 Business Process Modeling Notation... 2 Why Is It Important To Model With Bpmn?... 2 Introduction to BPMN...
More informationSoftware Metrics & Software Metrology. Alain Abran. Chapter 4 Quantification and Measurement are Not the Same!
Software Metrics & Software Metrology Alain Abran Chapter 4 Quantification and Measurement are Not the Same! 1 Agenda This chapter covers: The difference between a number & an analysis model. The Measurement
More informationBPMN Business Process Modelling Notation
BPMN Business Process Modelling Notation Knut Hinkelmann This chapter is based on the BPMN Tutorial of Stephen A. White and the book White, S.A., Miers, D. (2008) BPMN - Modeling and Reference Guide. Future
More informationBUSINESS ARCHITECTURE AND BPM ALIGNMENT
BUSINESS ARCHITECTURE AND BPM ALIGNMENT Austin, Texas, USA - September 17, 2014 INNOVATION WORKSHOP Lloyd Dugan, Business Process Management, Inc. Neal McWhorter, Strategic Value Partners Copyright 2014
More informationAn Automated Workflow System Geared Towards Consumer Goods and Services Companies
Proceedings of the 2014 International Conference on Industrial Engineering and Operations Management Bali, Indonesia, January 7 9, 2014 An Automated Workflow System Geared Towards Consumer Goods and Services
More informationScenario-based Requirements Engineering and User-Interface Design
Scenario-based Requirements Engineering and User-Interface Institut für Computertechnik ICT Institute of Computer Technology Hermann Kaindl Vienna University of Technology, ICT Austria kaindl@ict.tuwien.ac.at
More informationChange Pattern-Driven Traceability of Business Processes
Proceedings of the International MultiConference of Engineers and Computer Scientists 2014 Vol I,, March 12-14, 2014, Hong Kong Change Pattern-Driven Traceability of Business Processes Watcharin Uronkarn
More informationAbstraction in Computer Science & Software Engineering: A Pedagogical Perspective
Orit Hazzan's Column Abstraction in Computer Science & Software Engineering: A Pedagogical Perspective This column is coauthored with Jeff Kramer, Department of Computing, Imperial College, London ABSTRACT
More informationCATIA Drafting TABLE OF CONTENTS
TABLE OF CONTENTS Introduction...1 Drafting...2 Drawing Screen...3 Pull-down Menus...4 File...4 Edit...5 View...6 Insert...7 Tools...8 Drafting Workbench...9 Views and Sheets...9 Dimensions and Annotations...10
More informationQuantitative and qualitative methods in process improvement and product quality assessment.
Quantitative and qualitative methods in process improvement and product quality assessment. Anna Bobkowska Abstract Successful improvement of the development process and product quality assurance should
More informationA Process is Not Just a Flowchart (or a BPMN model)
A Process is Not Just a Flowchart (or a BPMN model) The two methods of representing process designs that I see most frequently are process drawings (typically in Microsoft Visio) and BPMN models (and often
More informationDr. Jana Koehler IBM Zurich Research Laboratory
Precise Modeling of Business Processes with the Business Process Modeling Notation BPMN 2.0 Dr. Jana Koehler IBM Zurich Research Laboratory ZRL BIT at a Glance Computer Science at ZRL: Security/Cryptography
More informationA METHODOLOGY FOR KNOWLEDGE DISCOVERY AND CLASSIFICATION. University of Massachusetts Amherst, MA 01003-2210. 15021 21 Drive, SE Mill Creek WA, 98012
A METHODOLOGY FOR KNOWLEDGE DISCOVERY AND CLASSIFICATION Janis Terpenny 1, Stephen Strong 2, Jiachuan Wang 1 1 Department of Mechanical and Industrial Engineering University of Massachusetts Amherst, MA
More informationCommunication Diagrams
Communication Diagrams Massimo Felici Realizing Use cases in the Design Model 1 Slide 1: Realizing Use cases in the Design Model Use-case driven design is a key theme in a variety of software processes
More informationSysML Modelling Language explained
Date: 7 th October 2010 Author: Guillaume FINANCE, Objet Direct Analyst & Consultant UML, the standard modelling language used in the field of software engineering, has been tailored to define a modelling
More informationChapter 6. Data-Flow Diagrams
Chapter 6. Data-Flow Diagrams Table of Contents Objectives... 1 Introduction to data-flow diagrams... 2 What are data-flow diagrams?... 2 An example data-flow diagram... 2 The benefits of data-flow diagrams...
More informationBusiness Process Management. Prof. Corrado Cerruti General Management Course
Business Process Management General Management Course Summary Business Process Management definition Business Process Management Life Cycle ARIS approach to BPM Business Process Identification; Designing
More informationHow To Create A Complex Diagram On A Computer Game
ENTERPRISE ARCHITECT IMPORT user guide No Magic, Inc. 2013 All material contained herein is considered proprietary information owned by No Magic, Inc. and is not to be shared, copied, or reproduced by
More informationMethods and Tolls for Business Process Modeling
Methods and Tolls for Business Process Modeling Operations Management Dr. Giuditta Pezzotta Università degli Studi di Bergamo 2011 Riproduzione riservata http://cels.unibg.it 1 Objectives of the lesson
More informationUsing UML Part Two Behavioral Modeling Diagrams
UML Tutorials Using UML Part Two Behavioral Modeling Diagrams by Sparx Systems All material Sparx Systems 2007 Sparx Systems 2007 Page 1 Trademarks Object Management Group, OMG, Unified Modeling Language,
More informationORACLE TUTOR BUSINESS PROCESS CONVERTER
ORACLE TUTOR BUSINESS PROCESS CONVERTER Organizations frequently find that their Visio based business process diagrams have become artifacts. Deploying these models effectively to employees can be difficult,
More informationVisualization methods for patent data
Visualization methods for patent data Treparel 2013 Dr. Anton Heijs (CTO & Founder) Delft, The Netherlands Introduction Treparel can provide advanced visualizations for patent data. This document describes
More informationDocument Engineering: Analyzing and Designing the Semantics of Business Service Networks
Document Engineering: Analyzing and Designing the Semantics of Business Service Networks Dr. Robert J. Glushko University of California Berkeley glushko@sims.berkeley.edu Tim McGrath Universal Business
More informationSection C. Requirements Elicitation
This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike License. Your use of this material constitutes acceptance of that license and the conditions of use of materials on this
More information1.1 Motivation and Definitions
1 Introduction Business process management has received considerable attention recently by both business administration and computer science communities. Members of these communities are typically characterized
More informationSoftware Service Engineering Architect s Dream or Developer s Nightmare?
Software Service Engineering Architect s Dream or Developer s Nightmare? Gregor Hohpe Google, 1600 Amphitheatre Parkway, Mountain View, CA 94043 gregor@hohpe.com Abstract. Architectural principles such
More informationService Oriented Architecture (SOA) Architecture, Governance, Standards and Technologies
Service Oriented Architecture (SOA) Architecture, Governance, Standards and Technologies 3-day seminar Give Your Business the Competitive Edge SOA has rapidly seized the momentum and center stage because
More informationLinking BPMN, ArchiMate, and BWW: Perfect Match for Complete and Lawful Business Process Models?
Linking BPMN, ArchiMate, and BWW: Perfect Match for Complete and Lawful Business Process Models? Ludmila Penicina Institute of Applied Computer Systems, Riga Technical University, 1 Kalku, Riga, LV-1658,
More information2 SYSTEM DESCRIPTION TECHNIQUES
2 SYSTEM DESCRIPTION TECHNIQUES 2.1 INTRODUCTION Graphical representation of any process is always better and more meaningful than its representation in words. Moreover, it is very difficult to arrange
More informationAn Automatic Tool for Checking Consistency between Data Flow Diagrams (DFDs)
An Automatic Tool for Checking Consistency between Data Flow Diagrams (DFDs) Rosziati Ibrahim, Siow Yen Yen Abstract System development life cycle (SDLC) is a process uses during the development of any
More informationSTSG Methodologies and Support Structure
STSG Methodologies and Support Structure STSG Application Life Cycle Management STSG utilizes comprehensive lifecycle tools that are fully integrated and provide capabilities for most of the roles in its
More informationDetecting Defects in Object-Oriented Designs: Using Reading Techniques to Increase Software Quality
Detecting Defects in Object-Oriented Designs: Using Reading Techniques to Increase Software Quality Current Research Team: Prof. Victor R. Basili Forrest Shull, Ph.D. Guilherme H. Travassos, D.Sc. (1)
More informationWhat is a metamodel: the OMG s metamodeling infrastructure
Modeling and metamodeling in Model Driven Development Warsaw, May 14-15th 2009 Gonzalo Génova ggenova@inf.uc3m.es http://www.kr.inf.uc3m.es/ggenova/ Knowledge Reuse Group Universidad Carlos III de Madrid
More information