The ‘Physical I/O Diagram’ supports two unique diagram constructs: an ‘Asset’ and an ‘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, Context, Environment, External System, Facility, Infrastructure, Materiale, Organization, Package, Personnel, Segment, Service, Subsystem, and/or System.

  In the diagram, this construct is represented as a rounded block containing the number and name of the ‘Asset.’

  

• 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. The Conduit connects to two Assets which are displayed on the Physical I/O Diagram. 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 directional line connecting two ‘Asset’ constructs and a line label containing the name of the ‘Input/Output.’