Issue 6700: UML 2.0 Kernel Operations Diagram and Features Diagram and mdl (uml2-rtf) Source: TimeWarp Engineering Ltd. (Mr. Steven T. Cramer, scramer(at)timewarpllc.com) Nature: Uncategorized Issue Severity: Summary: The operations diagram redefines the formalParameter Property and removes the {ordered subsets parameter subsets ownedMember}. The mdl file has an added associtation between Operation: ownedparameter and Parameter:operation that isn’t defined in the spec. I believe the intent was to specialize the property Parameter:operation but I do not find the Operation:formalParameter Parameter:operation association required at all and would recommend its removal. This would require the ownerformalParam be made navigable. But I feel that this change is already required to sync the OCL and Superstructure specs. An alternative would be to add a unidirectional derived Property to the Parameter Class named operation and the derivation simply being operation=ownerFormalParam Resolution: No longer applicable closed no chnage Revised Text: Actions taken: December 16, 2003: received issue February 18, 2005: moved from infrastructure April 25, 2011: closed issue Discussion: Disposition: Deferred to UML 2.4 RTF End of Annotations:===== ubject: UML 2.0 Kernel Operations Diagram and Features Diagram and mdl Date: Tue, 16 Dec 2003 11:33:41 -0700 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: UML 2.0 Kernel Operations Diagram and Features Diagram and mdl Thread-Index: AcPEAyDeYZoQNbNPSJemiyLuD8TqFQ== From: "Steven T. Cramer" To: Cc: "Jeff Wright" The operations diagram redefines the formalParameter Property and removes the {ordered subsets parameter subsets ownedMember}. The mdl file has an added associtation between Operation: ownedparameter and Parameter:operation that isn’t defined in the spec. I believe the intent was to specialize the property Parameter:operation but I do not find the Operation:formalParameter Parameter:operation association required at all and would recommend its removal. This would require the ownerformalParam be made navigable. But I feel that this change is already required to sync the OCL and Superstructure specs. An alternative would be to add a unidirectional derived Property to the Parameter Class named operation and the derivation simply being operation=ownerFormalParam Steven T. Cramer TimeWarp Engineering Ltd. SCramer@TimeWarpEngineering.com Subject: RE: Issue 6700 UML 2.0 Kernel Operations Diagram and Features Diagram and mdl Date: Tue, 16 Dec 2003 12:38:37 -0700 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Issue 6700 UML 2.0 Kernel Operations Diagram and Features Diagram and mdl Thread-Index: AcPEAyDeYZoQNbNPSJemiyLuD8TqFQABTvNgAACquZA= From: "Steven T. Cramer" To: The best I can tell the only Classes that inherit from BehaivoralFeature are Operation and Reception. Does paramerter have any meaning in Reception. What would the parameters of a Reception be? To my understanding a signal will contain all the properties that are relevant to the signal. Therefore the abstraction of parameters from an operation to the BehavioralFeature does not make since? Am I missing something? Steven T. Cramer TimeWarp Engineering Ltd. SCramer@TimeWarpEngineering.com -------------------------------------------------------------------------------- From: Steven T. Cramer Sent: Tuesday, December 16, 2003 12:12 PM To: uml2-superstructure-ftf@omg.org; mu2i-ftf@omg.org Subject: UML 2.0 Kernel Operations Diagram and Features Diagram and mdl The operations diagram redefines the formalParameter Property and removes the {ordered subsets parameter subsets ownedMember}. The mdl file has an added associtation between Operation: ownedparameter and Parameter:operation that isn’t defined in the spec. I believe the intent was to specialize the property Parameter:operation but I do not find the Operation:formalParameter Parameter:operation association required at all and would recommend its removal. This would require the ownerformalParam be made navigable. But I feel that this change is already required to sync the OCL and Superstructure specs. An alternative would be to add a unidirectional derived Property to the Parameter Class named operation and the derivation simply being operation=ownerFormalParam Steven T. Cramer TimeWarp Engineering Ltd. SCramer@TimeWarpEngineering.com