In this presentation, Ruhollah Delpak deals with the genealogy of a Legacy systems and after describing the three levels of refactoring, explains which types of refactoring has most value from DDD perspective. He goes to explain how a deeper understanding of the problem space, can results to a useful repercussion and deeper insight and save a system from failure.

1. ‫مرهم‬DDD‫بر‬‫زخم‬Legacy
‫چگونه‬‫توان‬‫می‬‫رویکرد‬ ‫از‬DDD
‫برای‬Refactor‫سیستم‬Legacy‫گرفت؟‬ ‫بهره‬
‫الله‬‫روح‬‫دلپاک‬‫رویداد‬ ‫دومین‬ ،DDDTalks‫آبان‬ ،۹۸

2. ‫داستان‬
‫تمدن‬ ‫سه‬

3. ‫تمدن‬ ‫اقوام‬T.S

4. ‫تمدن‬ ‫اقوام‬T.M

5. ‫تمدن‬ ‫اقوام‬D.M

6. Patterns of
Enterprise
Application
Architecture

7. ‫رسوم‬ ‫آمیختگی‬
‫قوم‬T.S
‫قوم‬ ‫و‬D.M
‫تمدن‬ ‫ظهور‬
A.D.M‫ها‬
‫برخورد‬
‫ها‬‫تمدن‬!

8. ‫قوم‬ ‫خصایل‬A.D.M

9. Table
Module
Transaction
Script
‫دار‬‫میراث‬‫کدام‬‫تمدنیم‬‫؟‬

10. Domain Model
‫دار‬‫میراث‬‫کدام‬‫تمدنیم‬‫؟‬
Anemic
Domain Model

11. 1- Code-Level Refactoring (MicroRefactoring)

12. 2- Refactoring to Patterns
Joshua Kerievsky

13. 3- Refactoring Toward Deeper Insight

14. PartI: Putting the Domain Model
to Work
PartII. Building Blocks of a Model-
Driven Design
Part III. Refactoring Toward
Deeper Insight
PartIV: Strategic
Design
Domain-Driven Design
Tackling Complexity in the Heart of Software

15. ‫شکنی‬ ‫خط‬(Breakthrough)
• Learning
• Deep Thinking
• Creativity
• Thinking about Improving
• Living in the Domain
• Knowledge Crunching
• Actively Searching
• Develop of Habits of Thoughts
• Trail & Error
• Domain Refactoring

16. ‫صید‬ ‫سهمیه‬ ‫کنترل‬‫شناورهای‬‫صیا‬‫دی‬
‫هدف؟‬

17. ‫اول‬ ‫مدل‬ ،‫اول‬ ‫درک‬

18. ‫درک‬
‫تر‬‫عمیق‬
‫مساله‬

19. ‫جدید‬ ‫مدل‬ ،‫جدید‬ ‫درک‬

20. ‫بقاء‬‫ذینفعان‬‫ماهیان‬ ‫ذخیره‬ ‫پایداری‬ ‫و‬!
‫نظام؟‬ ‫کدام‬
‫جریم‬ ‫و‬ ‫کنترل‬ ‫نظام‬‫ه‬‫پاید‬ ‫توسعه‬ ‫نظام‬‫ار‬

21. ‫شکنی‬ ‫خط‬(Breakthrough)
• Learning
• Deep thinking
• Creativity
• Thinking about improving
• Living in the domain
• Crunch Knowledge
• Actively Searching
• Develop of Habits of Thoughts
• Trail & Error
• Domain Refactoring

22. Success with domain-driven design comes
down to three points…
1. Sophisticated domain models are achievable and worth the trouble.
2. They are seldom developed except through an iterative process of
refactoring, including close involvement of the domain experts with
developers interested in learning about the domain.
3. They may call for sophisticated design skills to implement and use
effectively.

23. Worth the Trouble
Developers Interested in Learning
Design Skills

24. ‫چیست؟‬ ‫ما‬ ‫اث‬‫ر‬‫می‬
‫الله‬‫روح‬‫دلپاک‬
‫رویداد‬ ‫دومین‬DDDTalks
‫آبان‬۱۳۹۸