This section specifies the template PropertyValueNumeric.
The specification comprises a SysML Block that represents the template and an
associated Parametric Diagram that defines the templates and
PLCS PSMTemplate objects
instantiated by the PropertyValueNumeric template.
The specification comprises the following sections:
- Section Description provides a
description of the template;
- Section Template Block specifies the SysML
Block that represents the template;
- Section Template Properties specifies
the properties, i.e. the SysML Part, Reference and Value properties of the
templates SysML Block;
- Section Template Output Ports
specifies the SysML Output Ports of the templates SysML Block. These bind to the
templates and PLCS PSM objects
instantiated by the PropertyValueNumeric template as
described in section Template
Parametric Diagram;
- Section Template Constraints specifies
the constraints on PLCS PSMTemplate objects instantiated by the
PropertyValueNumeric template;
- Section Template Parametric
Diagram specifies the templates and PLCS PSMTemplate objects instantiated by the
PropertyValueNumeric template;
- Section Instantiated blocks specifies
the templates and PLCS PSMTemplate objects instantiated by the
PropertyValueNumeric template and bound to private
parts of the template;
- Section Default instances species the
instances that have been instantiated in the template. These are used to set
the default value of blocks.
- Section Constraint blocks identifies the
constraint blocks that have been specified in this template;
- Section Example data
provides example XML data sets that have been instantiated in accordance
with this template.
NOTE
An explanation of a template and its specification is provided in
the
Template
overview The PropertyValueNumeric template describes how to represent a single numerical value
with
unit for a specified property. It provides a context for the value, and optionally
includes the date/time when measured.
EXAMPLE
The number of hours taken to perform some action.
The SysML Block Definition diagram in Figure 1
shows how Properties are represented in the PLCS PSM.
NOTE
Figure 1 only shows minimal set of information needed to
represent properties. More advanced representation of properties that enables
representation of features such as tolerances is given in
Figure Properties
in the
PLCS PSM.
Figure 1 - Property model
The following templates are related to the PropertyValueNumeric template:
NOTE
The PropertyValueNumeric template may make reference
to other templates as part of the Parametric Diagram. These are not listed
here.
Figure 2 shows the SysML Block that represents the template. The Block is an abstraction
representing a pattern of templates and PLCS PSMTemplate 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 SysML Parametric diagrams for the template Block are shown in template parametric diagram section.
Figure 2 - Template block definition diagram for PropertyValueNumeric
The following SysML Part, Reference, and Value properties are defined for this template:
References:
property [1] (Block: Ap239Ap233Psm:
ProxyItemSelect)
The specification of the property that this is a value of.
The reference data used in Block: Ap239Ap233Psm:
ProxyItemSelect is restricted as follows:
RDL constraint 1:The reference data for:
ExternalOwlObject.individual
is restricted to individuals that are members of the
following
class:
unit [1] (Block: Ap239Ap233Psm:
ProxyItemSelect)
The unit for the value. e.g. "Kilogramme"
The reference data used in Block: Ap239Ap233Psm:
ProxyItemSelect is restricted as follows:
RDL constraint 1:The reference data for:
ExternalOwlObject.individual
is restricted to individuals that are members of the
following
class:
context [0..1] (Block: Ap239Ap233Psm:
NumericalContext)
The specification of the representation context, i.e. accuracy and unit information
for a class of numerical values.
This property is defaulted to a general context in which no information is specified
for accuracy and units.
Parts:
Values:
value [1] (Real)
The value of the property as a numeric representation e.g. 5.
dateMeasured [0..1] (Block: Ap239Ap233Psm:
DateTimeString)
The optional date/time when the property value was measured.
The following constraint, normally a uniqueness constraint, is
applicable when instantiating the DateTimeString:
rule.Ap239Ap233Psm.ExternalOwlClass.ur1
Constraint: XSDDATETIMESpecification: (OCL2.0)
self.matches('[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}Z')
significantDigits [0..1] (Integer)
An Optional number of significant digits that apply to the value.
The following output ports are defined for this template:
value (Block: Ap239Ap233Psm:
PropertyValue)
Enables the
Block: Ap239Ap233Psm:
PropertyValue instantiated by this template to be referenced
when the template is used.
The PropertyValue for use in relationships with other objects.
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 PSMTemplate objects that are required to
represent the template PropertyValueNumeric.
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.
NOTE
Restrictions on the reference data to be set on the public properties is
defined in the
Template Properties section.
The output ports are shown on the right of a Parametric Diagram.
PLCS PSM
objects are shaded khaki and
Templates
are shaded light green in a Parametric Diagram.
Figure 3 - Parametric diagram for PropertyValueNumeric
The following blocks are instantiated by this template and bound to private parts
of the
template as shown in the Parametric Diagram
section:
Private Part Property:
propertyValue [1] (Block: Ap239Ap233Psm:
NumericalValue)
Private Reference Property:
prop [1] (Block: Ap239Ap233Psm:
ExternalPropertyDefinition)
The following constraint, normally a uniqueness constraint, is
applicable when instantiating the ExternalPropertyDefinition:
rule.Ap239Ap233Psm.ExternalOwlClass.ur1
Constraint: UR1Specification: (OCL2.0)
ExternalPropertyDefinition::allInstances()->isUnique(definition)
Private Reference Property:
theUnit [1] (Block: Ap239Ap233Psm:
ExternalUnit)
The following constraint, normally a uniqueness constraint, is
applicable when instantiating the ExternalUnit:
rule.Ap239Ap233Psm.ExternalOwlClass.ur1
Constraint: UR1Specification: (OCL2.0)
ExternalUnit::allInstances()->isUnique(definition)
Private Reference Property:
dateMeasuredObj [0..1] (Block: Ap239Ap233Psm:
ExternalOwlClass)
The following constraint, normally a uniqueness constraint, is
applicable when instantiating the ExternalOwlClass:
rule.Ap239Ap233Psm.ExternalOwlClass.ur1
Constraint: ur1Specification: (OCL2.0)
ExternalOwlClass::allInstances()->isUnique(class)
Private Part Property:
dateClassification [1] (Template: OASIS:
Classifier)
Figure 3 shows the instances that have been instantiated in the template. These are
used to set the default value of blocks.
Figure 3 - Model instance diagram for PropertyValueNumeric
The following instances have been created:
classDateMeasured instance of Block: Ap239Ap233Psm:
ExternalOwlClass.
This is used in the definition of the template to ensure the date assignment is correctly
classified.
There are no constraint blocks defined in this template.
The following section provides an example XML dataset that has been instantiated in
accordance with this template.
Data set: Property
This example shows the XML instantiated to represent a property, its value and unit.
The Property is Weight, its value 1.3 kilogrammes: