Update DS Design Documentation and Requirements

[chillfig]

For requirements

• Review existing requirements for the module
• Analyze code for module, code changes/PRs since baseline
• Compare code with requirements; identify differences
  • If differences, determine if code or requirements contains desired behavior, and/or update the incorrect one (or create a ticket to resolve the code discrepancy)
  • May involve team discussion(s)

For design documentation

• End product: markdown document (single document for all of CF), using Mermaid for diagrams
• Sources of information:
  • SRD
  • App Developer's Guide
  • cFS Training
  • Source Code
• Module section:
  • Overview of Module
  • Behavioral/Structural Views/Algorithms
  • Code Structure
  • Design Decisions, Assumptions, Risks
  • Any Physical Data Models