Praxis Software Structure Model
Modules, packages, and cross-module dependency boundaries.
high · Package Diagram
Open the package-level diagram of managed_components, first confirm what project boundary it is, and then use the file size, symbol size, cross-module reference direction and drill-down diagram to determine whether it is an entry module, shared capability, runtime support or infrastructure boundary. You can continue to drill down to 4 Technical Hotspots.
high · Package Diagram
Open the package-level diagram of build.t_display_p4_tft, first confirm what project boundary it is, and then use the file size, symbol size, cross-module reference direction and drill-down map to determine whether it is an entry module, shared capability, runtime support or infrastructure boundary. You can continue to drill down to 1 Technical Hotspot.
high · Package Diagram
Open the package-level diagram of build.tdisplayp4_tft, first confirm what project boundary it is, and then use the file size, symbol size, cross-module reference direction and drill-down diagram to determine whether it is an entry module, shared capability, runtime support or infrastructure boundary. You can continue to drill down to 1 Technical Hotspot.
high · Package Diagram
Open the package-level diagram of boards, first confirm what project boundary it is, and then use the file size, symbol size, cross-module reference direction and drill-down diagram to determine whether it is an entry module, shared capability, runtime support or infrastructure boundary. You can continue to drill down to 2 Component Diagrams, 5 Class/Structural Diagrams, and 2 Technical Hotspots.
high · Package Diagram
Open the package-level diagram of build.tdisplayp4_amoled, first confirm what project boundary it is, and then use the file size, symbol size, cross-module reference direction and drill-down diagram to determine whether it is an entry module, shared capability, runtime support or infrastructure boundary. You can continue to drill down to 1 Technical Hotspot.
high · Package Diagram
Open the package-level diagram of build.c6_companion, first confirm what project boundary it is, and then use the file size, symbol size, cross-module reference direction and drill-down diagram to determine whether it is an entry module, shared capability, runtime support or infrastructure boundary. You can continue to drill down to 1 Technical Hotspot.
high · Package Diagram
Open the package-level diagram of apps/linux_uconsole_gtk, first confirm what project boundary it is, and then use the file size, symbol size, cross-module reference direction and drill-down map to determine whether it is an entry module, shared capability, runtime support or infrastructure boundary. You can continue to drill down to 8 Component Diagrams and 3 Technical Hotspots.
high · Package Diagram
Open the package-level diagram of apps/esp32_lvgl, first confirm what project boundary it is, and then use the file size, symbol size, cross-module reference direction and drill-down diagram to determine whether it is an entry module, shared capability, runtime support or infrastructure boundary. You can continue to drill down to 3 Component Diagrams and 6 Sequence Diagrams.
high · Package Diagram
Open the package-level diagram of the firmware, first confirm what project boundary it is, and then use the file size, symbol size, cross-module reference direction and drill-down diagram to determine whether it is an entry module, shared capability, runtime support or infrastructure boundary. You can continue to drill down to 2 Component Diagrams.
high · Package Diagram
Open the package-level diagram of apps/nrf52_node, first confirm what project boundary it is, and then use the file size, symbol size, cross-module reference direction and drill-down diagram to determine whether it is an entry module, shared capability, runtime support or infrastructure boundary.
high · Package Diagram
Open the package-level diagram of apps/linux_cardputer_zero, first confirm what project boundary it is, and then use the file size, symbol size, cross-module reference direction and drill-down diagram to determine whether it is an entry module, shared capability, runtime support or infrastructure boundary. You can continue to drill down to 4 Component Diagrams and 2 Technical Hotspots.
high · Package Diagram
Open the package-level diagram of apps/linux_sim_shell, first confirm what project boundary it is, and then use the file size, symbol size, cross-module reference direction and drill-down diagram to determine whether it is an entry module, shared capability, runtime support or infrastructure boundary.
high · Package Diagram
Open the package-level diagram of builds, first confirm what project boundary it is, and then use the file size, symbol size, cross-module reference direction and drill-down diagram to determine whether it is an entry module, shared capability, runtime support or infrastructure boundary.
high · Package Diagram
Open the package-level diagram of images, first confirm what project boundary it is, and then use the file size, symbol size, cross-module reference direction and drill-down diagram to determine whether it is an entry module, shared capability, runtime support or infrastructure boundary.
high · Package Diagram
Open the package-level diagram of cmake, first confirm what project boundary it is, and then use the file size, symbol size, cross-module reference direction and drill-down diagram to determine whether it is an entry module, shared capability, runtime support or infrastructure boundary.
high · Package Diagram
Open the package-level diagram of apps/README.md, first confirm what project boundary it is, and then use the file size, symbol size, cross-module reference direction and drill-down diagram to determine whether it is an entry module, shared capability, runtime support or infrastructure boundary.
high · Package Diagram
Open the package-level diagram of COPYRIGHT, first confirm what project boundary it is, and then use the file size, symbol size, cross-module reference direction and drill-down diagram to determine whether it is an entry module, shared capability, runtime support or infrastructure boundary.
high · Package Diagram
O