Praxis Software Structure Model
Key technical components, portals and collaboration objects.
high · Component Diagram
Open the component diagram of the function node: main and see what type of technical object it is located in apps/linux_cardputer_zero/tests/linux_cardputer_zero_business_wiring_smoke.cpp, what responsibilities it has, whether the reference/call relationship and external dependency/call relationship create change pressure, and its relationship with the structure diagram, sequence and hotspots. You can continue to drill down to 2 Technical Hotspots.
high · Component Diagram
Open the component diagram of the function node: contains, and see what type of technical object it is located in apps/linux_cardputer_zero/tests/linux_cardputer_zero_business_wiring_smoke.cpp, what responsibilities it has, whether the reference/call relationship and external dependency/call relationship create change pressure, and its relationship with the structure diagram, sequence and hotspots. You can continue to drill down to 2 Technical Hotspots.
high · Component Diagram
Open the component diagram of the function node: launchSettingsLayout and see what type of technical object it is located in apps/linux_uconsole_gtk/src/platform/gtk/gtk_uconsole_settings_layout.cpp, what responsibilities it has, whether the reference/call relationship and external dependency/call relationship create change pressure, and its relationship with the structure diagram, sequence and hotspots. You can continue to drill down to 3 Technical Hotspots.
high · Component Diagram
Open the component diagram of the function node: makeLabel and check what type of technical object it is located in apps/linux_uconsole_gtk/src/platform/gtk/gtk_uconsole_widgets.cpp, what responsibilities it has, whether the reference/call relationship and external dependency/call relationship create change pressure, and its relationship with the structure diagram, sequence and hotspots. You can continue to drill down to 3 Technical Hotspots.
high · Component Diagram
Open the component diagram of the function node: makeSettingsRow, and check what type of technical object it is located in apps/linux_uconsole_gtk/src/platform/gtk/gtk_uconsole_settings_layout.cpp, what responsibilities it has, whether the reference/call relationship and external dependency/call relationship create change pressure, and its relationship with the structure diagram, sequence and hotspots. You can continue to drill down to 3 Technical Hotspots.
high · Component Diagram
Open the component diagram of the function node: main, and check what kind of technical object it is located in apps/esp32_lvgl/tests/esp32_lvgl_sd_coredump_contract_smoke.cpp, what responsibilities it has, whether the reference/call relationship and the external dependency/call relationship create change pressure, and its relationship with the structure diagram, sequence and hotspots. You can continue to drill down to 5 Sequence Diagrams.
high · Component Diagram
Open the component diagram of the function node: not_contains, and see what type of technical object it is located in apps/linux_cardputer_zero/tests/linux_cardputer_zero_business_wiring_smoke.cpp, what responsibilities it has, whether the reference/call relationship and the external dependency/call relationship create change pressure, and its relationship with the structure diagram, sequence and hotspots. You can continue to drill down to 2 Technical Hotspots.
high · Component Diagram
Open the component diagram of the service object: main and see what type of technical object it is located in firmware/c6_companion/tests/test_tm_services_functional.cpp, what responsibilities it has, whether the reference/call relationship and the external dependency/call relationship create change pressure, and its relationship with the structure diagram, sequence and hotspots.
high · Component Diagram
Open the component diagram of the function node: contains, and see what type of technical object it is located in apps/esp32_lvgl/tests/esp32_lvgl_sd_coredump_contract_smoke.cpp, what responsibilities it has, whether the reference/call relationship and the external dependency/call relationship create change pressure, and its relationship with the structure diagram, sequence and hotspots. You can continue to drill down to 5 Sequence Diagrams.
high · Component Diagram
Open the component diagram of the function node: makeBoardProfile, and check what kind of technical object it is located in boards/t_echo_lite/include/boards/t_echo_lite/board_profile.h, what responsibilities it has, whether the reference/call relationship and the external dependency/call relationship cause change pressure, and its relationship with the structure diagram, sequence and hotspots. You can continue to drill down to 2 Class/Structural Diagrams and 2 Technical Hotspots.
high · Component Diagram
Open the component diagram of function node: pinNum, and check what kind of technical object it is located in boards/t_echo_lite/include/boards/t_echo_lite/board_profile.h, what responsibilities it has, whether the reference/call relationship and external dependency/call relationship create change pressure, and its relationship with the structure diagram, sequence and hotspots. You can continue to drill down to 2 Class/Structural Diagrams and 2 Technical Hotspots.
high · Component Diagram
Open the component diagram of the function node: refreshUi, and see what type of technical object it is located in apps/linux_uconsole_gtk/src/platform/gtk/gtk_uconsole_shell.cpp, what responsibilities it has, whether the reference/call relationship and external dependency/call relationship create change pressure, and its relationship with the structure diagram, sequence and hotspots. You can continue to drill down to 3 Technical Hotspots.
high · Component Diagram
Open the component diagram of the function node: refreshMap, and see what type of technical object it is located in apps/linux_uconsole_gtk/src/platform/gtk/gtk_uconsole_map_logic.cpp, what responsibilities it has, whether the reference/call relationship and the external dependency/call relationship create change pressure, and its relationship with the structure diagram, sequence and hotspots. You can continue to drill down to 3 Technical Hotspots.
high · Component Diagram
Open the component diagram of the function node: read_file, and see what type of technical object it is located in apps/linux_cardputer_zero/tests/linux_cardputer_zero_business_wiring_smoke.cpp, what responsibilities it has, whether the reference/call relationship and the external dependency/call relationship create change pressure, and its relationship with the structure diagram, sequence and hotspots. You can continue to drill down to 2 Technical Hotspots.
high · Component Diagram
Open the component diagram of the interface component: tm_services_record_error, and see what type of technical object it is located in firmware/c6_companion/components/tm_services/tm_services.c, what responsibilities it has, whether the reference/call relationship and the external dependency/call relationship create change pressure, and its relationship with the structure diagram, sequence and hotspots.
high · Component Diagram
Open the component diagram of the function node: main and check what type of technical object it is located in apps/linux_uconsole_gtk/tests/uconsole_meshtastic_node_payload_smoke.cpp, what responsibilities it has, whether the reference/call relationship and external dependency/call relationship create change pressure, and its relationship with the structure diagram, sequence and hotspots. You can continue to drill down to 3 Technical Hotspots.
high · Component Diagram
Open the component diagram of the function node: launchMapLayout, and see what type of technical object it is located in apps/linux_uconsole_gtk/src/platform/gtk/gtk_uconsole_map_layout.cpp, what responsibilities it has, whether the reference/call relationship and external dependency/call relationship create change pressure, and its relationship with the structure diagram, sequence and hotspots. You can continue to drill down to 3 Technical Hotspots.
high · Component Diagram
Open the component diagram of the function node: companion_enter, and see what type of technical object it is located in apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp, what responsibilities it has, whether the reference/call relationship and the external dependency/call relationship create change pressure, and its relationship with the structure diagram, sequence and hotspots. You can continue to drill down to 5 Sequence Diagrams.
high · Component Diagram
Open the component diagram of function node: expect, and check what type of technical object it is located in apps/linux_uconsole_gtk/tests/uconsole_meshtastic_node_payload_smoke.cpp, what responsibilities it has, whether the reference/call relationship and external dependency/call relationship create change pressure, and its relationship with the structure diagram, sequence and hotspots. You can continue to drill down to 3 Technical Hotspots.
high · Component Diagram
Open the component diagram of the function node: makeSwitch and see what type of technical object it is located in apps/linux_uconsole_gtk/src/platform/gtk/gtk_uconsole_settings_layout.cpp, what responsibilities it has, whether the reference/call relationship and the external dependency/call relationship create change pressure, and its relationship with the structure diagram, sequence and hotspots. You can continue to drill down to 3 Technical Hotspots.
high · Component Diagram
Open the component diagram of the function node: setLabel and check what type of technical object it is located in apps/linux_uconsole_gtk/src/platform/gtk/gtk_uconsole_widgets.cpp, what responsibilities it has, whether the reference/call relationship and external dependency/call relationship create change pressure, and its relationship with the structure diagram, sequence and hotspots. You can continue to drill down to 3 Technical Hotspots.
high · Component Diagram
Open the component diagram of the function node: makeSpin, and check what type of technical object it is located in apps/linux_uconsole_gtk/src/platform/gtk/gtk_uconsole_settings_layout.cpp, what responsibilities it has, whether the reference/call relationship and external dependency/call relationship create change pressure, and its relationship with the structure diagram, sequence and hotspots. You can continue to drill down to 3 Technical Hotspots.