Print

QCon 2008 features domain-driven development



Alex Handy
Email
November 20, 2008 —  (Page 1 of 2)
The many branches on the agile tree have given way to entirely new forests of guerilla development tactics. So say the attendees of the QCon development conference in San Francisco this week. The conference is focused on the many forms of agile, strategies for clouds, and the hulking presence of multithreading and parallelism.

With an entire track dedicated to domain-driven design and development, QCon promises a fresh perspective on the world of requirements gathering and business process modeling. Eric Evans, author of Domain-Driven Design: Tackling Complexity in the Heart of Software, is hosting this track, which is largely inspired by his book. But even outside of that track, the concepts of ubiquitous languages permeated the conference.

While Evans' track takes place tomorrow, Dan North, a consultant with enterprise software development consulting firm ThoughtWorks, discussed the domain-driven model in his talk yesterday. North spoke about what he called behavior-driven development.

At the core of both practices is a mandate for the creation of a language common to the business problem being solved. North said that business analysts and software developers think in different languages. But most of the terms needed to discuss a business problem cogently can be applied to both the digital and analog worlds.

“Let's just try all using the same words to mean then same thing,” said North. “I was consulting in a place where they handled things called credit derivatives, where you have this concept of pricing. It requires big grids. There [was] a pair of developers struggling with this pricing algorithm. A business analyst passed, and they had a conversation. I watched this. It was beautiful because at no point did he realize that they were talking about code. He was talking about pricing. They were having this fluid conversation. This guy didn't realize he was talking about objects.

“It's not just a thought exercise. Let's start having a shared language. A ubiquitous language is when you drive that into your software artifacts. Classes are named what they're named in the domain. What you'll find [is that] when you model stuff, you'll get work done.”



Related Search Term(s): agile development, cloud computing, requirements

Pages 1 2 


Share this link: http://sdt.bz/33066
 

close
NEXT ARTICLE
Guest View: Agile tablets in the cloud
Agile, Apple and the cloud: Three things that are coming together for a beautiful future. I think Read More...
 
 
 




News on Monday  more>>
Android Developer News  more>>
SharePoint Tech Report  more>>
Big Data TechReport  more>>

   
 
 

 


Download Current Issue
MAY 2013 PDF ISSUE

Need Back Issues?
DOWNLOAD HERE

Want to subscribe?


 
 
 
 

Events calendar tab
5/21/2013 to 5/23/2013
Las Vegas
CTIA

5/28/2013 to 5/31/2013
Boston
BZ Media LLC

5/28/2013 to 5/30/2013
San Francisco
O'Reilly Media

6/2/2013 to 6/7/2013
Las Vegas
SQE

6/2/2013 to 6/6/2013
Orlando
IBM Rational