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

Separate repository / artefacts for MCCS SPS devices

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

Details

    • Obs Mgt & Controls
    • Hide

      Low-level SPS-hardware-facing parts of the MCCS are moved to their own repository, with a new CI CD pipeline working with appropriate test coverage.

      Components remaining in the MCCS repository are to be updated to work with the new environment with all tests working as before.

      The forked Subrack device from PSI Low is merged back in to the MCCS Subrack, forming a more fully-featured device with a cleaner simulator split.

      Show
      Low-level SPS-hardware-facing parts of the MCCS are moved to their own repository, with a new CI CD pipeline working with appropriate test coverage. Components remaining in the MCCS repository are to be updated to work with the new environment with all tests working as before. The forked Subrack device from PSI Low is merged back in to the MCCS Subrack, forming a more fully-featured device with a cleaner simulator split.
    • 1
    • 1
    • 0
    • Team_MCCS
    • Sprint 5
    • Hide

      Subrack and Tile devices were removed from their original home in the ska-low-mccs repo. Tile was moved into ska-low-mccs-spshw, reflecting its role as a lower-level hardware-facing device. Subrack was developed from the Viola Subrack device (with accompanying simulator), but all the functionality of of the original MCCS Subrack was restored to it.

      The ska-low-mccs-spshw artefact is now being used by Viola for automated BDD testing against TPM hardware. The tests are passing. See LOW-386.

      Using the results of SP-3008 and facility definitions for PSI-LOW a set of functional tests of the Subrack device was shown to be passing when executed on PSI-Low hardware from the CI pipeline. This is linked below, indicating "OK" for PSI-LOW environment. (Note that this includes a test marked xfail due to a firmware issue, but XRay reports this as "OK" even so)

      Show
      Subrack and Tile devices were removed from their original home in the ska-low-mccs repo. Tile was moved into ska-low-mccs-spshw, reflecting its role as a lower-level hardware-facing device. Subrack was developed from the Viola Subrack device (with accompanying simulator), but all the functionality of of the original MCCS Subrack was restored to it. The ska-low-mccs-spshw artefact is now being used by Viola for automated BDD testing against TPM hardware. The tests are passing. See LOW-386. Using the results of SP-3008 and facility definitions for PSI-LOW a set of functional tests of the Subrack device was shown to be passing when executed on PSI-Low hardware from the CI pipeline. This is linked below, indicating "OK" for PSI-LOW environment. (Note that this includes a test marked xfail due to a firmware issue, but XRay reports this as "OK" even so)
    • 17.6
    • Stories Completed, Integrated, Outcomes Reviewed, Demonstrated, Satisfies Acceptance Criteria, Accepted by FO

    • PI24 - NOTRUN

    • Team_MCCS goal_O5 mccs_firmware mccs_software
    • SPO-2126

    Description

      It has been found useful to split off various sub-components of MCCS to their own repositories within the MCCS group. This facilitates development and testing because different sub-components are less-tightly coupled.

      For this feature we will investigate / implement applying this model to the "SPS" devices.

      • Separate these parts into their own repo
      • A facility (Jira test ticket, CI pipeline step, &c) to deploy to hardware-facing environment(s) and run functional tests
      • Test results uploaded to Jira Xray

       Note that work on splitting off part of the functionality of the Station device is covered by feature SP-3154.

      Attachments

        Issue Links

          depends on

          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
          mentioned in

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Structure

            Activity

              People

                v.mohile Mohile, Vivek
                S.Melhuish Melhuish, Simon
                Votes:
                0 Vote for this issue
                Watchers:
                1 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
                  Complete2743.0
                  Total2743.0

                  Dates

                    Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel