Issue 6208: UML 2 Super/Metamodel::UseCases/Extend and Include are not NamedElements (uml2-superstructure-ftf) Source: Simula Research Laboratory (Mr. Bran Selic, selic(at)acm.org) Nature: Uncategorized Issue Severity: Summary: Properties UseCase::extend and UseCase::include subset property Namespace::ownedMember, but classes Extend and Include are not types of NamedElement Resolution: see above Revised Text: Actions taken: September 7, 2003: received issue March 8, 2005: closed issue Discussion: This is an oversight. Both Extend and Include should also be made subclasses of NamedElement as shown in the new version of Figure 401 below. The following changes need to be made: ?? Figure 401 (changes indicated using a red pen): ?? Pg. 515 (added text indicated by underlining): It is a kind of DirectedRelationship, such that the source is the extending use case and the destination is the extended use case. It is also a kind of NamedElement so that it can have a name in the context of its owning use case. ?? Pg. 518 (added text indicated by underlining): Include is a kind of DirectedRelationship between two use cases, implying that the behavior of the included use case is inserted into the behavior of the including use case. It is also a kind of NamedElement so that it can have a name in the context of its owning use case. End of Annotations:===== To: issues@omg.org Subject: UML 2 Super/Metamodel::UseCases/Extend and Include are not NamedElements X-Mailer: Lotus Notes Release 5.0.11 July 24, 2002 From: Branislav Selic Date: Sun, 7 Sep 2003 09:27:51 -0400 X-MIMETrack: Serialize by Router on D25ML05/25/M/IBM(Release 6.0.2CF1|June 9, 2003) at 09/07/2003 09:27:53, Serialize complete at 09/07/2003 09:27:53 Properties UseCase::extend and UseCase::include subset property Namespace::ownedMember, but classes Extend and Include are not types of NamedElement. Bran Selic IBM Software Group -- Rational Software 770 Palladium Drive Kanata, Ontario, Canada K2V 1C8 ph. (613) 591-7915 fax (613) 599-3912 e-mail: bselic@ca.ibm.com