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

CLONE - (mini) ODA prototype

    XporterXMLWordPrintable

Details

    • Obs Mgt & Controls
    • Hide

      The OSO Data Archive (ODA) forms the main point of interface between the OSO tools, acting as the repository for the storage and retrieval of the data products of the OSO tools, such as proposals, projects, scheduling blocks, scripts, plans and execution records.

      It is therefore a useful building block towards the development of these prototypes, and a minimal version is required as soon as more than one tool exists and there is a requirement for some kind of user to be able to store, retrieve and update project and SB definitions - such as will be the case for PSI use.

      An early version also provides a mechanism for demonstrating the consistency and completeness of the interfaces between the OSO tools.

      An early prototype could also exercise potential final technology solution (database variants), though this may require more effort.

      A potential added benefit of a small (mini) prototype ODA is for developer testing of OSO tools, without the need to use a production version.

      Show
      The OSO Data Archive (ODA) forms the main point of interface between the OSO tools, acting as the repository for the storage and retrieval of the data products of the OSO tools, such as proposals, projects, scheduling blocks, scripts, plans and execution records. It is therefore a useful building block towards the development of these prototypes, and a minimal version is required as soon as more than one tool exists and there is a requirement for some kind of user to be able to store, retrieve and update project and SB definitions - such as will be the case for PSI use. An early version also provides a mechanism for demonstrating the consistency and completeness of the interfaces between the OSO tools. An early prototype could also exercise potential final technology solution (database variants), though this may require more effort. A potential added benefit of a small (mini) prototype ODA is for developer testing of OSO tools, without the need to use a production version.
    • Hide

      The very first version of the ODA prototype should be able to:

      • Allow other OSO tools to store and retrieve SB definitions and instances;
      • Allow users to query or list available SB definitions.
      Show
      The very first version of the ODA prototype should be able to: Allow other OSO tools to store and retrieve SB definitions and instances; Allow users to query or list available SB definitions.
    • 2
    • 2
    • 2
    • 1
    • Team_BUTTONS
    • Sprint 4
    • Hide

      ODA development was significantly impacted by unavailability of the developer for 4 weeks due to illness. At the the time of writing, the ODA status is as follows:

      • The ODA project has been set up and fully integrated with SKA GitLab, CI/CD, and ReadTheDocs.
      • ODA APIs have been designed and tested with a ODA implementation that provides non-persistent storage of Scheduling Block Instances, using the ‘Repository’ and ‘Unit of Work’ patterns.
      • A REST server has been implemented that allows retrieval and storage of a single SB, utilising the non-persistent backend described above. The REST server is expected to be extended to allow storage of multiple entities in a single transaction during the I&P sprint.
      • All code is tested and documented to SKA DoD standards.
      Show
      ODA development was significantly impacted by unavailability of the developer for 4 weeks due to illness. At the the time of writing, the ODA status is as follows: The ODA project has been set up and fully integrated with SKA GitLab, CI/CD, and ReadTheDocs. ODA APIs have been designed and tested with a ODA implementation that provides non-persistent storage of Scheduling Block Instances, using the ‘Repository’ and ‘Unit of Work’ patterns. A REST server has been implemented that allows retrieval and storage of a single SB, utilising the non-persistent backend described above. The REST server is expected to be extended to allow storage of multiple entities in a single transaction during the I&P sprint. All code is tested and documented to SKA DoD standards.
    • 15.4
    • Stories Completed, Outcomes Reviewed, Demonstrated, Satisfies Acceptance Criteria, Accepted by FO

    Description

      The very first version of the ODA prototype should be able to:

      • Allow other OSO tools to store and retrieve SB definitions and instances;
      • Allow users to query or list available SB definitions.

      Though it is expected that the production ODA will be a relational DB this very first version could be as simple as a simple interface to a file system, with definitions serialised as JSON strings.

      A beneficial extension though would be to use a small relational database system.

      Attachments

        Issue Links

          clones

          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-78 (mini) ODA prototype

          • 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.
          • Done
          mentioned in

          Page Loading...

          Structure

            Activity

              People

                a.bridger Bridger, Alan
                m.bartolini Bartolini, Marco
                Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Feature Progress

                  Story Point Burn-up: (0%)

                  Feature Estimate: 2.0

                  IssuesStory Points
                  To Do00.0
                  In Progress   00.0
                  Complete50.0
                  Total50.0

                  Dates

                    Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel