Uploaded image for project: 'SAFe Solution'
  1. SAFe Solution
  2. SS-5

Evolutionary Prototype/SKAMPI

    XporterXMLWordPrintable

Details

    • Epic
    • Could have
    • PI8, PI9, PI10, PI11, PI12
    • None
    • Evolutionary Prototype
    • Data Processing, Obs Mgt & Controls, Services

    Description

      Epic Hypothesis Statement (https://www.scaledagileframework.com/epic/)

      For SKA software developers, the SKA engineering community, and potential SKA users
      who Are developing, testing, and integrating SKA software components
      the SKAMPI (SKA MVP Prototype Integration)
      is a set of software artefacts that represent a System-level prototype, and the accompanying integration pipelines in the Continuous Integration/Continuous Development facility
      that provides an end-to-end control system software also capable of data processing that can be deployed in multiple environments.
      Unlike other software development initiatives in the SKA
      our solution================== provides all stakeholders with a running, tested system, that can be deployed in multiple environments with a certain expectation of correctness, and show compliance to the following Non-Functional Requirements: Reliability, Maintainability, Observability, Diagnosability, Modifiability, and Resilience
         
      Outcome hypothesis
      • All MVP/SKAMPI code is on Gitlab
      • All MVP/SKAMPI artefacts exist as docker images on Nexus
      • Continuous Integration pipelines for testing different deployments
      • Chaos-monkey-style tool running against processes in a subarray not affecting any other subarrays
      • Chaos-monkey-style tool running against processes in a subarray does not impact reliability, with process re-spawning when needed
      Leading Indicators
      • Time between a broken build and a restored build is < 10 minutes;
      • Number of deployments on PSI that are broken is less than 1 per month
      NFRs Reliability, Maintainability, Observability, Diagnosability, Modifiability, and Robustness

       

      Attachments

        Issue Links

          Parent Of

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. SP-612 JACAL MVP

          • Done

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. SP-617 Taranta (WebJive) and UI/UX Tool Development

          • Done

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. SP-618 MVP Consolidation and Extension

          • Done

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. SP-619 OSO Tool Development in support of the MVP

          • Done

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. SP-620 LFAA Development and MVP Integration

          • Done

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. SP-622 Pulsar Timing Roadmap

          • Done

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. SP-623 CSP-Low Roadmap

          • Done

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. SP-624 CSP-Mid.CBF (TDC) Roadmap

          • Done

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. SP-611 PSS pipeline MVP

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

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. SP-613 SKA Regional Centre Science Analysis Platform and Data-lake Prototypes

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

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. SP-595 SDP Prototype

          • Not Assigned - Priority is not assigned yet.
          • Done

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. SP-610 Precursor systems (MeetKAT+ SDP, ...)

          • Not Assigned - Priority is not assigned yet.
          • Done

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. SP-604 Data Model Libraries

          • Discarded

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. SP-605 Processing Component Library

          • Discarded

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. SP-606 Workflow Scalability Prototype

          • Discarded

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. SP-607 SKA Regional Centre Workflow Pack

          • Discarded

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. SS-19 NFRS for MVP: Keep Assessing and improving

          • 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

          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-458 Spike on evaluation of scalability of Monitor and Control architecture

          • Not Assigned - Priority is not assigned yet.
          • Funnel

          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-236 MVP incorporates delays from KATpoint API

          • Not Assigned - Priority is not assigned yet.
          • Done

          Spike - A time limited investigation to get some knowledge SP-296 Spike to benchmark performance of WebJive

          • Not Assigned - Priority is not assigned yet.
          • Done

          Spike - A time limited investigation to get some knowledge SP-408 MVP Extensions: Investigate Recoverability

          • Not Assigned - Priority is not assigned yet.
          • Done

          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-434 SDP error handling and propagation

          • Not Assigned - Priority is not assigned yet.
          • 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-478 Investigate sub array isolation: Fault containment

          • Not Assigned - Priority is not assigned yet.
          • 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-1249 Instantiate, run and stop PSS pipeline using LMC (Cheetah part)

          • Not Assigned - Priority is not assigned yet.
          • Done

          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-1250 Steps towards deployment of a simple CBF emulator in MVP

          • Not Assigned - Priority is not assigned yet.
          • Done

          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-941 Sub array isolation: Testing interop of different software versions

          • Not Assigned - Priority is not assigned yet.
          • Discarded
          relates to

          Spike - A time limited investigation to get some knowledge SP-687 Harmonize approaches to handling errors and exceptions

          • Done

          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-709 Harmonize approaches to handling errors and exceptions: Followup to SP687

          • Not Assigned - Priority is not assigned yet.
          • Done
          mentioned in

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Structure

            Activity

              People

                j.santander-vela Santander-Vela, Juande
                r.brederode Brederode, Ray
                Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  Structure Helper Panel