: Public Note
Created: |
06/08/2008 00:23:29 |
Modified: |
07/01/2009 11:32:33 |
|
Project: |
|
Author: |
T. Kostic |
Version: |
1.0 |
Phase: |
1.0 |
Status: |
Proposed |
Complexity: |
Easy |
Difficulty: |
|
Priority: |
|
Multiplicity: |
|
Advanced: |
|
UUID: |
{61607353-1A38-4b12-9E86-617B4D2F0C20} |
Appears In: |
issue1126UserAttributeEtcAsCompound |
Classes in green are typical examples of classes that:<br/>- should have stereotype #lt;#lt;Compound#gt;#gt;, and,<br/>- we should be able to replace their current usage through bi-directional association with either a multi-valued attribute or a uni-directional association (it makes no sense to have the named association end on the side of e.g. Curve; CurveData need not know which Curve owns it).<br/>Usage as multi-valued attribute would simplify model and unclutter diagrams.<br/><br/>==#gt; Add #lt;#lt;Compound#gt;#gt; stereotype on classes in green.<br/>==#gt; Define attribute on owning classes which currently links to a compound, and provide doc for it, then remove association.<br/>==#gt; Remove this diagram when done.<br/>