There is a tendency to abandon the domain model once the requirements are thought to be understood and focus shifts to design and implementation. Hence the analysis model becomes obsolete and can even be a source of confusion.
MDD is a pattern listed in several texts. The distinction between MDD and DDD (Domain-Driven Design) is muddy. Also, MDD is easily confused with OMG's widely reviled Model-Driven Architecture or MDA. In my view the key insight is that the domain model evolves into the domain layer of the design model through a series of iterations. The goal of the early iterations is to faithfully represent the application domain. MDA refers to the later iterations, where the goal is modeling the implementation, but without breaking the connection to the domain. In short, the distinction between analysis model and the domain layer of the design model disappears. If problems occur during design or implementation, it's possible they are caused by an incomplete or confused understanding of the domain.