Sequence Diagram Constructs

Last modified on July 30th, 2014.


This section defines the building blocks of a 'Sequence Diagram' in Innoslate. The 'Sequence Diagram' supports three (3) unique diagram constructs: a 'Lifeline', a 'Message', and a 'Found Message'. Each diagram construct is described in more detail below:

Sequence Diagram Constructs

Last modified on July 30th, 2014. 


This section defines the building blocks of a ‘Sequence Diagram’ in Innoslate. The ‘Sequence Diagram’ supports three (3) unique diagram constructs: a ‘Lifeline’, a ‘Message’, and a ‘Found Message’. Each diagram construct is described in more detail below:

  • Lifeline

    This construct is used to capture the physical components of a system which are interacting with each other.

    In the system model, an Asset entity is used to represent a ‘Lifeline’ construct. 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 rectangle shape containing the name of the ‘Lifeline’ with a dashed vertical line centered below it, as shown below:

    Lifeline Construct

  • Message

    This construct is used to capture any interactions made between ‘Lifeline’ constructs.

    In the system model, an Input/Output entity is used to represent a ‘Message’ construct. Innoslate’s default database schema includes labels to specify the type of this Input/Output entity as a(n) Analog, Digital, Event, Mixed, Physical, Product, Response, and/or Verbal.

    In the diagram, this construct is represented as an arrow pointing to a destination ‘Lifeline’ which originates from a source ‘Lifeline’ and a line label containing the name of the ‘Message’, as shown below:

    Message Construct

  • Found Message

    This construct is used to capture incoming interactions made outside of this diagram.

    In the system model, an Input/Output entity is used to represent a ‘Found Message’ construct. A ‘Message’ that has no source ‘Lifeline’ is known as a ‘Found Message’. Innoslate’s default database schema includes labels to specify the type of this Input/Output entity as a(n) Analog, Digital, Event, Mixed, Physical, Product, Response, and/or Verbal.

    In the diagram, this construct is represented as an arrow pointing to a destination ‘Lifeline’ which originates from a filled-in circle and a line label containing the name of the ‘Found Message’, as shown below:

    Found Message Construct