Goal

• The RHIVOS team needs to create a high-level software architecture diagram for inclusion in the certification evidence.
• The RHVIOS team is requesting that the Platform Tools team document the high-level dependencies for each of the RHIVOS glibc components, and capture them in the "User space component dependencies" table in the following document:
  • https://docs.google.com/document/d/1Gcho_zBaCBlDs6-ow-LQ_yu9d-mBe9cdbYhZvxRM6fg/edit?usp=sharing
• There are additional details and examples within the document itself.
• Note that only the first level of dependency is requested (A calls B). Transitive dependency does not need to be captured (A calls B calls C).
• Note also that this is not expected to be an exhaustive analysis with 100% accuracy. It only needs to be a best-effort representation of the major dependencies.

Acceptance Criteria

The high-level dependencies for each glibc component have been added into the "User space component dependencies" table.