Interface Control Diagram Constructs

Last modified on June 12th, 2020.


The ‘Interface Control Diagram’ supports four unique diagram constructs: a Parent ‘Asset’, Child ‘Asset’, Child ‘Conduit’, and ‘Input/Output’. Each diagram construct is described in more detail below:

Asset

This construct is used to capture the physical components of a system.

In the system model, a simple Asset entity is generated to represent an ‘Asset’ construct with no additional diagram specific information. Innoslate’s default database schema includes labels to specify the type of this Asset entity as a(n) Architecture, Block, Context, Environment, External System, Facility, Infrastructure, Materiale, Organization, Package, Personnel, Segment, Service, Subsystem, and/or System.

In the diagram, the parent construct is represented as a blue block containing the number and name of the Parent ‘Asset.’ The child construct is represented as a rounded block containing the number and name of the ‘Asset.’ Parent constructs can be displayed two at a time in the ‘Interface Control Diagram’.



      Parent Asset Construct
Child Asset Construct

Conduit

This construct is used to capture the relationships between physical components of a system.

In the system model, a Conduit entity is generated to represent a ‘Conduit’ construct with the "connects to" relationship to each of the entities which represent the two connected constructs. Innoslate’s default database schema includes labels to specify the type of this Conduit entity as a(n) Aggregation, Association, Cable, Composition, Downlink, Interface, Network, Pipe, Roadway, Uplink, and/or Wireless.

In the diagram, this root construct is represented as a gray box and child conduit is represented as a solid blue line and a line label containing the name of the Conduit. The line can then be connected to child or parent ‘Asset’ constructs. The Latency and Capacity is also shown on the line. Latency is on the left and Capacity on the right. 

Parent Conduit Construct

Child Conduit Construct

Input/Output

This construct is a functional representation of data that is passed between ‘Action’ constructs through a ‘Conduit’ connected between ‘Assets’.

In the system model, an Input/Output entity is used to represent an ‘Input/Output’ construct with at least one generated by/generates relationship to an Action entity representing an ‘Action’ construct and at least one received by/receives relationship to another Action entity representing an ‘Action’ construct in the diagram. The Input/Output is transferred over a ‘Conduit’, through the transferred by relationship. Innoslate’s default 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 a solid green parallelogram the name of the Input/Output. A child ‘Conduit’ must be present to attach ‘Input/Output’ to the diagram. 

Input/Output Construct

Interface Control Diagram Constructs

Last modified on June 12th, 2020. 


The ‘Interface Control Diagram’ supports four unique diagram constructs: a Parent ‘Asset’, Child ‘Asset’, Child ‘Conduit’, and ‘Input/Output’. Each diagram construct is described in more detail below:

Asset

This construct is used to capture the physical components of a system.

In the system model, a simple Asset entity is generated to represent an ‘Asset’ construct with no additional diagram specific information. Innoslate’s default database schema includes labels to specify the type of this Asset entity as a(n) Architecture, Block, Context, Environment, External System, Facility, Infrastructure, Materiale, Organization, Package, Personnel, Segment, Service, Subsystem, and/or System.

In the diagram, the parent construct is represented as a blue block containing the number and name of the Parent ‘Asset.’ The child construct is represented as a rounded block containing the number and name of the ‘Asset.’ Parent constructs can be displayed two at a time in the ‘Interface Control Diagram’.



      Parent Asset Construct
Child Asset Construct

Conduit

This construct is used to capture the relationships between physical components of a system.

In the system model, a Conduit entity is generated to represent a ‘Conduit’ construct with the "connects to" relationship to each of the entities which represent the two connected constructs. Innoslate’s default database schema includes labels to specify the type of this Conduit entity as a(n) Aggregation, Association, Cable, Composition, Downlink, Interface, Network, Pipe, Roadway, Uplink, and/or Wireless.

In the diagram, this root construct is represented as a gray box and child conduit is represented as a solid blue line and a line label containing the name of the Conduit. The line can then be connected to child or parent ‘Asset’ constructs. The Latency and Capacity is also shown on the line. Latency is on the left and Capacity on the right. 

Parent Conduit Construct

Child Conduit Construct

Input/Output

This construct is a functional representation of data that is passed between ‘Action’ constructs through a ‘Conduit’ connected between ‘Assets’.

In the system model, an Input/Output entity is used to represent an ‘Input/Output’ construct with at least one generated by/generates relationship to an Action entity representing an ‘Action’ construct and at least one received by/receives relationship to another Action entity representing an ‘Action’ construct in the diagram. The Input/Output is transferred over a ‘Conduit’, through the transferred by relationship. Innoslate’s default 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 a solid green parallelogram the name of the Input/Output. A child ‘Conduit’ must be present to attach ‘Input/Output’ to the diagram. 

Input/Output Construct