The ‘Requirement Diagram’ supports two unique diagram constructs: a ‘Requirement’ and an ‘Entity.’
This construct is used to represent a physical or functional capability necessary of the system being modeled.
In the system model, a Requirement entity is used to represent a ‘Requirement’ construct. Innoslate’s default database schema includes labels to specify the type of this Requirement entity as a(n) Environmental Requirement, Functional Requirement, Interface Requirement, Performance Requirement, Reliability Requirement, Safety Requirement and/or Verification Requirement.
In the diagram, this construct is represented as a rounded block with two sections. The top section which contains the name of the ‘Requirement’ and the bottom section contains the identifier, text and rationale of the ‘Requirement.’
In the system model, an entity of any schema-based class can be used in the ‘Requirement Diagram.’ The purpose of this ability is to derive relationships between the entity and the ‘Requirement’ constructs. In the diagram, this construct is represented as a rounded block which contains the name of the entity.