The document introduces domain-driven design (DDD), emphasizing the importance of understanding and collaborating on the core concepts within a complex domain to create effective software. It distinguishes between design as a process and design as a product, advocating for a software structure that accurately reflects domain elements and relationships. Additionally, it mentions layered architecture and provides resources for deeper exploration of DDD principles.

1. Introduction toDomain-Driven DesignPaul RaynerSolutions Architect

3. The principle that we should befocusing on the deep issues of the domain our users are engaged in,that the best part of our minds should be devoted to understanding that domain, andcollaborating with experts in that domain to wrestle it into a conceptual form that we can use to build powerful, flexible software.Eric EvansDOMAIN-DRIVEN DESIGN

4. The overwhelming problem with software developmentis thateverything is part of the design process.“What Is Software Design?” - Jack Reeves

5. For reasons that I do not understand, reasonably intelligent people insist upon confusing the concept ofdesign as process versus design as product“What Is Software Design? – 13 Years Later” - Jack Reeves

6. design as product

8. design as processDOMAIN MODEL

9. UBIQUITOUSLANGUAGE

10. Domain-Driven Design applies whenever we are operating in a complex, intricate domainMake the software a reflection of the domain Incorporate and express the core concepts and elements of the domain Precisely realize the relationships between them.

11. John,In the system for Client A, please tell me the source for populating the field Retail Price?PamAccountantWe Rock!, Inc.Pam,Retail Price = ARRAMT in ARRTRXPF ... It comes out of the BARCSTPF ... either directly or as calculated percentage from BARCSTPF. JohnDeveloperWe Rock!, Inc.

12. Claire <Business Analyst>,Can you please tell me what the @*&#^&^# field John is referring to? I haven't memorized all of the column headers in the tables in the system that I never see . . . :-)I'm guessing he means the product maintenance menu, and the screens 1 - 3 and the field marked "sale price" . . .PamAccountantWe Rock!, Inc.

13. LAYEREDARCHITECTURE

14. http://jeffreypalermo.com/blog/the-onion-architecture-part-1

15. ENTITIES

16. Identity…

17. VALUE OBJECTS

18. AGGREGATES

19. SERVICES

20. FACTORIES

21. REPOSITORIES

22. BOUNDED CONTEXT

23. Thanks to Dave Laribee (codebetter.com/blogs/david_laribee) for permission to use his presentation ideasRESOURCES

24. Paul Raynerpaul@virtual-genius.com303.374.4370@virtualgenius (Twitter)http://virtualgenius.spaces.live.comSolutions Architect