Scroll Down to Continue
More recently, IBM bought Rational Software and when that happened, Microsoft's enthusiasm for UML cooled a lot. Well ... in fact, it froze solid. There's nothing like having your biggest competitor buy the standard to cool your jets about it. Visual Studio Team System has a built in methodology that is not UML anymore and the "Three Amigos" who created UML are divided once again. (One is for Microsoft, one is against them and I can't figure out what the third one wants.)
But, somehow, analysis methodology isn't generating the same level of passion today that it did back then. These days, we seem to have moved closer to the actual end product and development methodology wars are taking center stage. For example, in the upcoming Visual Studio Launch (see ... Visual Studio 2010 Launch Event), you can attend sessions about not only the built-in development support in Visual Studio, but also sessions about Agile Development, Scrum and MVVM. (See the GOB - The About Visual Basic "Glossary of Buzzwords" - for definitions of these and more.)
About Visual Basic Reader Ollie McPhee recently posted a message in the About Visual Basic forum asking for help in deciding which development methodology is the right one to choose.
Do you have an opinion about development methologies? Do you have real-life experience in using one? Do you think it's all a fraud? Tell us which development methodology is the right one in the Reader Response.
Komentar
Posting Komentar