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

Fix & test "echos" from LMC_base_class upgrade (0.11)

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

Details

    • Feature
    • Must have
    • PI12
    • None
    • Obs Mgt & Controls
    • Hide

      Completion of this feature would allow, if desired, to resume the on going integration of MCCS into TMC low from the PI following that in which this feature is completed.

      Show
      Completion of this feature would allow, if desired, to resume the on going integration of MCCS into TMC low from the PI following that in which this feature is completed.
    • Hide

      By the end of this PI ska-low-mccs should be in a position to make an operationally stable release of the software which can at least interface with the TMC Low.

      Show
      By the end of this PI ska-low-mccs should be in a position to make an operationally stable release of the software which can at least interface with the TMC Low.
    • 0.5
    • 1
    • 40
    • 80
    • Team_MCCS
    • Sprint 5
    • Hide

      The purpose of this feature was to assess the impact of adopting v0.11 base_classes upon MCCS. Following this we used this feature to make adjustments and corrections in order to restore MCCS to what was required.

      A number of changes where made to management functions, and choreography was spiked and implemented. The last of the major typehints implementations was completed and some refactoring in preparation for deployment of MCCS onto AAVS was done.

      Clone SP-2076 will continue to further stablize the MCCS code base as we work toward the AAVS deployment.

      Show
      The purpose of this feature was to assess the impact of adopting v0.11 base_classes upon MCCS. Following this we used this feature to make adjustments and corrections in order to restore MCCS to what was required. A number of changes where made to management functions, and choreography was spiked and implemented. The last of the major typehints implementations was completed and some refactoring in preparation for deployment of MCCS onto AAVS was done. Clone SP-2076 will continue to further stablize the MCCS code base as we work toward the AAVS deployment.
    • 12.6
    • Stories Completed, Integrated, Outcomes Reviewed, NFRS met, Demonstrated, Satisfies Acceptance Criteria, Accepted by FO

    Description

      During PI11, MCCS undertook a significant task through SP-1717 to refactor its ska-low-mccs code base to use version 0.11 of the base-classes. Many benefits were realised through this, including the introduction of asynchronisity and a step change in stability during operation.  However due to the scale of the effort involved in the refactor there was concern raised that some fundamental functions may have been lost or not verified as operating as intended.

       

      The purpose of this feature is to take a closer more critical look at ska-low-mccs post v0.11 adoption and initially identify key areas where there is a need to verifiy correct / desirable operation of MCCS against the design, ADR and ICD. This idenification exercise should then progress toward the execution, verification and where necessary rectification of issues.

      Attachments

        Issue Links

          Structure

            Activity

              People

                v.mohile Mohile, Vivek
                r.braddock Braddock, Ralph
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Feature Progress

                  Story Point Burn-up: (100.00%)

                  Feature Estimate: 0.5

                  IssuesStory Points
                  To Do00.0
                  In Progress   00.0
                  Complete615.0
                  Total615.0

                  Dates

                    Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel