Issue 4464: Component notation: logical compartments (uml2-superstructure-ftf) Source: Pivot Point (Mr. Cris Kobryn, ) Nature: Uncategorized Issue Severity: Minor Summary: The current component notation does not provide for separate logical compartments when nesting implementation classes and artifacts in a component, as shown in Notation, Figure 3-95. It would be useful to provide separate logical compartments for this, as we do for subsystems and classes. Resolution: Revised Text: Actions taken: August 3, 2001: received issue March 9, 2005: closed issue Discussion: Subsystems and components have been harmonized in UML 2.0 (with logical compartments removed from both due to scalability issues), so this issue is no longer applicable. End of Annotations:===== Date: Fri, 03 Aug 2001 13:05:24 -0700 From: Cris Kobryn Subject: UML 1.5 issues: component notation and compliance To: issues@omg.org Cc: Juergen Boldt , Guus Ramackers Reply-to: Cris.Kobryn@telelogic.com Message-id: MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Content-transfer-encoding: 7BIT Importance: Normal X-Priority: 3 (Normal) X-MSMail-priority: Normal Content-Type: text/plain; charset=iso-8859-1 X-UIDL: -AZ!!hc]!!U19!!4W"!! The following are some component notation and compliance issues which should be addressed in the next minor revision: _________________________________________ Descriptor: Component notation: logical compartments Reference: UML 1.4, Notation, Fig. 3-95, p. 3-176 Nature: Typo Severity: Medium Summary: The current component notation does not provide for separate logical compartments when nesting implementation classes and artifacts in a component, as shown in Notation, Figure 3-95. It would be useful to provide separate logical compartments for this, as we do for subsystems and classes.