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

Test and integrate Abort and Restart commands in Low.CBF, PST leaf node

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

Details

    • Obs Mgt & Controls
    • Hide

      Alignment to the L1 requirements.

      Ensure recoverability. 

      Show
      Alignment to the L1 requirements. Ensure recoverability. 
    • Hide

      These elements being able to stop their work and on command revert to the obsState = EMPTY state (as per the decisions in ADR-8).

      This feature will be used for piloting the new Cross Team review so teams should plan adequate time for these reviews

       

       

      Show
      These elements being able to stop their work and on command revert to the obsState = EMPTY state (as per the decisions in ADR-8 ). This feature will be used for piloting the new Cross Team review so teams should plan adequate time for these reviews    
    • 2
    • 1
    • 0.5
    • 19.5

    • PI22 - UNCOVERED

    • Team_CREAM Team_PERENTIE
    • SPO-545 SPO-560 SPO-716 SPO-863

    Description

      NOTE: In the discussion for PI17 it was suggested that this was already done in LOW.CBF; what may remain is the integration and end to end testing with LMC and TMC AND modified the title accordingly. However this would not be possible in PI17 so this feature is considered as a Could for PI18.

      -------------------------------------------------------------------------------------

      The obsState state machine for a subarray includes an Abort command that can be accepted in some obsStates. It should be possible to send an Abort command to the Subarray controller, and have the current activity stop, and all devices move to the ABORTED state. As much as possible the child devices should retain existing configurations, allowing examination of the current system state.

      From the ABORTED state it should then be possible to issue the Restart command to set all child devices to a known obsState, the EMPTY obsState, in which the subarray device has no resources assigned. See the Decision in --ADR-8--.

      This ticket clones SP-754, which is for the implemenation on the TMC side. See Feature SP-1114  for Mid.CBF Sub-array.

      Attachments

        Issue Links

          Child Of

          Capability - SAFe program capability SS-27 Implement Abort and Restart commands

          • 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
          clones

          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-754 Implement Abort and Restart commands in TMC

          • Not Assigned - Priority is not assigned yet.
          • Done
          is cloned 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-1100 Implement Abort and Restart commands in CSP.LMC

          • Not Assigned - Priority is not assigned yet.
          • Done
          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-1013 OET abort functionality

          • Not Assigned - Priority is not assigned yet.
          • Done
          relates to

          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-1269 Additional BDD scenarios for abort restart reset functionality

          • Not Assigned - Priority is not assigned yet.
          • Done

          Structure

            Activity

              People

                a.bridger Bridger, Alan
                j.santander-vela Santander-Vela, Juande
                Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Feature Progress

                  Story Point Burn-up: (0%)

                  Feature Estimate: 2.0

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

                  Dates

                    Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel