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

Testing of the visibility receive workflow for AA0.5 use

Change Owns to Parent OfsSet start and due date...
    XporterXMLWordPrintable

Details

    • Feature
    • Must have
    • PI11
    • COM SDP SW
    • None
    • Data Processing
    • Hide

      Being able to capture visibility data is one of the core functions expected to be provided by SDP for AA0.5. While previous developments have resulted in a workflow that is approaching what is needed for AA0.5 use, in order to derisk this function further we need to:

      1. Testing the current visibility receive code against data rates for AA0.5 and common failure modes anticipated to be encountered (this ticket)
      2. Advancing the design, so that metadata not provided by the data stream from CSP is accessible for writing a valid MS file. (SP-1755)
      Show
      Being able to capture visibility data is one of the core functions expected to be provided by SDP for AA0.5. While previous developments have resulted in a workflow that is approaching what is needed for AA0.5 use, in order to derisk this function further we need to: Testing the current visibility receive code against data rates for AA0.5 and common failure modes anticipated to be encountered (this ticket) Advancing the design, so that metadata not provided by the data stream from CSP is accessible for writing a valid MS file. ( SP-1755 )
    • Hide
      • Develop tests required to establish if the current code meets operational resilience needed for AA0.5, taking into account of:
        • Maximum data rate with appropriate data dimensions. (MID: 4 dishes, 400MHz correlated bandwidth, 25kHz channels, LOW: 6 stations, 75 MHz correlated bandwidth, 5.4kHz channels)
        • Resilience to the partial loss of data / dropped packets streamed from the CBF
        • Resilience to repeated, long-running operation including consideration of file size and chunking for writing to MS.
        • (Stretch) Failures of other SDP services this workflow may depend on
      • TBD: Coordinated with SP-1755, move CBF-SDP Emulator (visibility receive) code into SDP subgroup in GitLab and refactor/rename to meet SKA code naming policy 
      Show
      Develop tests required to establish if the current code meets operational resilience needed for AA0.5, taking into account of: Maximum data rate with appropriate data dimensions. (MID: 4 dishes, 400MHz correlated bandwidth, 25kHz channels, LOW: 6 stations, 75 MHz correlated bandwidth, 5.4kHz channels) Resilience to the partial loss of data / dropped packets streamed from the CBF Resilience to repeated, long-running operation including consideration of file size and chunking for writing to MS. (Stretch) Failures of other SDP services this workflow may depend on TBD: Coordinated with SP-1755 , move CBF-SDP Emulator (visibility receive) code into SDP subgroup in GitLab and refactor/rename to meet SKA code naming policy 
    • 1
    • 1
    • 60
    • Team_YANDA
    • Sprint 3
    • Hide

      See comment and attached script

      Show
      See comment and attached script
    • 14.2
    • Stories Completed, Integrated, Outcomes Reviewed, NFRS met, Demonstrated, Satisfies Acceptance Criteria, Accepted by FO

    • PI22 - UNCOVERED

    Attachments

      Issue Links

        relates to

        Enabler - An Enabler supports the activities needed to extend the Architectural Runway to provide future business functionality. These include exploration, architecture, infrastructure, and compliance. SP-1755 Development of minimal telescope configuration data interface for visibility receive

        • Should have - Items labelled as "Should have" are important but not necessary for delivery in the current delivery timebox. While "Should have" items can be as important as "Must have", they are often not as time-critical or there may be another way to satisfy the requirement so that it can be held back until a future delivery timebox.
        • Done

        Feature - A Feature is a service that fulfills a stakeholder need. Each feature includes a benefit hypothesis and acceptance criteria, and is sized or split as necessary to be delivered by a single Agile Release Train (ART) in a Program Increment (PI). SP-950 Updated visibility receive workflow integrated into the SDP prototype

        • Not Assigned - Priority is not assigned yet.
        • Done

        Feature - A Feature is a service that fulfills a stakeholder need. Each feature includes a benefit hypothesis and acceptance criteria, and is sized or split as necessary to be delivered by a single Agile Release Train (ART) in a Program Increment (PI). SP-1606 CBF Emulator Integration Cleanup

        • Not Assigned - Priority is not assigned yet.
        • Done

        Feature - A Feature is a service that fulfills a stakeholder need. Each feature includes a benefit hypothesis and acceptance criteria, and is sized or split as necessary to be delivered by a single Agile Release Train (ART) in a Program Increment (PI). SP-1706 Correlator Output Packets

        • Must have - Items labelled as "Must have" are critical to the current delivery timebox in order for it to be a success.
        • Discarded

        Feature - A Feature is a service that fulfills a stakeholder need. Each feature includes a benefit hypothesis and acceptance criteria, and is sized or split as necessary to be delivered by a single Agile Release Train (ART) in a Program Increment (PI). SP-1857 Address technical debt and failure modes for SDP AA0.5 visibility receive workflow (and assocated interface emulators)

        • Must have - Items labelled as "Must have" are critical to the current delivery timebox in order for it to be a success.
        • Done

        Enabler - An Enabler supports the activities needed to extend the Architectural Runway to provide future business functionality. These include exploration, architecture, infrastructure, and compliance. SP-1656 Elaboration and consolidation of SDP happy route tests

        • Must have - Items labelled as "Must have" are critical to the current delivery timebox in order for it to be a success.
        • Discarded

        Structure

          Activity

            People

              b.mort Mort, Ben
              f.graser Graser, Ferdl
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Feature Progress

                Story Point Burn-up: (100.00%)

                Feature Estimate: 1.0

                IssuesStory Points
                To Do00.0
                In Progress   00.0
                Complete36.0
                Total36.0

                Dates

                  Created:
                  Updated:
                  Resolved:

                  Structure Helper Panel