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?
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.
@@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.
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?
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.
@@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.