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

OET: introduce event bus

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

Details

    • Enabler
    • Not Assigned
    • PI8
    • COM OSO SW
    • None
    • Obs Mgt & Controls
      • Enables an OET implementation that follows the CDR design.
      • Saves future effort in refactoring: code does not grow assuming another architecture
    • Hide
      • Script execution service from SP-404 is demonstrated to publish events at significant points in the script execution lifecycle
      • Script execution service responds to events that trigger actions, e.g., request the service prepares for and starts script execution
      Show
      Script execution service from SP-404 is demonstrated to publish events at significant points in the script execution lifecycle Script execution service responds to events that trigger actions, e.g., request the service prepares for and starts script execution
    • 4
    • 3
    • 5.25
    • Team_BUTTONS
    • Sprint 3
    • Hide

      Copying outcomes from AT2-528, since that was the 'capstone' for the OET architectural changes completed for this feature:
      "Event bus implementation introduced and OET architecture modified to be event driven. OET now follows a standard pattern, with components executing in their own Python interpreter and sending messages as significant events occur. This is now the standard OET implementation on master."

      much of the prototyping of an implementation was done in AT2-527, and the detailed notes of what was changed is listed in the description of AT2-528

      This feature is marked as the parent of AT2-552, however that's a documentation for future development story, and not part of the implementation itself. Thus, we continue to work on that but consider the work on the event bus implementation itself complete.

      Show
      Copying outcomes from AT2-528, since that was the 'capstone' for the OET architectural changes completed for this feature: "Event bus implementation introduced and OET architecture modified to be event driven. OET now follows a standard pattern, with components executing in their own Python interpreter and sending messages as significant events occur. This is now the standard OET implementation on master." much of the prototyping of an implementation was done in AT2-527, and the detailed notes of what was changed is listed in the description of AT2-528 This feature is marked as the parent of AT2-552, however that's a documentation for future development story, and not part of the implementation itself. Thus, we continue to work on that but consider the work on the event bus implementation itself complete.
    • 8.6
    • Stories Completed, Integrated, BDD Testing Passes (no errors), Outcomes Reviewed, NFRS met, Demonstrated, Satisfies Acceptance Criteria, Accepted by FO

    • PI24 - UNCOVERED

    Description

      The event bus is the major architectural element of the CDR design. The bus allows components to be loosely coupled and allows a natural separation of domain between operator intent / telescope actions (run SB, allocate resources, stop observation, etc.) and the script execution domain (run script, terminate script, send signal). The event bus improves the OET's non-functional qualities, giving observability, composability, and maintainability to the OET.

      SP-404 implements a script execution service, but without the event bus. Deferring its implementation will result in technical debt as the design diverges from CDR, OET components become more tightly coupled to each other, and a less considered design emerges without any overall architecture.

      This feature introduces the event bus early into the OET, so that subsequent OET features (e.g., SP-405, project accounting, inter-subarray failure monitoring, user interfaces, etc.) can be implemented following the CDR design and without having to invest in interim designs and/or a major refactoring at a later date.

      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-404 OET MVP

          • Not Assigned - Priority is not assigned yet.
          • Done
          is required by

          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-1012 Observability of executions within the OET

          • Not Assigned - Priority is not assigned yet.
          • Done

          Enabler - An Enabler supports the activities needed to extend the Architectural Runway to provide future business functionality. These include exploration, architecture, infrastructure, and compliance. SP-405 OET as Tango Device

          • Won't have (this time) - Items labelled as "Won't have", have been agreed by stakeholders as the least-critical, lowest-payback items, or not appropriate at that time. As a result, "Won't have" items are not planned into the schedule for the next delivery timebox.
          • Discarded
          mentioned in

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Structure

            Activity

              People

                a.bridger Bridger, Alan
                s.williams Williams, Stewart
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Feature Progress

                  Story Point Burn-up: (100.00%)

                  Feature Estimate: 4.0

                  IssuesStory Points
                  To Do00.0
                  In Progress   00.0
                  Complete513.0
                  Total513.0

                  Dates

                    Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel