Question

When designing code, which of the following best describes the purpose of a Post Mortem Review?

To obtain feedback on the code
To translate pseudocode to program code
To use code only one time
To check if others have the same code

Answer 1

Post-mortem review, I think, takes place after the code is in a completed state; sort of like an "in-hindsight" report.
I think "To obtain feedback on the code" is the best answer.
Pseudocode would happen much earlier in the process.
Using the code only one time would kind of defeat the purpose of writing a program.
To check if others have the same code would be more of a concern while the code is being designed, and it's not the focus of a post-mortem

Answer 2

If you want a more precise definition, a post-mortem review is the process of looking back on a project after it has been completed in order to summarize what was accomplished and evaluate the results.
This would certainly encompass "obtain feedback", among other things as well