I did not use to be a fan of code reviews because the code review
checklist focused on coding style rather than finding logic errors in
the code. But after modifying the checklist to include common coding
errors and to make sure that code naming standards follow industry
standards I have become a fan of code reviews. We perform a 2 level
code review, the first is done by the software engineer who wrote the
code, the second is done by fellow team members.
Since you are proposing to review existing codebase you must ask
yourself the following questions.
1. Will code be rewritten based on the audit?
2. What kind of things are you looking for in the review? ie naming
standards, logic errors, code documentation etc.
Code reviews are most effective if they are done early in the
development cycle. We had one application that did not follow the
design pattern of the other applications and it is more difficult for
another program to maintain. An early code review would have caught
this and the application probably would have followed a similiar
design as the others.
Michael
ar******@yahoo.com (Arvie) wrote in message news:<69**************************@posting.google. com>...
I need some advice guys.. I am proposing that we get someone to do a
complete audit/review of our Java application codebase, about 1000
JSPs/Servlets and 100 EJBs. If I get firms to submit proposals, what
should I be asking /looking out for? I realise that running the
applications through a migration tool will help but I am looking for a
more through analysis of the actual codebase as well as assessment of
the architecture
Thanks
Arvie