If you have old documentation from a system to be replaced and no running version exists, what is the best technique to leverage this information?

Utilizing old documentation through document analysis is a highly effective technique in this scenario. Document analysis involves a thorough examination of existing documentation to extract valuable insights about the system that has been in place. This can include understanding the functionality, processes, and requirements that were previously implemented.

Although the system itself may no longer be running, the documentation can still provide a wealth of information regarding its architecture, workflows, and user interactions. By dissecting this material, stakeholders can gain a deep understanding of what the old system aimed to achieve and how it operated. This understanding can then guide the development of the new system, ensuring that important features are preserved or enhanced and that previous shortcomings are addressed.

In contrast, options such as discarding the documentation due to concerns about its accuracy overlook the potential value that can still be gained from analyzing historical information. Surveys might collect more recent perspectives but could miss essential details that are already documented. Interface analysis typically focuses on understanding how different systems interact rather than evaluating the functional legacy of the system, making it less relevant in this context. Thus, document analysis stands out as the best method for effectively leveraging the information from old documentation in the absence of a running system version.