TECHNIQUES FOR ENTEPRISE MODELLING

Manfredi Bruccoleri# 1

Business process management Technical Module A1

!

Module A1TECHNIQUES FOR ENTEPRISE

MODELLING



!What is enterprise modelling?



!Remember business process mng?

Manfredi Bruccoleri!

# 16!

Business Process Management!Theory Module T2!

Process Design

Process

Analysis

Process

Implementation

Business Process Design!

Modelling methodologies and graphical standardized languages for easy formalization

and engineering of business processes!



!

–  IDEF0 –  BPMN

Techniques for Enterprise Modelling



!

S.A.D.T. / IDEF0, Structured Analysis and Design Technique is a technique developed by Softech Inc. since 1975 for the development and documentation of IT systems.

S.A.D.T. / IDEF0 was already used as a de facto standard for over a decade by the Department of Defence, the U.S. Federal Government for business applications, and logistics specialist (such as e.g. command and control systems)

S.A.D.T. / IDEF0 is currently plugged-in the name of IDEF0-in the following standards bodies:•  FIPS (Federal Information Processing Standard) is the organization that certifies standards in law

for the U.S. Federal government; IDEF0 technique is recommended as a standard for process modeling;

•  IEEE (Institute of Electrical and Electronic Engineering): IDEF0 in this context has been included in the standardization process;

•  ISO (International Standards Organization) is the international body that sets standards, accepted by all member countries (all major states adhere to the organization); IDEF0 has been proposed by NIST (National Institute for Standards USA) and by the Italian ISO representation as a reference technique for process modelling.

IDEF0 functional modelling method



!

S.A.D.T. / IDEF0 is based on these concepts:

•  the system to be analyzed is represented by means of models, described using a precise graphical language which provides a limited set of elements to ensure clarity and conciseness;

•  models are constructed in terms of "objects" and "activity" and more specifically, information flows and transformations that operate on them;

•  analysis is conducted according to the hierarchical structure (top-down), and structured in a modular fashion, to ensure the deepening of the details and precise description of the interfaces;

•  specific roles and control rules are defined for conducting of the business to ensure product quality and efficient management of the production process, even in projects of great size and complexity.

IDEF0



!

SADT/IDEF0 involves the construction of models to describe the processes of a system.A model is a sequence of diagrams, organized hierarchically, where the upper level represents the entire system and each diagram introduces a limited amount of details to facilitate the understanding.

To build a model the following elements should be considered:1.  the definition and delimitation of the problem to be analyzed (context);2.  the purposes for which we proceed to the production model (purpose);3.  the perspective from which the problem is analyzed (the point of view).

In fact, even if the system to be analyzed, that is, the context, always presents the same characteristics, the importance of each feature, the terminology used, the level of detail required may be different depending on the purpose and the point of view established.

IDEF0



!

A model is a hierarchical and structured sequence of diagrams.Each diagram is embodied in a graphical representation consists of blocks (boxes) connected by arrows.Each block represents an activity (process), each arrow a given (object). The formalism ICOM (Inputs, Controls, Outputs, Mechanisms) is represented as in figure.

Function or activity(verb)

Inputs Outputs

Mechanisms

Controls

What is transformed by the process or what is requested to

start the process (trigger) such as raw material, a purchase order, a

manager signature)

What is produced by the activity in terms of finished product/services or

results such as reports, documents, products,

improvements, etc.

What is needed for conducting the activity in terms of resources, business units,

etc..

Constraints on activities, such as lows, procedures, budget, etc.

IDEF0 (I.C.O.M. formalism)



!

Codes, rules, regulations Project specifications

Client requirements

Time and Budget

IDEF0 (I.C.O.M. formalism)



!

In a model, each box delimits a context of activity, the title of the box briefly describes the function, the interface objects define more precisely the function itself.

Each box in a diagram can be decomposed and this decomposition is represented by a diagram at the level of detail immediately below the model.

The breakdown of a box in a diagram can then be introduced into the model an additional level of detail, identifying other activities related to each other interface object, proceeding in a hierarchical top-down.

The process stops at the level of detail sufficient for its intended purpose, i.e. the model is clear and complete.

IDEF0 (Decomposition)



!IDEF0 (Decomposition)



!

The context qualifies the object of the model as part of a larger system, in particular defines the boundary between it and the surrounding environment and indicates how it interacts with the outside. The context of the model should be clarified and made explicit in the Context Diagram, both by the arrows of the contour with the use of appropriate explanatory text.For example, finding vendor information is not part of the process

IDEF0 (context diagram)



!

Establishes goals and intentions of the person making the modeling. Depending on the purpose of the model is identified the most appropriate point of view which is adopted for drafting of the model. The purpose of the model will also determine the extent, both "horizontally" (i.e. how much of the process it is necessary to model), that "depth" (i.e. at what level of detail we should go into).Example: The goal is to document the activities associated with the process of developing new products and to identify those that are non-value added and that could be eliminated

IDEF0 (modelling goal)



!

Determine what can be seen within the context and from what perspective. According to the purpose to be achieved, various points of view within the same context may be adopted. For each model, among these points of view, one has to be established and kept for all levels of detail in which the model is broken. If you need more explicit points of view, you can create more models of the same system / process.Example: The viewpoint is that of the Business analyst

IDEF0 (Viewpoint)



!

The tools Microsoft Visio® (Windows)

Omnigraffle® (Mac)



!

While IDEF0 describes “What an enterprise does”, BPMN describes “How an enterprise does what it does”

Also, contrarily to IDEF0, BPMN: -  Describes the process from the point of view of the workflow (process

centered);-  Captures time and logical sequences;-  Captures decision-making activities and flow ramification mechanisms-  Supports descriptions of collaborative processes

BPMN



!

The Business Process Modelling Notation (BPMN) is a standardized graphical notation for modelling business processes. The first of the BPMN specifications were released in May 2004 by BPMI (Business Process Management Initiative) and was recently acquired by OMG (Object Management Group - www.omg.org);

The primary objective of the BPMI Notation Working Group in the definition of the BPMN notation was to provide a graphical language that is easily understandable by all business users (from the functional analyst who tracks the initial draft of the process, to technology implementers, until those guys who will manage and monitor the process itself);

BPMN has also been designed in such a way that can be easily translated in software code according to one of the languages based on XML and used to run existing business processes, such as the BPEL4WS or XPDL;

This leads to the conclusion that BPMN is a standard that bridges the gap between design and implementation processes.

BPMN



!

BPMN can be calibrated for both a high and low level of modelling detail and, thus, can be used by both business analysts (and users) and software implementers. Business users should be able to read and understand easily a BPMN diagram. Business analysts and implementers of the process shouldinstead be able to enrich the diagram with further details to represent the process in his physical development.

With regard to the objectives of the modelling activity, there are four ways of using BPMN when building a business process model: •  Modelling of Internal Business Processes (private);•  Modelling of Internal Business Processes (public);•  Modelling of B2B Collaboration Processes;•  Modelling of Choreographies.

BPMN



!

An internal business process generally focuses on the point of view of a single organization or business entity.

Although internal processes often show interactions with external participants, these define the activities that are not normally visible to the public and therefore are "private activity”.

If a swimlanes-like notation is used (e.g., a Collaboration, see later) then a private Business Process will be contained within a single Pool. The Process flow is therefore contained within the Pool and cannot cross the boundaries of the Pool. The flow of Messages can cross the Pool boundary to show the interactions that exist between separate private Business Processes.

Modelling of Internal Business Processes (private)

BPMN



!

Modelling of Internal Business Processes (private)

BPMN



!

A public Process represents the interactions between a private Business Process and another Process or Participant. Only those Activities that are used to communicate to the other Participant(s) are included in the public Process. All other “internal” Activities of the private Business Process are not shown in the public Process. Thus, the public Process shows to the outside world the Message Flows and the order of those Message Flows that are needed to interact with that Process. Public Processes can be modelled separately or within a Collaboration to show the flow of Messages between the public Process Activities and other Participants.

Modelling of Internal Business Processes (public)

BPMN



!

Modelling of Internal Business Processes (public)

BPMN



!

A B2B collaborative process describes the interactions between two or more business entities. The diagrams for these types of processes are generally made from a global point of view that shows the interactions between the participants.The interactions are described as a sequence of activities or messages exchanged between the participants, the messages can be considered the "contact points" between the participants and then the process defines the interactions that are visible to the public.When you look at the process shown in only one Pool (namely that of a participant), the public process is also called "abstract process".

Modelling of B2B Collaboration Processes

BPMN



!

Modelling of B2B Collaboration Processes

BPMN



!

A self-contained Choreography (no Pools) is a definition of the expected behaviour, basically a procedural contract, between interacting Participants. While a normal Process exists within a Pool, a Choreography exists between Pools (or Participants).The Choreography looks similar to a private Business Process since it consists of a network of Activities, Events, and Gateways. However, a Choreography is different in that the Activities are interactions that represent a set (1 or more) of Message exchanges, which involves two or more Participants.

Modelling of Choreographies

BPMN



!BPMN Modelling of Choreographies



!

The activity of modelling the business process often begins by identifying the high-level tasks and then proceed to split them up at lower levels of detail in separate diagrams.There may be multiple levels of diagrams according to the methodology used for the development of the model.The figure shows an example of high-level process, which is basically a series of three sub-processes with a decision-making point within the process.

Different precision levels during the modelling

BPMN



!

The graphical elements of BPMN elements are divided into primary and secondary elements. The primary elements (CORE SET) are divided into four categories:

CORE SET•  Flow Objects;•  Connecting Objects;•  Swimlanes;•  Artifacts.

For modellers who need or want a low level of precision to create process models for the purposes of communication and documentation, the primary elements (in particular flow objects and connecting objects) provide the ability to easily create diagrams to their purposes .

Graphical elements

BPMN



!

EVENT: An event is represented by a circle and is something that happens during the process. These events affect the flow of the process and usually represent a cause (trigger) or an impact (result). The events are open circles to allow internal markers to differentiate the various causes and impacts. There are three types of events, based on when they take part in the flow: Start, Intermediate, End (from left to right in the figure).

FLOW OBJECTS•  Event•  Activity•  Gateway

BPMN



!

ACTIVITY: An activity is represented by a rectangle with rounded angles. An activity can be atomic or not atomic. The types of activities are: Task and Sub-Process. The sub-process is distinguished by a small "+" sign in the bottom centre of the figure.

BPMN FLOW OBJECTS•  Event•  Activity•  Gateway



!

GATEWAY: A Gateway is represented by a diamond and is used to control the convergence (FAN-IN) or divergence (FAN-OUT) of the workflow. It is used to represent decisions, but also mechanisms for forking, merging and joining behaviour.

BPMN FLOW OBJECTS•  Event•  Activity•  Gateway



!

SEQUENCE FLOW: it is represented by an arrow and is used to show the way in which (their order and sequence) the activities will take place in the process.MESSAGE FLOW: it is represented by a dotted arrow and is used to show the flow of messages between two participants in the process.ASSOCIATION: it is represented by an arrow with dotted line and is used to associate data, text and everything you need to specify (e.g. inputs and outputs of activities).

BPMN CONNECTING OBJECTS•  Sequence flow•  Message flow•  Association



!

Many techniques of process modelling use the concept of “swimlanes” as a mechanism to organize tasks into separate categories, with the aim of illustrating the different functional capabilities or responsibilities.

BPMN SWIMLANES•  Pool•  Lane



!

The Pool is used when the diagram involves two separate business entities, which are physically separated. The flow of messages shows how the communication between the two participants is resolved in the connection between the two Pool.

BPMN SWIMLANES•  Pool



!

The Lane are often used to separate the activities associated with a specific business function or unit. The Sequence Flow can cross the boundaries of Lane in a Pool, while the Message Flow can not be used between two Flow Objects in the two different Lanes of the same Pool

BPMN SWIMLANES•  Lane



!

BPMN is designed to allow modellers some flexibility in their business process modelling by extending the basic notation and providing additional graphical elements for modelling specific situations or Industry specific process characteristics (e.g. insurance or banking).Modellers can create their own types of artifact, which add more details on the process. However, the basic structure of the process consists of activities, and Gateway Sequence Flow, does not change with the addition of the Artifact as can be seen by comparing the following figures

BPMN ARTIFACTS•  Data Object•  Group•  Annotation



!BPMN



!

For modellers who need a higher level of precision in the process model, additional details (secondary elements) shown through internal indicators can be added to the primary elements (core set).

BPMN



!

Primary elements plus the additional secondary elements constitute the so called COMPLETE SET

For example, the secondary elements associated to Events are shown in the figure. They represent different ways in which the Start and Intermediate Events may be caused, or also different type of results that an End Event can generate

For all secondary elementsLINK atBPMN Quick Reference Guide

BPMN



!

According to the BPMN formalism a message exchange between two business entities can directly connect the two pools for the various entities within a single pool or it can connect directly two flow objects.Furthermore, if there is an Expanded Sub-Process in one of the Pool, then the message can be connected both with boundaries in the sub-process and with any object inside. In the first case, it is like if the incoming message was connected with the Star Event or the outgoing message was connected with the End Event.

BPMN



!BPMN



!

Process breakLooping

Call and wait Call and continue

BPMN



!

The tool Bizagi Process Modeler®

TECHNIQUES FOR ENTEPRISE MODELLING

Documents

Transcript of TECHNIQUES FOR ENTEPRISE MODELLING