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

Implement Abort and Restart commands in TMC

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

Details

    • Feature
    • Not Assigned
    • PI7
    • None
    • Obs Mgt & Controls
    • Hide

      Alignment to the L1 requirements.

      Ensure recoverability. 

      Show
      Alignment to the L1 requirements. Ensure recoverability. 
    • 8
    • 8
    • 3.5
    • Team_NCRA
    • Sprint 5
    • Hide

      A TMC that is able to issue Abort and Restart commands per SB/Subarray, as defined in the decision of ADR-8. Other elements being able to stop their work and on command revert to the obsState = EMPTY state (as per the decisions in ADR-8).

      Show
      A TMC that is able to issue Abort and Restart commands per SB/Subarray, as defined in the decision of ADR-8 . Other elements being able to stop their work and on command revert to the obsState = EMPTY state (as per the decisions in ADR-8 ).
    • 7.6

    • PI24 - UNCOVERED

    • Team_NCRA
    • SPO-560

    Description

      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-.

      Note that this ticket was clones SP-1094, which is for the implemenation on the CBF/PST side.

      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
          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-1094 Test and integrate Abort and Restart commands in Low.CBF, PST leaf node

          • 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.
          • Discarded

          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-755 SDP MVP can Abort a workflow

          • Not Assigned - Priority is not assigned yet.
          • Discarded
          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-826 system tests for newer "MVP"

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

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Structure

            Activity

              People

                d.espada Espada, Daniel [X] (Inactive)
                j.santander-vela Santander-Vela, Juande
                Votes:
                0 Vote for this issue
                Watchers:
                7 Start watching this issue

                Feature Progress

                  Story Point Burn-up: (100.00%)

                  Feature Estimate: 8.0

                  IssuesStory Points
                  To Do00.0
                  In Progress   00.0
                  Complete1546.0
                  Total1546.0

                  Dates

                    Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel