Does it make sense to use UML in Domain Driven Design, how to do it

The pub­lic­a­tion includes a descrip­tion of a short design pat­tern: Domain Driv­en Design, MVC and Bound­ary Con­trol Entity. It also includes examples of mod­els made in UML.

Descrip­tion Table of Contents:
1 Description
1.1 The Build­ing Blocks Of A Mod­el-Driv­en Design
1.2 Layered Architecture
1.3 Hexagon­al architecture
1.4 Microservices vs. mono­lith and gen­er­al idea
1.5 Microservices architecture
1.6 Microservices can be imple­men­ted in vari­ous technologies
1.7 Design­ing process
1.8 BCE Pattern
2 DDD Pro­file UML
3 The applic­a­tion model
3.1 The applic­a­tion mod­el Use Case Diagram
3.2 Sys­tem High-Level Archi­tec­ture Com­pon­ent Diagram
3.3 Applic­a­tion ser­vice 1
3.3.1 Primary Actors
3.3.2 Details
3.3.3 Scenarios
3.3.3.1 New document
3.3.4 Relationships
3.3.5 Sub Diagrams
3.3.5.1 App 1 New Doc­u­ment – HLD scen­ario – sequence diagram
3.3.5.2 App 1 New Doc­u­ment – LLD scen­ario – sequence dia­gram BCE
3.3.5.3 App 1 New Doc­u­ment – LLD scen­ario – sequence dia­gram DDD
3.3.5.4 Applic­a­tion ser­vice 1 Class Dia­gram LLD archi­tec­ture with BCE
3.3.5.5 Applic­a­tion ser­vice 1 Class Dia­gram LLD archi­tec­ture with DDD
3.3.5.6 Doc­u­ment as an aggregate
3.3.5.7 Doc­u­ment Struc­ture Com­pos­ite Struc­ture Diagram
3.3.6 Traceability