[TYPO3-50-general] Last minute concept fix? Incosistent class naming for domain models ...

Martin Kutschker masi-no at spam-typo3.org
Thu May 28 23:21:31 CEST 2009


Nino Martincevic schrieb:
> 
> The customer has not to understand the *code* but the code has to
> reflect the customer's concepts, the Ubiquitous Language (key concept of
> DDD!) you gonna develop with him and the whole team.
> 
> You don't talk of Repositories with him, he doesn't need to know that a
> ShippingItem is an AR that is being retreived by a Repository.
> They are not interested in such specific backend and technical things,
> they want to know if all the processes they talk about are reflected in
> the software, not how and what patterns you use.
> 
> And the benefit of DDD (it's not really an invention of DDD) is to have
> code that reflects the domain (the domain is not the software).
> Then you could draw diagrams (even UML) and discuss it with the customer
> and everybody talks about the same. I.e. if you both talk about a
> shipping specification of a shop item, the diagrams reflect the concept
> of a shipping spcification for an item and the code has a
> ItemShippingSpecification etc.
> 
> It is a great benefit compared to "old-school" techniques where all
> stuff has technical or cryptical names. Some of my customers do not have
> a problem reading UML sequence diagrams, because all terms therein are
> well-known in their own language.
> You won't see the word "Repository" there :-)

Ah, now thing's are getting interesting. Until now I though that DDD is
just another nice way to have your code organized. Being able to discuss
the software creation process with a layman with a shared vocabulary
sounds like a dream.

Masi


More information about the TYPO3-project-5_0-general mailing list