This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Who Should Read This Book ? Do we need some agile programming experience. Could you please briefly describe agile model-driven development (AMDD). TDD vs AMDD (which is better) thanks in advance. Anushe SCJP,SCWCD.
Could you please briefly describe agile model-driven development (AMDD). TDD vs AMDD (which is better)
You can read Scott's description of AMDD here. Among other things, the essay includes the answer to your question about the relationship between TDD and AMDD. Regarding the first two questions, you might get some kind of an idea by reading the table of contents and the back cover. [ January 13, 2004: Message edited by: Lasse Koskela ]
The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus
Joined: Jul 17, 2003
Originally posted by Ilja Preuss: Avi, what do you mean by "process oriented"?
What I meant by 'process oriented' is that the methodology which is not XP/Agile, but the one which we normally follow (life-cycle project management) - i.e., the process where we document each and every step (srs, high-level design document, low-level design document, etc...) [ January 14, 2004: Message edited by: Avi Nash ] [ January 14, 2004: Message edited by: Avi Nash ]
Joined: Jan 23, 2002
"Document-oriented" would perhaps be a more accurate description, then. (in fact, that sounds like a straight waterfall to me...)
Joined: Jan 23, 2002
[ conversation.setMode("off-topic") ]
the one which we normally follow
Wouldn't it be weird if we would follow a waterfallish process while driving a car? Think about it. Five opportunities to touch the steering wheel during the whole trip to the supermarket? Scary... Wait, the sidewalk. "Oh crap, I'm gonna walk right in front of that speeding car but my next milestone is in 86 minutes so I can't stop right now!"
Do we need some agile programming experience. Scott: It would help but isn't required. Could you please briefly describe agile model-driven development (AMDD). Scott: See http://www.agilemodeling.com/essays/amdd.htm. The basic idea is to do just enough modeling following the principles and practices of AM. Modeling can and should be a part of your development efforts, even if "all you're doing" is creating CRC cards, user stories, or sketches. TDD vs AMDD (which is better) Scott: They work together. Do AMDD to think through the big issues, TDD to think through the detailed design issues. thanks in advance. Anushe SCJP,SCWCD.