I haven't read through all the posts and there are some great suggestions and strategies that have been outlined.
I've been through the same situation quite a few times in my career.
Have you been able to track down any of the project artifacts developed as the software was being created.
Business requirements, functional requirements, use cases, design docs, database designs, user guides, etc.
I know these documents, if they exist, can be out of date, incomplete, or puzzle pieces for how the software has evolved over time.
However, what may exist might be able to provide a high level picture of the software from different perspectives and shed some light on little nuances.
Slashdot Mirror
I haven't read through all the posts and there are some great suggestions and strategies that have been outlined.
I've been through the same situation quite a few times in my career.
Have you been able to track down any of the project artifacts developed as the software was being created.
Business requirements, functional requirements, use cases, design docs, database designs, user guides, etc.
I know these documents, if they exist, can be out of date, incomplete, or puzzle pieces for how the software has evolved over time.
However, what may exist might be able to provide a high level picture of the software from different perspectives and shed some light on little nuances.