Tools and Methodologies for Software Archaeology
You have an enterprise software project to complete, and you decided that there is no need to reinvent wheel.You researched open source projects and pinpointed the ones which you can use. On the other hand, not all of open source projects are well-documented and well-tested. You want to produce high quality software, so you need to understand modules you imported and test them deeply. 

While researching on topic, I came across the [Software Archaeology][1], but I couldn't find deep knowledge about practice of it. My main interest is in Java perspective, but all information and discussion is welcome. 

I think that this is an important issue, because there are lots of open source projects and if you can use them successfully, you can leverage speed of your software development process.   


  [1]: http://en.wikipedia.org/wiki/Software_archaeology
Tools and Methodologies for Software Archaeology
===

You have an enterprise software project to complete, and you decided that there is no need to reinvent wheel.You researched open source projects and pinpointed the ones which you can use. On the other hand, not all of open source projects are well-documented and well-tested. You want to produce high quality software, so you need to understand modules you imported and test them deeply. 

While researching on topic, I came across the [Software Archaeology][1], but I couldn't find deep knowledge about practice of it. My main interest is in Java perspective, but all information and discussion is welcome. 

I think that this is an important issue, because there are lots of open source projects and if you can use them successfully, you can leverage speed of your software development process.   


  [1]: http://en.wikipedia.org/wiki/Software_archaeology