Conformance checks should happen to ensure the object diagram always conform to the class diagram (i.e., it does not violate any constraints imposed by the class diagram).
This is not trivial, since minimal multiplicity constraints are always violated when an object is being initialized. It makes sense to do the following:
add an state construct (see other issue);
whenever the state is left, the object is deemed constructed and conformance is checked (note that all objects should be initialized, as conformance can potentially affect all objects);
when an object/link is deleted, conformance is checked;
local constraints (on instance variable values, for example) are checked whenever an object is stable.
When conformance is violated, an exception is raised (see other issue).
Conformance checks should happen to ensure the object diagram always conform to the class diagram (i.e., it does not violate any constraints imposed by the class diagram).
This is not trivial, since minimal multiplicity constraints are always violated when an object is being initialized. It makes sense to do the following:
- add an <initial> state construct (see other issue);
- whenever the <initial> state is left, the object is deemed constructed and conformance is checked (note that *all* objects should be initialized, as conformance can potentially affect all objects);
- when an object/link is deleted, conformance is checked;
- local constraints (on instance variable values, for example) are checked whenever an object is stable.
When conformance is violated, an exception is raised (see other issue).
Conformance checks should happen to ensure the object diagram always conform to the class diagram (i.e., it does not violate any constraints imposed by the class diagram).
This is not trivial, since minimal multiplicity constraints are always violated when an object is being initialized. It makes sense to do the following:
When conformance is violated, an exception is raised (see other issue).