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

Mid.CBF Software Architecture (including TDC)

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

Details

    • Obs Mgt & Controls
    • Hide

      Mid.CBF DDD presented at the CDR provides hi-level software architecture; more detailed design is required to support work on implementation. This document defines Mid.CBF software architecture and shows how  implementation evolves to support all releases, starting with TCD MVP up to full Mid. CBF implementation (AA 4). 

       

       

      Show
      Mid.CBF DDD presented at the CDR provides hi-level software architecture; more detailed design is required to support work on implementation. This document defines Mid.CBF software architecture and shows how  implementation evolves to support all releases, starting with TCD MVP up to full Mid. CBF implementation (AA 4).     
    • Hide

      Mid.CBF Software Architecture completed to include the latest architectural decisions (states and modes), dynamic views and scenarios.  

      Mid.CBF and TDC Software Architecture presented at System Demo

       

      Show
      Mid.CBF Software Architecture completed to include the latest architectural decisions (states and modes), dynamic views and scenarios.   Mid.CBF and TDC Software Architecture presented at System Demo  
    • 2
    • 2
    • 4
    • Team_CIPA
    • Sprint 5
    • Hide

      Mid.CBF Software Architecture document released for review.
      A copy of the document is attached.
      The document has been updated with the latest architectural and design decisions.
      The document will be updated as per review comments and formally released.
      Some formatting issues persist, in particular references and have to be fixed. Also some of the template instructions appear in printed version - that will be fixed in the next release.

      Show
      Mid.CBF Software Architecture document released for review. A copy of the document is attached. The document has been updated with the latest architectural and design decisions. The document will be updated as per review comments and formally released. Some formatting issues persist, in particular references and have to be fixed. Also some of the template instructions appear in printed version - that will be fixed in the next release.
    • 7.6

    • PI22 - UNCOVERED

    • Mid.CBF TDC Team_CIPA
    • SPO-559

    Description

       Mid.CBF Software Architecture developed during PI6 will be enhanced to  describe how software supports all planned Array Assemblies (from 0.5 to 4). Dynamic views will be added to show flow of M&C messages, states machine (updated as per latest architectural decisions), and scenarios. 

      Dynamic view: 

      States and modes for: Mid.CBF Master Mid.CBF Subarray, VCC, FSP. 

      1. Master (on, off)  Consider: restart, reset. 

      2. Subarray new state machine: 

      1.  on, off, addReceptors, configureScan, startSan, endScan) 
      2. Abort, Restart, Reset 

      TDC views 

      Later array releases - brief overview.

      Scenariois.

      Components - MCS :

      • Master
      • Subarray
      • VCC
      • FSP

       

       

      Attachments

        Issue Links

          clones

          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-448 TDC Software Design

          • Not Assigned - Priority is not assigned yet.
          • Done
          depends on

          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-442 TDC Firmware Design

          • Not Assigned - Priority is not assigned yet.
          • 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-515 TDC High-level Design Document

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

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Structure

            Activity

              People

                j.santander-vela Santander-Vela, Juande
                s.vrcic Vrcic, Sonja
                Votes:
                0 Vote for this issue
                Watchers:
                1 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
                  Complete510.0
                  Total510.0

                  Dates

                    Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel