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

DSH LMC Roadmap

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

Details

    • Enabler
    • Could have
    • PI12
    • None
    • Obs Mgt & Controls
    • Hide

      Co-operate with the DISH Consortium, to identify:

      1. what the SAFe software organization need to get from the DISH Consortium and the TDT team in order to successfully  plan, design and develop DISH.LMC.
      2. which qualification and testing events the SAFe software organization has to support.
      3. what the SAFe software organization has to deliver to DISH Consortium to support DISH CDR (and possibly earlier integration, testing and qualification events).
      4. what is required for AA0.5.

      Based on this generate the roadmap for DISH.LMC development, integration and testing.

      Cooperate with the DISH Consortium, in particular with the DISH Structure supplier (CETC54), and with the teams working on the design of the Single Pixel Feed (SPF) and SPF receiver (digitiser, led by Mike Pleasance, NRC Canada) to support ICD development and updates. It is assumed that all the ICDs (except ICD TM to DISH) will be developed and updated by the DISH Consortium.

      Review the existing version of the ICD TM to DISH to determine impact of the changes in the dish design, and to determine is the ICD defined in sufficient detail to support implementation.

      If possible (i.e. if sufficient information is available) update the ICD TM to DISH.

      Identify what is required for the following milestones: DISH Structure CDR, DISH CDR and AA0.5.

      Define the roadmap (a high-level plan) for the development of DISH.LMC (including all the required inputs, activities and deliverables).

      Show
      Co-operate with the DISH Consortium, to identify: what the SAFe software organization need to get from the DISH Consortium and the TDT team in order to successfully  plan, design and develop DISH.LMC. which qualification and testing events the SAFe software organization has to support. what the SAFe software organization has to deliver to DISH Consortium to support DISH CDR (and possibly earlier integration, testing and qualification events). what is required for AA0.5. Based on this generate the roadmap for DISH.LMC development, integration and testing. Cooperate with the DISH Consortium, in particular with the DISH Structure supplier (CETC54), and with the teams working on the design of the Single Pixel Feed (SPF) and SPF receiver (digitiser, led by Mike Pleasance, NRC Canada) to support ICD development and updates. It is assumed that all the ICDs (except ICD TM to DISH) will be developed and updated by the DISH Consortium. Review the existing version of the ICD TM to DISH to determine impact of the changes in the dish design, and to determine is the ICD defined in sufficient detail to support implementation. If possible (i.e. if sufficient information is available) update the ICD TM to DISH. Identify what is required for the following milestones: DISH Structure CDR, DISH CDR and AA0.5. Define the roadmap (a high-level plan) for the development of DISH.LMC (including all the required inputs, activities and deliverables).
    • 2
    • 2
    • 8
    • 4
    • Team_KAROO
    • Sprint 5
    • Hide

      Features and enablers for PI13 is defined.

      Roadmap informs at high level the work for Dish LMC software development from PI14 to AA0.5.

      Plan to support Dish CDR.

      Potential collaboration between INAF and SKA SAFe identified.

      Show
      Features and enablers for PI13 is defined. Roadmap informs at high level the work for Dish LMC software development from PI14 to AA0.5. Plan to support Dish CDR. Potential collaboration between INAF and SKA SAFe identified.
    • 12.6
    • Stories Completed, Outcomes Reviewed, Demonstrated, Satisfies Acceptance Criteria, Accepted by FO
    • PI24 - UNCOVERED

    • DISH DISH.LMC
    • SPO-1388

    Description

      There is a need to create a plan for the design, development and delivery of the DISH LMC, and potentially other DISH software components required  to support the DISH Structure CDR, DISH CDR and AA0.5.

      Current status:

      1. DISH.LMC developed by the DISH Consortium (INAF, Catania)  has been developed in C++ and does not adhere to the SKA standards. 
      2. DISH.LMC simulator, developed in Python and based on the SKA TANGO base classes has been integrated in the MVP.
      3. A new version of the DISH Structure is being developed. Work on the definition of the interface between the DISH Structure and DISH LMC started (but its in an early phase).
      4. ICD DISH.LMC to Digitizer (SPFRx) has to be updated to reflect design changes.
      5. ICD DISH.LMC to SPF (Single Pixel Feed) has to be reviewed to verify that it is still valid and that the level of detail is sufficient to support software development.

      A decision has to be made to develop a new version of DISH.LMC software aligned with the SKA standards (Python, TANGO).

      The purpose of this enabler is to investigate status of existing ICDs and work with DISH Consortium on the updates, if required.  It is assumed that the DISH consortium will update the ICDs, while an agile team will review the proposals and help model the data exchange interfaces to facilitate integration in the SKA MID Telescope.

      Review the existing version of the ICD TM to DISH to determine impact of the changes in the dish design, and also to determine is the ICD defined in sufficient detail to support implementation.  

      Work on this Enabler requires co-operation with the DISH Consortium, in particular with the DISH Structure supplier (CETC54),  and with the teams working on the design of the Single Pixel Feed (SPF) and SPF receiver (digitiser, led by Mike Pleasance, NRC Canada).

      If possible (i.e. if sufficient information is available) update the ICD TM to DISH.

      Identify what is required for the following milestones: DISH Structure CDR, DISH CDR and AA0.5.

      Define the roadmap (and if possible a plan) for the development of  DISH.LMC (including all required inputs, activities and deliverables).

      Work on this enabler will be informed and supported by work on SP-1810.

      Attachments

        Issue Links

          Structure

            Activity

              People

                s.vrcic Vrcic, Sonja
                s.valame Valame, Snehal
                Votes:
                1 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
                  Complete710.0
                  Total710.0

                  Dates

                    Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel