As far as identifying application dependencies go, one technique is to run SQL server profiler while the application is being used (It's resource intensive, so ideally you'd want to run this in a test environment). If feasible, you can perhaps have someone run through all the major functions in a test environment, while profiler is running. Then inspect the traces to identify all the objects which the application uses. I can provide more details if you need.