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

Computing API Demonstrator

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

Details

    • Feature
    • Not Assigned
    • None
    • None
    • SRCnet
    • Hide

      Have a proof of concept implementation of a Computing API allows to:

      • Do the assessment of the federated computing paradigm, required in the SRCNet architecture
      • Identify weakness/bugs and directions of improvement
      Show
      Have a proof of concept implementation of a Computing API allows to: Do the assessment of the federated computing paradigm, required in the SRCNet architecture Identify weakness/bugs and directions of improvement
    • Hide

      Demo of the demonstrator

      Show
      Demo of the demonstrator
    • 4
    • 0
    • 24.2

    • PI24 - UNCOVERED

    • service-integration

    Description

      Demonstrate Computing Services API on SRC prototypes / Mini-SRC

        • Simple concrete example of API usage (both discovery and access)

      Attachments

        Issue Links

          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-3557 Data Model for Computing Service API

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

          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-3559 Analysis of IVOA Execution Planner Solution

          • 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

          Structure

            Activity

              People

                r.bolton Bolton, Rosie
                C.Gheller Gheller, Claudio
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Feature Progress

                  Story Point Burn-up: (0%)

                  Feature Estimate: 4.0

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

                  Dates

                    Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel