Incorporate Changes from Architecture documentation Review

[Weltraumschaf]

• Chapter 01 Introduction & Golas
  • [x] Requirements Overview
    • UC Diagram: What are Data Processor? Elastic or DefectDojo?
    • line between "Parsing UC" & "Cascading UC" we do not understand. Why?
    • Maybe remove diagram or change it.
    • Add Autodiscovery UC?
  • [x] Stakeholders
    • remove Jop
• Chapter 02 Architecture Constraints
  • [x] Does this chapter make sense? We do not have hard external constraints in the true sense. That we build 100% on S3 and k8s was our free decision and therefore rather a solution strategy.
    • [x] Ask Jan.
• Chapter 03 System Scope andContext
  • [x] Context Boundary
    • [x] remove ArtifactHub bc is only Docu-Scraper from our Chart-Repo.
    • [x] DefectDojo -> Write 3rd Party Tool e.g. DefectDojo, Elastic
    • [x] CLI -> add that we mean kubectl
• Chapter 04 Solution Strategy
  • [x] k8s
  • [x] Data store in S3
• Chapter 05 Buidling Block View
  • [x] White Box Overall
    • Arrow from Hooks to Hook SDK
    • Parser as new Componente with arrow to Parser SDK
    • s. DraWIO File (Editable PNG)
  • [x] Refine textual descriptions of components.

[Weltraumschaf]

Realized by https://github.com/secureCodeBox/documentation/pull/271

[Weltraumschaf]

Jan suggested to remove the "architecure constrints" chapter and write two ADRs about k8s and s3 and reference them in the chapter "solution strategy".