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

Science software distribution roadmap for during v0.1

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

Details

    • SRCnet
    • Hide

      At the moment, science software distribution effort has mainly focused on how the system will be implemented (see SP-4323).

      What is less well understood (or less well socialised) is what software will be distributed, to whom, and when.

      Relevant artefacts are fragmented: e.g. a SRC requirements Jira, various SRCNet confluence pages, national SRC work, previous user interviews, user stories ...

      By consolidating this information into a live, shared, source of truth for SRCNet software distribution, a plan for during v0.1 can be developed and software packaging efforts will deliver better, early value for SRCNet contributors and users.

      Show
      At the moment, science software distribution effort has mainly focused on how the system will be implemented (see SP-4323 ). What is less well understood (or less well socialised) is what software will be distributed, to whom, and when. Relevant artefacts are fragmented: e.g. a SRC requirements Jira, various SRCNet confluence pages, national SRC work, previous user interviews, user stories ... By consolidating this information into a live, shared, source of truth for SRCNet software distribution, a plan for during v0.1 can be developed and software packaging efforts will deliver better, early value for SRCNet contributors and users.
    • Hide

      AC1: A live, shared, source of truth for understanding SRCNet software distribution is made available. Other such artefacts are retired.

      AC2: After AC1, any gaps regarding user expectations during v0.1 are resolved via lightweight investigation only. (User interviews/interactions are to be coordinated by a Science Delivery team from PI25 onwards). 

      AC3: Is is clearly understood what software package categories and subdivisions there shall be. An initial prioritised list of software packages planned to be populated during v0.1 has been shared. (This list is not yet fixed).

      AC4 At least one software package to SRCNet standards is uploaded to the reference implementation of science software distribution system SP-4552. This package is made accessible for testing. 

      Show
      AC1: A live, shared, source of truth for understanding SRCNet software distribution is made available. Other such artefacts are retired. AC2: After AC1, any gaps regarding user expectations during v0.1 are resolved via lightweight investigation only. (User interviews/interactions are to be coordinated by a Science Delivery team from PI25 onwards).  AC3: Is is clearly understood what software package categories and subdivisions there shall be. An initial prioritised list of software packages planned to be populated during v0.1 has been shared. (This list is not yet fixed). AC4 At least one software package to SRCNet standards is uploaded to the reference implementation of science software distribution system SP-4552 . This package is made accessible for testing. 
    • Intra Program
    • 2
    • 2
    • 0
    • Team_TEAL
    • Sprint 5

    • PI24 - UNCOVERED

    • PI24-PB Team_Tangerine science-gateway team_TEAL

    Description

      Under the Development value stream, implementing the software distribution system is part of Science Enabling (L2 product).

      Using that system is part of the Science Delivery value stream, to take form from PI25 onwards. For the time being, we will pretend this feature is development work.

       

      Some old text / text from SP-4553, before the BH/ACs were updated:

      As we move towards v0.2, we need to think about populating the science software repository (SP-4323) with software that users will want to work with data.

      When we have a software distribution reference implementatiomn, we need to be able to assess how this implementation compares to the actual expectations and requirements of our users. In this feature we will conduct investigations to define what the users expect, require and wish for in a software implementation system.

      is not . There are several ways in which that can be done but it seems likely that we will need a number of containers that cover common use cases, together with some thought about a standard Python environment for notebook analysis. This work is to generate a preliminary list and possibly to start building some example distributions meeting SRCNet standards.

      Attachments

        Issue Links

          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-4552 Finish reference implementation of science software distribution system

          • Could have - Items labelled as "Could have" are desirable but not necessary and could improve the user experience or customer satisfaction for a little development cost. These will typically be included if time and resources permit.
          • Implementing
          mentioned in

          Page Loading...

          Page Loading...

          Structure

            Activity

              People

                b.mort Mort, Ben
                M.Hardcastle Hardcastle, Martin
                Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Feature Progress

                  Story Point Burn-up: (0%)

                  Feature Estimate: 2.0

                  IssuesStory Points
                  To Do49.0
                  In Progress   00.0
                  Complete00.0
                  Total49.0

                  Dates

                    Created:
                    Updated:

                    Structure Helper Panel