Block Definition Diagram Constructs

Last modified on March 5th, 2015.


This section defines the building blocks of a 'Block Definition Diagram' in Innoslate. The 'Block Definition Diagram' supports eight (8) unique diagram constructs: a 'Block', a 'Port', a 'Value', an 'Operation', an 'Input Parameter', a 'Return Type', a 'Constraint', and a 'Logical Connection'. Each diagram construct is described in more detail below:

Block Definition Diagram Constructs

Last modified on March 5th, 2015. 


This section defines the building blocks of a ‘Block Definition Diagram’ in Innoslate. The ‘Block Definition Diagram’ supports eight (8) unique diagram constructs: a ‘Block’, a ‘Port’, a ‘Value’, an ‘Operation’, an ‘Input Parameter’, a ‘Return Type’, a ‘Constraint’, and a ‘Logical Connection’. Each diagram construct is described in more detail below:

  • Block

    In the system model, an Asset entity with label ‘Block’ is used to represent a ‘Block’ construct. A ‘Block’ must be added to the diagram first before any of the other constructs can be added. In the diagram, this construct is represented as a rounded box and contains the name of the ‘Block’ in the top section, as shown below:

    Block Construct

  • Port

    In the system model, a Port entity is used to represent a ‘Port’ construct. A ‘Block’ must be added to the diagram first before this construct can be added. In the diagram, this construct is represented as a small square on the edge of a ‘Block’ with the name of the ‘Port’ underneath, as shown below:

    Port Construct

  • Value

    In the system model, a Characteristic entity is used to represent an ‘Value’ construct. A ‘Block’ must be added to the diagram first before this construct can be added. In the diagram, this construct is represented as a line of text containing the name of the ‘Value’, a semicolon, and the units of the ‘Value’ in middle section of the ‘Block’, as shown below:

    Value Construct

  • Constraint

    In the system model, an Equation entity is used to represent an ‘Constraint’ construct.  A ‘Block’ must be added to the diagram first before this construct can be added.  In the diagram, this construct is represented as a line of text containing the name of the ‘Constraint’ in bottom section of the ‘Block’, as shown below:

    Constraint Construct

  • Operation

    In the system model, an Action entity is used to represent an ‘Operation’ construct. A ‘Block’ must be added to the diagram first before this construct can be added. In the diagram, this construct is represented as a line of text containing the name of the ‘Operation’ in bottom section of the ‘Block’, as shown below:

    Operation Construct

  • Input Parameter

    In the system model, an Input/Output entity is used to represent a ‘Input Parameter’ construct. An ‘Operation’ must first be added to a ‘Block’ in the diagram before this construct can be added. In the diagram, this construct is represented as a line of text containing the name and units of the ‘Input Parameter’ in parenthesis, as shown below:

    Input Parameter Construct

  • Return Type

    In the system model, an Input/Output entity is used to represent a ‘Return Type’ construct. An ‘Operation’ must first be added to a ‘Block’ in the diagram before this construct can be added. In the diagram, this construct is represented as a semicolon and a line of text containing the units of the ‘Return Type’, as shown below:

    Return Type Construct

  • Logical Connection

    In the system model, a Logical entity is used to represent a ‘Logical Connection’ construct. At least two (2) ‘Block’ constructs must be added to the diagram first before a ‘Logical Connection’ can be added. In the diagram, this construct is represented as a solid line connecting two (2) ‘Block’ constructs and a line label containing the name of the ‘Logical Connection’, as shown below:

    Logical Connection Construct