: Public Note
Created: |
9/29/2021 4:30:50 PM |
Modified: |
2/15/2022 11:40:37 AM |
|
Project: |
|
Author: |
1362763084C |
Version: |
1.0 |
Phase: |
1.0 |
Status: |
Proposed |
Complexity: |
Easy |
Difficulty: |
|
Priority: |
|
Multiplicity: |
|
Advanced: |
|
UUID: |
{F40B9B2B-8843-4d91-A82D-64ABE9CB17D6} |
Appears In: |
Roll-Up Patterns |
This rollup pattern is built consistent with similar work done in MagicDraw/Cameo Systems Modeler. Cameo provides a menu operation to apply a rollup pattern, which Sparx EA does not have. The block elements in the rollup are in the typical tree structure, and when the pattern is applied to the tree, the individual blocks indicate that they are "redefined" and "subsetted" by the rollup pattern. Search YouTube for Cameo Rollup Pattern. You'll get several examples.<br/><br/>To get this to look reasonably right, I had to make the constraint a property of the RollUpPattern, but notice this was not done using the composite (whole-part) aggregation relationship. For some reason using that relationship didn't work as expected. <br/><br/>On the system side it will be used to roll up system parametrics like weight, various power limits (peak and average), maybe even current limits (in-rush, quiescent, etc.). In the programmatic side (the business process model) this can be used with the WBS elements to roll up cost (in labor hours) and management reserve (again in labor hours). The DateRange will be used to roll up schedule information and as such has a distinctly different set of constraint equations which are really conditional inequalities. Additionally, if desired, component cost could also be captured on the system side for "as built" systems, providing a system cost breakdown, and supported by the same type of roll-up pattern. <br/>