liveBook · Manning

Dynamic analysis

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

How 3 Manning books explain it

Memory Safe C++

Analysis of software behavior by executing the software and observing its runtime properties.

How it is used
Tests running code for memory defects as part of a safety-critical C++ memory-safety process.
How deep it goes
Explains an AddressSanitizer test workflow and its dependence on exercised inputs, without detailing tool internals.
Examples
Uses a sensor label copied into a 32-byte array to contrast 31-, 32-, and 33-byte test inputs.
What you can do after
Apply it via AddressSanitizer by running tests with boundary inputs and interpreting where reports appear.

Read how Memory Safe C++ explains dynamic analysis →

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 →

Also covered in

What to know first

Related concepts

Questions about dynamic analysis

What is dynamic analysis?

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

Which Manning books explain dynamic analysis?

Memory Safe C++, The Art of Code and Event Processing in Action.

What should I know before learning dynamic analysis?

Manning books that teach dynamic analysis usually introduce static analysis first.

What is the difference between dynamic analysis and static analysis?

Dynamic analysis is the examination of a program or system by executing it and observing its behavior during operation. Static analysis is the examination of source code or other software artifacts without executing the program to infer properties or identify potential issues.

What kinds of dynamic analysis are there?

Kinds of dynamic analysis include simulation and tracing.

What is dynamic analysis part of?

Dynamic analysis is part of validation. Validation is the process of checking data, behavior, or results against defined criteria to determine their correctness, acceptability, or suitability for a purpose.

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.