Guidelines of Business Process Modeling Team: Alejandra Saavedra Andrea Rodriguez Ez Lawrence

1. Complexity and Quality of Business Process Models Popularity of different process management Effects Number and Variety of model designers and users Number and Variety of purposes process models Knowledge

1. Complexity and Quality of Business Process Models Design of Process Models Economic Efficiency Personal resources Software tools Economical Risk Modeling exercise

2. Guidelines of Modeling (GoM) Generally Accepted Accounting Principles (GAAP)

2. Guidelines of Modeling (GoM) Design recommendation in order to increase the quality of models beyond the fulfillment of syntactic rules Six Guidelines Process quality Product quality

2. Guidelines of Modeling (GoM) Level 1 Level 2 Level 3 Six General Guidelines Different views, Process Models Modeling Techniques, Event – driven Process Chains

2. Guidelines of Modeling (GoM) Optional character Basic Guidelines: Necessary precondition

2.1 Guidelines of Modeling (GoM) Basic Guidelines Correctness Relevance Economic Efficiency

2. Guidelines of Modeling (GoM) Correctness Syntactic Semantic Consistent and complete against the meta model Structure and the behavior must be consistent with the real world

2.1 Guidelines of Modeling (GoM) Relevance -To select a relevant object system -To take a relevant modeling system or to configure an existing meta model adequately -To develop a relevant model system Economic Efficiency Cost/benefit constraint

2.2 Guidelines of Modeling (GoM) Optional Guidelines Clarity Comparability Systematic Design The model user must understand Consistent of models, same certain and rules Well defined relationship between models of different views

2.3 Guidelines of Modeling (GoM) The GoM Meta Model Integrate and Structure the different project topics Shows that a perspective is defined as a person – purpose – model -relationship

3. Guidelines for Selected Purpose of Business Process Modeling Workflow Management Serve in system planning and development as a communication platform for those who work on the project

3.1 Workflow Management Organization View Function View Data View Which organization units are there? (e.g. purchasing, sales, accounting) Which functions are processed? (e.g. Create inquiries, verify invoices) Which information is important? (e.g. customer, supplier, product, bill of material) Relationship between data, functions and organization units Control View

3.1 Workflow Management ARIS Modeling Methods

Avoided manual functions Start and end conditions precisely Deadline is exceeded Data View Every function the description of the necessary input and output data is required. Describe the data flow. Can’t precede the control flow. Complete and not visualization Function View

Role 、 organization unit 、 position 、 position type 、 person as a static information XOR-Relationship 、 AND- Relationship Resource The logic relationships between the workflow functions Various splitting and joining connections without that the modeler has to be concerned about the process execution OR-splits 、 OR-Joins 、 ELSE-exit. Control View Organization View

3.2 Simulation Business Process Simulation (BPS) Hansen(1994) － an engineering approach to process reengineering that incorporates modeling and simulation is necessary. Kettinger(1997) － a need for more user-friendly and media-rich capture of business by providing easy visualization and allowing team participation in process design.

3.2 Simulation Three Principles in designing models The structuring of similar objectives in phases The reuse of solution components The application of conventions to restrict the degree of freedom phases components conventions

3.2 Simulation Phase model for simulation model design

Model components Goal ： A more efficient and correct model construction.Goal ： A more efficient and correct model construction. The structure components describe coordination mechanisms on different complexity levels where components can consist of less complex components.The structure components describe coordination mechanisms on different complexity levels where components can consist of less complex components. 3.2 Simulation Model Components

3.2 Simulation Design conventions Methods of process modeling contain generally just a set of syntactic rules, which give model designers a wide degree of freedom. An objective has to be taken into account due to the high number and variety of involved model designers and users of model. Important intensions: (1)ensure a uniform, clear and unequivocal understanding of models of all involved users. (2)support to cope with the requirements of perspectives.

There are six ways of customizing different perspectives: Different Layout Conventions Different Naming Conventions Different Information Objects Different Information Objects Types Different Use of a Process Modeling Technique Different Meta Models TECHNIQUES FOR ADJUSTING MODELS TO PERSPECTIVES Perspectives on process models can be distinguished by the involved persons and by the modeling purpose.

4.1 DIFFERENT LAYOUT CONVENTIONS The models of two perspectives concerning the number and the naming of the information objects are identical, but different in their presentation. This kind of model is more determined by the way of using the model than by the model content. Example: Clothes Factory

4.2 DIFFERENT NAMING CONVENTIONS A different naming in models related to different perspectives is of high importance in distributed, especially international modeling and requires the possibility to administer synonyms for the relevant model construct. It is recommended to use a business term catalogue, which defines and relates the main terms within a company. Between the single business term exist a typical relationship like “is related to”, “classifies”, “is part of”, “is a” or “is a synonym of”. Example:

4.3 DIFFERENT INFORMATION OBJECTS The Perspectives are much more individual than different Layout or Naming conventions, when different information objects are relevant for them. Each area is interested in a detailed description of the information, thus different perspectives can be characterized as different projections on one common model. DEPARTMENT OF FINANCES DEPARTMENT OF PRODUCTION DEPARTMENT OF SALES PRICE COST QUANTITY OF UNITS SOLD IN STORES MATERIAL COLOR SIZES 4.4 DIFFERENT INFORMATION OBJECT TYPES Different perspectives can be characterized as different projections on a common meta model.

5. DIFFERENT USE OF A PROCESS MODELING TECHNIQUE This kind of perspective differentiation requires individual rules to transform one model into the other. MODEL TECHNIQUE 1 MODEL TECHIQUE 2 MODEL TECHINIQUE 3 MODEL TECHNIQUE N The RULES transform the model’s Techniques MODEL 1 MODEL 2 MODEL 3 MODEL N These are models that has a common root and leads to the fact that in many cases perspectives can be distinguished because they are slightly different in their meta model.

4.5 DIFFERENT META MODELS When the perspectives have a high degree of individualization they have designed with different models techniques, so is recommended to design relationship meta models, which relate the elements and relationships of the involved modeling techniques to each other. DIFFERENT NAMING CONVENTIONS DIFFERENT INFORMATION OBJECTS DIFFERENT INFORMATION OBJECTS TYPES

Thank you very much