UPDM — Various properties for InformationExchange (appearing in DoDAF 1.5) should be modelled as Measurements in UPDM

Various properties for InformationExchange (appearing in DoDAF 1.5) should be modelled as Measurements in UPDM. Is it really done intuitively or should we create a class library of some kind?
Diagram OV-3
Document Issue UPDM (OMG Beta) Jan 2009

Source Andrius StrazdauskasNo Magicandriuss@nomagic.com

Resolution: Since these properties could be different for various implementations, we shouldn't include these on the stereotypes as tagged values. Instead, we'll add a section to the non-normative part of the document that describes a potential class library of MeasurementSets that fulfil the current DoDAF/MODAF requirements.

Since these properties could be different for various implementations, we shouldn't include these on the stereotypes as tagged values. Instead, we'll add a section to the non-normative part of the document that describes a potential class library of MeasurementSets that fulfil the current DoDAF/MODAF requirements.
Add new class ExchangeProperties stereotyped <<MeasurementSet>>, add following attributes:
accountability
interoperabilityLevelAchievable
classification
classificationCaveat
criticality
periodicity
protectionDuration
protectionSuspenseCalendarDate
protectionTypeName
timeliness
transactionType
protectionDurationCode
releasability
size
throughput
Add new class InformationAssuranceProperties stereotyped <<MeasurementSet>>, add following attributes:
accessControl
availability
confidentiality
disseminationControl
integrity
nonRepudiationConsumer
nonRepudiationProducer