Issue 4667: Figure 3.8, page 21 (spem-ftf) Source: France Telecom R&D (Mr. Mariano Belaunde, mariano.belaunde@orange-ftgroup.com) Nature: Uncategorized Issue Severity: Summary: - Figure 3.8, page 21 A package cannot import a model element individually (an "Import" dependency (inherited from UML) cannot be used since the client and the supplier need to be Packages (see UML 1.4 and section 7.2) The UML association Package/importedElement/ModelElement need to be included in the SPEM_Foundation package. Resolution: see above Revised Text: Actions taken: November 7, 2001: received issue October 23, 2002: closed issue Discussion: Resolution: The SPEM spec does not imply that model elements can be imported individually. It is proposed to reject this issue End of Annotations:===== From: BELAUNDE Mariano FTRD/DTL/LAN To: spem-ftf@omg.org Subject: Issues to the SPEM document Date: Wed, 7 Nov 2001 12:43:16 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" X-UIDL: Nnl!!iMLe9;"'!!~>;!! Hi all, You will find below a list of issues regarding the current version of the SPEM specification. Regards, Mariano Belaunde France Telecom R&D ------------------------------------------------------ MAJOR issues - Figure 3.8, page 21 A package cannot import a model element individually (an "Import" dependency (inherited from UML) cannot be used since the client and the supplier need to be Packages (see UML 1.4 and section 7.2) The UML association Package/importedElement/ModelElement need to be included in the SPEM_Foundation package.