the current slots set of the Attribute_Value Class doesn't allow the association with any instance of EA_Class or EA_Relation despite the definition of the Attribute and Attribute_Value Classes. It will be beneficial to allow association with instances of type other than Technology_instance.
The requested change is similar with the one lastly applied to the Security_Classification metamodel.
Code: Select all
Attribute :
Meta class that is used to define attributes for other classes.
The modeller should create instances of this class in order to define a particular attribute, e.g. cost.
Usages of this class are then associated with Instances of artefacts that have that attribute in order to
specify the value for that attribute.
Code: Select all
Attribute_Value :
Meta class that is, in effect, a usage of an instance of an Attribute class with
the associated value of the attribute in a particular instance.
E.g. the cost of a Business Process.
SLOT NAME : inverse_of_technology_instance_attributes
INVERSE SLOT NAME : technology_instance_attributes
TARGET CLASS : Technology_Instance
Suggestion :
Code: Select all
New Slots
1° ea_instance_attributes
Multiple
Value Type : instance of Attribute_Value Class or SubClass
Domain : EA_Class, EA_Relation, :EA_Graph_Relation
2° inverse_of_ea_instance_attributes
Multiple
Value Type : instance of EA_Class, EA_Relation, :EA_Graph_Relation Class or SubClass
Domain : Attribute_Value
Code: Select all
Change on existing Slots
1° attribute_value
Multple
Value Type : any primitive value or Instance
With the suggested change we could for instance model Export or Import as Product
and define Country of Origin, Country of destination, Dates, Goods, Importer, and Exporter as Attribute Values linked to instances of other classes.
No need to defne new Classes or Slots. No impact on the complexity of the metamodel.
Best regards,
Tshitshi