The Approval template describes how to represent a formal record of the fact that
items fullfil agreed criteria.
The SysML Block Definition diagram in Figure 1
shows how an Approval is represented in the PLCS PSM.
The following SysML Part, Reference, and Value properties are defined for this template:
References:
Parts:
ids [0..*] (Template: OASIS:
Identification)
The collection of identifiers of the approval.
The reference data used in Template: OASIS:
Identification is restricted as follows:
RDL constraint 1:The id must be classified as an Approval_identification_code or a
subclass thereof.
The reference data for:
OASIS:Identification.role -> ExternalOwlClass.class
is restricted to the following class or a subclass:
status [0..1] (Template: OASIS:
StateAssertion)
the status of the approval.
The reference data used in Template: OASIS:
StateAssertion is restricted as follows:
RDL constraint 1:The status is represented subclasses of State_of_approval.
The reference data for:
OASIS:StateAssertion.sameAs -> ExternalOwlObject.individual
is restricted to the following class or a subclass:
names [0..*] (Template: OASIS:
Name)
The names of the approval.
classifications [0..*] (Template: OASIS:
Classifier)
The classification of the approval.
The reference data used in Template: OASIS:
Classifier is restricted as follows:
RDL constraint 1:The reference data for:
OASIS:Classifier.class -> ExternalOwlClass.class
is restricted to the following class or a subclass:
Values:
validDate [0..1] (Block: Ap239Ap233Psm:
DateTimeString)
the date when the approval become valid.
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')