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

Data Management Use Case Analysis

    XporterXMLWordPrintable

Details

    • Data Processing
      1. Representative set of DLM use cases collected and documented.
      2. Analysis of use cases to derive impact on implementation choices.
      3. Backlog proposals generated for follow on work in the next 2-3 PIs.
    • Inter Program
    • 2
    • 0
    • Team_YANDA
    • Sprint 3

    • PI22 - UNCOVERED

    • Team_YANDA

    Description

      Collect and analyse use cases for the SKA Data Life-cycle Management (DLM) System, including but not limited to:

      • Data product ingest use cases for various products (if requirements are significantly different)
      • Data product retrieval use cases for various scenarios, e.g. staging to hot buffer for batch processing, user retrieval to internal and external storage
      • Data product query use cases for commissioning, early science and internal and external users (if applicable)
      • Data product retirement, deletion and purging use cases
      • Use cases to address specific needs of anticipated storage technologies for the various levels of the DLM system.

      Attachments

        Issue Links

          clones

          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-3667 Review and consolidate design/architecture for data management

          • 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.
          • Done
          is cloned by

          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-3861 Data Management Storage Infrastructure

          • 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.
          • Funnel

          Structure

            Activity

              People

                m.bartolini Bartolini, Marco
                b.mort Mort, Ben
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Feature Progress

                  Story Point Burn-up: (0%)

                  Feature Estimate: 2.0

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

                  Dates

                    Created:
                    Updated:

                    Structure Helper Panel