![domain driven design interview questions domain driven design interview questions](https://devopedia.org/images/article/233/9553.1581163851.png)
We begin by understanding what are why trying to solve, how this problem came into existence and the projected value of the solution. But the one that I present here is one that has given me the best results, which means high value deliver at a lower cost There are many different ways, and which one to apply depends and several factors like what would be the value of the project, what is the projected cost, who and why are the stakeholders, etc. So if we need to develop a complex system, how do we go about it? The benefit is that it facilitates the creation of well cohesive systems In the thought process it means to understand the big picture, decompose it, and understand the relationships between the parts. Is a way to design complex system by creating models and sub models of the domain that the system tries to implement. The benefit is that it offers a more precise and organized conversation between developers and domain expertsĭDD stands for Domain Driven Design. In the thought process means thinking from outside the system in. While it is a refinement to TDD, it concentrates in understanding the user’s behavior, and yields nicely to a good acceptance of the end system. The benefit is that it promotes simpler designs, and promotes confidence that the system works as expectedīDD stands for Behavioral Driven Development. In the thought process it means thinking from inside the system out. You know you are done when the function passes the test.
DOMAIN DRIVEN DESIGN INTERVIEW QUESTIONS SOFTWARE
Is a way of software development where the test for a function gets written first, then the function. Me: Sure… (I have the feeling that I am been trolled) Him: How can you work like that? Making sure the system works is the most important thing Me: Testing is important, but more important is to deliver a system that provides the functionality expected, and testing is part of the process to reach that objective Him: So you don’t believe that testing is important? Me: But I didn’t say that we shouldn’t use TDD, I said that TDD has a place in the whole development cycle
![domain driven design interview questions domain driven design interview questions](https://i.pinimg.com/originals/7d/f0/09/7df0095da58769000d5e647419c5d314.jpg)
We already prove that TDD is the One True Way™
![domain driven design interview questions domain driven design interview questions](https://res.cloudinary.com/practicaldev/image/fetch/s--ylPIwIUg--/c_imagga_scale,f_auto,fl_progressive,h_900,q_auto,w_1600/https://dev-to-uploads.s3.amazonaws.com/i/41tgg0r22nddgaimoi7f.png)
Me: I think that we need to use BDD to capture the usage stories, then DDD to design, and TDD to make sure the deliverable works Him: So it is obvious that we need to use TDD all the way A few months ago, I had a conversation with a colleague that went like this: