You are on page 1of 24

IDEF0 Workshop

Presented by
Dr. Paul J. Myers

Objectives
Gain an understanding of IDEF family
of methods
Specifically IDEF0
Use a sample process to put that
understanding to work

Approach
Provide background on IDEF family
Introduce and discuss IDEF0
Apply IDEF0 to sample process
Develop familiarization with A10 Win
6.0 tool from KBSI
Apply actual process to IDEF0 tool

Purpose of IDEF0
Provide a structured representation
of activities occurring in a system or
environment
Link contextualized information to
each activity

A model is simply a representation of a real-world system

What is IDEF?

IDEF = ICAM DEFinition language


Integrated Computer-Aided
Manufacturing
Air Force NASA joint project

Integrated DEFinition language


1993 National Institute of Standards
and Technology (NIST)
Current released standard

IDEF Family of Methods


IDEF0 = Functional Modeling
IDEF1 = Information Modeling
IDEF1X = Data Modeling
IDEF3 = Process Description
IDEF4 = Object-Oriented Design
IDEF5 = Ontology Description

Graphic Representation

Simple Box and Arrow graphics


C1
Controls

Inputs
I1

Outputs
Context Title

Inputs
Controls
Outputs
Mechanisms

O1
0

Context number

A0

Detail Reference
Expression

Mechanisms
M1

Diagrams
Controls specifications, policies,
and constraints necessary to
produce correct output
Outputs data or
objects produced
Process
Inputs items consumed
or transformed to
produce outputs

1
A1

Process number
Child diagram

Mechanisms provide the means to


transform or consume input such as
tools and processes

IDEF0 Rules - Activities

Activities are represented as boxes


showing the name of the activity
Each box must have at least one
Control and one Output
No fewer than 3, no more than 6
boxes on a diagram
There is always an A-0 context
diagram describing the overall
system
Each box is numbered left to right in
lower right corner on each diagram
starting with one
Successive detail (child) diagrams
are numbered in relation to their
parent

Control
Order
Supplies

Output
3
A3

IDEF0 Rules - Concepts

Concepts are graphical


representations of the interfaces
between activities
Horizontal or vertical solid lines
Attached at sides of boxes
Inputs interface at left
Controls interface at top
Outputs interface at right
Budget
Mechanism interface at bottom I1
Parallel arrows are forked and
I2
Plan
joined
Inputs and Outputs are numbered
in descending order
Concepts and Mechanisms are
numbered left to right

C1
Regulation
Process

Report
O1

Spreadsheet
M1 M2

IDEF0 Rules - Boundaries

Internal arrows connect boxes internal to all diagrams


Boundary arrows go from diagram boundary to boxes
Parentheses at the external, unconnected end of a concept
(arrow) indicate a concept that is not attached to parent
activity
()

Diagram
Boundary

I1

C1

Process
1
M1

Parent
Number

O1
Parentheses
Process
2
M2

A-2

O2
Process
3

O3
()

IDEF0 Rules - Feedback


Control
feedback is up
and over
Input feedback
is down and
under
Mechanism
feedback is
down and under

Process Control Feedback


1
Process
2
Process Input Feedback
1
Process
2

Process Mechanism Feedback


1
Process
2

IDEF0 Rules Child Diagrams


Process
1

0
A0

Process
2

Process
3

A-0

()

Title

A-3
A0

()
()
Process
1

Process
1

Process

Process
2

A-32
A-32
A-3

Process

Activity Modeling
Cost Analysis Document
An

A0: Life Cycle Cost analysis


An

An

A1: Develop Cost Estimate


An

A11: Collect cost data

An

A12: Validate cost data

An

A13: Compute estimate

An

A14: Report cost estimate

A2: Allocate Costs

Name of Mode - describes a system


that produces, according to inputs,
controls, and mechanisms
A0 activity - Context Title
that defines context of model
A1 and A2 are children
processes of A0. They are the
decomposed processes
referred to in the A0 diagram

A11 through A14 are children


tasks of A1. They are
decomposed tasks referred to
in the A1 diagram

Sample Problem
Desire for a Sandwich
Inputs = stuff that gets
processed to make a
sandwich

Controls = desire to
eat a particular kind
of sandwich

Basic Ingredients
Condiments

Sandwich

Make a BLT
Sandwich
0
A0

Mechanisms = necessary
tools to actually make
sandwich

Tools

Outputs = result of
using tools to
produce a sandwich

A0 tells us that there is a


child diagram with more
detail

Control
C1
Desire

Process begins with a need

A0

BLT Process

Input #1
C1
Desire
I1

Bacon
Lettuce
Tomato
Bread

I2

A0

To fulfill our need, we require specific


inputs - that is, stuff to convert into a
sandwich that will fulfill our desire
such as basic sandwich ingredients
and condiments

Mayonnaise

BLT Process

Tools
C1
Desire
I1

Bacon

Bacon Strips

Fry
1

Skillet

I2

We need some tools to prepare our


inputs into usable form

Mayonnaise
Lettuce
Tomato
Bread
M1

A0

BLT Process

Feedback
C1
Desire
I1

Bacon

Bacon Strips

Fry
1

Skillet

I2

Mayonnaise
Lettuce

Check

Underdone Bacon

Part of our desire (specifications) is


that we like our bacon crisp

Tomato
Bread
M1
A0

BLT Process

Input #2
C1
Desire
I1

Bacon

Bacon Strips

Fry
1

Skillet

Check

Underdone Bacon
Bread

I2

Mayonnaise

Spread

Lettuce

Tomato
Knife
M1
A0

BLT Process

Outputs Not Satisfactory Yet


C1
Desire
I1

Bacon

Bacon Strips

Fry
1

Skillet

Crisp Bacon
Check

Output #1

Underdone Bacon
Bread

I2

Mayonnaise

Spread

Lettuce

Bread with Mayo


3

Tomato
Knife
M1
A0

BLT Process

Output #2

Final Output
C1
Desire
I1

Bacon

Bacon Strips

Fry
1

Skillet

Crisp Bacon
Check

Underdone Bacon
Bread

I2

Mayonnaise

Spread

Lettuce

Bread with Mayo


3
Stack

Tomato
Knife

4
A4

M1
A0

BLT Process

Sandwich

O1

Child Task of A4
C1

C2

Bread with Mayo

Crisp Bacon
Drain

Position
1

I1

I2

A4

Lettuce

Tomato

Place

Place

Sandwich

Place
5

BLT Stacking

O1

Summary
Models are used to provide a graphic
portrayal of real-world activities
IDEF family of methods provide a
standardized approach to developing
such models
Tools like AI0 Win 6.0 automate this
process