DDD and MDD approaches focus on accurately modeling a problem before designing a solution. In general, DDD is considered more abstract, with no specifically suggested technologies or design tools. MDD/MDA is considered more specific, with suggestions to use UML for design work. The Model-View-Controller (MVC) is an architectural pattern that separates an application into three main logical components: the model, the view, and the controller.

thank you Krunalkumar Shah

I have conflict between DDD and MDD

1- what is the difference between domain and model?

2- how can we identify them from empirical viewpoint?

3- how do MVC provide modularity to code? what is the meaning of modulairty here?

4- in software engineering phase, can we consider that :

" MVC is a architecture pattern that is used in development and maintenace phase, while DDD and MDD are used in analysis phase" ?

Model would be your identified set of data structures, domain would represent ones business logic, domain is defined as - "a specified sphere of activity or knowledge" so this is probably best described as a set of existing objects to represent each aspect of the business logic. These objects would each encapsulate a model that pertains to each aspect that the object imitates...Totally different imho.

MVC provides modularity is the design and implementation of software such that one could remove and replace newer hardware for instance without having to perform significant software refactoring. MVC should promote the implementation of clear crisp interfaces all along the development cycle. i. e, a hardware device, a hardware device driver that directly interfaces to the registers of the device on one hand and provides the read(), write() on the other. The component interface that interfaces to the device driver on one hand and to the application on the other. So if you upgrade the hardware device, you only update the device driver nothing else.

thank you William Williams , I know that each business object represent a domain. and each domain isolated from the other because of single responsibility principle (SPR).

But

I not understand that ( These objects would each encapsulate a model that pertains to each aspect that the object imitates ), & (model is as a set of data structure) can you declare that ,please - with example if you prefer

MVC, DDD, MDD are not analysis approach just concepts on how to implement your design. They do have an affect on the system architecture and performance and sustainability. They can affect how you approach the implementation however the analysis to me is the breaking down of the requirements into manageable pieces that you can code. This would be the process of taking your written requirements and breaking them down into paragraphs, then into nouns and verbs, etc. finally into manageable functions and procedures.

Ok a domain would be a teacher say, this teacher (domain) has courses (object), in each "course" is a student (object). objects would be "courses", "students". the object "courses" would encapsulate courses (data structure) the object "students" would encapsulate students (data structure) does that make sense?

thank you William Williams for your useful answers.

I agree with you in DDD and MDD are approaches of how system will implement (breaking system to collection of domains or models, then convert the business logic of each domain or model to code)...correct me if I have wrong.

- there are some system's architecture is built based on DDD and other based on MDD.

I semi understand how breaking system to domains, but I didn't with MDD.

- unfortunalty, I can't understand your example well and can't apply it for system. let's take e-commerce as example. I attached domains in document....Am I correct in my view? can you review it please.

Amany, I will be glad to respond but please give me some time... I am currently at work. But just a quick look... Shows me you are trying to do to much in say product catalog for instance... You are purchasing in a product catalog object, an object should perform what its name is, product catalog has nothing to do with purchasing... does that make sense? I will send you a word doc back this evening at the latest tomorrow.

Dear William Williams thanks for your interest, take your time.

this document is my scratched scrawl to apply what I understand from my reading and research in Domain driven design and system architecture. so you may find it without helpful details.

you are right, I missed purchasing domain.

product catalog is business object (domain) responsible for products in e-commerce system whether in store or in point-for-sale.

I would say your on the right track Amany...

Dear William Williams How are you?

1- are content in my attach is correct?

2- to can understand a model meaning, based on e-commerce example, how it breaking to model?

mvc is a completely different subject than the other two.

1- Model View Controller (MVC) is a programming architecture that divides software into three separate parts. These sections include Model for database communication, View for creating a user interface to display and change database data, and Controller for processing user requests.

But DDD and MDD are software analysis and design methodologies, each of which looks at the issue from a different angle of view, and with tools, best practices, and designing patterns such as factory and repository, etc., it is impossible to solve it....

2- As mentioned, DDD and MDD are introduced during software analysis and design, the effect of which continues until the moment of application, but mvc is the architecture of programming layering(3 tier), which is in C# ASP .Net MVC

3- All three of these affect the architecture of the system. DِِDD and MDD affect the type of business operation of the system and its service and the type of its facilities, and ultimately affect the classes and services.But mvc is an independent architecture that separates the program into three different layer

In software engineering, MVC is a design pattern, which structures the system-to-be in three layers improving thus the system scalability. The principle of MVC is simple: the model or the domain classes (objects) could only communicate with the view's objects through the controler class.

Meanwhile, DDD and MDD mean the same thing. They are different names to call the UML classes diagram of the analysis phase.

In fact, At this phase of software engineering, MDD or DDD represent the domain or the model classes with their attributes and without providing methods.

Next, in the design phase, once the methods are defined, the DDD or MDD will be enriched by those methods as well as new design classes and even applying some design patterns, such as MVC.

In software Application design , Model View Controller (MVC) is one of the software design patterns for multi-tier software architecture. So it has nothing to do with the analysis. One of the main purposes (supposedly) of the MVC is separation of concerns which is one of the principles of the Object Orientation Design (OOD) .

DDD = Detailed Design Document, is one of the design artifacts that the application architect needs to author. DDD must include specific diagrams like:

1- Concept and Context Diagrams

2- Logical and Topology Diagrams

4- Data Model Diagrams (Logical and physical)

3- Class and Object Diagrams

4- Sequence, Interaction, Workflow and State Diagrams

….These diagrams can be authored using one or both modelling languages:

(a) Unified Modelling Language (UML). and/or

(b) ArchiMate which is recommended by TOGAF.

You can use Visio or Enterprise Architect tools to help you authoring the diagrams.

Besides the DDD, the System Specification Document must be produced

The DDD use the following as an input:

(a) Top Level Design (TLD). TLD includes the Concept, Context and Logical Diagrams, and

(b) Requirement Specification Document (RSD).

RSD is the most important analysis document that uses the Requirement Document (RD) as an input. RD is considered as an analysis document. The RSD list all possible Analysis Use Cases, Process (workflow) diagrams and typically contains the sign-off matrix.

If you were to write a short document about what your application needs to do for the business, and, the business agrees with it; then, you likely would have a domain-focused explanation. Using their business terms, the verbs in your document are functions or methods and the nouns are the data. If your design uses this language and remains true to a specific domain, I believe you would be as close to domain-driven design as possible to explain in less than many books.

All of them are architecture style to implement separation of concern. The key objective of these design practices is to organize code for ease of maintainability.

MVC seprate code logic into model, view and controller.

DDD domain driven design is more business oriented, it group code logic for specific business feature/capability like order details, order list

MDD model driven design is problem focus development. How to take care two way communication.

in case study, can we say sale, inventory, store....are models in e-commerce web application?

A sale would likely have a view to a user where they can select the items they want. The selection would be processed through appropriate steps by the controller. The inventory would be in the database and be brought forward by the model methods to be viewed and would be updated by the model methods to correct the inventory accounting for the sale. Model, View, and Controller are a way to separate the software into a processing standard to help understand the design. The data (nouns) are not the model, but would be managed by code at the model layer.

I believe you mean to write a business case (not case study) for ERP (Enterprise Resource Planning) system [Inventory, orders (Sales and Purchase), Invoices (AR & AP) , Shipping (Packing & Receiving), user subscription] that you mentioned, I would recommend that your visit this site: www.INTooSolutions.com ( I was the CTO and CEO of the company before selling it last Dec 2019)

However, if you are doing that as part of your research project I can help you. my email is: [email protected]