Collection of DM subsystem updates to LDM-240 for all project years
READY FOR INTERNAL REVIEW
Preliminary version of LDM-240 merge
A cut/paste error in the row labels for 02C.01.02 (SQuaRE) is corrected in v33 of LDM-240, uploaded here and on Docushare.
A slightly more polished version has been uploaded here and on Docushare: LDM-240, internal version v32. This is meant to be used for a full internal review. The Docushare preferred version remains v26 pending the completion of this update cycle and the necessary TCT and JK/MJ action.
A new version is available with the posted updates from AP, DRP, and SUI, together with privately received updates from Kian-Tat Lim on interfaces, Frossie Economou on SQuaRE, and Jeff Kantor on networking and integration milestones. I have not been able to do an obsessive proofread of this version yet, and Jeff's addition of FY21 has not been carried through completely to all tabs.
I have merged the available inputs into a new version of LDM-240, internal version v29. This applies the WBS changes from LCR-343. Initial inputs from 02C.01, 02C.03, and 02C.09 are still needed; I encourage people to apply them to v29 now rather than continue to work with an old version. The old "Use Cases" tab has been removed and the main roadmap tab is now called "Milestone Roadmap", per Jeff Kantor's future plan for this document, and the "Dependencies" tab is now called just that. LDM-240 v29 is available as an upload to this page and as Docushare version 17. The Docushare preferred version remains v26 pending the completion of this update cycle and the necessary TCT and JK/MJ action.
To be explicit, please use v29 as your base and use v29_(string) in your filename and the internal version number, if you need to create a new version. To request minor changes, you can also just post comments to this Confluence page.
The reference copy of LDM-240 to begin this process is internal version v27, available in Docushare and as an attachment to this page. v27 differs from the March 20th baseline of v26 only in that all the missing WBS items concerning hardware, networking, and integration have been added to 02C.07, 02C.08, and 02C.09.
Subsystems are asked to review and update their rows (only) in the two tabs "Software Development Roadmap" and "Dependencies (transposed)". Note that the dependency rows for WBS item X should record, in column Y, the other DM WBS components' release versions that version Y of X needs - that is, you record what you depend on, and how that evolves, not what depends on you. It is now possible, and useful, for you to record dependencies against the newly added hardware and networking WBS items.
It is acceptable to suggest changes to WBS item names, or even additions or changes to the structure. This is easiest at the fourth level and below, though if a significant increase in clarity is achieved by changes at the third level, they can be considered.
If you spot the need for changes to other rows, please alert the CAM for that subsystem of that and have the changes come through their update. This will help ensure a consistent understanding of the plan.
For this update cycle, you are also invited to suggest changes or additions to the Key Performance Metrics tab.
The "SW Dev Roadmap - Use Cases" tab should not be edited. The intent is that this be replaced by a representation of the traceability of JIRA Agile Epics to the Roadmap entries.
When you have a draft, please update the version string in cell I1 of "Software Development Roadmap" to something like "v27_(string)", and upload a copy to this page. All the updates will be collected centrally and edited into a new common version. We appreciate your patience with this rather old-fashioned process and are looking for better tools for future cycles: - RFC-17Getting issue details... STATUS .
Reference material
Action items
(Due dates are from DMLT meeting minutes of recent weeks.)
- Frossie Economou Provide first pass of updates to SQuaRE sections in 02C.01; analyze 02C.07.03.01 for parts that should move to SQuaRE
- Gregory Dubois-Felsmann, Frossie Economou Provide first pass of updates to Level 3, 02C.01.02.02
- Kian-Tat Lim, Gregory Dubois-Felsmann Determine what, if anything, is worth mentioning in the 02C.02 (Systems Engineering) section
- Simon Krughoff Provide first pass of updates to Alert Production (UW), 02C.03
- John Swinbank Provide first pass of updates to Data Release Production (Princeton), 02C.04
- Unknown User (ciardi), Unknown User (xiuqin) Provide first pass of updates to SUI (IPAC), 02C.05
- Jacek Becla Provide first pass of updates to Databases (SLAC), 02C.06
- Donald Petravick, Margaret Gelman Provide first pass of updates to NCSA sections, 02C.07 and 02C.08
- Jeff Kantor, Unknown User (rlambert) Provide information for NOAO (networking) rows, 02C.08.03
- Mario Juric Determine what, if anything, is worth mentioning in the 02C.09 (Integration) section
- Gregory Dubois-Felsmann, Kian-Tat Lim Update external interface information
- Mario Juric, Kian-Tat Lim Update release goals, data in, data out
- Gregory Dubois-Felsmann First pass of integration of inputs
- Gregory Dubois-Felsmann Second pass of integration of inputs (esp. 02C.01, 02C.03, 02C.09)
- Mario Juric, Kian-Tat Lim Review integration of inputs
Subsystem input files
1 Comment
Gregory Dubois-Felsmann
Marked all action items as complete. Carried forward a question to Slack #dm-camelot about how dependencies will be modeled after the re-plan.