DDD Primer for non-technical people

[Pfil Broering]

Anyone have a good suggestion of a DDD primer for non-technical people? Spent about an hour looking for talks, articles, or books and came up pretty dry.

Thanks

[Ben Kloosterman]

The Blue book , is fairly low tech which anyone managing or working with software should be able to follow. 

Ben

On Sun, Feb 7, 2016 at 4:32 AM, Pfil Broering <the....@gmail.com> wrote:

Anyone have a good suggestion of a DDD primer for non-technical people? Spent about an hour looking for talks, articles, or books and came up pretty dry.

Thanks

--
You received this message because you are subscribed to the Google Groups "DDD/CQRS" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dddcqrs+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Stijn Volders]

Eric has also a document on his website on what/how to read the blue book for non technical people.

https://domainlanguage.com/ddd/howtoreadthebook/

Stijn
@one75

On Feb 6, 2016 18:32, "Pfil Broering" <the....@gmail.com> wrote:

Anyone have a good suggestion of a DDD primer for non-technical people? Spent about an hour looking for talks, articles, or books and came up pretty dry.

Thanks

[Phil Boyd]

http://www.infoq.com/minibooks/domain-driven-design-quickly

[Aryeh]

Domain Driven Design is about basing your system or solution to a complex problem on a rich domain model. It then proposes and describes ways to implement that model in code as part of a working system.

Let me quote Eric Evans from the book Domain Driven Design:

"The goal of domain-driven design is to create better software by focusing on a model of the domain rather than technology."

What is a domain model?  It is an object model of your problem domain.

That being said, most practitioners concentrate on everything but the model.  Articles and forums are full of references to Aggregates, Aggregate Roots, Bounded Contexts and technologies rather than the model at the heart of Model-Driven design.

Regards, Aryeh

[Douglas Gugino]

DDD is about the options of implementing business logic in the language of the business.  There is no need for a technical primer !  Perhaps there should be a joint discussion about what 'formalization' of a process is.  AND for business people the command side has always been different than the read side !  And we always use events  And we always used documents And we always new about information being stale And ..... etcetera :)