>How about the concept of WinDNA?

Hmmm. Would this not be an architecture? A structure for components. I like to think of "Methodologies" as process guides, rather like checklists of things you should know (or be aware of) as inception, development, and implementation unfold.

Things like
* Rational Unified Process (formerly OOSE and Objectory (Jacobsen) + OMT (Rumbaugh) + OOAD (Booch))
* Extreme (Beck, Cunningham et al)
* Fusion and Evo-Fuison (Coleman)
* Shlaer/Mellor
and so on.

I think MS is really weak in this particular area though, to be fair, MS Press has some gems like Rapid Development, and other books which discuss general development philosophy by Steve McGuire and others by Steve McConnell, among others.

I've seen dick-all on all of MSDN on analyzing requirements and structuring teams, precious little on configuration management, and ditto for things like work allocation and timeboxing, tracking, testing, bug reporting and issue tracking, the feedback loops, and of course there is essentially nothing on software quality control on MSDN :-)

Forgive me I love Microsoft bashing.

http://fox.wikis.com/wc.dll?Wiki~MethodologySpace has a thing or two that deserve elaboration...

**--** Steve