Uploaded image for project: 'SAFe Program'
  1. SAFe Program
  2. SP-1352

SDP PSI usage scenarios documented (and tested)

    XMLWordPrintable

    Details

    • Type: Feature
    • Status: Discarded
    • Priority: Not Assigned
    • Fix Version/s: PI10
    • Component/s: None
    • Labels:
      None
    • ARTs:
      Data Processing
    • Benefit hypothesis:
      Hide

      Maintaining a set of documented usage scenarios for the SDP functionality will greatly help focus testing and help ensure that common failures modes are not missed.

      This is also anticipated to be extremely helpful as input to documenting and testing end-to-end system behaviour where SDP is a critical element of the signal chain.

      Show
      Maintaining a set of documented usage scenarios for the SDP functionality will greatly help focus testing and help ensure that common failures modes are not missed. This is also anticipated to be extremely helpful as input to documenting and testing end-to-end system behaviour where SDP is a critical element of the signal chain.
    • Feature Points:
      2
    • WSJF:
      26.5
    • Acceptance criteria:
      Hide
      • Review and update SDP user documentation to include a description of typical usage scenarios expected to be required for PSI deployment and testing.
      • Documentation should be easily discoverable through the developer portal.
      • Provide instructions for testing these scenarios manually and/or by means of automated testing.
      • Identify and review the user documentation with at least one stakeholder not already intimately involved in the development and testing of the SDP code (ie perhaps someone from the VIOLA team or a new developer on the ART).
      • Identify and capture issues and/or UX improvements (eg on a Confluence page linked to the ticket) so that they can be acted upon in future PIs.
      Show
      Review and update SDP user documentation to include a description of typical usage scenarios expected to be required for PSI deployment and testing. Documentation should be easily discoverable through the developer portal. Provide instructions for testing these scenarios manually and/or by means of automated testing. Identify and review the user documentation with at least one stakeholder not already intimately involved in the development and testing of the SDP code (ie perhaps someone from the VIOLA team or a new developer on the ART). Identify and capture issues and/or UX improvements (eg on a Confluence page linked to the ticket) so that they can be acted upon in future PIs.
    • Overdue:
    • Outcomes:
      Hide
      Link to documentation with usage scenarios: <TODO!>
      List of issues raised or improvements identified for future work: <TODO!>
      Show
      Link to documentation with usage scenarios: <TODO!> List of issues raised or improvements identified for future work: <TODO!>
    • Story Point Burn-up:
    • Epic Link:
    • Resolved PI.Sprint:
      9.5

      Description

      All SDP PSI user/usage scenarios documented.

      Note this feature supersedes SP-1215.

      Manual testing of documented scenarios against a well-defined version of SDP is a must, automated testing is highly encouraged but may be beyond the scope of this feature given the 3FP allocation.

      Consider implementing as a contribution to the SKAMPI user documentation SP-974 (and work following from this in PI9)

      User scenarios/use cases should include but not limited to:

      • Basic start-up and health monitoring
      • Executing visibility receive workflow
      • How to view signal displays
      • How to access received data products
      • How to recover from errors

       

        Attachments

          Issue Links

            Structure

              Activity

                People

                Assignee:
                b.mort Mort, Ben
                Reporter:
                r.brederode Brederode, Ray
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                  Feature Progress

                  Story Point Burn-up: (0%)

                  Feature Estimate: 2.0

                  IssuesStory Points
                  To Do00.0
                  In Progress   00.0
                  Complete00.0
                  Total00.0

                    Dates

                    Created:
                    Updated:
                    Resolved:

                      Structure Helper Panel