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

Build a prototype ODT back-end

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

Details

    • Obs Mgt & Controls
    • Hide

      This feature enables the initial implementation of a 'full' ODT architecture

      Show
      This feature enables the initial implementation of a 'full' ODT architecture
      • Initial implementation of 'full' ODT services
    • 3
    • 3
    • 13
    • 4.333
    • Team_BUTTONS
    • Sprint 5
    • Hide
      • A prototype ODT back-end has been created which uses OpenAPI
      • This is able to communicate with the ODT front-end
      • The ability to create, load and save (both to disk and to the ODA) has been implemented
      • Full ODA->PostgreSQL DB was demonstrated by Thad on Thursday 18 August at the OMC ART System Demo.
      Show
      A prototype ODT back-end has been created which uses OpenAPI This is able to communicate with the ODT front-end The ability to create, load and save (both to disk and to the ODA) has been implemented Full ODA->PostgreSQL DB was demonstrated by Thad on Thursday 18 August at the OMC ART System Demo.
    • 15.6
    • Stories Completed, Integrated, Outcomes Reviewed, NFRS met, Demonstrated, Satisfies Acceptance Criteria, Accepted by FO
    • PI22 - UNCOVERED

    • Cross_Team_Code_Review Team_BUTTONS

    Description

      The ODT has two components: a browser-accessible frontend that presents the ODT user interface and a backend component that interfaces with SKA systems (ODA, AAA, etc.) to provide services required by the front end. The frontend and backend work together to provide ODT editing (frontend) and ODT storage (mainly backend) functionality. SBD storage is a good example of how the two work together:, the ODT frontend does not store edited SBDs directly into the ODA; instead, it uploads them to the backend which processes the SBDs, validates them (again), and uploads them to the ODA.

      This feature calls for the development of a prototype of the ODT backend. The ODT frontend will use the backend for SBD retrieval and storage. Implementation of the ODT/ODA interface is being covered in SP-2297.

      Starting point: SB object created in ODT backend - retrieved by front end, modified and sent back

      Scope of SB creation: the parts of an SB that the front end can handle

      Web client -> ODT service -> ODA storage

      NOTE: creating something in the web client doesn't store in the ODA yet if it's just a filestore.

       

       

       

      Attachments

        Issue Links

          Structure

            Activity

              People

                a.bridger Bridger, Alan
                p.klaassen Klaassen, Pamela
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Feature Progress

                  Story Point Burn-up: (100.00%)

                  Feature Estimate: 3.0

                  IssuesStory Points
                  To Do00.0
                  In Progress   00.0
                  Complete1026.0
                  Total1026.0

                  Dates

                    Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel