© Minder Chen, 1995 - IDEF 85 - Methods and Tools for BPR An Integrated Framework for Methods and Tools for BPR Process Modeling Methods and Tools –IDEF0.

Slides:



Advertisements
Similar presentations
Chapter 11 Describing Process Specifications and Structured Decisions
Advertisements

1 FUNCTION MODELING USING IDEF-0 IE 590 INTEGRATED MANUFACTURING SYSTEMS Lecture 7.
S Y S T E M S E N G I N E E R I N G.
Business Process Reengineering:
Describing Process Specifications and Structured Decisions Systems Analysis and Design, 7e Kendall & Kendall 9 © 2008 Pearson Prentice Hall.
Software Design Process A Process is a set of related and (sequenced) tasks that transforms a set of input to a set of output. Inputs Outputs Design Process.
Accounting Information Systems 9th Edition
Chapter 6: Documenting Accounting Information Systems
MIS 325 PSCJ. 2  Business processes can be quite complex  Process model: any abstract representation of a process  Process-modeling tools provide a.
©2003 Prentice Hall Business Publishing, Accounting Information Systems, 9/e, Romney/Steinbart 6-1 Systems Development and Documentation Techniques.
ITIL: Service Transition
Chapter 4.
Systems Analysis and Design 9th Edition
1.  Integrated Computer-Aided Manufacturing (ICAM) Definition Languages  Comprehensive, formal syntax for describing a process  Better analysis and.
Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall Process Specifications and Structured Decisions Systems Analysis and Design, 8e Kendall.
Chapter 9 Describing Process Specifications and Structured Decisions
Chapter 9 Describing Process Specifications and Structured Decisions Systems Analysis and Design Kendall & Kendall Sixth Edition © 2005 Pearson Prentice.
Chapter 9 Describing Process Specifications and Structured Decisions
INDUSTRIAL & SYSTEMS ENGINEERING
1 Process Mapping BA 339 Mellie Pullman. 2 Objectives Service Process Differences Little’s Law Process Analysis & Mapping.
Kendall & KendallCopyright © 2014 Pearson Education, Inc. Publishing as Prentice Hall 9 Kendall & Kendall Systems Analysis and Design, 9e Process Specifications.
Chapter 9 Using Data Flow Diagrams
Advanced Accounting Information Systems
Introduction to SAP R/3.
Chapter 6, Process-Flow Analysis
Copyright © 2015 Pearson Education, Inc. Systems Documentation Techniques Chapter
Examine Quality Assurance/Quality Control Documentation
Systems Documentation Techniques
[ §4 : 1 ] 4. Requirements Processes II Overview 4.1Fundamentals 4.2Elicitation 4.3Specification 4.4Verification 4.5Validation Software Requirements Specification.
Process Modeling SYSTEMS ANALYSIS AND DESIGN, 6 TH EDITION DENNIS, WIXOM, AND ROTH © 2015 JOHN WILEY & SONS. ALL RIGHTS RESERVED. 1 Roberta M. Roth.
Introduction to Systems Analysis and Design Trisha Cummings.
Systems Analysis and Design: The Big Picture
Data Flow Diagrams (DFDs)
- 1 - © Minder Chen, Methods and Tools for BPR An Integrated Framework for Methods and Tools for BPR Process Modeling Methods and Tools –IDEF0:
Bina Nusantara 2 C H A P T E R INFORMATION SYSTEM BUILDING BLOCKS.
Data and Process Modeling
Systems Analysis – Analyzing Requirements.  Analyzing requirement stage identifies user information needs and new systems requirements  IS dev team.
Accounting systems design & evaluation 9434SB 12 April 2002.
Chapter 9 Describing Process Specifications and Structured Decisions
Chapter 7 Structuring System Process Requirements
Introduction to Transaction Processing and Documentation Techniques COPYRIGHT © 2007 Thomson South-Western, a part of The Thomson Corporation. Thomson,
Describing Process Specifications and Structured Decisions Systems Analysis and Design, 7e Kendall & Kendall 9 © 2008 Pearson Prentice Hall.
1-1 System Development Process System development process – a set of activities, methods, best practices, deliverables, and automated tools that stakeholders.
IDEF0 Modelling techniques
Chapter 8 Transaction Processing, Electronic Commerce, and Enterprise Resource Planning Systems.
1 DATA FLOW DIAGRAM. 2 Outline Process decomposition diagrams Data flow diagram (DFD)
Project quality management. Introduction Project quality management includes the process required to ensure that the project satisfies the needs for which.
Advanced Accounting Information Systems
Foundations of Information Systems in Business. System ® System  A system is an interrelated set of business procedures used within one business unit.
Project Management Project Integration Management Minder Chen, Ph.D. CSU Channel Islands
Enterprise Systems Modeling EGN 5623 Enterprise Systems Optimization Fall, 2012.
Chapter 7 Part II Structuring System Process Requirements MIS 215 System Analysis and Design.
Copyright © 2011 Pearson Education Process Specifications and Structured Decisions Systems Analysis and Design, 8e Kendall & Kendall Global Edition 9.
Systems Analysis and Design in a Changing World, Fourth Edition
Systems Development and Documentation Techniques BAB 3 PERTEMUAN SIA-UMBY.
Introduction for the Implementation of Software Configuration Management I thought I knew it all !
ITIL: Service Transition
Your own footer Your Logo.
The Components of Information Systems
Tools Of Structured Analysis
Information systems modeling tools
Process-Flow Analysis
Introduction to Transaction Processing
Process & Logic Modeling
The Components of Information Systems
Chapter 11 Describing Process Specifications and Structured Decisions
Chapter 4: documenting information systems
Information System Building Blocks
Information systems modeling tools
Presentation transcript:

© Minder Chen, IDEF 85 - Methods and Tools for BPR An Integrated Framework for Methods and Tools for BPR Process Modeling Methods and Tools –IDEF0 –Functional Flowchart Data Modeling Methods and Tools –IDEF1x Supporting Technologies for BPR Activities –Groupware –Process Simulation –Organization Modeling Tools

© Minder Chen, IDEF 86 - A Framework of Integrating Methods & Tools for BPR Elicit semi-formal process and data models Construct/ revise static business process models Analyze the dynamics of the process Analyze the activity costs of the process information of a process semi-formal process model cost and performance data compared to the baseline performance data activity cost data Target information system generated finalized process model GDSS (GroupSystems V) ABC Tool (IDEFCost, Easy ABC) Simulation Tool (SIMROCESS) CASE Tool (IEF) Construct/ revise business data models Data Modeling Tools (ERwin, BDF) Construct formal IS models & generate information systems semi-formal data model Process Modeling Tools (IDEFine, BDF)

© Minder Chen, IDEF 87 - IDEF Notations Function Inputs Outputs Controls Mechanism Legends Process Order Customer order Processed order Order processing policy Order processing system Order processing clerks Work schedule

© Minder Chen, IDEF 88 - Process Modeling for BPR Process 1. Entry Conditions 2. Exit Conditions 3. Decomposition Inputs:  Materials & Information Suppliers Requirements Outputs:  Materials & Information Customers Satisfiers Controls Specifications Schedules Mechanism Resources Infrastructures Costs

© Minder Chen, IDEF 89 - ICOM in IDEF The ICOM of a function represents certain system principles: Inputs are transformed into outputs, controls constrain or dictate under what conditions transformations occur, and mechanisms describe how the function is accomplished. "Inputs are transformed by the function into outputs according to controls, using mechanisms." An IDEF box and its ICOM can be described as: I C O M

© Minder Chen, IDEF 90 - Definition of ICOM Input: Describe resources or data that are needed to perform the function and are transformed by the function into outputs. Control: Describe the conditions, rules, procedures, or circumstances that govern the execution of the function. An arrow is a control unless it obviously serves only as input. Each function should have at least one control arrow. Most of controls are in the form of data. Output: The data or objects produced when the function is performed. Mechanism: Define the supporting mechanisms that carry out the function. A mechanism may be a person, an organizational unit, a physical device, or a computer program.

© Minder Chen, IDEF 91 - An Example of an IDEF Diagram NODE:TITLE:NUMBER: AØFMaintain Repairable Spares (FEO) pg. 4-5 Asset (after repair) Remove & Replace 1 Schedule into Shop 2 Inspect or Repair 3 Monitor & Route 4 In-service asset Detected or suspected malfunction, or Item is scheduled for bench-check Replaced asset Man-hour standards and personnel availability Spare asset Asset (before repair) Repairable asset Assets awaiting parts Replacement or original (repaired) Status records Completed asset Spare or NRTS Source: Integrated Computer-Aided Manufacturing (ICAM): Functional Modeling Manual (IDEF0), June 1981, p. 4-5.

© Minder Chen, IDEF 92 - IDEF0 as a Constraint Diagram (Function B is constrained by one input and two controls, and produces a single output, which constrains Function C). FUNCTION A B C

© Minder Chen, IDEF 93 - IDEF0 Model Structure A0 A4 A-0 A GENERAL DETAILED The diagram A0 is the "parent" of the diagram A4. I1 I2 C1 O1 Abstraction Refinement I1 I2 O1 C1

© Minder Chen, IDEF 94 - Node Tree Manufacture Product A1 Plan for Manufacture A11 Assume a Structure and Method of Manufacturing A12 Estimate Requirements, Cost, Time to Produce A13 Develop Production Plans A14 Develop Support Activities Plan

© Minder Chen, IDEF 95 - Node Index A0 Manufacture Product A1Plan for Manufacture A11Assume a Structure and Method of Manufacture A12Estimate Requirements, Cost, Time to Produce A13Develop Production Plans A14Develop Support Activities Plan A

© Minder Chen, IDEF 96 - Attributes of Processes Basic –Name –Description –Author –Audit trails Performance data –Importance: Core, Critical –Value Added: Business, Customer, None –Cycle time: Mean, Variance, and Distribution –Cost/Unit

© Minder Chen, IDEF 97 - ICOM Balancing: The Match Must Be Complete and Consistent Parent Diagram Detail Diagram 1 Parent Box This arrow is a control from the parent This arrow continue on the parent This arrow is an input from the parent

© Minder Chen, IDEF 98 - ICOM Codes Are Written on the Detail Diagram This is C2 below This is C1 below This is C3 below This is I1 below This is I2 below Box of Parent to be Detailed This is O1 below This is O2 below C1 C2 1 2 I1 I2 C3 O1 O2 ICOM code must be written at the unconnected ends of all boundary arrows except for A-0 diagram and on tunneled arrows. 3

© Minder Chen, IDEF 99 - Tunneled Arrows Tunneling an arrow at the unconnected end indicates that the data conveyed is not relevant to or supplied by the parent diagram. Tunneled Arrows at Unconnected Ends Tunneled Arrows at Connected Ends ( ) Tunneling an arrow where it connects to a box indicates that the data conveyed is not necessary at the next level of decomposition. ( )

© Minder Chen, IDEF Tunneled Arrows and ICOM Codes A0PARENT DIAGRAM A2DETAIL DIAGRAM corporate policy Control will not be shown on detail diagram This arrow is still labeled as C3 status report to controller's office Output not shown on parent diagram ( ) I1 C1 C3 O1

© Minder Chen, IDEF Process Evaluation Eliminate Simplify Combine Parallelize Automate Create value-adding processes

© Minder Chen, IDEF Inputs Evaluation Type: Data, Material Performance: –Quality –Cost/Unit: include cost of processing purchase order, shipping cost, cost of the inputs, and inventory cost. –Delivery timeliness –Volume: Average and peak Reduce the cost of inputs. Alternative sources of inputs. Ensure timeliness of inputs delivery.

© Minder Chen, IDEF Controls Evaluation Reduce unnecessary controls Embed controls as part of the process Let the workers who perform the process conduct the checking. Improve the procedures and guidelines of the process. Empower workers to learn and think and give them authority to make decision to make changes and improvements

© Minder Chen, IDEF Mechanism Evaluation Who should perform the process? Are tools used for performing the process adequate? What are emerging and matured techniques, tools, and information technologies that may help the improvement of process productivity or effectiveness? What is the cost of the resources in employing the mechanism? Are there alternatives? Are there adequate training programs for employees in using tools and methods?

© Minder Chen, IDEF Standard Flowchart Symbols Activity Movement/ Transportation Decision Point Paper document Delay Storage Connector Begin/End Annotation Direction of process flow Transmission

© Minder Chen, IDEF Functional Flowchart (Process Mapping) Customer Service Credit Checking Inventory Shipping Begin Enter Order Check Credit OK Order Processing Update Inventory Ship order End PROCESSPROCESS  CYCLECYCLE  ACTIVITYACTIVITY