Uploaded image for project: 'Release Management'
  1. Release Management
  2. REL-315

SKA-LOW v23.1-rc1

    XporterXMLWordPrintable

Details

    • System Version
    • Resolution: Unresolved
    • PI17
    • LOW Telescope
    • None

    Description

      A system release used for verification in LOW-PSI environment where CSP integration is verified.

      SUT1  in Low test plans is planning to integrate in PSI LOW.

      PSI Low chart is available with set of sub-systems being verified.

      Summary

      A system version available in order to achieve solution goal SPO-2114. The system version from PSI low is availalbe with limited integration. 

      Added

      • A ska-psi-low version 0.1.0 is published with limited integration as part of LOW-386 Enabler:
        • SPS Tango devices
        • MccsDaqReceiver
        • BDD tests against TPM hardware 
      • Integration of CSP LMC, Low CBF is successfully verified in PSI Low environment and demoed in System demo as part of feature SP-2961
      • SDP integration in PSI Low with Emulated CBF is verified successfully and demoed in System demo as part of feature SP-2932 
      • PST is separately verified for PSI Low integration (not integrated with Low CBF yet)

      Attachments

        Issue Links

          Delivers

          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-2932 SDP Receive for CSP PSI-Low Data Capture

          • Must have - Items labelled as "Must have" are critical to the current delivery timebox in order for it to be a success.
          • 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-2961 CSP.LMC integration with LOW.CBF (HW control)

          • Must have - Items labelled as "Must have" are critical to the current delivery timebox in order for it to be a success.
          • 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-3008 Monitoring and control of PSI-Low hardware using MCCS

          • 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

          Features

          Structure

            Activity

              People

                Unassigned Unassigned
                Snehal.Ujjainkar Ujjainkar, Snehal
                Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                  Created:
                  Updated:

                  Structure Helper Panel