ICT EMMSAD’05 13/6-2005 1 Assessing Business Process Modeling Languages Using a Generic Quality Framework Anna Gunhild Nysetvold* John Krogstie *, § IDI,

Slides:



Advertisements
Similar presentations
© Telelogic AB Modeling DoDAF Compliant Architectures Operational Systems Technical.
Advertisements

2009 – E. Félix Security DSL Toward model-based security engineering: developing a security analysis DSML Véronique Normand, Edith Félix, Thales Research.
Systems Documentation Techniques
Programming Distributed Systems Lab Institute of Computer Science University of Augsburg Universitätsstraße 14, D Augsburg Tel.: (+49) 821/ ,
Exercise lecture : Exercise 2 and 3 Rune / Yun. Overview Intro to exercise 3 Aspects from exercise 2.
An Integrated Approach to Enterprise Architecture LIACS, Martijn Wiering 23 juni ‘04.
Object-Oriented Analysis and Design
Modeling Process-Oriented Integration of Services Using Patterns and Pattern Primitives Uwe Zdun and Schahram Dustdar Distributed Systems Group Institute.
Reference Architecture for Enterprise Integration CIMOSA GRAI/GIM PERA Dima Nazzal.
Knowledge Acquisitioning. Definition The transfer and transformation of potential problem solving expertise from some knowledge source to a program.
The Data Mining Visual Environment Motivation Major problems with existing DM systems They are based on non-extensible frameworks. They provide a non-uniform.
Introduction to UML Visual modeling Models and its importance
Requirements Analysis Concepts & Principles
Creating Architectural Descriptions. Outline Standardizing architectural descriptions: The IEEE has published, “Recommended Practice for Architectural.
Itntroduction to UML, page 1 Introduction to UML.
Purpose of Requirements Analysis Process of discover, refinement, modeling, and specification o Bridge gap between system level SW allocation and design.
The Software Product Life Cycle. Views of the Software Product Life Cycle  Management  Software engineering  Engineering design  Architectural design.
David Harrison Senior Consultant, Popkin Software 22 April 2004
Course Instructor: Aisha Azeem
Architectural Design Establishing the overall structure of a software system Objectives To introduce architectural design and to discuss its importance.
Visualization By: Simon Luangsisombath. Canonical Visualization  Architectural modeling notations are ways to organize information  Canonical notation.
Basic Concepts The Unified Modeling Language (UML) SYSC System Analysis and Design.
Romaric GUILLERM Hamid DEMMOU LAAS-CNRS Nabil SADOU SUPELEC/IETR.
Chapter 10 Architectural Design
1 An Analytical Evaluation of BPMN Using a Semiotic Quality Framework Terje Wahl & Guttorm Sindre NTNU, Norway Terje Wahl, 14. June 2005.
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.
Chapter 8 Architecture Analysis. 8 – Architecture Analysis 8.1 Analysis Techniques 8.2 Quantitative Analysis  Performance Views  Performance.
ArchiMate Authors : eSchoolink Group - ITNLU. Contents 1. What’s ArchiMate ? 2. Why ArchiMate ? 3. Main Benefits of ArchiMate 4. Layers of ArchiMate 5.
SOFTWARE DESIGN AND ARCHITECTURE LECTURE 21. Review ANALYSIS PHASE (OBJECT ORIENTED DESIGN) Functional Modeling – Use case Diagram Description.
Key Challenges for Modeling Language Creation by Demonstration Hyun Cho, Jeff Gray Department of Computer Science University of Alabama Jules White Bradley.
METACASE. WHAT THIS PRESENTATION IS ABOUT  What’s META MODELING?  What’s METACASE?  METAEDIT+ 5.1 EVALUTION PROGRAM  Diagram and its kinds.
1 Chapter 5 Software Engineering Practice. 2 What is “Practice”? Practice is a broad array of concepts, principles, methods, and tools that you must consider.
SOFTWARE DESIGN.
Effective Requirements Management – an overview Kristian Persson Field Product Manager, Telelogic Asia/Pacific.
Using UML, Patterns, and Java Object-Oriented Software Engineering Chapter 4, Requirements Elicitation.
1 Sobah Abbas Petersen Adjunct Associate Professor TDT4252 Modelling of Information Systems Advanced Course Lecture 6: Process Modelling.
Conceptual Modelling – Behaviour
Illustrations and Answers for TDT4252 exam, June
Information Systems Engineering. Lecture Outline Information Systems Architecture Information System Architecture components Information Engineering Phases.
Software Engineering Prof. Ing. Ivo Vondrak, CSc. Dept. of Computer Science Technical University of Ostrava
UML Use Case Diagramming Guidelines. What is UML? The Unified Modeling Language (UML) is a standard language for specifying, visualizing, constructing,
System Context and Domain Analysis Abbas Rasoolzadegan.
FDT Foil no 1 On Methodology from Domain to System Descriptions by Rolv Bræk NTNU Workshop on Philosophy and Applicablitiy of Formal Languages Geneve 15.
Using Meta-Model-Driven Views to Address Scalability in i* Models Jane You Department of Computer Science University of Toronto.
Unified Modeling Language. Object Oriented Methods ► What are object-oriented (OO) methods?  OO methods provide a set of techniques for analyzing, decomposing,
MODEL-BASED SOFTWARE ARCHITECTURES.  Models of software are used in an increasing number of projects to handle the complexity of application domains.
Architecture View Models A model is a complete, simplified description of a system from a particular perspective or viewpoint. There is no single view.
Parastoo Mohagheghi 1 A Multi-dimensional Framework for Characterizing Domain Specific Languages Øystein Haugen Parastoo Mohagheghi SINTEF, UiO 21 October.
Science and Technology Norwegian University of NTNU Rolv Bræk, January Introduction to Systems Engineering by Rolv Bræk NTNU.
Ivar Jacobson, Grady Booch, and James Rumbaugh The Unified Software Development Process Addison Wesley, : James Rumbaugh's OOMD 1992: Ivar Jacobson's.
1 Model-based Development and Evolution of Information Systems Quality of models and modeling languages John Krogstie Professor, IDI, NTNU UPC,
CSCI 3428: Software Engineering Tami Meredith UML Unified Modeling Language.
 CMMI  REQUIREMENT DEVELOPMENT  SPECIFIC AND GENERIC GOALS  SG1: Develop CUSTOMER Requirement  SG2: Develop Product Requirement  SG3: Analyze.
Be.wi-ol.de User-friendly ontology design Nikolai Dahlem Universität Oldenburg.
 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.
Software Engineering Lecture 10: System Engineering.
From Use Cases to Implementation 1. Structural and Behavioral Aspects of Collaborations  Two aspects of Collaborations Structural – specifies the static.
1 7 Systems Analysis and Design in a Changing World, 2 nd Edition, Satzinger, Jackson, & Burd Chapter 7 The Object-Oriented Approach to Requirements.
Introduction to Software Engineering 1. Software Engineering Failures – Complexity – Change 2. What is Software Engineering? – Using engineering approaches.
From Use Cases to Implementation 1. Mapping Requirements Directly to Design and Code  For many, if not most, of our requirements it is relatively easy.
Course Outcomes of Object Oriented Modeling Design (17630,C604)
SysML v2 Formalism: Requirements & Benefits
Daniel Amyot and Jun Biao Yan
Specifying collaborative decision-making systems
Introduction to UML.
BPMN - Business Process Modeling Notations
Chapter 9 Architectural Design.
TDT4252 Modelling of Information Systems Advanced Course
Software Architecture & Design
Presentation transcript:

ICT EMMSAD’05 13/ Assessing Business Process Modeling Languages Using a Generic Quality Framework Anna Gunhild Nysetvold* John Krogstie *, § IDI, NTNU * and SINTEF § Norway

ICT EMMSAD’05 13/ Overview of presentation Quality of models and modeling languages Objectives of business process models Description of case - Vital Evaluation results Concluding remarks

ICT EMMSAD’05 13/ Framework for quality of models

ICT EMMSAD’05 13/ Quality of modeling languages

ICT EMMSAD’05 13/ Different objectives of business process modeling Human-sense making and communication Computer-assisted analysis/simulation Business Process Management Gives the context for a traditional system development project Model deployment and activation : Through people guided by process 'maps', Automatically, as in most workflow engines. Interactively, where the computer and the users co-operate

ICT EMMSAD’05 13/ Description of case-study environment Vital: One of Norway’s largest insurance companies Large number of life insurance and pension insurance customers Going from a functionally oriented architecture to a process/service oriented architecture Need to support complete business processes in the architecture Main usage area of process models: Context for system development (but human sense-making and communication is also important)

ICT EMMSAD’05 13/ Approach to evaluation Identified main criteria based on Vital experiences and the quality framework approx. 70 requirements derived from the general framework, evaluated according to relevance to Vital 32 requirements found sufficiently relevant to use in the evaluation Identify short-list of languages to evaluate Evaluate languages based on identified criteria Analytically Empirically (based on modeling of cases using the same independent modeling tool (METIS)) Getting feedback from Vital on evaluations as we went along Evaluations on a 0-3 scale on each criteria

ICT EMMSAD’05 13/ Short-list of languages BPMN (Business Process Modeling Notations) UML Activity diagrams EEML (Extended Enterprise Modeling Language)

ICT EMMSAD’05 13/ BPMN - BPD

ICT EMMSAD’05 13/ UML Activity diagrams

ICT EMMSAD’05 13/ EEML

ICT EMMSAD’05 13/ Overall results No.Requirement descriptionUML ADBPMNEEML 1.1 The language should support the following concepts (a) processes, that must be possible to decompose (b) activities (c) actors/roles (d) decision points (e) flow between activities, tasks and decision points The language should support (a) system resources (b) states Basic control patterns Advanced branching and synchronization patterns00,53 1.5Structural patterns01,5 1.6Patterns involving multiple instances1, State based flow patterns Cancellation patterns Extension mechanisms to fit the domain Elements in the process model must be possible to link to a data/information model Hierarchical models333 22,520,527,5

ICT EMMSAD’05 13/ The language must be easy to learn, preferably being based on a language already being used in the organization Appropriate level of abstraction Concepts should be named similarly as it is in the domain Intuitive representation to the stakeholders Good guidelines for the use of the language Easy diff. between different concepts Number of concepts should be reasonable The language should be flexible in precision Easy to differentiate between the different symbols in the language The language must be consistent One should strive for graphical simplicity Grouping of related statements The language should have a formal syntax Formal semantics Generate BPEL –documents from the model Represent web-services in the model Automatic execution and testing The language must be supported by available tools Traceability between the process model and any automated process support system Models that can improvement the quality of the process The language should support the development of models that help in the follow-up of separate cases 112 Sum63,572,563,5 Sum without technical actor appropriateness55.557,555,5 Sum without participant language knowledge appropriateness53,559,553,5

ICT EMMSAD’05 13/ Concluding remarks The framework found useful after specializing it to specific goals of the organization Overly simplistic valuation ? Weighting of importance (base more on metrics for e.g. complexity) Weighting between expressiveness, learnability, comprehension, technical and organizational appropriateness On later uses use several valuation schemes in parallel Also include evaluation of the meta-model and notation guides as models Useful to first focus on the language, but language quality is only a mean to achieve model quality. Through including organizational appropriateness, tool-support and appropriate techniques to support the development of high-quality models on all levels is partly included also at this level

ICT EMMSAD’05 13/ Assessing Business Process Modeling Languages Using a Generic Quality Framework Anna Gunhild Nysetvold* John Krogstie *, § IDI, NTNU * and SINTEF § Norway