Issue 18739: use of Generalization to implement Aliasing (updm-2-0-rtf) Source: MITRE (Dr. Fatma Dandashi, dandashi(at)mitre.org) Nature: Enhancement Severity: Significant Summary: Issue 18739: Name: Fatma Dandashi Employer: Mitre Corp. mailFrom: dandashi@mitre.org Terms_Agreement: I agree Specification: UPDM Profile Section: FormalNumber: dtc/12-12-17 Version: 2.1 Doc_Year: 2012 Doc_Month: December Doc_Day: 17 Page: 218 Title: use of Generalization to implement Aliasing Nature: Enhancement Severity: Significant CODE: B1: Report Issue Remote Name: Remote User: Time: Description: DMM defines system as a DoDAF-only alias for ResourceArtifact: Profile then defines the following: (this is probably true for all elements that are aliases). Using generalization in this manner means that vendor implementations allow one to use both System as well as ResourceArtifact in the same model, regardless if one is using DoDAF or MODAF. System is an alias for MODAF’s ResourceArtifact in DODAF only. That is, System should not be available as a choice in MODAF/NAF. More importantly: generalization is really not the best UML construct to implement aliasing. If you choose System in NAF, you will not be able to use composition and aggregation relationships on SV-1. One should be able to use System in exactly the same manner as a ResourceArtifact, especially the a Resolution: Revised Text: Actions taken: May 29, 2013: received issue Discussion: End of Annotations:===== iler: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Wed, 29 May 2013 11:40:50 -0400 To: issues@omg.org, updm-2-0-rtf@omg.org From: Juergen Boldt Subject: issue 18739 -- UPDM 2.2 RTF issue X-Virus-Scanned: amavisd-new at omg.org Issue 18739: Name: Fatma Dandashi Employer: Mitre Corp. mailFrom: dandashi@mitre.org Terms_Agreement: I agree Specification: UPDM Profile Section: FormalNumber: dtc/12-12-17 Version: 2.1 Doc_Year: 2012 Doc_Month: December Doc_Day: 17 Page: 218 Title: use of Generalization to implement Aliasing Nature: Enhancement Severity: Significant CODE: B1: Report Issue Remote Name: Remote User: Time: Description: DMM defines system as a DoDAF-only alias for ResourceArtifact: [] Profile then defines the following: (this is probably true for all elements that are aliases). [] Using generalization in this manner means that vendor implementations allow one to use both System as well as ResourceArtifact in the same model, regardless if one is using DoDAF or MODAF. System is an alias for MODAF.s ResourceArtifact in DODAF only. That is, System should not be available as a choice in MODAF/NAF. More importantly: generalization is really not the best UML construct to implement aliasing. If you choose System in NAF, you will not be able to use composition and aggregation relationships on SV-1. One should be able to use System in exactly the same manner as a ResourceArtifact, especially the ability to draw Composite and Aggregate Associations among systems. Juergen Boldt Director, Member Services 109 Highland Ave Needham, MA 02494 USA Tel: 781 444 0404 x 132 fax: 781 444 0320 www.omg.org []