No.
The trouble is that methodologies either fit - in which case they may well be used, or they don't fit - in which case they will probably be used anyway because the developer is familiar with the methodology and get get it to work, even if it isn't the best.
We can't say "It's 'X' type of project, so use methodology 'Y'" because the definition of 'X' type of project isn't 'static code analyzer' it's to do with how it's going to work, how it's going to present to the user, a huge range of other factors - and there are as many different ways to write "a static code analyzer" as there are developers trying to write them!
Have a look at this:
http://www.cms.gov/Research-Statistics-Data-and-Systems/CMS-Information-Technology/XLC/Downloads/SelectingDevelopmentApproach.pdf[
^] and this:
http://www.icbl.hw.ac.uk/ltdi/cookbook/preparation/selecting.html[
^] and google for
choosing a developement methodology[
^] to see how many different idea on how to pick one there are!
Submit an article or tip