Concept model, with the purpose of defining concepts and types we want to use in a Solution model.
Solutions model, using the generated types defined in the concept-model to model test solution models.
While building a solutions model, often we see a need for new types, that is not defined in the Concept model yet.
We then need to use a temporarily/preliminary object.
As we are using the IRTV types already, I suggest we use the Information object for this purpose.
If we add a new attribute for the proposed type and make it visible on the object, its possible to indicate both the name of the object and the proposed typename.
f.ex:
Name: Delivery
Type: Schedule
When the suggested type is approved, we can update the Concept model and generate the type.
For relationship types we can maybe use the generic or make a new reltype for this use.
If this modelling approach is accepted, I suggest to remove "EntityType" from the Solution modelling palette.
Preliminary object types.
As for now, AKMM support 2 main types of models:
While building a solutions model, often we see a need for new types, that is not defined in the Concept model yet. We then need to use a temporarily/preliminary object.
As we are using the IRTV types already, I suggest we use the Information object for this purpose. If we add a new attribute for the proposed type and make it visible on the object, its possible to indicate both the name of the object and the proposed typename.
f.ex:
Name: Delivery Type: Schedule
When the suggested type is approved, we can update the Concept model and generate the type.
For relationship types we can maybe use the generic or make a new reltype for this use.
If this modelling approach is accepted, I suggest to remove "EntityType" from the Solution modelling palette.