USA: +1(669)289-8683 
Sign in
ASAP
IDEF0
– Integration Definition for
Function Modeling
Overview
IDEF0 is a modeling language for developing a graphical representation of a system. IDEF0 was developed by the US Air Force and taken from Structured Analysis and Design Technique. IDEF0 was published by National Institute of Standards and Technology (NIST) as a draft in December 1993 and was withdrawn in September 2002. It is now apparently maintained by Knowledge Based Systems.
IDEF0 is one of a number of related modeling standards that include:
| IDEF0 | Function Modeling |
|
IDEF1 |
Information Modeling |
|
IDEF1X |
Data Modeling (particularly relational databases) |
|
IDEF2 |
Simulation Model Design |
|
IDEF3 |
Process Description Capture |
|
IDEF4 |
Object-Oriented Design |
|
IDEF5 |
Ontology Description Capture |
|
IDEF6 |
Design Rationale Capture |
|
IDEF8 |
User Interface Modeling |
|
IDEF9 |
Scenario-Driven IS Design |
|
IDEF10 |
Implementation Architecture Modeling |
|
IDEF11 |
Information Artifact Modeling |
|
IDEF12 |
Organization Modeling |
|
IDEF13 |
Three Schema Mapping Design |
|
IDEF14 |
Network Design |
From their website,
IDEFØ is a method designed to model the decisions, actions, and activities of an organization or system. IDEFØ was derived from a well-established graphical language, the Structured Analysis and Design Technique (SADT). The United States Air Force commissioned the developers of SADT to develop a function modeling method for analyzing and communicating the functional perspective of a system. Effective IDEFØ models help to organize the analysis of a system and to promote good communication between the analyst and the customer. IDEFØ is useful in establishing the scope of an analysis, especially for a functional analysis. As a communication tool, IDEFØ enhances domain expert involvement and consensus decision-making through simplified graphical devices. As an analysis tool, IDEFØ assists the modeler in identifying what functions are performed, what is needed to perform those functions, what the current system does right, and what the current system does wrong. Thus, IDEFØ models are often created as one of the first tasks of a system development effort.
Building blocks are the box and arrows:
· Controls – Specifies the conditions required for the function to produce correct outputs.
· Inputs – Something that is transformed or consumed by the function
· Outputs – Data or objects produced by the function
· Mechanism – Means that support the execution of the function
· Call – Support information provided to other functions
· Function name shall be an active verb or phase (process parts, design system, …)
· Arrows identify data or objects needed or produced by the function and are labeled with a noun or noun phrase (specifications, budget, design engineer, …)
Hierarchical diagrams are supported:
Some examples of its use:
Ref: IDEF0 Standard – page 60
� Knowledge Based Systems – website � HYPERLINK “http://www.idef.com/” �http://www.idef.com/�
_996496697.unknown
