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

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

      Benefit Hypothesis from PI14
      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
      Benefit Hypothesis from PI14 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

      Acceptance criteria from PI14

      • 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
      Acceptance criteria from PI14 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.  
    • 2
    • 2
    • 0

    • System Version REL-92 SKA-MID-MVP v0.1.0-experiment

    • Team_BUTTONS
    • Sprint 3
    • Hide
      Show
      A Code Review was undertaken and all recommendations from this addressed The OET BDD tests (telescope on, resource allocation and de-allocation, create sbi and telescope standby) now pass in the SKAMPI CI/CD pipeline and the OET branch has been merged into SKAMPI The relevant XRAY tests are here: https://jira.skatelescope.org/browse/XTP-776 The passing tests can also be seen here: https://jira.skatelescope.org/browse/VTS-225 Documentation detailing the use of the OET command-line interface is available here: https://developer.skao.int/projects/ska-oso-oet/en/latest/cli.html .
    • 15.6
    • Stories Completed, Integrated, Solution Intent Updated, BDD Testing Passes (no errors), Outcomes Reviewed, NFRS met, Demonstrated, Satisfies Acceptance Criteria, Accepted by FO

    • PI24 - UNCOVERED

    • Team_BUTTONS

    Description

      CLONE of SP-2356:

      Outcomes from SP-2356:

      • 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.
        Work moved to PI15 in CLONE Feature:

      <TBD>

      Description from PI14
      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

          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-2356 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
          Is delivered by

          System Version - System releases - ie MID, LOW SW. Configured releases of SKAMPI REL-92 SKA-MID-MVP v0.1.0-experiment

          • Discarded
          mentioned in

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Structure

            Activity

              People

                a.bridger Bridger, Alan
                Adam.Avison Avison, Adam
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Feature Progress

                  Story Point Burn-up: (100.00%)

                  Feature Estimate: 2.0

                  IssuesStory Points
                  To Do00.0
                  In Progress   00.0
                  Complete415.0
                  Total415.0

                  Dates

                    Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel