Runtime Analysis

Intent

Analyze the runtime behavior of the system, e.g. with respect to time and resource consumption or creation.

Ask stakeholders about perceived runtime behavior - double check by measuring.
Measure runtime behavior, e.g. with profilers, logs or traces.
Inspect artifacts created at runtime (e.g. logfiles, protocols, system-traces) for information about problems, root-causes or system behavior.
Perform Infrastructure Analysis to learn about the technical infrastructure.

WARNING: Measuring might influence behavior. That can be especially disturbing in multi-threaded, multi-user or multi-core applications.

Infrastructure Analysis
Analyze the technical infrastructure of the system, e.g. with respect to time and resource consumption or creation. Part of Runtime Analysis.
Instrument System
Find out how the system is really used and what the runtime relationships are, as well as other facts that can not be easily determined by Static Code Analysis even in situation where the system under design is largely undocumented and the architecture work thus mostly relies on assumptions, interviews and lore.
Quantitative Analysis
Measure artifacts or processes within the system, e.g. source code.

Found a mistake or want to add your experience? Edit this pattern on GitHub.