Issue 4083: Conflicting constraint between ActivityGraph and StateMachine. (uml2-superstructure-ftf) Source: Model Driven Solutions (Eugenio Alvarez, nobody) Nature: Revision Severity: Minor Summary: Since an ActivityGraph is derived from a StateMachine its constraints must be consistent with that of a StateMachine. If an ActivityGraph has a Package as its context it violates the constraint inherited from StateMachine. ActivityGraph Constraint (Semantics 2.13.3, Pg. 2-188): (self.context.oclIsTypeOf(Package) xor self.context.oclIsKindOf(Classifier) xor self.context.oclIsKindOf(BehavioralFeature)) StateMachine Constraint (Semantic 2.12.3, Pg. 2-165) : self.context.oclIsKindOf(BehavioralFeature) or self.context.oclIsKindOf(Classifier) One way to avoid this problem is to change the StateMachine constraint to be applicable when self is oclIsTypeOf(StateMachine) so the constraint is not applied to it children. A general mechanism to disable inherited constraints could also solve the problem. Resolution: Revised Text: The metamodel for activities is no longer dependent on the metamodel of state machines in UML 2.0, so this issue is no longer relevant. Actions taken: November 29, 2000: received issue March 9, 2005: closed issue Discussion: This is an AWG problem: it does not seem meaningful for a Package, an M1 entity with no M0 manifestation, to have behavior. Identified UML 2.0 RFP issue: SM and AG will be based on separate metamodels End of Annotations:===== From: Eugenio Alvarez To: issues@omg.org Subject: Conflicting constraint between StateMachine and ActivityGraph (um l-rtf) Date: Wed, 29 Nov 2000 13:38:23 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain X-UIDL: 7i]d9F~ed9e]?!!M;Z!! Descriptor: Conflicting constraint between ActivityGraph and StateMachine. Source: Eugenio J. Alvarez ( eugenio-a@dataaccess.com ) Reference: 00-11-01 UML Version1.4 beta R1, Semantics, Section 2.13.3 Well-Formedness Rules, Pg. 2-188 Nature: Revision Severity: Minor Summary: Since an ActivityGraph is derived from a StateMachine its constraints must be consistent with that of a StateMachine. If an ActivityGraph has a Package as its context it violates the constraint inherited from StateMachine. ActivityGraph Constraint (Semantics 2.13.3, Pg. 2-188): (self.context.oclIsTypeOf(Package) xor self.context.oclIsKindOf(Classifier) xor self.context.oclIsKindOf(BehavioralFeature)) StateMachine Constraint (Semantic 2.12.3, Pg. 2-165) : self.context.oclIsKindOf(BehavioralFeature) or self.context.oclIsKindOf(Classifier) One way to avoid this problem is to change the StateMachine constraint to be applicable when self is oclIsTypeOf(StateMachine) so the constraint is not applied to it children. A general mechanism to disable inherited constraints could also solve the problem. Date: Thu, 30 Nov 2000 13:58:23 +0000 From: Guus Ramackers Organization: Oracle Corporation X-Mailer: Mozilla 4.7 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 CC: uml-rtf@emerald.omg.org Subject: Re: issue 4083 -- UML RTF issue References: <4.2.0.58.20001129153839.05d0f300@emerald.omg.org> Content-Type: multipart/mixed; boundary="------------AAFDD12EC7A5E60E20434FD2" X-UIDL: 7XPe9!p!"!P=&!!&pd!! > One way to avoid this problem is to change the StateMachine constraint to be > applicable when self is oclIsTypeOf(StateMachine) so the constraint is not > applied to it children. > > A general mechanism to disable inherited constraints could also solve the > problem. Another way is to override the specific constraint, which is what happened here. We need to be more explicit about that in the spec for 2.0 I guess. Thanks, Guus > > > ================================================================ > > Juergen Boldt > Senior Member of Technical Staff > > Object Management Group Tel. +1-781 444 0404 ext. 132 > 250 First Avenue, Suite 201 Fax: +1-781 444 0320 > Needham, MA 02494, USA Email: juergen@omg.org > URL: www.omg.org > > ================================================================ [] Guus.Ramackers.vcf