: Public Note
Created: |
08/01/2011 13:30:04 |
Modified: |
09/01/2011 01:09:53 |
|
Project: |
|
Author: |
T. Kostic |
Version: |
1.0 |
Phase: |
1.0 |
Status: |
Proposed |
Complexity: |
Easy |
Difficulty: |
|
Priority: |
|
Multiplicity: |
|
Advanced: |
|
UUID: |
{7B169FA4-BD27-4a06-87BF-1920A36F2FED} |
Appears In: |
13-IntervalSchedules |
[tk, 2011-01-09]<br/><ul>
<li><font color="#ff0000">Mkt_RegularIntervalSchedule is not needed (no own attributes or associations) - AreadLoadCurve can inherit directly from RegularIntervalSchedule. - </font><font color="#008040"><b>Removed Mkt_RegularIntervalSchedule added direct inheritance.</b></font></li><li>DynamicSchedule should inherit from either Regular or IrregularIntervalSchedule if it is meant to convey curves (multiple values as a function of time). Otherwise (which seems to be the intent through relationship with 1 Mkt_Measurement, so sending/receiving a single value), it should inherit just from IdentifiedObject instead of from BasicIntervalSchedule; it should probably also be renamed somehow to avoid "Schedule".</li><li>DynamicSchedule: Its attribute 'dynSchedStatus' should be renamed to e.g. 'isActive' and assigned Boolean type (according to the attribute doc). And its attribute 'dynSchedSignRev' should be renamed simply to 'reverseSign' or 'reverseDirection'.</li><li>Mkt_IrregularTimePoint: Why does it define startTime/stopTime in addition to inherited IrregularTimePoint.time? In a set of IrregularTimePoint-s, the <i>smallest</i> value of IrregularTimePoint.time <b><i>is</i></b> the Mkt_IrregularTimeInterval.startTime, and the <i>largest</i> is Mkt_IrregularTimeInterval.stopTime - then the receiving app can transform that into UTC time string. If this reasoning is correct, Mkt_IrregularTimeInterval is just superfluous and should be removed. - <font color="#008040"><b>Removed, not necessary.</b></font></li></ul>
<br/><br/>