For Goal-Driven Business Process Modeling Saeed A.Behnam,  Daniel Amyot, Gunter Mussbacher SITE, University of.

Slides:



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

International Telecommunication Union © ITU-T Study Group 17 Integrated Application of URN Daniel Amyot University of Ottawa, Canada
Based on Powerpoint slides by Gunter Mussbacher, Gregor v. Bochmann User Requirements Notation (URN) SEG3101 (Fall 2010)
UML Profile for Goal-oriented Modelling Muhammad Rizwan Abid Supervising Professors: Daniel Amyot Stéphane Sotèg Somé.
Requirements Engineering n Elicit requirements from customer  Information and control needs, product function and behavior, overall product performance,
Realizing OPM Philosophy in the Context of Full Life- Cycle Support Avi Soffer Technion, Israel Institute of Technology Thesis Advisor: Prof. Dov Dori.
Requirements Analysis Concepts & Principles
Analysis Concepts and Principles
Creating Architectural Descriptions. Outline Standardizing architectural descriptions: The IEEE has published, “Recommended Practice for Architectural.
® Problem Solving for Root Cause Analysis An overview for CLARION Case Competition 2009 Presented by: Sandra Potthoff, Ph.D. Director of Program in Healthcare.
Institute for Software Research©2001, University of California, Irvine Product-Line Architectures André van der Hoek Institute for Software Research University.
Course Instructor: Aisha Azeem
project management office(PMO)
Company LOGO Business Process Monitoring and Alignment An Approach Based on the User Requirements Notation and Business Intelligence Tools Pengfei Chen.
Developing Enterprise Architecture
Romaric GUILLERM Hamid DEMMOU LAAS-CNRS Nabil SADOU SUPELEC/IETR.
Software Engineering Muhammad Fahad Khan
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 18 Slide 1 Software Reuse.
Engineering, Operations & Technology | Information TechnologyAPEX | 1 Copyright © 2009 Boeing. All rights reserved. Architecture Concept UG D- DOC UG D-
Requirements Analysis
Advanced Topics in Requirement Engineering. Requirements Elicitation Elicit means to gather, acquire, extract, and obtain, etc. Requirements elicitation.
TOWARDS ADVANCED GOAL MODEL ANALYSIS WITH JUCMNAV Daniel Amyot, Azalia Shamsaei, Jason Kealey, Etienne Tremblay, Andrew Miga, Gunter Mussbacher, and Mohammad.
Demystifying the Business Analysis Body of Knowledge Central Iowa IIBA Chapter December 7, 2005.
Business Analysis and Essential Competencies
1 Process Engineering A Systems Approach to Process Improvement Jeffrey L. Dutton Jacobs Sverdrup Advanced Systems Group Engineering Performance Improvement.
1 GRL Tools JUCMNav vs. OpenOME CSI5112 – Project Winter 2008 Bo Peng, Li Chen, Yessine Daadaa.
Requirements Elicitation. Who are the stakeholders in determining system requirements, and how does their viewpoint influence the process? How are non-technical.
Jan 20-21, 2005Weiss and Amyot, MCETECH 051 Designing and Evolving Business Models with the User Requirements Notation Michael Weiss (Carleton University)
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 18 Slide 1 Software Reuse.
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.
S CHOOL OF I NFORMATION T ECHNOLOGY AND E NGINEERING U NIVERSITY OF O TTAWA, C ANADA Daniel Amyot Q18/17 (URN) Rapporteur User Requirements.
Using UML, Patterns, and Java Object-Oriented Software Engineering Chapter 4, Requirements Elicitation.
Chapter 11 Analysis Concepts and Principles
Design engineering Vilnius The goal of design engineering is to produce a model that exhibits: firmness – a program should not have bugs that inhibit.
Abstract Use Case Map (UCM) scenarios are useful for elicitation and analysis of software requirements However, they must be used in cooperation with complementary.
IHE-Europe – Use Case Based Approach to eHealth Interoperability Peter Künecke, SIEMENS Medical Solutions IHE-Europe „vendor“ co-chair Integrating the.
Requirements Engineering Requirements Elicitation Process Lecture-6.
A Lightweight GRL Profile for i* Modeling Presenter: Alexei Lapouchnian Daniel Amyot, Jennifer Horkoff, Daniel Gross, and Gunter Mussbacher {damyot,
Supporting Scenario-Based Requirements Engineering IEEE TRANSACTIONS ON SOFTWARE ENGINEERING, VOL. 24, NO. 12, DECEMBER, 1998 A. G. Sutcliffe, N. A. M.
Object-Oriented Software Engineering using Java, Patterns &UML. Presented by: E.S. Mbokane Department of System Development Faculty of ICT Tshwane University.
Welcome Science 5 and Science 6 Implementation Workshop.
1 Software Engineering: A Practitioner’s Approach, 6/e Chapter 5 Practice: A Generic View Software Engineering: A Practitioner’s Approach, 6/e Chapter.
Chapter 4 Requirements Engineering (3/3) Yonsei University 2 nd Semester, 2015 Sanghyun Park.
Software Architecture Evaluation Methodologies Presented By: Anthony Register.
27/3/2008 1/16 A FRAMEWORK FOR REQUIREMENTS ENGINEERING PROCESS DEVELOPMENT (FRERE) Dr. Li Jiang School of Computer Science The.
Gregor v. Bochmann, University of Ottawa Based on Powerpoint slides by Gunter Mussbacher(2009) with material from Amyot User Requirements Notation (URN)
Design Reuse Earlier we have covered the re-usable Architectural Styles as design patterns for High-Level Design. At mid-level and low-level, design patterns.
(c) Adaptive Processes Consulting Be with the Best!
Rational Unified Process (RUP)
S CHOOL OF I NFORMATION T ECHNOLOGY AND E NGINEERING U NIVERSITY OF O TTAWA, C ANADA Daniel Amyot Q18/17 (URN) Rapporteur User Requirements.
Adding Hypermedia Requirement to Goal-Driven Analysis Presented by Chin-Yi Tsai.
21/1/ Analysis - Model of real-world situation - What ? System Design - Overall architecture (sub-systems) Object Design - Refinement of Design.
Requirement Engineering with URN: Integrating Goals and Scenarios Jean-François Roy Thesis Defense February 16, 2007.
Lectures 2 & 3: Software Process Models Neelam Gupta.
A framework that describes the activities performed at each stage of a software development project. A life-cycle or a software process is the organisational.
1 Towards Integrated Tool Support for the User Requirements Notation Jean-François Roy
Introduction to Software Engineering 1. Software Engineering Failures – Complexity – Change 2. What is Software Engineering? – Using engineering approaches.
A focus group is actually gathering of people who are customers or users representatives for a product to gain its feedback. The feedback can be collected.
Design Engineering 1. Analysis  Design 2 Characteristics of good design 3 The design must implement all of the explicit requirements contained in the.
1 The XMSF Profile Overlay to the FEDEP Dr. Katherine L. Morse, SAIC Mr. Robert Lutz, JHU APL
Object-Oriented Software Engineering Using UML, Patterns, and Java,
Daniel Amyot and Jun Biao Yan
SOFTWARE ARCHITECTURE AND DESIGN
Cloud Modeling Framework CloudMF
Provider and Member Education in Managed Care Pharmacy
Object oriented analysis and design
Engineering design is the process of devising a system, component, or process to meet desired needs. It is a decision-making process in which the basic.
Chapter 8, Design Patterns Introduction
Sepsis Program Development
Going from local to generalizable: The role of implementation science to improve learning from QI Lisa Hirschhorn, MD MPH Professor Medical Social Sciences.
Presentation transcript:

for Goal-Driven Business Process Modeling Saeed A.Behnam,  Daniel Amyot, Gunter Mussbacher SITE, University of Ottawa 1

Motivation There is a gap between business goals and business processes Difficulties in modeling requirements in the form of goal models Difficulties in creating business processes that realize the goals 2

Objectives Facilitate creating business goal models with business process models that realize them Reuse recurring solutions for recurring problems in the domain 3

Proposed Solution Patterns that capture the knowledge of domain A framework that includes a collection of patterns for a particular domain User Requirements Notation (URN) is a standard language for elicitation, analysis, specification and validation of requirements using a combination of goal-oriented and scenario-based modeling 4

User Requirements Notation (URN) 5 Goal-oriented Requirement Language (GRL) enables: Modeling of stakeholders, goals, requirements, alternatives and rationales Understanding the problems that ought to be solved Use Case Map (UCM) enables: Modeling of causal scenarios Organizing complex models in hierarchical structures

Patient Safety Domain Adverse events are undesirable patient outcomes caused by medical care rather than the underlying disease Focusing on hospital patients, Canadian studies estimate that one in twelve patients experiences an adverse event 9250 to deaths from adverse events in 2000 could have been prevented in Canada 6

Components of Pattern-Based Framework Processes Framework Establishment Process Customization and Extraction Process Structure Framework Metamodel: A URN profile 7

Establishing Framework – Steps 8 Observe and analyze goals that define the problem Create Goal Templates that capture recurring excerpts of goal graphs Observe and analyze process models that realize goals Identify a set of strategies to address the problem Create Business Process Templates that capture the behavioral and structural details of strategies Create Patterns, each composed of a Goal Template and corresponding Business Process Templates

Establishing a Framework 9 Collect Data Increase Quality of Care in Long Term «external» Decrease Costs «external» Deploy Advanced Infrastructure «external» Goal Template Increase Patient Safety «main» Generate Informative Outcome Information Make Safety Decision Adopt Decision Increase Quality of Care in Long Term «external» Decrease Costs «external» Deploy Advanced Infrastructure «external» Goal Template Increase Patient Safety «main» Generate Informative Outcome Information Collect Data Make Safety Decision Adopt Decision A A B B B B Making Safety Decision Adopting Decision Business Process Template Collecting Data Generating Informative Outcome Information Business Process Template Collecting Data Generating Informative Outcome Information A B Increase Quality of Care in Long Term «external» Decrease Costs «external» Deploy Advanced Infrastructure «external» Increase Patient Safety «main» A A AB B B B B

Establishing Framework-cont 10 Business Process Template Increase Quality of Care in Long Term «external» Goal Template Collect Data «main» Collect Outcome Data Collecting Outcome Data Business Process Template C C E E D E Collect Process Data Collecting Process Data Business Process Template D Collecting Outcome Data Collecting Process Data Increase Quality of Care in Long Term «external» Collect Data «main» C C D DEE E

Customization and Extraction 11 After a framework is established it can be used by organizations within the domain in order to: Create goal models and business process models Take advantage of available knowledge in the framework

12 Customization and Extraction Organizational Goal Model Healthcare Institute A Increase Patient Safety (100) Increase Quality of Care (100) Decrease Costs (25) Support Research on Adverse Events (20) Implement Advanced Infrastructure -75 Making Safety Decision Adopting Decision Business Process Template Collecting Data Generating Informative Outcome Information Deploy Advanced Infrastructure «external» Goal Template Generate Informative Outcome Information Collect Data Make Safety Decision Adopt Decision Increase Quality of Care in Long Term «external» Decrease Costs «external» Increase Patient Safety «main» Collecting Data Generating Informative Outcome Information Business Process Template Deploy Advanced Infrastructure «external» Goal Template Generate Informative Outcome Information Collect Data Make Safety Decision Adopt Decision Increase Quality of Care in Long Term «external» Decrease Costs «external» Increase Patient Safety «main» * Organizational Goal Model Healthcare Institute A Increase Patient Safety (100) Increase Quality of Care (100) Decrease Costs (25) Support Research on Adverse Events (20) Implement Advanced Infrastructure * * Deploy Advanced Infrastructure «external» Goal Template Generate Informative Outcome Information Collect Data Make Safety Decision Adopt Decision Increase Quality of Care in Long Term «external» Decrease Costs «external» Increase Patient Safety «main» * Organizational Goal Model Healthcare Institute A Increase Patient Safety (100) Increase Quality of Care (100) Decrease Costs (25) Support Research on Adverse Events (20) Implement Advanced Infrastructure * * Increase Patient Safety «realization link» AB

Framework Metamodel 13 The Framework Metamodel lays down the structure for frameworks The concepts in the framework are formalized with a URN profile URN already includes all necessary concepts for the suggested framework

Framework Metamodel 14

Conclusion 15 The framework proposes a solution to address the mentioned gap between goals and business processes by: Capturing the knowledge in the domain Designing business processes that better satisfy the goals and requirements of stakeholders Increasing the reusability of recurring solutions Taking advantage of the URN language, its notations and its tool support

Future Work 16 Using more processes from different hospitals will improve the framework Evolution mechanisms will improve the framework when changes happen in the domain

Questions 17