This section defines the building blocks of a 'Sequence Diagram' in Innoslate. The 'Sequence Diagram' supports two unique diagram constructs: a 'Lifeline' and a '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.
Message
This construct is used to capture any interactions made between 'Lifeline' constructs.
In the system model, an Action entity is used to represent a 'Message' construct. 'Lifelines' perform these Actions, which act as the processes that send and receive Input/Outputs between the 'Lifelines'.
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.'
Sequence Diagram Constructs
Last modified on May 5th, 2020.
This section defines the building blocks of a ‘Sequence Diagram’ in Innoslate. The ‘Sequence Diagram’ supports two unique diagram constructs: a ‘Lifeline’ and a ‘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.
Message
This construct is used to capture any interactions made between ‘Lifeline’ constructs.
In the system model, an Action entity is used to represent a ‘Message’ construct. ‘Lifelines’ perform these Actions, which act as the processes that send and receive Input/Outputs between the ‘Lifelines’.
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.’