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

Update TMC nodes to utilise base class version 0.11.3

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

Details

    • Obs Mgt & Controls
    • Hide

      Use of up to date code allows for greater stability and allows easier integration and testing.

      Show
      Use of up to date code allows for greater stability and allows easier integration and testing.
      • TMC Nodes are updated to use the latest base classes 0.11.3 (TMC Subarray Node, SDP Master Leaf Node, SDP Subarray Leaf Node and Dish Leaf Node)
      • TMC Nodes follow state transitions of the 0.11 model.
    • 3
    • 3
    • 0
    • Team_NCRA
    • Sprint 5
    • Hide

      TMC subarray node, SDP Master Leafnode and SDP subarray nodes are refactored using the updated base classes version- 0.11.3

      Show
      TMC subarray node, SDP Master Leafnode and SDP subarray nodes are refactored using the updated base classes version- 0.11.3
    • 13.6
    • Stories Completed, Integrated, Solution Intent Updated, Satisfies Acceptance Criteria, Accepted by FO

    • PI24 - UNCOVERED

    • Cross_Team_Code_Review Team_NCRA

    Description

      Feature to update TMC Nodes to utilise v0.11.3 of the base classes. 

      Currently the future of this feature is dependent on the outcomes of ADR-52 and ADR-53.

      The refactored TMC nodes will utilize the version 0.11.3 of base classes. The scope for PI-13 targets the TMC Subarray Node, the SDP Master Leaf Node, SDP Subarray Leaf Node and the Dish Leaf Node.

       

      Attachments

        Issue Links

          is required by

          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-2262 Integration effort: End-to-End On/Off Command Test: OET → TMC → SDP

          • Won't have (this time) - Items labelled as "Won't have", have been agreed by stakeholders as the least-critical, lowest-payback items, or not appropriate at that time. As a result, "Won't have" items are not planned into the schedule for the next delivery timebox.
          • Discarded
          mentioned in

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Structure

            Activity

              People

                Adam.Avison Avison, Adam
                Adam.Avison Avison, Adam
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Feature Progress

                  Story Point Burn-up: (100.00%)

                  Feature Estimate: 3.0

                  IssuesStory Points
                  To Do00.0
                  In Progress   00.0
                  Complete25.0
                  Total25.0

                  Dates

                    Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel