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

DISH.LMC interface with Dish Structure

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

Details

    • Feature
    • Must have
    • PI12
    • None
    • Obs Mgt & Controls
    • Hide

      A new version of the DISH.LMC to Dish Structure Interface Control Document is needed to begin work on implementation of the DISH.LMC.   Development of DISH LMC is lagging behind other subsystems, while the DISH is a key subsystem required for AA 0.5.   This enabler will update the Dish LMC to DS ICD with the latest information (new DS).

      Show
      A new version of the DISH.LMC to Dish Structure Interface Control Document is needed to begin work on implementation of the DISH.LMC.   Development of DISH LMC is lagging behind other subsystems, while the DISH is a key subsystem required for AA 0.5.   This enabler will update the Dish LMC to DS ICD with the latest information (new DS).
    • Hide

      Actively participated in the relevant DISH Structure meetings, in particular with the team developing DS interface with DISH LMC.

      Provided suggestions on how to best align the DS interface with the SKA standards -  i.e. help with modelling of the data exchange interface to facilitate integration in the SKA MID Telescope (monitor points, events/alarms, commands). 

      Reviewed a draft version of the DISH LMC to DISH Structure ICD, performed a detailed analysis of the proposed interface and its suitability for the MID Telescope, and provided comments. Added sections to the document, as needed.

      Performed analysis of the software required to support DISH  Structure CDR and estimate the effort, if required by DISH Consortium.

       

      Show
      Actively participated in the relevant DISH Structure meetings, in particular with the team developing DS interface with DISH LMC. Provided suggestions on how to best align the DS interface with the SKA standards -  i.e. help with modelling of the data exchange interface to facilitate integration in the SKA MID Telescope (monitor points, events/alarms, commands).  Reviewed a draft version of the DISH LMC to DISH Structure ICD, performed a detailed analysis of the proposed interface and its suitability for the MID Telescope, and provided comments. Added sections to the document, as needed. Performed analysis of the software required to support DISH  Structure CDR and estimate the effort, if required by DISH Consortium.  
    • 2
    • 2
    • 20
    • 10
    • Team_KAROO
    • Sprint 5
    • Hide

      Draft CETC Dish Structure ICD review comments inform improvement of the ICD by CETC in PI13.

      Draft ICD indicating enough similarity of interface with that of the ODC/MTM informs Dish LMC roadmap. 

      Show
      Draft CETC Dish Structure ICD review comments inform improvement of the ICD by CETC in PI13. Draft ICD indicating enough similarity of interface with that of the ODC/MTM informs Dish LMC roadmap. 
    • 12.6
    • Stories Completed, Outcomes Reviewed, Satisfies Acceptance Criteria, Accepted by FO

    • PI22 - UNCOVERED

    • DISH Team_KAROO
    • SPO-1388

    Description

      It is expected that the Dish Consortium  (Dish Structure supplier) will write an ICD for the interface between Dish LMC and Dish Structure during PI2.  This feature is for an agile team to cooperate with the DISH Consortium during the development to help model the interface to facilitate integration in the SKA MID Telescope. This enabler includes review of the draft (potentially more than one version) and discussions.

      Attachments

        Issue Links

          is cloned 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-2123 DISH.LMC interface with Dish Structure (Part 2)

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

          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-2107 DISH.LMC software evolution

          • Must have - Items labelled as "Must have" are critical to the current delivery timebox in order for it to be a success.
          • 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-1809 DSH LMC Roadmap

          • 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...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Structure

            Activity

              People

                s.vrcic Vrcic, Sonja
                s.vrcic Vrcic, Sonja
                Votes:
                0 Vote for this issue
                Watchers:
                6 Start watching this issue

                Feature Progress

                  Story Point Burn-up: (100.00%)

                  Feature Estimate: 2.0

                  IssuesStory Points
                  To Do00.0
                  In Progress   00.0
                  Complete34.0
                  Total34.0

                  Dates

                    Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel