Manfred Reichert, Barbara Weber, Victoria Torres Large Process Models and Process Model Collections: - Challenges, Methods, Technologies - Barbara Weber.

Slides:



Advertisements
Similar presentations
3° Workshop Nazionale del Gruppo di Interesse in Ingegneria del Software Genova, 2-3 ottobre 2006 CASE – Libera Università di Bolzano-Bozen RCOST – Università
Advertisements

1 Service Oriented Architectures (SOA): What Users Need to Know. OGF 19: January 31, 2007 Charlotte, NC John Salasin, Ph.D, Visiting Researcher National.
Conquering Complex and Changing Systems Object-Oriented Software Engineering Chapter 12, Software Life Cycle.
Computer Science Department
CSC 480 Software Engineering
BPMN 2.0 Interchange: W5 Denis Gagné, CEO & CTO Trisotech BPMN 2.0 FTF Member XPDL 2.2 and 3.0 Co-Editor.
UML Diagrams Jung Woo. What is UML? Standard language for specifying, visualizing, constructing, and documenting the artifacts of software systems, business.
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall A.1.
Service Design / Figure 3.11 The Generic Process Elements.
An Architecture-Based Approach to Self-Adaptive Software Presenters Douglas Yu-cheng Su Ajit G. Sonawane.
Software engineering for supply chains:
Lecture 3: Requirements Modeling Intro Professor Aditya Ghose Director, Decision Systems Lab School of IT and Computer Science University of Wollongong.
1 CS 425 Software Engineering Project Preparation Use Case Modeling [Based on Chapters 3 & 4, Arlow and Neustadt, “UML and the Unified Process,” Addison-Wesley,
21-February-2003cse Architecture © 2003 University of Washington1 Architecture CSE 403, Winter 2003 Software Engineering
Model Eco-systems Decision Systems Lab University of Wollongong.
1/31 CS 426 Senior Projects Chapter 1: What is UML? Chapter 2: What is UP? [Arlow and Neustadt, 2005] January 22, 2009.
More on RDT Robert John Walters. RDT – a reprise A Graphically based formal modelling language Models represented as diagrams (not text) Communications.
Copyright 2004 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Second Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Appendix.
Requirements modelling motivations: I We need a language for communicating shared perceptions of the requirements for the target system between human stakeholders.
1 CS 426 Senior Projects Chapter 1: What is UML? Chapter 2: What is UP? [Arlow and Neustadt, 2002] January 26, 2006.
Business process management (BPM) Petra Popovičová.
MSF Testing Introduction Functional Testing Performance Testing.
What is Business Analysis Planning & Monitoring?
What is UML? What is UP? [Arlow and Neustadt, 2005] January 23, 2014
© Drexel University Software Engineering Research Group (SERG) 1 Based on the paper by Philippe Kruchten from Rational Software.
Modeling Process CSCE 668Set 14: Simulations 2 May be several algorithms (processes) runs on each processor to simulate the desired communication system.
Software Engineering CS3003 Lecture 3 Software maintenance and evolution.
9/14/2012ISC329 Isabelle Bichindaritz1 Database System Life Cycle.
1 Chapter 15 Methodology Conceptual Databases Design Transparencies Last Updated: April 2011 By M. Arief
Design Document Presentation. Review Quoridor – a board game played on a grid where players must advance tokens across a board to win. Our basic objective:
Copyright 2001 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Appendix A Object-Oriented.
SOFTWARE DESIGN (SWD) Instructor: Dr. Hany H. Ammar
Programming in Java Unit 3. Learning outcome:  LO2:Be able to design Java solutions  LO3:Be able to implement Java solutions Assessment criteria: 
What is a Business Analyst? A Business Analyst is someone who works as a liaison among stakeholders in order to elicit, analyze, communicate and validate.
European Operational Concept Validation Methodology E-OCVM Version 3: What’s New Episode 3 - CAATS II Final Dissemination Event Matthias Poppe DFS Episode.
1/26/2004TCSS545A Isabelle Bichindaritz1 Database Management Systems Design Methodology.
1 Introduction to Software Engineering Lecture 1.
Barbara Weber Univ. of Innsbruck, Austria Manfred Reichert Univ. of Ulm, Germany Presenter: Arghyadip Paul Refactoring Process Models in Large Process.
Terminology and Use Cases Status Report David Harrington IETF 88 – Nov Security Automation and Continuous Monitoring WG.
UML diagrams What is UML UML diagrams –Static modeoing –Dynamic modeling 1.
Project Management For the Non Project Manager 1.
Logical view –show classes and objects Process view –models the executables Implementation view –Files, configuration and versions Deployment view –Physical.
BSBPMG507A Apply Communication Management Techniques 10.3 Distribute Information The process of making relevant information available to project stakeholders.
Business Analysis. Business Analysis Concepts Enterprise Analysis ► Identify business opportunities ► Understand the business strategy ► Identify Business.
Assignment Help From Requirements Elicitation to Elicitation.
1 Technical & Business Writing (ENG-715) Muhammad Bilal Bashir UIIT, Rawalpindi.
SWE 513: Software Engineering
Chapter 5 System Modeling. What is System modeling? System modeling is the process of developing abstract models of a system, with each model presenting.
21/1/ Analysis - Model of real-world situation - What ? System Design - Overall architecture (sub-systems) Object Design - Refinement of Design.
Copyright 2007, Information Builders. Slide 1 iWay Web Services and WebFOCUS Consumption Michael Florkowski Information Builders.
Project Communication Management Manage Communications - Inputs Inputs Communications Management Plan Work Performance Reports Enterprise Environmental.
UML (Unified Modeling Language)
 The processes used for RE vary widely depending on the application domain, the people involved and the organisation developing the requirements.  However,
Model Checking Early Requirements Specifications in Tropos Presented by Chin-Yi Tsai.
Business process management (BPM)
UML Diagrams By Daniel Damaris Novarianto S..
The Development Process of Web Applications
What is UML? What is UP? [Arlow and Neustadt, 2005] October 5, 2017
Inputs Outputs Tools and Techniques.
Business process management (BPM)
Systems Analysis and Design in a Changing World, Fifth Edition
UML Diagrams Jung Woo.
Krishnakumar Balasubramanian
Appendix A Object-Oriented Analysis and Design
Mumtaz Ali Rajput +92 – SOFTWARE PROJECTMANAGMENT– WEEK 4 Mumtaz Ali Rajput +92 – 301-
ETVX Process Notation.
ENVRI Reference Model (RM) Information Viewpoint components
CS 420/620 HCI Use Case Modeling Project Preparation
CS 425 Software Engineering
CS 425/625 Software Engineering
Presentation transcript:

Manfred Reichert, Barbara Weber, Victoria Torres Large Process Models and Process Model Collections: - Challenges, Methods, Technologies - Barbara Weber Victoria Torres Manfred Reichert

Presenters Barbara Weber University of Innsbruck Manfred Reichert University of Ulm Victoria Torres Polytechnic University of Valencia

Agenda  Challenges & Basic Notions  Part I: Large Process Models  Part II: Large Process Model Collections  Part III: Large Process Structures  References

4 Large Process Models – An Example!

5

Process Model Process model Node Activity Event Control connector Control edge Data object Atomic activity Complex activity Resource Operation contains connect is a executes contains is a input output contains describes

Process model Node Activity Event Control connector Control edge Data object Atomic activity Complex activity Resource Operation contains connect is a executes contains is a input output contains describes operational organizational informational behavioural structural temporal Process Model

Process model Node Activity Event Control connector Control edge Data object Atomic activity Complex activity Resource Operation contains connect is a executes contains is a input output contains describes operational organizational informational behavioural structural temporal Process Model

Process model Node Activity Event Control connector Control edge Data object Atomic activity Complex activity Resource Operation contains connect is a executes contains is a input output contains describes operational organizational informational behavioural structural temporal Process Model

Process model Node Activity Event Control connector Control edge Data object Atomic activity Complex activity Resource Operation contains connect is a executes contains is a input output contains describes operational organizational informational behavioural structural temporal Process Model

Process model Node Activity Event Control connector Control edge Data object Atomic activity Complex activity Resource Operation contains connect is a executes contains is a input output contains describes informational operational organizational behavioural structural temporal Process Model

informational Process model Node Activity Event Control connector Control edge Data object Atomic activity Complex activity Resource Operation contains connect is a executes contains is a input output contains describes operational organizational behavioural structural temporal Process Model is a

Process Model Collections

 Sets of process models –Sharing goals Collections of process model variants –Targeted at different stakeholders Collections of process model user views –Described at different abstraction levels Collections of process model at different level of detail –Dealing with process model evolution Collections of process model versions –Stored within the same repository Collections of enterprise process models

-- 15 Process Structures

Lifecycle Phases

 Analysis & Design –BP identification and modelling Based on domain requirements BP Modelling notation and languages –Validation & Verification Simulation techniques support Validation »Resulting artefact: BP model »Fostering communication between different stakeholders

Lifecycle Phases  Configuration –Implementation of BP models –Implementation platform has to be chosen –BP model preparation for enactment Interaction with the enterprise eco-system – users & existing systems Tests to check desired behaviour »Resulting artefact: Ready-to-enact BP model

Lifecycle Phases  Enactment –BP instance execution Guaranteeing BP model constraints compliance –Monitoring & Visualizing techniques Allow discovering the status of active BP cases »Resulting artefacts: »Business Process instances »Execution logs

Lifecycle Phases  Diagnosis –Analysis of execution logs Identification of poor quality designs –Fragments that are not used at all Identification of problems regarding execution environment adaptation »Resulting artefact: Process model and configuration changes report

Lifecycle Phases  Evolution –Application of changes to BP models based on New requirements Improvement opportunities »Resulting artefact: BP Model more accurate to the BP and its environment