Download as PDF, PPTX
![10 / 문서의 제목
Representation[Semantic] Gap
The gap between our mental model of the domain and
its representation in software
Low Representation Gap
Name from domain vocabulary
Responsibility derived from
domain concept
LionCat](https://image.slidesharecdn.com/domain-drivendesign-140803000834-phpapp01/75/Domain-Driven-Design-10-2048.jpg)
![10 / 문서의 제목
Representation[Semantic] Gap
The gap between our mental model of the domain and
its representation in software
Low Representation Gap
Name from domain vocabulary
Responsibility derived from
domain concept
LionCat](https://crownmelresort.com/image.slidesharecdn.com/domain-drivendesign-140803000834-phpapp01/75/Domain-Driven-Design-10-2048.jpg)
Uploaded byYoung-Ho Cho
Domain Driven Design
The document discusses Domain-Driven Design (DDD). It explains that DDD focuses on properly modeling the problem domain and using this domain model to drive the software design. This involves developing a ubiquitous language within the bounded context of the domain model and ensuring consistency between this language, the domain model, and the software code. Patterns like entity, value object, aggregate, and repository can be used, but the domain model is the most important pattern in DDD.
More Related Content
![[Final] ReactJS presentation](https://cdn.slidesharecdn.com/ss_thumbnails/65cfd4f9-740f-4f41-b769-b496b6e60802-170119143904-thumbnail.jpg?width=640&height=640&fit=bounds)
![[수정본] 우아한 객체지향](https://cdn.slidesharecdn.com/ss_thumbnails/woowahan-oo-190624161343-thumbnail.jpg?width=640&height=640&fit=bounds)
![[JWPA-1]의존성 주입(Dependency injection)](https://cdn.slidesharecdn.com/ss_thumbnails/dependencyinjection-140711035044-phpapp02-thumbnail.jpg?width=640&height=640&fit=bounds)
![[PreSchool-1] 프로그래밍 '개념' 맛보기](https://cdn.slidesharecdn.com/ss_thumbnails/2014preschoolclass2-140310094959-phpapp02-thumbnail.jpg?width=640&height=640&fit=bounds)
![[NEXT 프연 Week2] UNIX 명령어 간단하게 살펴보기](https://cdn.slidesharecdn.com/ss_thumbnails/week2-unix-140729102628-phpapp01-thumbnail.jpg?width=640&height=640&fit=bounds)
![[NEXT 프연 Week1] Git 시작하기](https://cdn.slidesharecdn.com/ss_thumbnails/week1-140711211237-phpapp02-thumbnail.jpg?width=640&height=640&fit=bounds)
![[JWAP-2] DI & Spring](https://cdn.slidesharecdn.com/ss_thumbnails/jwpaweek02-140714104419-phpapp02-thumbnail.jpg?width=640&height=640&fit=bounds)
![[NHN NEXT] Java 강의 - Week1](https://cdn.slidesharecdn.com/ss_thumbnails/plinjava-week01-140723044157-phpapp02-thumbnail.jpg?width=640&height=640&fit=bounds)
![[NEXT 프연 Week3] C# Data Type](https://cdn.slidesharecdn.com/ss_thumbnails/week3-datatype-140803094224-phpapp02-thumbnail.jpg?width=640&height=640&fit=bounds)
![[NHN NEXT] Java 강의 - Week2](https://cdn.slidesharecdn.com/ss_thumbnails/plinjava-week02-140723044456-phpapp02-thumbnail.jpg?width=640&height=640&fit=bounds)
![[NHN NEXT] 2014 NHN NEXT 창의체험](https://cdn.slidesharecdn.com/ss_thumbnails/2014-04-140526093239-phpapp02-thumbnail.jpg?width=640&height=640&fit=bounds)
![[NHN NEXT] Java 강의 - Week4](https://cdn.slidesharecdn.com/ss_thumbnails/plinjava-week04-140812103158-phpapp02-thumbnail.jpg?width=640&height=640&fit=bounds)
![[NHN NEXT] Java 강의- Week3](https://cdn.slidesharecdn.com/ss_thumbnails/plinjava-week03-140723044604-phpapp01-thumbnail.jpg?width=640&height=640&fit=bounds)
Domain Driven Design
- 1. Tackling Complexity inthe Heart of Software Domain-Driven Design 카페서비스개발팀 조영호
- 2. 2. What isDomain-Driven Design? 3. Patterns of Domain-Driven Design 목차 4. Conclusion 1. Domain & Software
- 3. 1. Domain &Software
- 4. 4 / 문서의제목 Domain-Driven Design - Book By Eric Evans Addison-Wesley, 2003
- 5. 5 / 문서의제목 Domain & Software The subject area to which the user applies a program is the domain of the software. The critical complexity of most software projects is in understanding the domain itself.
- 6. 6 / 문서의제목 Domain & Software Software has to Model the Domain
- 7. 7 / 문서의제목 But... Spring ORM Dependency Injection Database J2EE Ajax Continuous Integration Hadoop Coarse Grained Lock Strategy Hibernate Mockito ActiveMQ RoRGrailsAOP Naked Object
- 8. 8 / 문서의제목 Cargo cargoid originid destination customers clearance(opt) weight Haz Mat Code Routing Service Database table : cargo_bookings Cargo_id Transport Load Unload origin destination customers clearance (opt) populate cargo_bookings table "If we give the Routing Service an origin, destination, and arrival time, it can look up the stops the cargo will have to make and, well . . . stick them in the database." Conversation Based on Technology
- 9. 2. What isDomain-Driven Design?
- 10. 10 / 문서의제목 Representation[Semantic] Gap The gap between our mental model of the domain and its representation in software Low Representation Gap Name from domain vocabulary Responsibility derived from domain concept LionCat
- 11. 11 / 문서의제목 Ice Age of EJB Cat High Representation Gap <<interface>> CatHome <<interface>> Cat CatEJB <<interface>> EJBHome <<interface>> EJBObject <<interface>> EntityBean Domain Concept Design
- 12. 12 / 문서의제목 Technology Exodus OO design is more important than any particular implementation technology (such as J2EE, or even Java). And now important than even Spring or Hibernate
- 13. 13 / 문서의제목 DOMAIN MODEL Pattern An object model of the domain that incorporates both behavior and data. Sale getTotalPrice() : long setTotalPrice(long) getLineItems() : Collection setLineImtes(Collection) LineItem getPrice() : long setPrice(long) getPrioduct() : Product setProduct(Product) Sale calclulatePrice() : Money addLineItem(LineItem) LineItem calculatePrice() : long * TRANSACTION SCRIPT & ANEMIC DOMAIN MODEL RICH DOMAIN MODEL Back to the Origin of the OO
- 14. 14 / 문서의제목 Continuous Design in Agile Specification Test Design Code Big Up-front Design Incremental Design Refactoring
- 15. 15 / 문서의제목 Analysis = Design = Implementation Analysis Model seatId ReservationSeat Showing time Design Model seatId ReservationSeat Showing time : TimeOfDay 1 Implementation Model Showing showing = showingRepository.getShowingWithLock(showingId); Reservation reservation = showing.reserveSeats(seatIds, adultSeatCount, teenagerSeatCount); reservationRepository.saveReservation(reservation);
- 16. 16 / 문서의제목 And Finally Focus on Domain Complexity, not Technology Complexity Everything is Driven By Domain
- 17. 17 / 문서의제목 And Finally Tackling Complexity in the Heart of Software
- 18. 18 / 문서의제목 And Finally UBIQUITOUS LANGUAGE MODEL-DRIVEN DESIGN
- 19. 19 / 문서의제목 Model
- 20. 20 / 문서의제목 Model A system of abstractions that describes selected aspects of a domain and can be used to solve problems related to that domain A model is not right or wrong, only more or less useful
- 21. 21 / 문서의제목 Domain Modeling Documentary Film A domain modeler chooses particular model for usability
- 22. 22 / 문서의제목 Model & Diagram A Domain Model is not a particular diagram. It is the knowledge that the diagram is intended to convey. The Diagram is a representation of Model Not a Model
- 23. 23 / 문서의제목 Model-Driven Design
- 24. 24 / 문서의제목 The MODEL and the heart of the DESIGN shape each other Model-Driven Design DOMAIN MODEL seatId ReservationSeat Showing time DESIGN seatId ReservationSeat Showing time : TimeOfDay 1 CODE Showing showing = showingRepository.getShowingWithLock(showingId); Reservation reservation = showing.reserveSeats(seatIds, adultSeatCount, teenagerSeatCount); reservationRepository.saveReservation(reservation);
- 25. 25 / 문서의제목 Find the Model that works for Analysis, Design and Implementation Model-Driven Design Lower Representation Gap Object-Oriented Paradigm is the most Powerful The Code is an expression of Model
- 26. 26 / 문서의제목 A Programmer is a Modeler. Hands-On Modelers
- 27. 27 / 문서의제목 UBIQUITOUS LANGUAGE
- 28. 28 / 문서의제목 UBIQUITOUS LANGUAGE Conversations among Developers Discussions among Domain Experts Expressions in the Code Discussion between Developers and Domain Experts All based on the same language, derived from a shared Domain Model
- 29. 29 / 문서의제목 UBIQUITOUS LANGUAGE technical aspects of design technical terms technical design patterns business terms developers don’t understand business terms everyone uses that don’t appear in design domain model terms names of BOUNDED CONTEXT terminology of large-scale structure many patterns from Domain-Driven Design book
- 30. 30 / 문서의제목 Use the Domain Model as the backbone of a Language UBIQUITOUS LANGUAGE Use the same language in diagrams, writing, and especially speech Use the UBIQUITOUS LANGES in all communication within team and in the code One Team, One Language
- 31. 31 / 문서의제목 And Domain-Driven Design DOMAIN MODEL seatId ReservationSeat Showing time UBIQUITOUS LANGUAGE Showing Reservation Reservation Seat CODE Showing showing = showingRepository.getShowingWithLock(showingId); Reservation reservation = showing.reserveSeats(seatIds, adultSeatCount, teenagerSeatCount); reservationRepository.saveReservation(reservation);
- 32. 32 / 문서의제목 And Domain-Driven Design DOMAIN MODEL seatId ReservationSeat Showing time UBIQUITOUS LANGUAGE Showing Reservation Reservation Seat CODE Showing showing = showingRepository.getShowingWithLock(showingId); Reservation reservation = showing.reserveSeats(seatIds, adultSeatCount, teenagerSeatCount); reservationRepository.saveReservation(reservation);
- 33. 33 / 문서의제목 And Domain-Driven Design DOMAIN MODEL seatId ReservationSeat Showing time UBIQUITOUS LANGUAGE Performance Reservation Reservation Seat CODE Showing showing = showingRepository.getShowingWithLock(showingId); Reservation reservation = showing.reserveSeats(seatIds, adultSeatCount, teenagerSeatCount); reservationRepository.saveReservation(reservation);
- 34. 34 / 문서의제목 And Domain-Driven Design DOMAIN MODEL seatId ReservationSeat Performance time UBIQUITOUS LANGUAGE Performance Reservation Reservation Seat CODE Showing showing = showingRepository.getShowingWithLock(showingId); Reservation reservation = showing.reserveSeats(seatIds, adultSeatCount, teenagerSeatCount); reservationRepository.saveReservation(reservation);
- 35. 35 / 문서의제목 And Domain-Driven Design DOMAIN MODEL seatId ReservationSeat Performance time UBIQUITOUS LANGUAGE Performance Reservation Reservation Seat CODE Performance performance = performanceRepository.getPerformanceWithLock( performanceId); Reservation reservation = showing.reserveSeats(seatIds, adultSeatCount, teenagerSeatCount); reservationRepository.saveReservation(reservation);
- 36. 36 / 문서의제목 And Domain-Driven Design A Showing is...
- 37. 37 / 문서의제목 And Domain-Driven Design A Performance is...
- 38. 38 / 문서의제목 Cargo cargoid originid destination customers clearance(opt) weight Haz Mat Code Routing Service Database table : cargo_bookings Cargo_id Transport Load Unload origin destination customers clearance (opt) populate cargo_bookings table "If we give the Routing Service an origin, destination, and arrival time, it can look up the stops the cargo will have to make and, well . . . stick them in the database." Conversation Based on Technology
- 39. 39 / 문서의제목 Cargo cargoid weight Haz Mat Code Routing Service Route Specification origin destination customers clearance (opt) Itinerary Leg 0..1 {Itinerary must satisfy specification} a Route Specification an Itinerary satisfying the Route Specification "A Routing Service finds an Itinerary that satisfies a Route Specification.” Conversation Based on Model
- 40. 3. Patterns ofDomain-Driven Design
- 41. 41 / 문서의제목 Domain-Driven Design & Patterns DDD is not about patterns such as ENTITY, VALUE OBJECT, AGGREGATE, REPOSITORY, SERVICE, FACTORY DDD is a better way of thinking about software design Patterns may take your software more stable or more maintainable, but it is the methodology that guides you to deliver something fit for purpose
- 42. 42 / 문서의제목 DOMAIN MODEL is a King
- 43. 43 / 문서의제목 A King, DOMAN MODEL is RICH, Not ANEMIC <<interface>> ShowingRepository getShowingWithLock(showingId) :Showing seatId <<interface>> SeatState AbstractSeatState Reserved 1 0..1 1 0..* 1 0..1 leftSeat 0..1 rightSeat 0..1 nextSeatState 0..1 previousSeatState <<interface>> ScheduleService reserve(showingId, seats,adultSeatCount, teenagerSeatCount) : Reservation ReservationSeat -showingRepository -reservationRepository ScheduleServiceImpl Occupied Sold <<interface>> ReservationRepository saveReservation(reservation) ShowingFactory create(dayOfYear, showingSpecification) : Showing Showing time:TimeOfYear Reservation amount:Money
- 44. 44 / 문서의제목 <<interface>> ShowingRepository getShowingWithLock(showingId) :Showing seatId <<interface>> SeatState AbstractSeatState Reserved 1 0..1 1 0..* 1 0..1 leftSeat 0..1 rightSeat 0..1 nextSeatState 0..1 previousSeatState <<interface>> ScheduleService reserve(showingId, seats,adultSeatCount, teenagerSeatCount) : Reservation ReservationSeat -showingRepository -reservationRepository ScheduleServiceImpl Occupied Sold <<interface>> ReservationRepository saveReservation(reservation) ShowingFactory create(dayOfYear, showingSpecification) : Showing Showing time:TimeOfYear Reservation amount:Money A King, DOMAN MODEL is RICH, Not ANEMIC SERVICE ENTITY AGGREGATE VALUE OBJECT REPOSITORY FACTORY
- 45. 45 / 문서의제목 A King should be Protected
- 46. 46 / 문서의제목 Layered Architecture User Interface Application Domain Infrastructure
- 47. 47 / 문서의제목 CONTEXT is a King’s Domain
- 48. 48 / 문서의제목 BOUNDED CONTEXT
- 49. 49 / 문서의제목 BOUNDED CONTEXT Model Model CONTEXT CONTEXT
- 50. 50 / 문서의제목 Translate two UBIQUATIOUS LABUAGES
- 51. 51 / 문서의제목 CONTEXT MAP Model Model CONTEXT CONTEXT TRNSLATION MAP
- 52. 52 / 문서의제목 CONTINUOUS INTEGRATION Model Model CONTEXT CONTEXT CONTINUOUS INTEGRATION per each CONTEXT
- 53. 53 / 문서의제목 A king should learn continuously
- 54. 54 / 문서의제목 DISTILLATION User Interface Application Infrastructure Domain CORE DOMAIN GENERIC SUBDOMAIIN COHESIVE MECHANISM SEGREGATED CORE ABSTRACT CORE Refactoring
- 55. 55 / 문서의제목 CONTEXT & MODEL No duplication...within a context! Model Model CONTEXT CONTEXT Single, Unified Model within Any One Context Duplication between...AOK!
- 56.
- 57. 57 / 문서의제목 No Silver Bullet
- 58. 58 / 문서의제목 Essence of Software Complexity Conformity Changeability Invisibility
- 59. 59 / 문서의제목 Essence of Software Complexity Conformity Changeability Invisibility Related to Domain & Domain Model
- 60. 60 / 문서의제목 Domain-Drive Design Back to the Basics Software should model the Domain Software & Project should be based on the Domain Model Software that provides rich functionality based on a fundamental understanding of the core domain Tackling Essence in the Heart of Software
- 61. 61 / 문서의제목 But Remember... No Silver Bullet
- 62. 62 / 문서의제목 Resources - Domain-Driven Design, Eric Evans, Addison-Wesley, 2003 - Patterns of Enterprise Application Architecture, Martin Fowler, Addison-Wesley, 2002 - Applying Domain-Driven Design and Patterns, Jimmy Nilson, Addison-Wesley, 2006 - Domain Driven Design Quickly, http://www.infoq.com/minibooks/domain-driven- design-quickly - Domain-Driven Design Step-By-Step, http://dddstepbystep.com/cfs- filesystemfile.ashx/__key/CommunityServer.Components.SiteFiles/Domain-Driven- Design-_2D00_-Step-by-Step.pdf - Domain-Driven Design Community, http://domaindrivendesign.org/ - Eternity’s Chit-Chat, http://aeternum.egloos.com/
- 63.
- 64.