SeriesSlot Annotations -- Development Estimates -- February
2007 -- HIT REFRESH
See also prior design
document and screenshots
Current status: GUI and data-model support is functional (with about 90% of the documented functionality) -- but without any persistence (i.e. model file store) or any other I/O.
The Design and High-Level design document was updated with a new section describing the following support:
Item | Est. Days (Phil) |
Completed | Task Description |
1.1 | 0.5 | Open SeriesSlot Dialogs: Support for the optionally-shown Annotation Item Column in Export Copy. | |
1.2 | 1.0 | Limited support (Icon and Tooltip Only) for the multiple-Slot applications of the SlotQtDlg classes -- similar to the support implemented for the SCT. That is, for the Edit Account and Object Account Summary dialogs. (Note: The tooltip part of this is already working, as a function of the existing mechanism in these classes). | |
1.3 | negl. | Clear Workspace needs to delete the Annotation Groups. | |
1.4 | 1.5 | Editable Slot Notes Column -- editable only when the Slot is associated with exactly one Annotation Group. | |
1.5 | 1.0 | Additional testing | |
Subtotal: | 4.0 | [days] |
Note: The only DMI support considered here is for the "old-style" DMIs (External Program / Control File-based). Exporting or importing annotation data with the "Direct Database Connection" DMI seems to not be supportable in DSS (no analogous properties are available). This may also be true for HDB, but in any case, would need substantial analysis.
Item | Est. Days (Bill)* |
Completed | Task Description |
2.0 | --- | Model File Persistence, and SimObj & Account import/export | |
2.1 | 0.5 | Write data | |
2.2 | 2.0 | Read / Parse Data (using Tcl) | |
2.3 | 1.0 | GUI Support -- presenting options, reporting results, error detections. | |
3.0 | --- | DMI support (only External Program / Control File-based DMIs). | |
3.1 | 1.0 | Bill
and I will handle this in the course of development |
Format design requirements. The format would have to be worked out with users since the DMI programs they maintain would have to support the format. |
3.2 | 0.5 | [Bill] |
DMI Control File: Add keyword for annotations. |
3.3 | 1.0 | 3-1-2007 | Write data (from various contexts) |
3.4 | 3.0 | Read / Parse Data (requires custom coded parsing, as no special parsing technology is used). | |
3.5 | 1.0 | There
really isn't any GUI work to do. |
GUI Support -- presenting options, reporting results, error detections. |
Subtotal: | 10 | [days] |
*Estimates devised with Bill. Phil could do this work too, but would need Bill
for consultation.
---