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

Observational Scan (including configure) for TMC in Mid

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

Details

    • Feature
    • Won't have (this time)
    • PI15
    • None
    • Obs Mgt & Controls
    • Hide

      The basic flow for an observation execution can be run. (note this ability is dependent on the successful implementation of https://jira.skatelescope.org/browse/SP-2402)

      Show
      The basic flow for an observation execution can be run. (note this ability is dependent on the successful implementation of  https://jira.skatelescope.org/browse/SP-2402 )
    • Hide

      A set of passing BDD tests for switching on and assigning resources; 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 switch on telescope elements and assign resources to a subarray.

      Show
      A set of passing BDD tests for switching on and assigning resources; 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 switch on telescope elements and assign resources to a subarray.
    • 1
    • 40
    • 40

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

    • 16.3

    • PI24 - UNCOVERED

    Description

      Deliver the basic (but verified/validated and fully documented) observational control functionality for (TMC in the Low ) allowing for

      1) Configuring a generic scan to run for 1-second -> CONFIGURING -> READY

      2) Running the configured scan READY -> SCANNING -> READY

      In particular, this feature shall depend on the necessary refactoring work to ensure the CSP leaf node can allow for a scan to be configured and run as well as The Dish leaf Node. (see https://jira.skatelescope.org/browse/SP-2301)

      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.

      This Feature subsumes part of the original features below:

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

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

      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-2364 SDP Integration in an end-to-end software deployment

          • 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

          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-2115 Integration and regression testing of the TMC MVP post SS-82; Identify bugs to be fixed

          • Must have - Items labelled as "Must have" are critical to the current delivery timebox in order for it to be a success.
          • 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-1687 Refactor Test Cases for TMC code refactoring

          • 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
          mentioned in

          Page Loading...

          Structure

            Activity

              People

                g.leroux Le Roux, Gerhard [X] (Inactive)
                g.leroux Le Roux, Gerhard [X] (Inactive)
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Feature Progress

                  Story Point Burn-up: (0%)

                  Feature Estimate: 1.0

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

                  Dates

                    Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel