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

Initial SDP AA0.5 visibility receive workflow and test preparation

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

Details

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

      Being able to receive and capture visibilities in Measurement Set format is a critical function for the SDP AA0.5 system.

      As such, formalising the release of this workflow and ensuring that an integrated and tested version is ready as possible for use at AA0.5, and in the PSI and ITF environments before that, is valuable to AVI and commissioning stakeholders.

      Show
      Being able to receive and capture visibilities in Measurement Set format is a critical function for the SDP AA0.5 system. As such, formalising the release of this workflow and ensuring that an integrated and tested version is ready as possible for use at AA0.5, and in the PSI and ITF environments before that, is valuable to AVI and commissioning stakeholders.
    • Hide
      • Well defined release of an initial version of the visibility receive workflow, tested both with the SDP system and with the deployment of SKA software using SKAMPI. 
        • Release artefacts in CAR, release page in Jira setting up a changelog for future updates
        • Support creating the JIRA release ticket
      • Acceptance tests added for both happy and sad routes (preferably using Gherkin language and exposed as Jira XRay tests)
      • Automated workflow (component) tests for testing NFRs related to performance and robustness following work done on SP-1857 - these do not need to be executed as an end-to-end integrated solution including control interfaces
      • At least one SKA1-MID and SKA1-LOW example MS output produced by this pipeline is made available for further analysis by the SKAO system science team (in order to assess if it can be used with standard tools (CASA etc) and contains sufficient meta-data to meet the needs of commissioning tests) and to drive further work next PI if needed.
      Show
      Well defined release of an initial version of the visibility receive workflow, tested both with the SDP system and with the deployment of SKA software using SKAMPI.   Release artefacts in CAR, release page in Jira setting up a changelog for future updates Support creating the JIRA release ticket Acceptance tests added for both happy and sad routes (preferably using Gherkin language and exposed as Jira XRay tests) Automated workflow (component) tests for testing NFRs related to performance and robustness following work done on SP-1857 - these do not need to be executed as an end-to-end integrated solution including control interfaces At least one SKA1-MID and SKA1-LOW example MS output produced by this pipeline is made available for further analysis by the SKAO system science team (in order to assess if it can be used with standard tools (CASA etc) and contains sufficient meta-data to meet the needs of commissioning tests) and to drive further work next PI if needed.
    • 3
    • 3
    • 13
    • 4.333
    • Team_YANDA
    • Sprint 5
    • Hide
      • – tests added for both happy and sad routes (preferably using Gherkin language and exposed as Jira XRay tests)

      BDD test adapted to use scheduling block as input model.

      • Automated workflow (component) tests for testing NFRs related to performance and robustness following work done on SP-1857 - these do not need to be executed as an end-to-end integrated solution including control interfaces

      New python notebook added performs the basic task ipython notebook used in the demo

      • At least one SKA1-MID and SKA1-LOW example MS output produced by this pipeline is made available for further analysis by the SKAO system science team (in order to assess if it can be used with standard tools (CASA etc) and contains sufficient meta-data to meet the needs of commissioning tests) and to drive further work next PI if needed.

      SKA Low measurement sets generated still lacking many tables. But a small MS included that ran through the demo. There is still work to add more tables and perhaps test the derived parameters. 

      Measurement Set

      Show
      – tests added for both happy and sad routes (preferably using Gherkin language and exposed as Jira XRay tests) BDD test adapted to use scheduling block as input model. Automated workflow (component) tests for testing NFRs related to performance and robustness following work done on SP-1857 - these do not need to be executed as an end-to-end integrated solution including control interfaces New python notebook added performs the basic task  ipython notebook used in the demo At least one SKA1-MID and SKA1-LOW example MS output produced by this pipeline is made available for further analysis by the SKAO system science team (in order to assess if it can be used with standard tools (CASA etc) and contains sufficient meta-data to meet the needs of commissioning tests) and to drive further work next PI if needed. SKA Low measurement sets generated still lacking many tables. But a small MS included that ran through the demo. There is still work to add more tables and perhaps test the derived parameters.  Measurement Set
    • 14.4
    • Stories Completed, Demonstrated

    • PI24 - UNCOVERED

    • SPO-1448

    Description

      System Demo 12.5 demonstrated tests of failure modes for the visibility receive workflow and System Demo 12.6 demonstrated a test of the visibility receive workflow as an SDP integration test.

      This ticket is intended to further improve testability (system-level integration tests in SKAMPI, and tests that the MS written by this pipeline can be used in CASA) in preparation of a more formal release of the Visibility Receive Workflow in a future PI.

      Attachments

        Issue Links

          Child Of

          Enabler - An Enabler supports the activities needed to extend the Architectural Runway to provide future business functionality. These include exploration, architecture, infrastructure, and compliance. SS-86 Reintegrate single software components into SKAMPI

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

          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-2466 CBF-SDP emulator sends correlator data dumps

          • Won't have (this time) - Items labelled as "Won't have", have been agreed by stakeholders as the least-critical, lowest-payback items, or not appropriate at that time. As a result, "Won't have" items are not planned into the schedule for the next delivery timebox.
          • Funnel

          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-2363 Visibility Receive workflow enhancements

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

          Spike - A time limited investigation to get some knowledge SP-1825 Investigate how to automate SDP processing script testing

          • Won't have (this time) - Items labelled as "Won't have", have been agreed by stakeholders as the least-critical, lowest-payback items, or not appropriate at that time. As a result, "Won't have" items are not planned into the schedule for the next delivery timebox.
          • Funnel

          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-2149 Telescope Model Data service

          • 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-2158 Collected Execution Framework development (DALiuGE & EAGLE)

          • 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
          links to

          Web Link Measurement Set from Pipeline Run

          mentioned in

          Page Loading...

          Page Loading...

          Page Loading...

          Structure

            Activity

              People

                b.nikolic Nikolic, Bojan
                b.mort Mort, Ben
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Feature Progress

                  Story Point Burn-up: (100.00%)

                  Feature Estimate: 3.0

                  IssuesStory Points
                  To Do00.0
                  In Progress   00.0
                  Complete67.0
                  Total67.0

                  Dates

                    Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel