IDEF0 Diagram Constructs

Last modified on August 1st, 2014.


This section defines the building blocks of a 'IDEF0 Diagram' in Innoslate. The 'IDEF0 Diagram' supports five (5) unique diagram constructs: a 'Function' a 'Mechanism', an 'Input', an 'Output', and a 'Control'. Each diagram construct is described in more detail below:

IDEF0 Diagram Constructs

Last modified on August 1st, 2014. 


This section defines the building blocks of a ‘IDEF0 Diagram’ in Innoslate. The ‘IDEF0 Diagram’ supports five (5) unique diagram constructs: a ‘Function’ a ‘Mechanism’, an ‘Input’, an ‘Output’, and a ‘Control’. Each diagram construct is described in more detail below:

  • Function

    This construct is used to represent the classic systems engineering function or task.

    In the system model, a simple Action entity is used to represent a ‘Function’ construct with no additional diagram specific information. By default, Innoslate’s database schema includes labels to specify the type of this Action entity as a(n) Activity, Capability, Function, Mission, Process, Program, Project, Task, and/or Use Case.

    In the diagram, this construct is represented as a rounded block containing the number and name of the ‘Function’, as shown below:

    Function Construct

  • Mechanism

    This construct is used to capture the physical means of performing a system function.

    In the system model, an Asset entity is used to represent a ‘Mechanism’ construct with a performs relationship to the entity which represents the ‘Function’ construct being pointed to. By default, Innoslate’s database schema includes labels to specify the type of this Asset entity as a(n) Architecture, Context, Environment, External System, Facility, Infrastructure, Materiale, Organization, Package, Personnel, Segment, Service, Subsystem, and/or System.

    In the diagram, this construct is represented as an arrow (directed line) which points up to the bottom of a ‘Function’ construct.

    Mechanism Construct

  • Input

    This construct is used to capture anything introduced into the system being modeled.

    In the system model, an Input/Output entity is used to represent an ‘Input’ construct with a received by relationship to the entity which represents the ‘Function’ construct being pointed to. By default, Innoslate’s database schema includes labels to specify the type of this Input/Output entity as Analog, Digital, Event, Mixed, Physical, Product, Response, and/or Verbal.

    In the diagram, this construct is represented as an arrow (directed line) which points toward a ‘Function’ construct from the left.

    Input Construct

  • Output

    This construct is used to capture anything produced by the system being modeled.

    In the system model, an Input/Output entity is used to represent an ‘Output’ construct with a generated by relationship to the entity which represents the ‘Function’ construct being pointed away from. By default, Innoslate’s database schema includes labels to specify the type of this Input/Output entity as Analog, Digital, Event, Mixed, Physical, Product, Response, and/or Verbal.

    In the diagram, this construct is represented as an arrow (directed line) which points away from the right of a ‘Function’ construct.

    Output Construct

  • Control

    This construct is used to capture system components which regulate the behavior of other system components.

    In the system model, an Input/Output entity is used to represent a ‘Control’ construct with a received by relationship to the entity which represents the ‘Function’ construct being pointed to. By default, Innoslate’s database schema includes labels to specify the type of this Input/Output entity as Analog, Digital, Event, Mixed, Physical, Product, Response, and/or Verbal.

    In the diagram, this construct is represented as an arrow (directed line) which points down to the top of a ‘Function’ construct.

    Control Construct