I am looking for resources and advice to guide me through the process of taking ownership of a large, complex source code project.
My outline so far looks like this:
1. Catalog all files contained in the compiled program we have (estimate approx. 300+ programs and configuration files.)
2. Catalog current database structures for all data files/formats.
3. Request any technical documentation that is available from the original developing people. This stuff may or may not exist.4. Check each “sub” program out of the escrow account, dissect it, and document all functions, variables, and dependencies.
5. Place each “sub” program in a visual diagram of the n-tier archtecture with the goal of visually showing the entire product’s flow. Remove that “sub” program and its config files from the catalog (step 1)
6. Review original catalog to identify any unaccounted for “parts”.
7. Review visual diagram to identify any gaps in flow.
In addition, we are considering partnering with outside resources to assist us in this critical process. Any suggestions for candidates and the criteria we should be reviewing for qualifications? Your war stories and experiences would be greatly appreciated.
