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

Update Dish to TMC ICD to match the design

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

Details

    • True
    • MID ART
    • Hide

      Reduced risk for Dish LMC and TMC MID integration. 

      Better understanding of the required functionality.

      Solution intent is maintained.

      Show
      Reduced risk for Dish LMC and TMC MID integration.  Better understanding of the required functionality. Solution intent is maintained.
    • Hide

      A draft revision of the TM MID to Dish ICD which matches the current design   exists in the Solution Intent in Google drive. The changes are tracked, to allow for easy identification of changes and additions.  The updated version is aligned with the current version of the design, contains definition and description of the functionality as planned. Where current implementation does not match planned functionality that may be indicated.

      Show
      A draft revision of the TM MID to Dish ICD which matches the current design   exists in the Solution Intent in Google drive. The changes are tracked, to allow for easy identification of changes and additions.  The updated version is aligned with the current version of the design, contains definition and description of the functionality as planned. Where current implementation does not match planned functionality that may be indicated.
    • 3
    • 3
    • 3
    • 1
    • Team_KAROO
    • Sprint 5
    • PI24 - UNCOVERED

    • Demo_24.5 Team_KAROO
    • Mid G2

    Description

      TMC to DISH ICD has not been kept up to date with the evolution of the design and is outdated; it cannot be used as a base of the development not for development of the test plans.   An updated document would be useful for integration team, and both for DISH LMC  team and TMC team.

      A historic record of the changes and discussions is available via links provided below, but interface evolved further,  at this time we do not have a colmplete record of the changes needed.  The team will have to consult the code, relevant architectural decisions as well as design documents for dish sub-systems  to come up with a more complete description of this interface.

      Historic record:

      Architects, Dish group, Karoo and NCRA agreed on resolution for the issues raised in TMC MID - Dish LMC Interaction.

      Where do you observe the technical debt in the development artefacts?

      • SKA‐TEL‐SKO‐0000150, SKA1-MID Interface Control Document TM to DSH, Rev 04

      What remedial work is needed to eliminate the debt? Describe the rework needed.

      • ICD needs to be updated to reflect the latest CS Guidelines and ADRs.

      Why is it important to address this technical debt item i.e. consequences or costs accrued by this item?
      Consequence of technical debt is deviation of Dish LMC from CS Guidelines and incompatibility of TMC MID and Dish LMC with regards to implementation of the CS Guidelines.

      • An ECP needs to be raised to ensure all affected parties are consulted.

      Attachments

        Issue Links

          Structure

            Activity

              People

                s.vrcic Vrcic, Sonja
                p.swart Swart, Paul [X] (Inactive)
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Feature Progress

                  Story Point Burn-up: (0%)

                  Feature Estimate: 3.0

                  IssuesStory Points
                  To Do00.0
                  In Progress   00.0
                  Complete00.0
                  Total00.0

                  Dates

                    Created:
                    Updated:

                    Structure Helper Panel