Use Case Driven Development

The main content of the following image is from books: Use Case Driven Object Modeling with UML Theory and Practice and Object-Oriented Software Engineering: a Use Case Driven Approach.

It is a whole process about how to convert Functional Requirements to Working Code in Industrial System Development. It frist identifies the actors who will use the application; then identifies use cases of each actor; break each use case into boundary, controll and entity; design the relationship betwen them; and finally imeplements the code.

If we replace the End-User and Customer with Domain Exports, can this approach work with Domain Driven Development?