TrickyFish DAL D Verification

This is the project page for TrickyFish DAL D Verification.

1. DAL-D minus (straight DO-178c) vs DAL_D plus (Deos PSAC)
   1. Plan for Trickyfish: DAL-D minus, even for dvms components that will go on to DAL-A in 2024 or 2025
   2. After much deliberation, we agreed we can use our current set of plans and procedures for DAL-D minus
   3. Reqs Review Checklist: add a java script filter to remove unnecessary items
   4. High level Reqs and Test approach:
      1. DVMS - vfile-level requirements will cover all dvms components: core, exfat, journal, mmc-sdhc
      2. trickyfish BSP - will cover Uboot and deosboot
      3. High level reqs written at system/functional level, not API level - only need to test features that are available to users (this eliminates some exfat features)
      4. Question: Need to test normal/success path behavior. Do we need to test abnormal/failure behavior?
      5. Reqs will include trace tags to provide traceability to tests only (no code trace tags)
   5. The system level test suites will be very useful for developing new vfile-based drivers; ie, not throw-away effort
2. ToDo Kelly: schedule meeting with the test teams (dvms and bsp) to firm up test approach

June 1 Meeting

1. One Issue: current plans and procedures do not align with DAL-D proposal
   1. Currently, DDCI's plans, procedures and howtos apply to single Deos components, and this plan is proposing a vfile-interface approach that has 1 Reqs Doc and 1 test suite that encompasses multiple Deos components
   2. Solution: modifications to DDCI's Plans and Procedures will be captured in Trickyfish Supplemental Doc
2. Only customer trickyfish requirements need to be tested - as documented in the Trickyfish Supplemental Doc
   1. vfile APIs and configuration (combination of features) = trickyfish-filesystem "blob"
   2. Custom BSP reqs + kernel BSP requirements = trickyfish-bsp "blob"
   3. High Level Requirements Documents (drafts) need to be provided to customer asap for confirmation
   4. ToDo Kelly: follow up with Boeing on which vfile APIs are being used, and if PDLA feature is being used
3. Test teams will noodle on the plan, and we'll get back together next Thursday (ToDo Kelly: set up a meeting)

DAL_D_Dev_Verf_Project - provides guidance

Burndown charts: TBD
Completion style: style="background:#90ff90

Component	Customer	Charge/Task	Planning CCB	Verf Complete	Assignees
TrickyFish-BSP	Tricky Fish	Tricky Fish	No	2023-10-24	Avionyx
TrickyFish-dvms-components	Tricky Fish	Tricky Fish	No	2023-10-09	TBD