liveBook · Manning

Dynamic analysis

Dynamic analysis is the examination of a program or system by executing it and observing its behavior during operation.

How 2 Manning books explain it

The Art of Code

Dynamic analysis is the examination of software by observing its behavior during execution.

How it is used
Measures runtime behavior to assess efficiency, energy consumption, and environmental impact.
How deep it goes
Defines runtime observation and names measurement tools, but stops short of explaining instrumentation or analysis procedures.
Examples
Uses JMH, BenchmarkDotNet, pytest-benchmark, VisualVM, JDK Flight Recorder, Async-Profiler, and py-spy as examples.
What you can do after
Diagnose runtime CPU, memory, and energy behavior with benchmarks and language-specific profilers.

Read how The Art of Code explains dynamic analysis →

Event Processing in Action

Analysis of a program or system based on its execution and observed behavior.

How it is used
Validates event processing networks by observing runtime behavior that a static model alone may not reveal.
How deep it goes
Distinguishes simulation from tracing and lists runtime observations, without detailing their implementation procedures.
Examples
Uses realized loops, inactive but reachable EPAs, unused outputs, and the provenance of a shipment-delay event.
What you can do after
Diagnose runtime termination, activation, and output-use problems, and trace event provenance.

Read how Event Processing in Action explains dynamic analysis →

Related concepts

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.