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

DISH.LMC software evolution

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

Details

    • Feature
    • Must have
    • PI13
    • None
    • Obs Mgt & Controls
    • Hide
      • Dish LMC software is in the gitlab repository with an accepted SKA license.
      • ska-dish-lmc project in gitlab created (either by re-naming dish-lmc-prototype or by creating a new project.
      • ska-dish-lmc project layout matches https://confluence.skatelescope.org/display/SE/Standardising+Project+Structure+and+Content
      • Devices are containerized.
      • Container helm charts / images are published in Central Artefact Repository via the CI.
      • Results of the DISH.LMC component tests (at least for Dish modes and pointing) are available.
      Show
      Dish LMC software is in the gitlab repository with an accepted SKA license. ska-dish-lmc project in gitlab created (either by re-naming dish-lmc-prototype or by creating a new project. ska-dish-lmc project layout matches  https://confluence.skatelescope.org/display/SE/Standardising+Project+Structure+and+Content Devices are containerized. Container helm charts / images are published in Central Artefact Repository via the CI. Results of the DISH.LMC component tests (at least for Dish modes and pointing) are available.
    • 2
    • 2
    • 13
    • 6.5

    • Sub-system Version REL-38 Dish LMC v1.0.0

    • Team_KAROO
    • Sprint 5
    • Hide
      Show
      ska-dish-lmc  Gitlab repository created. ska-dish-lmc  is updated to SKA Standardising Project Structure and Content SKA Dish LMC TANGO devices are containerised. Container helm charts / images are published in Central Artefact Repository via the CI. Results of Dish LMC confidence tests and acceptance tests for Dish modes are available and inform the Dish LMC Roadmap  (see  SP-2357 ).
    • 13.6
    • Stories Completed, Outcomes Reviewed, Satisfies Acceptance Criteria, Accepted by FO

    • PI24 - UNCOVERED

    • DISH Team_KAROO

    Description

      Following the work in SP-1809 and SP-1810 commence software development for the DISH.LMC.

      Initial work to improve compliance of Dish LMC software with the SKA Software Quality standards:

      • license
      • gitlab repository
      • development environment helm charts
      • containerisation
      • artefact repository
      • integration tests (Gherkin) for Dish LMC (Python)

      Attachments

        Issue Links

          is cloned by

          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-2357 DISH.LMC software evolution

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

          Sub-system Version - A version of a sub-system, used in the Release Management and Configuration Management process REL-38 Dish LMC v1.0.0

          • Released
          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-2231 Continue System Integration Test 1 Definition MID PSI

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

          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-1810 DISH.LMC interface with Dish Structure

          • 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-2123 DISH.LMC interface with Dish Structure (Part 2)

          • 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-1809 DSH LMC Roadmap

          • Could have - Items labelled as "Could have" are desirable but not necessary and could improve the user experience or customer satisfaction for a little development cost. These will typically be included if time and resources permit.
          • Done
          mentioned in

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          mentioned on

          GitLab Merge request - SAR-330 Updated artefact repo links, included Gitlab CI templates, removed docker...

          Structure

            Activity

              People

                s.vrcic Vrcic, Sonja
                s.vrcic Vrcic, Sonja
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Feature Progress

                  Story Point Burn-up: (100.00%)

                  Feature Estimate: 2.0

                  IssuesStory Points
                  To Do00.0
                  In Progress   00.0
                  Complete48.0
                  Total48.0

                  Dates

                    Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel