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

Continue System Integration Test 1 Definition MID PSI

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

Details

    • Enabler
    • Must have
    • PI13
    • None
    • Services
    • 2
    • 2
    • 0
    • Team_ATLAS
    • Hide
      Show
      Created XTP-4804 (Test Plan for PI14) Features identified by OMC & DP ARTs for PI14 See SS-90: Reintegrate missing components into SKAMPI - Atlas will be involved during the meeting to provide guidance on priorities.
    • PI24 - UNCOVERED

    • Team_ATLAS

    Description

      This is a clone of SP-1939 - defining the first System Integration Test at the Mid PSI, based on product functionality planned to be integrated from the MID AIV Product Integration plan.

      During PI12 some progress was made (see outcomes of SP-1939)

      We needed to finalise the high level System Integration Test definition page:

      1. Complete Table info:
        1. Availability ETA
        2. Teams involved
        3. Release versions aimed for SUT
      2. Finalise range of integration and system tests
      3. Update MID Products for SI Plan up to AA0.5.

      Importantly, we needed to influence the Roadmaps of the DP & OMC ART development work. This was achieved.

      For the current work (PI13), the following details form the background:

      Following the bootstrap meeting for https://confluence.skatelescope.org/display/SE/SS-86+Reintegrate+software+components+into+SKAMPI, it was realised that driving the order and functionality aimed for during the reintegration of single Components into SKAMPI could be driven using this System Integration Test definition.

      Process for defining Tests from Use Cases

      Identifying a (set of) Use Case(s), linking the Use Case(s) to Requirements that can be tested using a Test Plan which consists of the End-to-end Tests, should be the main aim for this Feature during PI13, so that the Product Management Teams are able to focus the Features defined for future PI's from the Requirements that are tested.

      The specific scenarios to be used to put boundaries around the set of functionalities required by the end of PI13, will be Configuring of a Subarray:

      This is part of the Operate & Monitor Use Case (as indicated in https://confluence.skatelescope.org/display/SE/PSI+MID+System+Integration+Test+1

      VIOLA Reference Planning

      Refer to the simple scenario Startup Telescope for steps in this process: https://confluence.skatelescope.org/display/PEOS/AA0.5+Startup+LOW+Telescope+Scenario

      The stickies shown in https://miro.com/app/board/o9J_lrdwjCU=/?moveToWidget=3074457365565766831&cot=14 show the order of planned activities as well.

      Attachments

        Issue Links

          Structure

            Activity

              People

                X.Farr Farr, Xandri
                A.DeBeer De Beer, Adriaan
                Votes:
                0 Vote for this issue
                Watchers:
                6 Start watching this issue

                Feature Progress

                  Story Point Burn-up: (0%)

                  Feature Estimate: 2.0

                  IssuesStory Points
                  To Do32.0
                  In Progress   00.0
                  Complete10.0
                  Total42.0

                  Dates

                    Created:
                    Updated:

                    Structure Helper Panel