This section specifies the template Requirement.
The specification comprises a SysML Block that represents the template and an associated Parametric Diagram that defines the templates and PLCS PSM objects instantiated by the Requirement template.
The specification comprises the following sections:
The Requirement template describes how to represent a statement of need that should be met by the product or system to which the requirement is allocated.
The SysML Block Definition diagram in Figure 1 shows how a Part is represented in the PLCS PSM.
No templates have been explicitly defined as being related to the Requirement template.
Figure 2 shows the SysML Block that represents the template. The Block is an abstraction representing a pattern of templates and PLCS PSM objects.
The properties, i.e. the SysML Block Part, Reference and Value properties, of the template's SysML Block are described in the Template Properties section.
The output ports shown on the template's SysML Block are described in the template output ports section.
The following Part, Reference, and Value properties are defined for this template:
The following output ports are defined for this template:
There are no constraints defined for this template.
This section describes the template's Parametric Diagram. The diagram details the pattern of templates and PLCS PSM objects that are required to represent the template Requirement.
The public properties, i.e. those visible in the template's SysML block (See Figure 2) are shown on the left of a Parametric Diagram.
The output ports are shown on the right of the Parametric Diagram.
PLCS PSM objects are shaded khaki and template shaded light green in a Parametric Diagram.
The following blocks are instantiated by this template and bound to private parts of the template as shown in the Parametric Diagram section:
The following constraint, normally a uniqueness constraint, is applicable when instantiating the ExternalPropertyDefinition:
rule.Ap239Ap233Psm.ExternalOwlClass.ur1The following constraint, normally a uniqueness constraint, is applicable when instantiating the ExternalOwlObject:
rule.Ap239Ap233Psm.ExternalOwlClass.ur1Figure 3 shows the instances that have been instantiated in the template. These are used to set the default value of blocks.
The following instances have been created:
ExternalOwlObject.individual = http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/contexts/OASIS/refdata/plcs-rdl#Requirement_definition
Figure 3 shows the constraint blocks that have been created in the template.
Constraint Blocks are typically used to combine blocks into a collection that can then be bound to a property. For example, combining a set of identifications that can then be bound to property of type Identification.
The following constraint blocks have been created:
The following section provides an example XML dataset that has been instantiated in accordance with this template.
Requirement | requirement.xml | View | download |
This example shows the XML instantiated to represent a Requirement.