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

Decide on SBI lifecycle and content

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

Details

    • Obs Mgt & Controls
    • Hide

      SBIs are a key part of the OSO system design and are required to support SB execution.

      Show
      SBIs are a key part of the OSO system design and are required to support SB execution.
    • Hide
      1. Clear understanding of the control points for the creation of SBIs;
      2. When is an SBI created from an SBD, answering at least the questions raised in the description;
      3. Which component is responsible for creating an SBI?
      4. What information is stored in an SBI (how is the information from the SBD stored - by copy or by reference?)
      5. For compound SBs do we have a single SBI or multiple SBIs?
      6. For commensal SBs do we have a single SBI or multiple SBIs?
      7. There is a first draft "lifecycle" of SBIs.
      Show
      Clear understanding of the control points for the creation of SBIs; When is an SBI created from an SBD, answering at least the questions raised in the description; Which component is responsible for creating an SBI? What information is stored in an SBI (how is the information from the SBD stored - by copy or by reference?) For compound SBs do we have a single SBI or multiple SBIs? For commensal SBs do we have a single SBI or multiple SBIs? There is a first draft "lifecycle" of SBIs.
    • 1
    • 1
    • 0
    • Team_BUTTONS
    • Sprint 5
    • Hide
      • A document describing the decision made is available here: https://confluence.skatelescope.org/display/SE/Scheduling+Block+Instances
      • The decisions are
        • the SBI will consist of a reference to the version of the SBD that ran, the name of the activity within that SBD as well as any override arguments (which will include additional parameters for ToO observations)
        • the OET will create the SBI and persist it in the ODA
        • the OET will request an sbi_id from SKUID and then pass this to the script which then writes the ID into the EB
      • The OET has been updated to create an SBI when an activity of an SB is run and passes the sbi_id into the script.
      Show
      A document describing the decision made is available here: https://confluence.skatelescope.org/display/SE/Scheduling+Block+Instances The decisions are the SBI will consist of a reference to the version of the SBD that ran, the name of the activity within that SBD as well as any override arguments (which will include additional parameters for ToO observations) the OET will create the SBI and persist it in the ODA the OET will request an sbi_id from SKUID and then pass this to the script which then writes the ID into the EB The OET has been updated to create an SBI when an activity of an SB is run and passes the sbi_id into the script.
    • 19.6
    • Stories Completed, Integrated, Solution Intent Updated, Outcomes Reviewed, Demonstrated, Satisfies Acceptance Criteria, Accepted by FO
    • Team_BUTTONS Team_NAKSHATRA
    • OMC-G1

    Description

      This is partially to complete work started in SP-2923.  That spike was descoped to concentrate on EBs.  This should complete the work required by concentrating on SBIs.

      When is an SBI created from an SBD and which component is responsible for doing it?

      Should an SBI be the way repeated SBs used for monitoring projects are handled? When a monitoring SBI is executed at time T should an SBI be created at that moment with a timed execution of "T+monitor period"? Or...should the OSO system deduce (from ODA status entities) that an SBD was last executed "1 monitor period" ago and therefore it needs to be executed again and creates an SBI at moment of execution?

      When a ToO SB is to be executed at some time in the future (i.e. not urgent enough to be immediate) should that create an SBI (for future execution) at the moment of event receipt?

      Decide on the information stored in SBIs, particularly for information only discovered at SBI execution time. 

      Some (not necessarily complete) questions:

      How is the SBD (and its version) referenced? Is there any "by value" or is it only "by reference"?

      Does the SBI contain information on actual resources allocated?

      What are the link references between SBDs, SBIs and EBs?

      For compound SBs do we have a single SBI or multiple SBIs?

      For commensal SBs do we have a single SBI or multiple SBIs?

      Lifecycle of SBIs?: READY -> EXECUTING -> DONE/COMPLETE?

      Attachments

        Issue Links

          informs

          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-2578 Update PDM to elaborate SBI and EB definitions

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

          Sub-system Version - A version of a sub-system, used in the Release Management and Configuration Management process REL-721 OET v5.3.0

          • Released
          relates to

          Spike - A time limited investigation to get some knowledge SP-2923 Elaborate design of EBs and supporting applications

          • 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
                a.bridger Bridger, Alan
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Feature Progress

                  Story Point Burn-up: (100.00%)

                  Feature Estimate: 1.0

                  IssuesStory Points
                  To Do00.0
                  In Progress   00.0
                  Complete39.0
                  Total39.0

                  Dates

                    Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel