UML2.1.2: contains content quoted from the OMG UML specification documents for educational purposes.
[note] Submitted by webel on Tue, 13/01/2009 - 16:10
‹ UML2 note: this OBSOLETE trick of pseudo-nesting of Component classifiers was a workaround for older versions of MagicDraw UML; since 2007 MagicDraw UML correctly supports deep nesting of composite structures with parts and ports.
up
UML2: this diagram does NOT show connected "instances", it only shows "Dependency wiring" of proivided/required Interface contracts, i.e., where valid connections may be made when these EncapsulatedClassifiers are used in a higher context ! ›
- Printer-friendly version
- Login to post comments
Zones
- IT zone
- UML zone
- Galleries meta-index: overview of all UML and SysML gallery groups
- UML Parsing Analysis zone
- UML tools zone
- MagicDraw UML zone
- Galleries index: Webel's contribution to the MagicDraw UML and SysML online eSchool
- Video screencast: YouTube: MagicDraw UML: SysML Plugin active validation tutorial
- Notes
- Deep nesting of Property symbols in structure compartments and composite structure diagrams is permitted in some UML tools, and formally supported in SysML Internal Block Diagrams.
- MagicDraw UML permits display of InstanceSpecifications on Composite Structure Diagrams (and SysML Internal Block Diagrams)
- UML note: OBSOLETE: pre UML2 !
- UML note: from old version of MagicDraw UML, pre-UML2, no InformationFlows, no true Composite Structure, no Ports.
- UML note: these diagrams from 2005 contain workarounds for some limitations in UML2 composite structure support in an earlier version MD 10 EAP Beta2 of MagicDraw UML.
- UML2 note: this OBSOLETE trick of pseudo-nesting of Component classifiers was a workaround for older versions of MagicDraw UML; since 2007 MagicDraw UML correctly supports deep nesting of composite structures with parts and ports.
- UML2.1.2: contains content quoted from the OMG UML specification documents for educational purposes.
- UML2: this diagram does NOT show connected "instances", it only shows "Dependency wiring" of proivided/required Interface contracts, i.e., where valid connections may be made when these EncapsulatedClassifiers are used in a higher context !
- UML: consider using InformationFlow for data token types and to indicate direction on Association/Connector.
- Rational Software Architect (RSA) zone
- MagicDraw UML zone
- UML: notes
- Galleries index: some miscellaneous (and curious) UML galleries
- Tutorial: some UML modelling and diagramming tips, tricks, and best practices
- Tutorial: the UML2 Component as a logical and graphical «wrapper» (MagicDraw-centric)
- UML for Software Development
- Gallery: Tutorial: port-based software engineering with UML and Java
- Towards Executable UML
- Animated and simulated UML
- Java zone
- XML zone
- Drupal CMS zone
- SysML zone
- C++ zone
- Eclipse zone
- In MagicDraw UML, classifier-level sterotypes "show through" on symbols of instance level properties, unless that property has a visible (non-hidden) instance-level stereotype applied.
- Netbeans IDE zone
- Puredata synthesis zone
- Shibboleth zone
- Snippet-driven engineering: a meta-process for documentation-driven software and systems engineering
- Tools and Tips
- UML zone


















