Specifications
The following figure shows the architecture of ExplorViz containing realized software services with their most important employed framework and libraries.
All time-related communication data (e.g., Traces and communication between classes) is stored and processed as nanoseconds (devlivered by the monitoring framework Kieker) in ExplorViz. Thus, the default time unit is nanoseconds Other representations need to format this data.
The timestamps of landscapes are an exception as they are stored as milliseconds.
This UML classdiagram illustrates the employed data model for handling and storing reconstructed software landscapes. All classes extend the basic class "BaseEntity" (since version 1.2.0)
Please note: Communication (Application- or ClazzCommunication) is always outgoing within our data model.
This UML classdiagram illustrates the employed data model for handling and storing users.
This UML classdiagram illustrates the employed data model for handling the discovery process.
This diagramm illustrates the rendering loop of ExplorViz's frontend rendering components.
