Model-Driven Design Made Simple 1 | Model-Driven Architecture | MDA | Geekific
Support us on Patreon: / geekific
Discord Community: / discord
GitHub Repository: github.com/geekific-official/
In the previous video of this series, we highlighted the importance of an approach to software development that is centered on the business domain. And Domain-Driven Design is an approach to developing software that deeply connects the implementation, the code; to the core business concepts, to the domain. But how can we encapsulate these core concepts, how can we encapsulate the domain inside our code? This video attempts to answer this question by explaining Model-Driven Design and Architecture.
Timestamps:
00:00 Introduction
00:32 What’s a Domain Model?
01:33 Domain-Driven and Model-Driven Design
03:35 Modeling the Domain
05:50 Thanks for Watching!
If you found this video helpful, check other Geekific uploads:
- Object-Oriented Programming Fundamentals: • What is Object-Oriente...
- SOLID Principles and Best Practices: • SOLID Design Principle...
- Recursion Made Simple, Recursive Methods: • What is Recursion? | R...
- Heap Space vs. Stack Memory in Java: • Heap Space vs. Stack M...
- Introduction to Unit-Testing with TDD: • Introduction to Unit-T...
- Introduction to Threads and Processes: • What is a Thread? | Th...
- Must Know Java Keywords!: • Must Know Java Keyword...
- Domain-Driven Design Made Simple: • Domain-Driven Design M...
#Geekific #DomainDrivenDesign #ModelDrivenDesign #DDD #MDD
Пікірлер: 4
Huge prog.and Encyclopedy in Software great world
I have no idea about DDD, but in OOA/D, we create use cases and ERD entities from specific requirements, then transform them into BCE(aka domain context ). This corresponds to the analysis phase. During the design phase, we utilize class diagrams and sequence diagrams. How does this process occur in DDD?
@khajalieubarrie5088
6 ай бұрын
I think the power of DDD is realised mainly in the Design and Analysis phase u mentioned. It’s about breaking down the complex business problem you are trying to solve into a feasible solution. For example, how would one identify “use cases” in OOA/D in a domain they have no idea about. DDD is there to bridge the gap between developers and the general business world because non programmers don’t know about ERD’s for example and would likely not appreciate it in trying to communicate back and forth with a developer.
@mehdi-vl5nn
6 ай бұрын
@@khajalieubarrie5088 identifying "use cases" within an unfamiliar domain can be achieved through a methodology such as RUP (Rational Unified Process). RUP includes a dedicated phase for business modeling, where use cases are formulated. The process entails progressing from business modeling to domain modeling, with a focus on requirements. This transition leads to the development of BCE (Boundary-Controller-Entity) diagrams and communication diagrams during the analysis phase.