Welcome to the The Art of Agile Development website. Think of this as the "special features" DVD for the book, only without the DVD. (If you haven't bought the book yet, that's okay... we won't tell if you don't.) Here, you'll find a cornucopia of bonus material, such as downloadable posters, behind-the-scenes material, and new insights.

For more bonus material, see the table of contents.

(If you're getting a 404, this chapter has yet to be posted. Try the table of contents instead.)

 Print

The Art of Agile Development: Ubiquitous Language

30 Apr, 2008

in 99 words

Programmers should speak the language of domain experts to avoid miscommunication, delays, and errors. To avoid mental translation between domain language and code, design your software to use the language of the domain. Reflect in code how users of the software think and speak about their work. One powerful approach is to create a domain model.

The ubiquitous language is a living language. Domain experts influence design and code and the issues discovered while coding influence domain experts. When you discover discrepancies, it's an opportunity for conversation and joint discovery. Then update your design to reflect the results.

as haiku

Fireflies light the night--
Signaling for a mate, or
perhaps, a dinner

Commentary

That Funky Metaphor Stuff

Inside the Book

  • The Domain Expertise Conundrum
  • Two Languages
  • How to Speak the Same Language
  • Ubiquitous Language in Code
  • Refining the Ubiquitous Language
  • Questions
    • Should we avoid the use of technical terms altogether? Our business domain doesn't mention anything about GUI widgets or a database.
  • Results
  • Contraindications
  • Alternatives
  • Further Reading

Loading...

Loading comments...