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

Observational Execution of the basic instruction set of an OET script on Mid

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

Details

    • Obs Mgt & Controls
    • Hide

      The control over a basic observation in the context of the Mid telescope is working and ready to use for executing tests on Mid telescope components.

      Show
      The control over a basic observation in the context of the Mid telescope is working and ready to use for executing tests on Mid telescope components.
    • Hide

      A set of passing BDD tests for assigning resources configuring and running a scan; reflected on a Jira test in XRAY, and traced back to the Execute Observation Use Case.

      A documented API that ensures a client has all the necessary information to execute the control of Telescope observations.

      Show
      A set of passing BDD tests for assigning resources configuring and running a scan; reflected on a Jira test in XRAY, and traced back to the Execute Observation Use Case. A documented API that ensures a client has all the necessary information to execute the control of Telescope observations.
    • 3
    • 3
    • 40
    • 13.333

    • Flow USE-39 Operate and Monitor MID Telescope - Basic Flow

    • Team_BUTTONS
    • Sprint 5
    • Hide
      • A branch for reintegration of the OET into SKAMPI was created
      • A number of BDD tests have been written, but not all are passing, for various reasons
      • The work for this ticket was demonstrated on Thursday 26 May
      • Cross-team code review will take place early in PI15 and the OET will then finally be reintegrated into SKAMPI.
      Show
      A branch for reintegration of the OET into SKAMPI was created A number of BDD tests have been written, but not all are passing, for various reasons The work for this ticket was demonstrated on Thursday 26 May Cross-team code review will take place early in PI15 and the OET will then finally be reintegrated into SKAMPI.
    • 14.6
    • Stories Completed, Outcomes Reviewed, Demonstrated, Accepted by FO

    Description

      This feature has been reduced in scope as a consequence of TMC limitations:

      1. Functionality needed will only be that to do with the allocation of resources.

      Deliver the basic (but verified/validated and fully documented) script execution functionality for OET when running in the Mid telescope that allows for the following basic steps to be done.

      1) the allocation of resources to a subarray (EMPTY->IDLE)

      2) the configuration of that subarray for a scan (IDLE>READY) and-

      3) the running of an observational scan using a basic representative set of configurational data.

      Note the basic flow does not currently have to allow for failure scenarios but the design and implementation should ensure that this functionality can be added iteratively without requiring re-design or changes.

       

      Note this feature also includes the general planning/reviews and design overhead to achieve the above goals and to this end subsumes the following features originally placed on the board:

      https://jira.skatelescope.org/browse/SP-2116

      https://jira.skatelescope.org/browse/SP-2327

      Attachments

        Issue Links

          Child Of

          Enabler - An Enabler supports the activities needed to extend the Architectural Runway to provide future business functionality. These include exploration, architecture, infrastructure, and compliance. SS-90 Reintegrate missing components into SKAMPI

          • Must have - Items labelled as "Must have" are critical to the current delivery timebox in order for it to be a success.
          • Done
          clones

          Enabler - An Enabler supports the activities needed to extend the Architectural Runway to provide future business functionality. These include exploration, architecture, infrastructure, and compliance. SP-2195 Re-enable OET deployment and testing with SKAMPI

          • Must have - Items labelled as "Must have" are critical to the current delivery timebox in order for it to be a success.
          • 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-2619 CLONE - Observational Execution of the basic instruction set of an OET script on Mid

          • Must have - Items labelled as "Must have" are critical to the current delivery timebox in order for it to be a success.
          • 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-2116 Implement changes identified in components interfacing to TMC post SS-82

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

          Enabler - An Enabler supports the activities needed to extend the Architectural Runway to provide future business functionality. These include exploration, architecture, infrastructure, and compliance. SP-2327 CLONE - Re-enable OET deployment and testing with SKAMPI

          • Must have - Items labelled as "Must have" are critical to the current delivery timebox in order for it to be a success.
          • Discarded
          mentioned in

          Page Loading...

          Page Loading...

          Structure

            Activity

              People

                a.bridger Bridger, Alan
                g.leroux Le Roux, Gerhard [X] (Inactive)
                Votes:
                0 Vote for this issue
                Watchers:
                2 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
                  Complete1024.0
                  Total1024.0

                  Dates

                    Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel