1 Sobah Abbas Petersen Adjunct Associate Professor TDT4252 Modelling of Information Systems Advanced Course Lecture 6: Process Modelling.

Slides:



Advertisements
Similar presentations
Mahmut Ali GÖKÇEIndustrial Systems Engineering Lecture 2 System Identification ISE102 Spring 2007.
Advertisements

Chapter 3 - Modeling and Process Modeling1 Chapter 3 – Modeling and Process Modeling By Dr. Sartuk KARASOY Middle East Technical University
Chapter 22 Object-Oriented Systems Analysis and Design and UML Systems Analysis and Design Kendall and Kendall Fifth Edition.
Introduction To System Analysis and Design
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 8 Slide 1 System models.
Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 8 Slide 1 System models.
©Ian Sommerville 2000Software Engineering, 6/e, Chapter 71 System models l Abstract descriptions of systems whose requirements are being analysed.
Creating Architectural Descriptions. Outline Standardizing architectural descriptions: The IEEE has published, “Recommended Practice for Architectural.
Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 8 Slide 1 System models.
1/31 CS 426 Senior Projects Chapter 1: What is UML? Chapter 2: What is UP? [Arlow and Neustadt, 2005] January 22, 2009.
Basic Concepts The Unified Modeling Language (UML) SYSC System Analysis and Design.
TDT4252 Modelling of Information Systems Advanced Course
Introduction To System Analysis and design
Software Development Process
Chapter 6 System Engineering - Computer-based system - System engineering process - “Business process” engineering - Product engineering (Source: Pressman,
TDT4252 Modelling of Information Systems Advanced Course
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 7 Slide 1 System models l Abstract descriptions of systems whose requirements are being.
Chapter 4 System Models A description of the various models that can be used to specify software systems.
Chapter 8 Architecture Analysis. 8 – Architecture Analysis 8.1 Analysis Techniques 8.2 Quantitative Analysis  Performance Views  Performance.
System models Abstract descriptions of systems whose requirements are being analysed Abstract descriptions of systems whose requirements are being analysed.
© 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley 1 A Discipline of Software Design.
1 Sobah Abbas Petersen Adjunct Associate Professor TDT4252 Modelling of Information Systems Advanced Course Lecture 5: i*modelling.
1 TDT4252/DT8802 Assignment Sobah Abbas Petersen Adjunct Associate Professor TDT4252 Modelling of Information Systems Advanced Course TDT4252,
Introduction To System Analysis and Design
Chapter 7 System models.
System models l Abstract descriptions of systems whose requirements are being analysed.
Pertemuan 19 PEMODELAN SISTEM Matakuliah: D0174/ Pemodelan Sistem dan Simulasi Tahun: Tahun 2009.
Modified by Juan M. Gomez Software Engineering, 6th edition. Chapter 7 Slide 1 Chapter 7 System Models.
Software Engineering, 8th edition Chapter 8 1 Courtesy: ©Ian Somerville 2006 April 06 th, 2009 Lecture # 13 System models.
Sommerville 2004,Mejia-Alvarez 2009Software Engineering, 7th edition. Chapter 8 Slide 1 System models.
1 Introduction to Software Engineering Lecture 1.
Illustrations and Answers for TDT4252 exam, June
Information Systems Engineering. Lecture Outline Information Systems Architecture Information System Architecture components Information Engineering Phases.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 14 Slide 1 Object-oriented Design.
1 Sobah Abbas Petersen Adjunct Associate Professor TDT4252 Modelling of Information Systems Advanced Course TDT4252, Spring 2013 Lecture.
7 Systems Analysis and Design in a Changing World, Fifth Edition.
T3: Enterprise Systems Modeling Fall 2013 Chin-Sheng Chen Florida International University.
Systems Analysis and Design in a Changing World, 6th Edition
Computing and SE II Chapter 9: Design Methods and Design Models Er-Yu Ding Software Institute, NJU.
Architecture View Models A model is a complete, simplified description of a system from a particular perspective or viewpoint. There is no single view.
Winter 2011SEG Chapter 11 Chapter 1 (Part 1) Review from previous courses Subject 1: The Software Development Process.
Chapter 5 System Modeling. What is System modeling? System modeling is the process of developing abstract models of a system, with each model presenting.
CSCI 3428: Software Engineering Tami Meredith UML Unified Modeling Language.
CS223: Software Engineering
Enterprise Systems Modeling EGN 5623 Enterprise Systems Optimization Fall, 2012.
21/1/ Analysis - Model of real-world situation - What ? System Design - Overall architecture (sub-systems) Object Design - Refinement of Design.
1 SYS366 Week 1 - Lecture 1 Introduction to Systems.
 To explain why the context of a system should be modelled as part of the RE process  To describe behavioural modelling, data modelling and object modelling.
1 Sobah Abbas Petersen Adjunct Associate Professor, NTNU Researcher, Sintef TDT4252 Modelling of Information Systems Advanced Course TDT4252,
1 Sobah Abbas Petersen Adjunct Associate Professor TDT4252 Modelling of Information Systems Advanced Course Lecture 4: Introduction to.
Enterprise Systems Modeling EGN 5621 Enterprise Systems Collaboration (Professional MSEM) Fall, 2012.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 8 Slide 1 System models.
1 Sobah Abbas Petersen Adjunct Associate Professor TDT4252 Modelling of Information Systems Advanced Course TDT4252, Spring 2011 TDT4252,
Chapter 5 – System Modeling Lecture 1 1Chapter 5 System modeling.
Engineering, 7th edition. Chapter 8 Slide 1 System models.
Process Analysis and Modeling Using IDEF0
Chapter 5 – System Modeling
Information System Applications
Chapter 5 System modeling
Chapter 5 – System Modeling
Information systems modeling tools
The Engineering Design of Systems: Models and Methods 3rd Edition
System Modeling Chapter 4
Introduction To System Analysis and Design PART 2
Dynamic Modeling Lecture # 37.
TDT4252 Modelling of Information Systems Advanced Course
King Saud University College of Engineering IE – 462: “Industrial Information Systems” Fall – 2018 (1st Sem H) Chapter 4: Structured Analysis.
Chapter 4 System Modeling.
Information systems modeling tools
Presentation transcript:

1 Sobah Abbas Petersen Adjunct Associate Professor TDT4252 Modelling of Information Systems Advanced Course Lecture 6: Process Modelling TDT4252, Spring 2013

2 Overview of lecture today Process Modelling: IDEF0 and BPMN Based on the following articles: Vernadat, F. B. (1996), Chapter 4: Modelling Functional Aspects, in Enterprise Modelling and Integration: Principles and Applications. Chapman and Hall. ISBN: Noran, Ovidiu, S. Business Modelling: UML vs. IDEF, Griffiths University, Menzel, Christopher, Mayer, Richard J. The IDEF Family of Languages. (pages 1-11 only) Lecture 6: Process Modelling TDT4252, Spring 2013

3 From lecture on perspectives to conceptual modelling Structural Functional Behavioral Rule-oriented Object-oriented Social communication Actor/role-oriented Lecture 6: Process Modelling Perspectives of an enterprise TDT4252, Spring 2013

4 Functional Modelling Methods to model the functional aspects of an enterprise: the things to be done and the way things are done in an enterprise. The purpose of a functional modelling approach is to describe the enterprise functionality and enterprise behaviour to the level of detail required by business users. TDT4252, Spring 2013 Lecture 6: Process Modelling Ref: Vernadat, 1996

5 Enterprise Functionality Concerns the things to be done, i.e. activities and operations performed, either by humans or machines, within an enterprise. Enterprise functionality represents actions performed in the form of functions transforming input into output, over a period of time. TDT4252, Spring 2013 Lecture 6: Process Modelling Ref: Vernadat, 1996

6 Enterprise Behaviour Concerns flow of control within an enterprise, i.e. the sequence in which things are done. Enterprise behaviour governs the way enterprise functionality is performed according to occurrences of enterprise states and real-world events. TDT4252, Spring 2013 Lecture 6: Process Modelling Ref: Vernadat, 1996

7 Functional Modelling Methods Functions can be activities or processes. Functions are then connected by means of a precedence relationship to model the business processes of the enterprise. TDT4252, Spring 2013 Lecture 6: Process Modelling Most functional modelling methods are based on a functional decomposition principle: functions of the system modelled are decomposed into sub-functions, sub-functions into sub-functions, and so on. Ref: Vernadat, 1996

8 Terminology: Activity and Process Activity: An activity f performs something, usually transforming its inputs into outputs. Generally, this transformation may happen if some condition C is verified. –Activity f transforms an input state into an output state, under condition C. Process: Processes are logico-temporal sequences of activities. They are partially ordered sets of activities. Task: a part of a set of actions for completion. TDT4252, Spring 2013 Lecture 6: Process Modelling Ref: Vernadat, 1996

9 Taxonomy of Manufacturing Enterprise Activities DesignProduction Control Production Engineering ManufacturingProduction Planning Preliminary design Inventory controlProcess planningMachining and assembly activities Long-term forecasting Detailed designMaster production scheduling Manufacturing plant layout design Process controlMaster production scheduling Engineering design/ analysis Material requirements planning Part programmingQuality controlMaterial requirements planning DocumentationProduction scheduling Tool and fixture design Production scheduling TDT4252, Spring 2013 Lecture 6: Process Modelling Ref: Vernadat, 1996 Planning Scheduling

10 Business Processes A business process is a collection of related, structured activities or tasks that produce a specific service or product (serve a particular goal) for a particular customer or customers. ( Ref: Wikipedia ) A business process is a sequence (or partially ordered set) of enterprise activities, execution of which is triggered by some event and will result in some observable or quantifiable result. ( Ref: Vernadat, 1996 ) TDT4252, Spring 2013 Lecture 6: Process Modelling Goal Think as processes instead of functions and procedures!

11 Business Processes Modelling Business Process Models take into account the business goals, business structure and the resources that are available to achieve the business goals. This introduces additional concepts to the ones introduced in functional modelling: input transformed into output, under a specific condition.  Business Goals  Resources TDT4252, Spring 2013 Lecture 6: Process Modelling As-isTo-be

12 History TDT4252, Spring 2013 Lecture 6: Process Modelling Flow charts Control flow diagrams Gantt Charts Pert charts SADT/IDEF UML (Unified Modelling Language) BPMN (Business Process Modelling Notation)

13 SADT SADT: Structured Analysis Design Technique (Ross 1977, Ross and Schoman 1977) Originally developed as a “system-blueprinting” method for software engineering, i.e. a method for detailed requirements definition. Main strength: it is based on a structured methodology for decomposing complex systems into functions and sub-functions. -Not suitable for describing flows (it describes dependencies). -Only provides a static snapshot of the state of the system. TDT4252, Spring 2013 Lecture 6: Process Modelling

14 IDEF Languages (1) ICAM (Integrated Computer Aided Manufacturing) IDEF = ICAM DEFinition Language Originated in the 1970s, in the US Air Force and the ICAM program, based on SADT. Initially intended for use in Systems Engineering IDEF0 : for activity modelling or functional modelling. Later a suite of languages: IDEF1, IDEF2… for more advanced modelling. We will focus on IDEF0! TDT4252, Spring 2013 Lecture 6: Process Modelling

15 IDEF0 IDEF0 : for activity modelling or functional modelling. Models the decisions, actions and activities of an organisation or system, in order to communicate the functional perspective of a system. TDT4252, Spring 2013 Lecture 6: Process Modelling

16 IDEF0: Syntax A model of a function at the highest level of inputs, outputs, controls and mechanisms. TDT4252, Spring 2013 Lecture 6: Process Modelling Function Controls OutputsInputs Mechanisms Inputs: items that trigger or are transformed in the activity Controls: guide or regulate the activity Mechanisms: resources used to perform the activity Outputs: results of the activity or items processed or transformed ICOMs

17 IDEF0: Decomposition The top level is called a context. TDT4252, Spring 2013 Lecture 6: Process Modelling

18 IDEF0: ICOMs Input: –Can be a trigger –Input that is transformed to output. Control –Guide or regulate activity –!!! Distinction between input and control: inputs change, controls remain unchaged. Mechanism: resources needed to perform activity –People –Equipment, IT –Financial resources Outputs –Results of a performing the activity TDT4252, Spring 2013 Lecture 6: Process Modelling

19 IDEF0: Dependency & Flow Dependency: One process depends on another. Flow: something flows between processes: Information, material TDT4252, Spring 2013 Lecture 6: Process Modelling Remember the Barings Bank case?

20 IDEF0 Model in Metis (1) TDT4252, Spring 2013 Lecture 6: Process Modelling

21 IDEF0 Model in Metis (2) TDT4252, Spring 2013 Lecture 6: Process Modelling Role of ICOMs

22 IDEF0 Model in Metis (3) TDT4252, Spring 2013 Lecture 6: Process Modelling The ICOMs show their relevance to the processes. They can be considered in more detail as other domains.

23 IDEF0 Model in Metis (4) TDT4252, Spring 2013 Lecture 6: Process Modelling

24 IDEF0 Modelling in Metis Use MEAF template From Model Tree view, select: –Metis Enterprise Architecture Framework Process Domain Use Modelling Objects: –Process (object), Process Input (interface), Process Control(interface), Process Output (interface), Process Mechanism (interface) To link processes via the ICOMs, use the menu process modelling menu, available on the process and ICOM objects: –Point to a process or an ICOM –Click right mouse button, a list of possible relationships appear –Select appropriate relationship TDT4252, Spring 2013 Lecture 6: Process Modelling

25 Connecting IDEF0 ICOMs to Other Domains in Metis TDT4252, Spring 2013 Lecture 6: Process Modelling To link ICOMs to other domains in the model : Select the desired object (e.g. a document) Point to an ICOM Click right mouse button, a list of possible relationships appear Select appropriate relationship

26 IDEF0: Benefits Supports understanding of the organisation Helps improve our knowledge about the organisation Supports decision making Supports planning and improvement (e.g. by adding new processes easily) TDT4252, Spring 2013 Lecture 6: Process Modelling

27 IDEF0: Strengths & Weaknesses Strenghts: –Effective in detailing the system activities for function modelling. –Provide a concise description of systems, by using the ICOMs (Input, Control, Mechanism, Mechanism) –The hierarchical nature allows the system to be easily refined into greater detail. Weaknesses: –Can be so concise that only domain experts can understand. –Can be misinterpreted as representing a sequence of activities. TDT4252, Spring 2013 Lecture 6: Process Modelling

28 IDEF and UML IDEF Comes from manufacturing Addresses business environments Aims to cover O-O, knowledge representation and software development UML O-O software Driven by software development Focussed on designing software systems UML “business customisations” are based upon principles borrowed from IDEF. TDT4252, Spring 2013 Lecture 6: Process Modelling

29 Discussion: IDEF0 Is IDEF0 functional modelling or Process Modelling or both? How can you use IDEF0 in your assignment? How does IDEF0 link to the other modelling methods and languages we have looked at? TDT4252, Spring 2013 Lecture 6: Process Modelling

30 BPMN: Strenghts & Weaknesses Strenghts: –Connects business process representations with system design –Represents a more unified modelling language than some of its predecessors Weaknesses: –Difficult to model teamwork where the line of responsibility is not so clear. –Focussed towards process execution. TDT4252, Spring 2013 Lecture 6: Process Modelling

31 Discussion: BPMN How does BPMN compare to IDEF0? How does BPMN link to the other modelling methods and languages we have looked at? How can you use BPMN in your assignment? TDT4252, Spring 2013 Lecture 6: Process Modelling When should we use which method?

32 Next Lecture Product Modelling –Product Modelling in Metis TDT4252, Spring 2013 Lecture 6: Process Modelling