IS 788 4.21 Alternative process modeling methods and notations  The notation used in the 788 textbook (Harmon) – BPMN – is rapidly becoming a standard.

Slides:



Advertisements
Similar presentations
Gender Audit. Traditional use of audit relates to accounting: Analysis of gender budget Gender audit still evolving… -now used interchangeably with evaluation.
Advertisements

What is an M and E Plan?. Organizing the Work of M and E An M and E System -- the 12 components as a whole – Sets out broad vision at national level An.
Alternative Assesment There is no single definition of ‘alternative assessment’ in the relevant literature. For some educators, alternative assessment.
Chapter Fourteen Organization Culture.
Strategic Control Chapter 13
Supporting people with a learning disability Introduction to Project Management Presenter: Steve Raw FInstLM, FCMI.
IS After the strategy, the real work ;-)  After determining organizational value chains, after modeling the organizational architecture, after.
IMS1805 Systems Analysis Topic 3 (revisited and continued): Doing analysis – a ‘soft’ systems perspective.
Unit Five – Transforming Organizations
1 14. Project closure n An information system project must be administratively closed once its product is successfully delivered to the customer. n A failed.
Creating Architectural Descriptions. Outline Standardizing architectural descriptions: The IEEE has published, “Recommended Practice for Architectural.
Chapter 6 Functional Modeling
PPA 503 – The Public Policy Making Process
IS IS 788 [Process] Change Management  Wednesday, September 9  Pacific Bell Case – Ricky Medina  Lecture: Modeling Organizations (2 of 2)
System Engineering Instructor: Dr. Jerry Gao. System Engineering Jerry Gao, Ph.D. Jan System Engineering Hierarchy - System Modeling - Information.
The database development process
Foundations This chapter lays down the fundamental ideas and choices on which our approach is based. First, it identifies the needs of architects in the.
Certified Business Process Professional (CBPP®)
Certified Business Process Professional (CBPP®) Exam Overview
socio-organizational issues and stakeholder requirements
RWJF Common Ground-Using Work Flow Mapping Tools to Improve Chronic Disease Management Processes Adapted from presentations by: Minnesota Department of.
At the end of this module, participants should have a better understanding of the following : Elements of Gender Mainstreaming Basics of Gender Analysis.
GTM for Product Leaders Project Overview A project that guides product leaders and their teams in developing a successful go-to-market strategy.
Integration of Regulatory Impact Assessment into the decision making process in the Czech Republic Aleš Pecka Department of Regulatory Reform and Public.
SYSTEMS ANALYSIS. Chapter Five Systems Analysis Define systems analysis Describe the preliminary investigation, problem analysis, requirements analysis,
Basic Concepts The Unified Modeling Language (UML) SYSC System Analysis and Design.
Foundation in Business Analysis
Chapter 5 – System Modeling
Investment Portfolio Methodologies Pertemuan Matakuliah: A Strategi Investasi IT Tahun: 2009.
BPMN By Hosein Bitaraf Software Engineering. Business Process Model and Notation (BPMN) is a graphical representation for specifying business processes.
Module 4: Systems Development Chapter 13: Investigation and Analysis.
Copyright © 2014 by The University of Kansas Using the Evaluation System to Answer Key Questions About Your Initiative.
CB1004 Modelling Business Systems 71 Modelling Business Systems 7 Systems Methods.
ArchiMate Authors : eSchoolink Group - ITNLU. Contents 1. What’s ArchiMate ? 2. Why ArchiMate ? 3. Main Benefits of ArchiMate 4. Layers of ArchiMate 5.
1 Pathways to a World-Class Competitive Intelligence Function John E. Prescott, Ph.D Alessandro Comai, Ph.D candidate (ESADE Business.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 7 Slide 1 Requirements Engineering Processes.
Requirements Engineering Requirements Elicitation Process Lecture-8.
Module 4: Systems Development Chapter 12: (IS) Project Management.
© 2011 Underwriters Laboratories Inc. All rights reserved. This document may not be reproduced or distributed without authorization. ASSET Safety Management.
BUSINESS PROCESS REENGINEERING & ERP
Management & Development of Complex Projects Course Code MS Project Management Perform Qualitative Risk Analysis Lecture # 25.
The Development of BPR Pertemuan 6 Matakuliah: M0734-Business Process Reenginering Tahun: 2010.
1 Software Development Software Engineering is the study of the techniques and theory that support the development of high-quality software The focus is.
Chapter 15 Introduction to Systems Development. Learning Objectives Learn how information systems are developed Understand importance of managing SD process.
® IBM Software Group © 2006 IBM Corporation Writing Good Use Cases Module 1: Introduction to Use-Case Modeling.
1 Chapter 4 Analyzing End-to-End Business Processes.
Object-Oriented Software Engineering using Java, Patterns &UML. Presented by: E.S. Mbokane Department of System Development Faculty of ICT Tshwane University.
Project quality management. Introduction Project quality management includes the process required to ensure that the project satisfies the needs for which.
Begin at the Beginning introduction to evaluation Begin at the Beginning introduction to evaluation.
SYSTEMS DEVELOPMENT IN PERSPECTIVE
Software Architecture Evaluation Methodologies Presented By: Anthony Register.
Source : The Problem Learning and innovation skills increasingly are being recognized as the skills that separate students who are.
Copyright © 2014 by The University of Kansas Using the Evaluation System to Answer Key Questions About Your Initiative.
CSI—The Lifecycle Stage
Winter 2011SEG Chapter 11 Chapter 1 (Part 1) Review from previous courses Subject 1: The Software Development Process.
Copyright © 2014 McGraw-Hill Education. All rights reserved. No reproduction or distribution without the prior written consent of McGraw-Hill Education.
IT-465 Introduction to Lean part Two. IT-465 Lean Manufacturing2 Introduction Waste Walks and Spaghetti Charts Outcomes Understand what a waste walk is.
Concepts/ definitions/ meanings of program plan, program scheme, program development, concept paper Program plan is a systematic arrangement of elements.
Defining and Managing Project Scope. MOV Scope Phases Time Estimates Resources Tasks Schedule Budget Sequence Project Planning Framework.
Information Technology Project Management – Fourth Edition By Jack T. Marchewka Northern Illinois University Power Point Slides by Gerald DeHondt Grand.
Demand Response Use Case & Functional Requirements Development UCAIug Meeting Jan 6, 2009 Mark van den Broek.
MIS Project Management Instructor: Sihem Smida Project Man agent 3Future Managers1.
 The processes used for RE vary widely depending on the application domain, the people involved and the organisation developing the requirements.  However,
Managing Enterprise Architecture
© 2007 by Prentice Hall Management Information Systems, 10/e Raymond McLeod and George Schell 1 Management Information Systems, 10/e Raymond McLeod and.
Sample Fit-Gap Kick-off
Chapter 5 System modeling
Information Technology Project Management – Fourth Edition
Schools of Excellence Recognition Program For Century Learning
MODELLING BUSINESS PROCESSES
Presentation transcript:

IS Alternative process modeling methods and notations  The notation used in the 788 textbook (Harmon) – BPMN – is rapidly becoming a standard – in the US  The methodology presented in Harmon is well regarded.  However: Every BPM consultant and tool vendor has their own methodology Many tool vendors still use proprietary notation Different standards exist outside the US

IS Alternative notations  Northern Europeans, including Germany, have a fondness for UML  The most highly developed alternative notation to BPMN and – arguably – the most refined methodology for process analysis– is SPRINT from the UK

IS SPRINT  Was developed in the UK as a local initiative for government process improvement  It has since been widely adopted throughout the UK and is illustrated in a number of published studies  SPRINT is valuable as an integrated technique  AND – it illustrates some of the differences between European (and sometimes Japanese) and US approaches to process change

IS Socio-technical (‘soft’) approaches to system analysis and design  Originated in Europe (Enid Mumford in the UK in the 1970’s)  Views the organization as an organism rather than a machine  Includes as constraints on a system or process design humans and their social systems: Organizational culture Political and psychological needs

IS SPRINT combines ‘hard’ and ‘soft’ models  “Hard” techniques typically address “objective” (usually physical) aspects of the system: objects, events, physical flows  “Soft” techniques analyze and document context = ‘why’ as well as ‘what’  In addition to social and political issues, soft concerns (soft goals) include Product quality and QOS issues Broad organizational goals (how are these addressed in Harmon’s methodology) (discuss MBTI, self selection and ‘ST’ biases)

IS SPRINT overall method  Phase 1: Understand Process Context Who’s doing this and why – what are their perspectives (SSM) Goal Analysis Informal observation of AS-IS processes Formal AS-IS process modeling Benchmarking (as an integral part of the method!)

IS Phase 2  [Radical] Process Redesign Develop business vision in terms of key goals Re-think process Develop re-engineering proposals based on vision Articulate measurable business benefits

IS Phase 3  Implement Proposals Specify new process designs and relevant ICT in detail Devise change management strategy Implement new structures and ICT Evaluate and continuously improve

IS Draws from SSM  SPRINT is heavily influenced by Checkland’s Soft Systems Methodology  Part of the SPRINT toolkit for understanding process context is the notion of ‘rich pictures’  A rich picture is an informal notation for defining “soft” information – including participant attitudes - about the processes  Discuss handout:

IS Context, context and more context  From SPRINT Phase 1: two steps almost certainly missing from a US process assessment  Identify stakeholders and process settings Where does the process take place? What impact does the setting have? Don’t assume its ideal, fixed or doesn’t have an impact

IS Also from SPRINT, Phase 1  Identify stakeholder perspectives  What does this mean? How the stakeholder thinks about his or her part in the process and the process overall. This may be very different from other stakeholders  Why is it significant? It reveals commonalities to be leveraged and differences to be bridged: goal misalignment - cultural, economic, power, informational, etc.

IS SPRINT Notation: Role Activity Diagrams (RAD)  On a reasonably close reading, RAD notation and BPMN are nearly “informationally equivalent”  Any process can be described in either notation  Minor differences first (besides iconography) RAD explicitly includes cardinality

IS RAD explicitly includes triggers  Arrow indicates trigger condition – must occur before process can proceed

IS The major difference between SPRINT and BPMN is?  Department focus vs. role focus  What difference does this make i.e. are some processes best described in one or the other? (Hint – in what environment did each originate?)  In all likelihood governmental/bureaucratic processes are best modeled in SPRINT  However, the focus on soft information is invaluable in any modeling effort.