Process Analysis and Modelling

Process Analysis and Modeling
Using IDEF0
School of Mechanical,
Industrial, & Manufacturing
Engineering
IDEF0 Standard
http://www.itl.nist.gov/fipspubs/idef02.doc
Engineering
IDEF0
Engineering
Integrated DEFinition language 0

Originally SADT
System Analysis and Design Technique
Developed by Douglas T. Ross, SofTech
Used in USAFs Integrated Computer Aided

Manufacturing (ICAM) Program to model
manufacturing and logistics activities
Generally used for modeling complex

processes (activities, functions)
3
IDEF0 Application In Work System

Engineering
Engineering
Process Analysis
Start with Statement of Need
Model high-level process to meet Need
Decompose into detailed models of subprocesses
Requirements Development
Systematically examine subprocesses
Identify factors that will affect WS performance, safety
Identify requirements to optimize performance, safety
Process Design
Add details, based on requirements
Iteratively refine
Basis for equipment, procedure design, e.g.,

facility, equipment, tool specifications
procedure flow charts, (flow) process charts
written work procedures
IDEF0 Concepts
Engineering
Box and arrows language with syntax and semantics

Provides systems engineering approach to
performing system/process analysis at all levels (multiple levels of
abstraction).
producing reference documentation:
box & arrow diagrams
English text (descriptions/glossaries)
node indexes
communicating among analysts, designers, users, and managers.

promoting shared understanding.
managing large, complex projects.
providing a reference architecture for enterprise analysis,
information engineering and resource management.
Other Concepts & Characteristics of

IDEF0
Engineering
Gradual exposition of detail

Limitation of detail
Diagrams supported with text
Rigor and precision
detail exposition control

bounded context (no omissions or additional out-of-scope detail).
syntax rules for graphics (boxes and arrows).
uniqueness of names and labels on a diagram.
diagram connectivity data/object connectivity.
rules for determining role of data or objects.
arrow label requirements (minimum labeling rules).
purpose and viewpoint.
Syntax and Semantics

Engineering
Syntax of a representation
elements
structure
form
e.g., grammar
Semantics
meaning
Syntax: Boxes
Engineering
Solid lines
Verb or verb phrase
Box number
Syntax: Arrows
Engineering
Box and Arrow Syntax Rules

Engineering
Boxes
Boxes shall be sufficient in size to insert box name.
Boxes shall be rectangular in shape, with square corners.
Boxes shall be drawn with solid lines.
Arrows
Arrows that bend shall be curved using only 90 degree arcs.
Arrows shall be drawn in solid line segments.
Arrows shall be drawn vertically or horizontally, not
diagonally.
Arrow ends shall touch the outer perimeter of the function
box and shall not cross into the box.
Arrows shall attach at box sides, not at corners.
10
Semantics
Engineering
11
Semantics
Engineering
Something (matter, energy,

information, system)
transformed by the process
Something that guides,

facilitates, limits, or
constrains the process
Something
that results
from the
process
A means by which
the process is
performed
A reference to
another model.
12
Example
Engineering
13
More Box and Arrow Syntax Rules

Engineering
A box shall be named with an active verb or verb phrase.

Each side of a function box shall have a standard box/arrow
relationship:
a.
b.
c.
d.
Input arrows shall interface with the left side of a box.

Control arrows shall interface with the top side of a box.
Output arrows shall interface with the right side of the box.
Mechanism arrows (except call arrows) shall point upward and shall
connect to the bottom side of the box.
e. Mechanism call arrows shall point downward, shall connect to the
bottom side of the box, and shall be labeled with the reference
expression for the box which details the subject box.
Arrow segments, except for call arrows, shall be labeled with a

noun or noun phrase unless a single arrow label clearly applies to
the arrow as a whole.
A squiggle ( ) shall be used to link an arrow with its associated
label, unless the arrow/label relationship is obvious.
Arrow labels shall not consist solely of any of the following terms:
function, input, control, output, mechanism, or call.
14
IDEF0 Diagrams and Text

Engineering
Top-Level Context Diagram

Child Diagram
Parent Diagram
Text and Glossary
For Exposition Only Diagrams
15
Top-Level Context Diagram

Engineering
Subject of model represented by single box with

bounding arrows.
Called A-0 (A minus zero)
Box and arrows are very general
Sets model scope or boundary and orientation.
Should include
Purpose
Viewpoint
16
Example Context Diagram:

A-0 Assemble widgets
Engineering
Purpose: To illustrate
IDEF0 modeling for the
Work Systems Engineering
process.
Viewpoint:
Industrial/manufacturing
engineer.
17
Child Diagram
Engineering
Single process in Context Diagram (A-0) may be

decomposed into subprocesses and modeled in a
child (A0) diagram.
Each process in the A0 diagram may be decomposed
further into subprocesses and modeled in (grand-)
child (A1, A2, A6) diagrams.
Each (grand-) child process may be decomposed
further into subprocesses and modeling (great-grand-)
child diagrams.
And so on
18
Parent Diagram
Engineering
Diagram that contains one or more parent boxes, i.e.,

boxes detailed on child diagrams.
19
Process Decomposition
Engineering
A-0
A0
parent
A3
child
parent
20
child
Text and Glossary

Engineering
Text
Associated textual information used to clarify model.
Glossary
Definitions of
processes (activities, functions)

inputs
controls
outputs
mechanisms
Examples
Get widget parts (process)
The process of getting widget parts from the stock areas so that widgets may
be assembled.
Parts for widgets (output)

Parts retrieved from the workstation stock areas and ready to be used in
assembly.
21
For Exposition Only Diagram

Engineering
FEO (fee-oh)
Provides supplementary information to help reader
understand model.
Need not comply with IDEF0 rules
Example: Flowchart to describe a procedure
(action/decision sequence) that can be used to
perform the process.
22
Diagram Features
Engineering
Arrows As Constraints
Concurrent Operation
Arrows As Pipelines
Branching Arrows
Inter-Box Connections
Boundary Arrows
Tunneled Arrows
Call Arrows
23
Arrows As Constraints
Engineering
Connecting output of a box representing a process that is

input/control/mechanism to another box means that the second
process is constrained by the first.
24
Concurrent Operation
Engineering
Box order and connections do not necessarily imply sequence!

Processes may proceed concurrently.
Concurrent
with A32 and
A33
25
Arrows As Pipelines
Engineering
Think of arrows as pipelines or conduits.

High-level arrows have general labels.
Low-level arrows have specific labels.
If an arrow forks, the branches may have more specific labels.
26
Branching Arrows
Engineering
27
Engineering
Except for A-0, diagrams contain 3 6 boxes.

Normally organized on diagonal (staircase).
Any output of one box may be input, control, or
mechanism of another box.
If box is detailed on child diagram, every arrow
connected to the box appears on the child diagram
(unless it is tunneled).
28
Engineering
29
(arrows for child diagram)
Engineering
30
Boundary Arrows:
Arrows from parent box on parent diagram
Engineering
Coded by prefix
and number
31
to be continued
Engineering
32
WSE Project Assignment

Engineering
1. IDEF0 A-0 diagram (hand-drawn OK)

2. IDEF0 A0 diagram (hand-drawn OK)
3. IDEF0 glossary (typed)
4. Requirements Version 1
5. Progress Report 1
i. Cover: Memo Evaluation Form (provided by instructor)
ii. Memo (see syllabus)
iii. Separator page: Work Products Evaluation Form (provided by
instructor)
iv. Copies of work products (see above)
33

Process Analysis and Modelling

Uploaded by

Copyright:

Available Formats

Process Analysis and Modelling

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Process Analysis and Modelling

Uploaded by

Copyright:

Available Formats

Process Analysis and Modeling

Integrated DEFinition language 0

Used in USAFs Integrated Computer Aided

Generally used for modeling complex

IDEF0 Application In Work System

Basis for equipment, procedure design, e.g.,

Box and arrows language with syntax and semantics

communicating among analysts, designers, users, and managers.

Other Concepts & Characteristics of

Gradual exposition of detail

detail exposition control

Syntax and Semantics

Box and Arrow Syntax Rules

Something (matter, energy,

Something that guides,

More Box and Arrow Syntax Rules

A box shall be named with an active verb or verb phrase.

Input arrows shall interface with the left side of a box.

Arrow segments, except for call arrows, shall be labeled with a

IDEF0 Diagrams and Text

Top-Level Context Diagram

Top-Level Context Diagram

Subject of model represented by single box with

Example Context Diagram:

Single process in Context Diagram (A-0) may be

Diagram that contains one or more parent boxes, i.e.,

Text and Glossary

processes (activities, functions)

Parts for widgets (output)

For Exposition Only Diagram

Connecting output of a box representing a process that is

Box order and connections do not necessarily imply sequence!

Think of arrows as pipelines or conduits.

Except for A-0, diagrams contain 3 6 boxes.

Arrows from parent box on parent diagram

WSE Project Assignment

1. IDEF0 A-0 diagram (hand-drawn OK)

You might also like