Update documentation to outline three stages of P3 analysis and motivation for a database.
This was suggested by @tomdeakin over e-mail, so I'd appreciate a quick review from him too.
Note that the steps in the "Coverage" task are slightly different to an earlier version of this diagram that we'd discussed offline. "Source Code -> Compile & Instrument -> Run -> Extract Coverage" is only one of the possible ways to extract coverage, as something like Code Base Investigator aims to approximate coverage statically. "Source Code -> Analyze -> Extract Coverage" is generic enough to cover static analysis, run-time analysis of instrumented binaries, sampling, etc.
laserkelvin
commented
1 year ago
Related issues
N/A
Proposed changes
This was suggested by @tomdeakin over e-mail, so I'd appreciate a quick review from him too.
Note that the steps in the "Coverage" task are slightly different to an earlier version of this diagram that we'd discussed offline. "Source Code -> Compile & Instrument -> Run -> Extract Coverage" is only one of the possible ways to extract coverage, as something like Code Base Investigator aims to approximate coverage statically. "Source Code -> Analyze -> Extract Coverage" is generic enough to cover static analysis, run-time analysis of instrumented binaries, sampling, etc.