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

Resolve details and issues in multi-scan and configure design

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

Details

    • Obs Mgt & Controls
    • Hide

      This design has a symmetry that should make future evolution simpler;

      This will enable the science-essential multiple scanning that is currently not possible in the MVP;

      Some of the remaining issues are long-standing areas of doubt.

      Show
      This design has a symmetry that should make future evolution simpler; This will enable the science-essential multiple scanning that is currently not possible in the MVP; Some of the remaining issues are long-standing areas of doubt.
    • Hide

      A resolution of the key outstanding issues identified in the document https://docs.google.com/document/d/1t1-E48sigDjKurAfboSXJ0vF34GcQco7CTn15jdGrRU/edit

      Issue number 4 in that document does not need to be resolved at this stage, the other three should be. These are:

      1. Initial details of what goes into the “AssignResources” command to the SDP - sufficient for SP-873 to be implemented
      1. Initial design of the “scan type” concept;
      2. Initial description of what “Configure” might mean for the SDP;

      In addition the proposed design should be reviewed and any other outstanding issues identified and resolved sufficiently for a first implementation of the capability SS-37.

      The conclusions should be written as an evolution of the existing google document with a view to inclusion in the Solution Intent.

      In addition logical and physical descriptions of the involved data items (the details of issues 1-3 and any other related information) should be provided. The physical versions should be in the form of JSON schema.

       

      Show
      A resolution of the key outstanding issues identified in the document https://docs.google.com/document/d/1t1-E48sigDjKurAfboSXJ0vF34GcQco7CTn15jdGrRU/edit Issue number 4 in that document does not need to be resolved at this stage, the other three should be. These are: Initial details of what goes into the “AssignResources” command to the SDP - sufficient for SP-873 to be implemented Initial design of the “scan type” concept; Initial description of what “Configure” might mean for the SDP; In addition the proposed design should be reviewed and any other outstanding issues identified and resolved sufficiently for a first implementation of the capability SS-37 . The conclusions should be written as an evolution of the existing google document with a view to inclusion in the Solution Intent. In addition logical and physical descriptions of the involved data items (the details of issues 1-3 and any other related information) should be provided. The physical versions should be in the form of JSON schema.  
    • 2
    • 2
    • 14
    • Team_SSMT
    • Sprint 1
    • 6.2

    Description

      The document describing the intended architecture for configuring and scanning that allows for multiple scans: https://docs.google.com/document/d/1t1-E48sigDjKurAfboSXJ0vF34GcQco7CTn15jdGrRU/edit#

      leaves some remaining issues to be addressed. This spike should address those remaining issues and also review the design for any further issues or gaps prior to implementation in the MVP.

      Attachments

        Issue Links

          Child Of

          Capability - SAFe program capability SS-37 Enable multi-scan capability in the MVP, including reconfigurations

          • 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
          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-875 Align use of the "configure" command in the MVP

          • Done

          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-786 Execution of receive workflow(s) for multiple scans

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

          Page Loading...

          Page Loading...

          mentioned on

          GitLab Commit - AT1-493: Update the Scan command in alignment with SP-872.

          GitLab Commit - Merge branch 'story_AT1-493' into 'master'

          GitLab Merge request - Story_AT1-499: Implement unit test cases using device mocking for attributes, events and negative scenarios.

          GitLab Merge request - Update TMC-prototype to support SP-872 (Multi-scan functionality).

          Structure

            Activity

              People

                j.santander-vela Santander-Vela, Juande
                a.bridger Bridger, Alan
                Votes:
                0 Vote for this issue
                Watchers:
                3 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
                  Complete37.5
                  Total37.5

                  Dates

                    Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel