Issue 6425: UML 2 Infras./Interactions/ execution occurrence should not be abstract (uml2-superstructure-ftf) Source: Simula Research Laboratory (Mr. Bran Selic, selic(at)acm.org) Nature: Uncategorized Issue Severity: Summary: ExecutionOccurrence should not be abstract, as it has no specializations Resolution: see above Revised Text: Actions taken: November 4, 2003: received issue March 5, 2004: moved to the Superstructure FTF from Infrastructure March 8, 2005: closed issue Discussion: Change meta-model and the corresponding Figure 326,328 to make ExecutionOccurence a regular class. End of Annotations:===== ubject: UML 2 Infrastructure/Interactions/ execution occurrence should not be abstract? X-Mailer: Lotus Notes Release 6.0.2CF1 June 9, 2003 From: Branislav Selic Date: Tue, 4 Nov 2003 16:00:06 -0500 X-MIMETrack: Serialize by Router on D25ML05/25/M/IBM(Release 6.0.2CF1|June 9, 2003) at 11/04/2003 16:00:07, Serialize complete at 11/04/2003 16:00:07 ExecutionOccurrence should not be abstract, as it has no specializations 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 Issue 6425: UML 2 Infras./Interactions/ execution occurrence should not be abstract (uml2-superstructure-ftf) Source: International Business Machines (Mr. Bran Selic, bselic@ca.ibm.com) Nature: Uncategorized Issue Severity: Summary: ExecutionOccurrence should not be abstract, as it has no specializations Resolution: Revised Text: Actions taken: November 4, 2003: received issue March 5, 2004: moved to the Superstructure FTF from Infrastructure Discussion: Change meta-model and the corresponding Figure 326,328 to make ExecutionOccurence a regular class. Disposition: Resolved