Use Cases Are Not All the Same – Why We Should Speak More Precisely
Summary: “Use Case” in UML Describes business objectives and user value – a requirements artifact. In Clean Architecture, a UseCase (Interactor) refers to an application operation of the Application Layer that orchestrates repositories/services. These are different abstractions with different purposes. Clearly separating the two avoids misunderstandings and architectural erosion. A brief misunderstanding to start PM: “We need two new use cases: Login and Save note.” Developer: “Okay, I’ll create two use cases and bind them to the repositories.” ...