What’s Driving the ‘Driven’ Approaches?


Are there real differences between methodologies, or is it just marketing?


Email    print   
May 15, 2007 —  (Page 1 of 2)
It’s enough to drive a development manager crazy.

Model-driven development. Test-driven development. Feature-Driven Development. Requirements-driven development. There is even search-driven development.

Use of the word “driven” to describe a development approach is so widespread that the term has begun to signal a marketing strategy instead of

a methodology for writing software. “You talk about test-driven development because you sell testing tools. You talk about model-driven because you sell modeling tools,” said Forrester analyst Jeffrey Hammond.

That is not to say that model, test and other “driven” practices aren’t for the most part legitimate. They are. Test-driven development, for example, is an agile practice whereby developers don’t write a single line of code without first creating a test to verify whether or not the code works, said Dave Churchville, CEO of agile project tool provider ExtremePlanner Software. Test-driven development is really a misnomer as the practice is not about testing. “It’s about the intent: making sure the code does what it is supposed to do.”

Test-driven development is a concrete, valuable practice, noted Forrester analyst Carey Schwaber. “But people misuse the phrase.” She also said that tool makers are betting that the term “driven” will get development managers who depend on one of their offerings to buy additional, interrelated tools they sell.

“‘Driven’ is the use case for integration,” she said. “You have one tool; you need to buy the next. That is why vendors like [the term].”

Feature-Driven Development isn’t about tools at all. It’s an agile methodology, much the same way Extreme Programming (XP), Scrum and Crystal are, said Churchville. The approach is based on stories, known as features, that detail how a user will interact with an application, he explained.

THE CASE FOR MODEL-DRIVEN
But sometimes “driven” is part of a new name for an old idea, said Churchville. “Model-driven development used to be called CASE, he noted, referring to the acronym for Computer-Aided Software Engineering. “It’s a rebranding, a second coming.”




Pages 1 2 


Share this link: http://sdt.bz/30625
 
Most Read Latest News Blog Resources

Add comment


Name*
Email*  
Country     


  • Comment
Loading




close
NEXT ARTICLE
Zeichick's Take: Celestial navigation, driving by GPS and agile development
The old way of software development just doesn't cut it anymore not that agile is around Read More...
 
 
 
 
News on Monday
more>>
SharePoint Tech Report
more>>


   

 
 

Download Current Issue
FEBRUARY 2012 PDF ISSUE

Need Back Issues?
DOWNLOAD HERE

Want to subscribe?


 
blogs tab
Are you at risk for burnout?
Burnout is a severe problem and it can strike at any time. Here's how to tell if you are nearing the edge.
02/09/2012 02:16 PM EST

Agility, mom, and apple pie
If we're to evaluate the state-of-the-art in software development, we should start with the values espoused in the Agile Manifesto.
02/07/2012 11:57 AM EST

RIM woos developers with free tablet
How do you get more apps ported to the BlackBerry PlayBook? By giving every developer a free tablet, of course!
02/04/2012 01:57 PM EST

GitHire: Use Headhunters to Find Your Perfect Programmer
Are you a hiring manager tired of scouring the job boards? Check out this new service that will find 5 people interested in your jobs.
02/03/2012 12:17 PM EST

Facebook claims hacker cred
Facebook's SEC S-1 filing form includes a short essay on the Hacker Way by Mark Zuckerberg himself.
02/02/2012 08:26 AM EST

Ryan Dahl steps down
Ryan Dahl, creator of Node.js, steps back from his position as gatekeeper for the project.
02/01/2012 04:58 PM EST

 
Events calendar tab
2/13/2012 to 2/16/2012
Santa Clara
TechWeb

2/26/2012 to 2/29/2012
San Francisco
BZ Media

2/27/2012 to 3/2/2012
San Francisco
RSA

3/4/2012 to 3/7/2012
Las Vegas
IBM Tivoli

3/5/2012 to 3/9/2012
San Francisco
TechWeb