Process Diagram Technique for Business Processes Modeling

Slides:



Advertisements
Similar presentations
FPA – IFPUG CPM 4.1 Rules.
Advertisements

Alternative Approach to Systems Analysis Structured analysis
Chapters 7 & 9 System Scope
Chapter 7 Structuring System Process Requirements
Systems Analysis and Design, 7e Kendall & Kendall
Analysis Concepts, Principles, and Modeling
Object-oriented modeling Class/Object Diagrams
Introduction To System Analysis and Design
Use-case Modeling.
System Analysis - Data Modeling
PROCESS MODELING Transform Description. A model is a representation of reality. Just as a picture is worth a thousand words, most models are pictorial.
Section 04DFD - Top Level1 04 Data Flow Diagrams - Top Level DFD And Franchise Colleges By MANSHA NAWAZ.
Department of Computer Science 1 CSS 496 Business Process Re-engineering for BS(CS)
Chapter 7 Structuring System Process Requirements
6 Systems Analysis and Design in a Changing World, Fourth Edition.
Chapter 6: The Traditional Approach to Requirements
System Analysis Overview Document functional requirements by creating models Two concepts help identify functional requirements in the traditional approach.
Introduction To System Analysis and design
Chapter 1: Data Flow Diagram Structuring System Process Requirements
Database System Development Lifecycle © Pearson Education Limited 1995, 2005.
Chapter 6 System Engineering - Computer-based system - System engineering process - “Business process” engineering - Product engineering (Source: Pressman,
BPMN By Hosein Bitaraf Software Engineering. Business Process Model and Notation (BPMN) is a graphical representation for specifying business processes.
SOFTWARE ENGINEERING BIT-8 APRIL, 16,2008 Introduction to UML.
ANALYSIS REQUIREMENT ANALYSIS DESIGN IMPLEMENTATION TEST.
Chapter 7 Structuring System Process Requirements
© 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley 1 A Discipline of Software Design.
Database Design - Lecture 2
Introduction To System Analysis and Design
Copyright 2002 Prentice-Hall, Inc. Chapter 2 Object-Oriented Analysis and Design Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey.
Chapter 3 Systems Documentation Techniques Copyright © 2012 Pearson Education, Inc. publishing as Prentice Hall 3-1.
Requirements as Usecases Capturing the REQUIREMENT ANALYSIS DESIGN IMPLEMENTATION TEST.
1 6 Systems Analysis and Design in a Changing World, 2 nd Edition, Satzinger, Jackson, & Burd Chapter 6 The Traditional Approach to Requirements.
Modeling System Requirements: Events and Things. Objectives Explain the many reasons for creating information system models Describe three types of models.
OMT Modeling 1. Object Model : presented by the object model and the data dictionary. 2. Dynamic Model: presented by the state diagrams and event flow.
Chapter 7 Structuring System Process Requirements Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich.
UML - Development Process 1 Software Development Process Using UML.
6 Systems Analysis and Design in a Changing World, Fourth Edition.
Software Engineering Lecture 10: System Engineering.
© 2005 by Prentice Hall Chapter 7 Structuring System Process Requirements Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F. George.
System A system is a set of elements and relationships which are different from relationships of the set or its elements to other elements or sets.
Tools for Navigating and Analysis of Provenance Information Vikas Deora, Arnaud Contes and Omer Rana.
1 7 Systems Analysis and Design in a Changing World, 2 nd Edition, Satzinger, Jackson, & Burd Chapter 7 The Object-Oriented Approach to Requirements.
Chapter 5 – System Modeling Lecture 1 1Chapter 5 System modeling.
Introduction to OOAD and UML
5 Systems Analysis and Design in a Changing World, Fourth Edition.
CompSci 280 S Introduction to Software Development
Business System Development
Introduction to Management MGT 101
CHAPTER
Chapter 4: Business Process and Functional Modeling, continued
Business System Development
Data Flow Diagrams.
Chapter 5 System modeling
Systems Analysis and Design in a Changing World, Fourth Edition
Chapter 6 The Traditional Approach to Requirements.
Object-Oriented Analysis and Design
Software Engineering (CSI 321)
Unified Modeling Language
System Design.
Object Oriented Concepts -I
CSSSPEC6 SOFTWARE DEVELOPMENT WITH QUALITY ASSURANCE
Chapter 1: Data Flow Diagram Structuring System Process Requirements
Business System Development
IE352 System Analysis and Design
GROUP MEMBERS NAME ROLL NO SHAUBAN ALI 17-ARID-5650 UMAIR MUSHTAQ 17-ARID-5656 TARIQ SAEED 17-ARID-5657 MUSKAN WADOOD 17-ARID-5641.
Chapter 20 Object-Oriented Analysis and Design
Requirement Analysis using
Chapter 7: Data Flow Diagram Structuring System Process Requirements
Chapter 4 System Modeling.
Presentation transcript:

Process Diagram Technique for Business Processes Modeling Vaclav Repa University of Economics, Prague, Czech Republic ISD2000 Conference, Kristiansand, Norway, August 2000 V.Repa: Process Diagram Technique for BPM, ISD2000 Conference, Kristiansand, Norway, August 2000

Different Levels of the Technique Important Topics Agenda The Scope The Technique Diagram Elements Process Meta-Model Different Levels of the Technique Important Topics Events, Activities, and States from the Object vs. Process Point of View (Consistency Rules) Process Memory (Simple/Complex Processes) V.Repa: Process Diagram Technique for BPM, ISD2000 Conference, Kristiansand, Norway, August 2000

Model of the system of business processes which: The Scope Model of the system of business processes which: respects basic objectives and goals, current state and specific characteristics of the organization respects objective circumstances (those which are given outside the organization and are independent of the organization) which can play a significant role in the behavior of the organization is "optimal" in the sense of economic efficiency of the processes is "optimal" in the sense of maximum simplicity together with whole functionality is prepared for later optimization, implementation and installation of the system of processes which respect characteristics described above V.Repa: Process Diagram Technique for BPM, ISD2000 Conference, Kristiansand, Norway, August 2000

The Scope Convergence of BPE, WfM, and ISD V.Repa: Process Diagram Technique for BPM, ISD2000 Conference, Kristiansand, Norway, August 2000

The Scope Objects and processes as a basis for IS development V.Repa: Process Diagram Technique for BPM, ISD2000 Conference, Kristiansand, Norway, August 2000 Back

The Technique Process modeling diagram elements - basic set Symbol Explanation Element Activity Basic element of the process - input(s) to output(s) processing. Activity is decomposable on principle, i.e. it can be always regarded as the process (on the deeper level of detail). Activity Decision Elementary (i.e. undecomposable) activity. Decision on the particular follow-up of the process. Decision Event External stimulus for the activity. Information about the event outside of the process and independent of it. Event State Internal stimulus for the activity. Result of the preceding activity. State Logical Primitive decision without any information at the input (predefined decision). The only AND and OR (XOR) connectors are allowable. Connector AND V.Repa: Process Diagram Technique for BPM, ISD2000 Conference, Kristiansand, Norway, August 2000 Back

The Technique Process modeling diagram elements - external elements Symbol Explanation Element Information Set Set of the information for process control. Examples: manufacturing plan, strategic investment intention, delivery note etc. Information Set Material Set Set of the subjects of processing. I.e. raw material (at the input) or product (at the output), no matter whether it is material or data. Examples: engine component, car (final product) in the case of car manufacturing. Stock list, investment advice (final product) in the case of broker's business (information plays the role of the material here). Material Set Mixed Set Set of the combination of the subjects of processing as well as Mixed Set the information for controlling it. Example: delivery together with the delivery note Actor Abstract person - all kinds of the attendee of the process (person, organization unit, system, position, profession, role, Actor entity etc.). Problem Problem related to the process in the particular point. Problem Organization Unit of the organization where the process runs. Unit Organization Unit V.Repa: Process Diagram Technique for BPM, ISD2000 Conference, Kristiansand, Norway, August 2000 Back

The Technique Process meta-model V.Repa: Process Diagram Technique for BPM, ISD2000 Conference, Kristiansand, Norway, August 2000

The Technique Three levels of model simplification Description Purpose of simplification level 0 Full complexity. All elements used. Model without actors, problems and organization units. Description of the process itself without the respect to the related external aspects (actors, problems and organization). There is no possibility to analyze those external aspects (for the purpose of the information analysis of the legal IS for example). level 1 Level 1 model without sets (material, information or mixed). Description of the process itself without the respect to the inputs and outputs of the activities. Such a model describes the succession of the activities together with the process control (activity stimuli). It does not describe the substance of the processing. level 2 Level 2 model without states and control activities. Description of the process itself without the respect to the inputs and outputs of the activities. Such a model describes the succession of the activities only. No internal control is described. level 3 V.Repa: Process Diagram Technique for BPM, ISD2000 Conference, Kristiansand, Norway, August 2000

Consistency of processes and objects Outline of the consistency rules requirements concerning external facts (different meanings of the same fact) Fact Object Model Business Process Model Event Stimulus for: · object internal state change possible communication with other objects (send the message) in the case of the "common action" operation execution process state change output production possible communication with other processes (processes co-ordination) Output Consequence of object action Consequence of: operation execution (product) Outline of the consistency rules requirements concerning internal concepts (different meanings of the same concept) Concept Action Action executed/allowed by the object Causes: object state change possible output production Activity inside the process processes (co-ordination of processes) State Object life cycle state starting point for action processing result of action processing Process course state starting point for operation execution result of operation execution V.Repa: Process Diagram Technique for BPM, ISD2000 Conference, Kristiansand, Norway, August 2000 Illustration

Process memory includes: Why: The need to store the information about the actual process state in controlling complex processes (which often have complex relationships to other processes). The need to reduce the complexity of the process description. Process memory includes: actual process state identification attributes of actual state of the process data gathered by the process activities (once the data are gathered, they exist inside the process and can be used by its activities without any limitation (global data access)) Consequences: criterion for distinguishing between primitive and complex processes. (process without the need to store the information about the state is so simple that it is possible to take it (and implement it, as well) as a simple algorithm) indicates the possible parallelism inside the process or at least in the communication with other processes. V.Repa: Process Diagram Technique for BPM, ISD2000 Conference, Kristiansand, Norway, August 2000

Primitive Process (Order Receiving) V.Repa: Process Diagram Technique for BPM, ISD2000 Conference, Kristiansand, Norway, August 2000

Primitive Process (Order Receiving) - Aris Notation V.Repa: Process Diagram Technique for BPM, ISD2000 Conference, Kristiansand, Norway, August 2000

Complex Process (Order Transaction) Waiting for Store Action Waiting for Customer Action V.Repa: Process Diagram Technique for BPM, ISD2000 Conference, Kristiansand, Norway, August 2000