Issue 2243:  Misplaced Usage inheritance from SecurityClassifiable (pdm-rtf)
Source:  (, )
Nature:  Uncategorized Issue
Severity: 
Summary: Summary: Reference: PDM Enablers 2.7.3.2, 2.7.3.20
 
 Problem: As modelled, AssemblyComponentUsage inherits from
 SecurityClassifiable, but Usage does not.  If Usage is ever to have other
 subtypes (which is the only reason for separating AssemblyComponentUsage),
 the other usage relationships (such as MakeFrom) might also be classified.
 Usage should inherit from SecurityClassifiable, and AssemblyComponentUsage
 should inherit that from Usage.  When fixing this in the UML, "Classifiable"
 should be properly spelled "SecurityClassifiable".
 
 

Resolution: 
Revised Text:  As modelled, AssemblyComponentUsage inherits from
Actions taken:
December 7, 1998: received issue
August 24, 1999: closed issue
Discussion: 

End of Annotations:=====
Return-Path: <edbark@nist.gov>
X-Sender: edbark@mailhub.cme.nist.gov (Unverified)
Date: Mon, 07 Dec 1998 10:21:32 -0500
To: issues@omg.org
From: Ed Barkmeyer <edbark@nist.gov>
Subject: PDM Enablers -- UML/IDL problems with Usage
Cc: pdm-rtf@omg.org



Issue C: Misplaced Usage inheritance from SecurityClassifiable

Reference: PDM Enablers 2.7.3.2, 2.7.3.20

Problem: As modelled, AssemblyComponentUsage inherits from
SecurityClassifiable, but Usage does not.  If Usage is ever to have
other
subtypes (which is the only reason for separating
AssemblyComponentUsage),
the other usage relationships (such as MakeFrom) might also be
classified.
Usage should inherit from SecurityClassifiable, and
AssemblyComponentUsage
should inherit that from Usage.  When fixing this in the UML,
"Classifiable"
should be properly spelled "SecurityClassifiable".

-Ed