Uploaded image for project: 'Release Management'
  1. Release Management
  2. REL-96

ODA v0.1.0-experiment

    XporterXMLWordPrintable

Details

    • Sub-system Version
    • Resolution: Unresolved
    • PI15
    • COM OSO SW
    • None

    Description

      EXPERIMENTAL

      A persistent ODA instance is created plus an ODA Client Library which enables uniform communication paths between other OSO tools and the ODA. A prototype ODT back-end is created as a first step to SB propagation from the ODT to the ODA. The ODT front end is enhanced to cover a larger portion of the Scheduling Block information.

      Components involved:

      • ODA
      • OET
      • ODT

      Use Cases covered:

      At least partial coverage of USE-59, "Prepare and Manage Observation Scripts - Basic Flow".

      Associated test plan:

      <TBD>

      Attachments

        Issue Links

          Delivers

          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-2118 Build a prototype ODT back-end

          • Must have - Items labelled as "Must have" are critical to the current delivery timebox in order for it to be a success.
          • Done

          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-2297 Interface between ODT Back-end and ODA

          • Must have - Items labelled as "Must have" are critical to the current delivery timebox in order for it to be a success.
          • Done

          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-2531 Extend the ODA to connect to a real database

          • Must have - Items labelled as "Must have" are critical to the current delivery timebox in order for it to be a success.
          • Done

          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-2532 ODA client Library

          • Must have - Items labelled as "Must have" are critical to the current delivery timebox in order for it to be a success.
          • Done

          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-2533 Expanded coverage of unified SB in ODT front end

          • Must have - Items labelled as "Must have" are critical to the current delivery timebox in order for it to be a success.
          • Done
          mentioned in

          Page Loading...

          Page Loading...

          Page Loading...

          Features

          Structure

            Activity

              People

                Unassigned Unassigned
                Adam.Avison Avison, Adam
                Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                  Created:
                  Updated:

                  Structure Helper Panel