Uploaded image for project: 'Data Management'
  1. Data Management
  2. DM-13225

Edit SuperTask requirements for order-independence

    Details

    • Story Points:
      2
    • Team:
      Architecture

      Description

      MagicDraw enforces alphabetic order for requirements (within a package).  This makes it impossible to define the order of the requirements as they appear.

      The existing SuperTask requirements in LDM-556 were written without realizing this and contain references to previous requirements as "above".

      It is desirable for requirements to be meaningful in isolation in any event, so this task is to clean up the language and avoid positional references.

        Attachments

          Issue Links

            Activity

            Hide
            tjenness Tim Jenness added a comment -

            I think this ticket is blocking DM-13217.

            Show
            tjenness Tim Jenness added a comment - I think this ticket is blocking DM-13217 .
            Hide
            gpdf Gregory Dubois-Felsmann added a comment -

            Ordering in MagicDraw requirements docgens is now supported. Working on providing Tim Jenness the necessary inputs - ordering and edits.

            Show
            gpdf Gregory Dubois-Felsmann added a comment - Ordering in MagicDraw requirements docgens is now supported. Working on providing Tim Jenness the necessary inputs - ordering and edits.
            Hide
            gpdf Gregory Dubois-Felsmann added a comment -

            I've completed the requested work, adding prefixes to SuperTask requirement names to define their order in the docgen, removing inappropriate relative references (e.g., "see below"), and doing some basic copyediting.

            I've also noted that DMS-MWST-REQ-0009 and DMS-MWST-REQ-0013 appear to be redundant and have proposed removing -0009, with its useful Discussion folded into -0013.

            Show
            gpdf Gregory Dubois-Felsmann added a comment - I've completed the requested work, adding prefixes to SuperTask requirement names to define their order in the docgen, removing inappropriate relative references (e.g., "see below"), and doing some basic copyediting. I've also noted that DMS-MWST-REQ-0009 and DMS-MWST-REQ-0013 appear to be redundant and have proposed removing -0009, with its useful Discussion folded into -0013.
            Hide
            gpdf Gregory Dubois-Felsmann added a comment -

            I've also supplied previously missing text for DMS-MWST-REQ-0017, based on a brief discussion on #dm-middleware:

            The Pipeline design shall provide for the construction of a Pipeline specification via two methods: through a Python API as well as through a configuration language. The Pipeline design and implementation shall therefore include a “factory” or other similar means for instantiating a Pipeline’s Python object(s) from a configuration-language specification of the Pipeline.

            Show
            gpdf Gregory Dubois-Felsmann added a comment - I've also supplied previously missing text for DMS-MWST-REQ-0017, based on a brief discussion on #dm-middleware: The Pipeline design shall provide for the construction of a Pipeline specification via two methods: through a Python API as well as through a configuration language. The Pipeline design and implementation shall therefore include a “factory” or other similar means for instantiating a Pipeline’s Python object(s) from a configuration-language specification of the Pipeline.
            Hide
            gpdf Gregory Dubois-Felsmann added a comment -

            Responded to a couple of comments from Tim Jenness with edits in MagicDraw.

            • Moved a referenced requirements ID from Specification to Discussion.
            • Clarified the use of another requirements ID in the Specification.
            • Added reference to OSS-level Provenance requirement OSS-REQ-0122.
            • Clarified that DMS-MWST-REQ-0009 is proposed for deletion, and why, and that the consequential changes have already been made to DMS-MWST-REQ-0013.
              Ready for Tim Jenness to do docgen and submit RFC.
            Show
            gpdf Gregory Dubois-Felsmann added a comment - Responded to a couple of comments from Tim Jenness with edits in MagicDraw. Moved a referenced requirements ID from Specification to Discussion. Clarified the use of another requirements ID in the Specification. Added reference to OSS-level Provenance requirement OSS-REQ-0122. Clarified that DMS-MWST-REQ-0009 is proposed for deletion, and why, and that the consequential changes have already been made to DMS-MWST-REQ-0013. Ready for Tim Jenness to do docgen and submit RFC.
            Hide
            tjenness Tim Jenness added a comment -

            RFC-473 has been filed. I merged the ticket branch to master.

            Show
            tjenness Tim Jenness added a comment - RFC-473 has been filed. I merged the ticket branch to master.
            Hide
            gpdf Gregory Dubois-Felsmann added a comment -

            RFC-473 has been submitted.

            Show
            gpdf Gregory Dubois-Felsmann added a comment - RFC-473 has been submitted.
            Hide
            gpdf Gregory Dubois-Felsmann added a comment -

            The planned work is complete; any fine-tuning will now be carried out under RFC-473.

            Show
            gpdf Gregory Dubois-Felsmann added a comment - The planned work is complete; any fine-tuning will now be carried out under RFC-473 .

              People

              • Assignee:
                gpdf Gregory Dubois-Felsmann
                Reporter:
                gpdf Gregory Dubois-Felsmann
                Reviewers:
                Tim Jenness
                Watchers:
                Gregory Dubois-Felsmann, Tim Jenness
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Summary Panel

                    Time Tracking

                    Estimated:
                    Original Estimate - Not Specified
                    Not Specified
                    Remaining:
                    Remaining Estimate - 0 minutes
                    0m
                    Logged:
                    Time Spent - 1 day, 1 hour
                    1d 1h