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

Observational Control on CSP Mid

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

Details

    • Feature
    • Must have
    • PI14
    • None
    • Obs Mgt & Controls
    • Hide

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

      Show
      The control over a basic observation in the context of the CSP Mid is working and ready to use for executing tests on csp 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 CSP 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 CSP observations.
    • 1
    • 2.5
    • 40
    • 40

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

    • Team_CREAM
    • Sprint 4
    • Hide

      Relevant versions have been merged and tests run in master

      Show
      Relevant versions have been merged and tests run in master
    • 14.5
    • Stories Completed, Integrated, Outcomes Reviewed, Accepted by FO

    Description

      Deliver the basic (but verified/validated and fully documented) observational control functionality for CSP Mid allowing for

      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.

      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
          depends on

          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-2304 Exercise communication between CSP_MID.LMC and MID.CBF MCS

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

          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-2293 Study of reintegration of CSP into SKAMPI (time-boxed)

          • Won't have (this time) - Items labelled as "Won't have", have been agreed by stakeholders as the least-critical, lowest-payback items, or not appropriate at that time. As a result, "Won't have" items are not planned into the schedule for the next delivery timebox.
          • Discarded
          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-2303 Re-integrate CSP.LMC 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
          mentioned in

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          mentioned on

          GitLab Commit - Merge branch 'sp-2349' into 'master'

          GitLab Commit - SP-2349: added vscode back

          GitLab Commit - SP-2349: Accidently change .make subomodule, reverse change

          GitLab Commit - SP-2349: add flake8 settings

          GitLab Commit - SP-2349: add launch

          GitLab Commit - SP-2349: add semicolon

          GitLab Commit - SP-2349: change feature file for scanning check

          GitLab Commit - SP-2349: delete devcontainer

          GitLab Commit - SP-2349: delete devcontainer

          GitLab Commit - SP-2349: Fix csp jira test tags

          GitLab Commit - SP-2349: fix incorrect check before installing

          GitLab Commit - SP-2349: fix incorrect id

          GitLab Commit - SP-2349: Fix jira tag in mid csp scan test

          GitLab Commit - SP-2349: Fix startup in csp entry point

          GitLab Commit - SP-2349: ignore vscode

          GitLab Commit - SP-2349: install using poetry

          GitLab Commit - SP-2349: make pre install only in pipeline

          GitLab Commit - SP-2349: merge origin/master into sp-2349

          GitLab Commit - SP-2349: remove flake

          GitLab Commit - SP-2349: remove vscode

          GitLab Commit - SP-2349: revert back to pip

          GitLab Commit - SP-2349: Update ska-csp-lmc-mid to latest chart

          GitLab Commit - SP-2349: update skallop

          GitLab Commit - SP-2349: use env

          GitLab Merge request - CT-656 Update CSP textual Documentation of the code COMMON

          GitLab Merge request - SP-2349

          Structure

            Activity

              People

                g.leroux Le Roux, Gerhard [X] (Inactive)
                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: 1.0

                  IssuesStory Points
                  To Do00.0
                  In Progress   00.0
                  Complete717.0
                  Total717.0

                  Dates

                    Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel