Uploaded image for project: 'SAFe Solution'
  1. SAFe Solution
  2. SS-81

Alignment between PBS - Software Modules - Gitlab groups

    XporterXMLWordPrintable

Details

    • Enabler
    • Should have
    • PI14
    • None
    • None
    • Data Processing, Services, Obs Mgt & Controls
    • Hide

      A clear traceability between the SKA overall architecture and the software products is key to maintain a stable configuration for the entire project. 

      A clear mapping of the software development activity to the PBS aids the understanding of the software system from all the stakeholders in the SKA project. 

      Such a structure can more easily be used to inform reporting and configuration management. 

      Show
      A clear traceability between the SKA overall architecture and the software products is key to maintain a stable configuration for the entire project.  A clear mapping of the software development activity to the PBS aids the understanding of the software system from all the stakeholders in the SKA project.  Such a structure can more easily be used to inform reporting and configuration management. 
      • Gitlab repositories are re-organised in groups
      • Each high level PBS element is mapped to a Gitlab group 
      • repositories are named correctly following the grouping and the naming convention

    • PI24 - UNCOVERED

    Description

      the code repositories are organised in a way that is aligned with the PBS and with the SKA system modules view. 

      For each major element in https://confluence.skatelescope.org/display/SWSI/Views%3A+Module a Gitlab group is created that contains all the related repositories. 

      naming conventions are applied consistently. 

      See for example: https://gitlab.com/ska-telescope/sdp 

      Attachments

        Issue Links

          Parent Of

          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-1941 Establish / refine process / reporting tool(s) for determining the current status of functionality for each product

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

          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-1800 TMC - Restructure GitLab Repositories

          • 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-2183 Create OSO GitLab group and ensure repos are consistent with the SKA PBS

          • Should have - Items labelled as "Should have" are important but not necessary for delivery in the current delivery timebox. While "Should have" items can be as important as "Must have", they are often not as time-critical or there may be another way to satisfy the requirement so that it can be held back until a future delivery timebox.
          • Done
          mentioned in

          Page Loading...

          Features

          Structure

            Activity

              People

                m.bartolini Bartolini, Marco
                m.bartolini Bartolini, Marco
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Feature Progress

                  Story Point Burn-up: (66.67%)

                  Feature Estimate: 0.0

                  IssuesStory Points
                  To Do00.0
                  In Progress   12.0
                  Complete24.0
                  Total36.0

                  Capability Progress

                    Feature Point Burn-up: (66.67%)

                    Capability Estimate: 0

                    CountFeature Points
                    Todo12
                    In Progress   00
                    Done24
                    Total36

                    Dates

                      Created:
                      Updated:
                      Resolved:

                      Structure Helper Panel