Моделирование бизнес-процессов / Моделирование бизнес-процессов / I D E F / idef9
.pdfINFORMATION INTEGRATION FOR CONCURRENT
ENGINEERING (IICE)
TOWARD A METHOD FOR
BUSINESS CONSTRAINT DISCOVERY (IDEF9)
Richard J. Mayer, PhD
Michael K. Painter
Madhavi Lingineni
Knowledge Based Systems, Inc.
One KBSI Place
1500 University Drive East
College Station, Texas 77840-2335
HUMAN RESOURCES DIRECTORATE
LOGISTICS RESEARCH DIVISION
2698 G Street
Wright-Patterson Air Force Base, Ohio 45433-7604
APRIL 1995
Interim Technical Paper for Period February 1991 to March 1995
Approved for public release; distribution is unlimited
AIR FORCE MATERIEL COMMAND
WRIGHT-PATTERSON AIR FORCE BASE, OHIO 45433-7604
INFORMATION INTEGRATION FOR CONCURRENT ENGINEERING (IICE)
TOWARD A METHOD FOR BUSINESS CONSTRAINT DISCOVERY (IDEF9)
Version 1.0
Richard J. Mayer, PhD
Michael K. Painter
Madhavi Lingineni
Knowledge Based Systems, Inc. One KBSI Place
1500 University Drive East College Station TX 77840-2335 (409) 260-5274
APRIL 1995
Contract No.: F33615-90-C-0012
Prepared for: Armstrong Laboratory
Logistics Research Division
Wright-Patterson Air Force Base, Ohio 45433-7604 (513) 255-7775
Report Documentation Page
Abstract (Maximum 200 words)
Policies, rules, conventions, procedures, contracts, agreements, regulations, societal and physical laws are the defining structure for an enterprise. These items forge relationships between people, information, material, and machines to make a system. In this report, we refer collectively to these items as constraints. Constraints initiate, enable, govern, and limit the behavior of objects and agents to accomplish the goals or purposes of a system. If we want to change the behavior of a system for whatever reason (e.g., improve its performance, efficiency, or effectiveness) we need to know what the relevant constraints are. However, the collection of constraints that forge an enterprise system is generally poorly defined. That is to say, the knowledge of what constraints exists and how those constraints interact is at best incomplete, disjoint, distributed, and often completely unknown. The IDEF9 Business Constraint Discovery method described in this report was designed to assist in the discovery and analysis of constraints in a business system. Once these constraints have been cataloged they can be systematically examined and, if necessary, tuned or replaced to improve the performance of the system.
Subject terms: Integration, Integration Definition, IDEF, method, methodology, modeling, knowledge engineering, knowledge acquisition, constraint, systems engineering
i
TABLE OF CONTENTS |
|
TABLE OF CONTENTS ................................................................................................... |
iii |
LIST OF FIGURES............................................................................................................ |
vi |
LIST OF TABLES ............................................................................................................ |
vii |
PREFACE ....................................................................................................................... |
ix |
FOREWORD ..................................................................................................................... |
xi |
Method Anatomy....................................................................................................... |
xi |
Family of Methods .................................................................................................. |
xiii |
EXECUTIVE SUMMARY................................................................................................. |
1 |
INTRODUCTION............................................................................................................... |
3 |
What is a constraint? .................................................................................................. |
3 |
Motivation for collecting and managing business constraints ................................... |
6 |
Benefits of constraint identification ........................................................................... |
7 |
Motivation for a method to collect constraints........................................................... |
8 |
Users and beneficiaries of constraint discovery ......................................................... |
9 |
Potential Applications for IDEF9............................................................................. |
10 |
APPROACH OVERVIEW ............................................................................................... |
11 |
SUMMARY OF RESEARCH FINDINGS....................................................................... |
13 |
Basic concepts for constraint discovery ................................................................... |
13 |
Constraint .................................................................................................. |
13 |
Context ...................................................................................................... |
14 |
Evidence .................................................................................................... |
14 |
Effect(s) of a constraint ............................................................................. |
15 |
Symptom ................................................................................................... |
15 |
System ....................................................................................................... |
16 |
Rationale for the constraint ....................................................................... |
16 |
iii
Goal ........................................................................................................... |
16 |
IDEF9 Procedure...................................................................................................... |
16 |
Mode Zero: Define the Project................................................................. |
17 |
Define the purpose .............................................................................. |
18 |
Establish the Scope.............................................................................. |
19 |
Mode One: Organize for Data Collection ................................................ |
19 |
Mode Two: Collect and Analyze Evidence.............................................. |
21 |
Prepare for Interviews ......................................................................... |
21 |
Interview Domain Experts................................................................... |
23 |
Collect and Catalog Evidence ............................................................. |
24 |
Analyze Collected Data....................................................................... |
26 |
Mode Three: Hypothesize Candidate Constraints.................................... |
28 |
Mode Four: Validate and Refine Constraints........................................... |
29 |
Substantiate Candidate Constraints..................................................... |
29 |
Challenge candidate constraints .......................................................... |
30 |
Refine constraints................................................................................ |
30 |
IDEF9 language design research and development.................................................. |
32 |
The method language design process........................................................ |
32 |
Candidate schematic designs explored...................................................... |
34 |
Context Schematic .............................................................................. |
34 |
Constraint Resource Schematic........................................................... |
37 |
Constraint-relationship schematic ....................................................... |
40 |
Constraint Effects Schematic .............................................................. |
42 |
Goal schematic .................................................................................... |
44 |
Goal relationship schematic ................................................................ |
46 |
Symptom schematic ........................................................................... |
46 |
SIGNIFICANCE OF THE EFFORT................................................................................. |
49 |
POTENTIAL AREAS FOR FUTURE WORK ................................................................ |
51 |
CONCLUSION ................................................................................................................. |
53 |
iv
BIBLIOGRAPHY ............................................................................................................. |
55 |
GLOSSARY OF TERMS ................................................................................................. |
57 |
v
|
LIST OF FIGURES |
|
Figure 1 |
Anatomy of a Method................................................................................... |
xii |
Figure 2 |
Typical business systems................................................................................ |
4 |
Figure 3 |
Constraints can be enabling or limiting.......................................................... |
5 |
Figure 4 |
Targeted users of IDEF9 .............................................................................. |
10 |
Figure 5 |
Process description of the IDEF9 development approach............................ |
11 |
Figure 6 |
IDEF9 Project Summary Form..................................................................... |
18 |
Figure 7 |
Evidence Log................................................................................................ |
25 |
Figure 8 |
Candidate syntax for the context schematic ................................................. |
35 |
Figure 9 |
Example context schematic.......................................................................... |
36 |
Figure 10 |
Candidate syntax for the constraint resource schematic............................... |
38 |
Figure 11 |
Example constraint resource schematic ....................................................... |
39 |
Figure 12 |
Candidate syntax for the constraint relationship schematic ......................... |
40 |
Figure 13 |
Example constraint relationship schematic .................................................. |
41 |
Figure 14 |
Candidate syntax for the constraint effects schematic ................................. |
42 |
Figure 15 |
Example constraint effects schematic .......................................................... |
43 |
Figure 16 |
Candidate syntax for the goal schematic...................................................... |
44 |
Figure 17 |
Example goal schematic............................................................................... |
45 |
Figure 18 |
Candidate syntax for the symptom schematic .............................................. |
47 |
Figure 19 |
Example symptom schematic....................................................................... |
47 |
vi
|
LIST OF TABLES |
|
Table 1 |
Some typical problems ................................................................................... |
6 |
Table 2 |
Some benefits of constraint discovery............................................................ |
8 |
Table 3 |
Different relations illustrated by constraint statements................................ |
27 |
vii