UPDMRTF — use of Generalization to implement Aliasing

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