New answers tagged

1 vote

Use Cases in Clean Architecture, in Requirements Specifications from Software Engineering and Use Case Diagrams in UML

In short In the general sense, use-cases are meant to focus on user objectives and answer the question: "why would a user use this system? And for what purpose?". They therefore focus on ...
user avatar
  • 67.8k
4 votes
Accepted

Reduce changes needed after adding a new field to domain object

Excellent observation. Is this normal? Answer: it is unfortunately. People don't seem to notice or care about this issue. Every style / design / architecture that is based on separating technical ...
user avatar
0 votes

Clean architecture, Login UseCase with OAuth breaking Single responsability principle

You are logging in the user, part of that requires that the user be in the database, so if the user isn’t in the db they have to be added. What would you expect the use case ...
user avatar
  • 10.4k
0 votes

Clean architecture, Login UseCase with OAuth breaking Single responsability principle

Sorry for being a lil late, and please consider my answer. Well for the 1st problem (multiple responsibilities) and like others pointed before, responsibility is different than functionality, meaning ...
user avatar
  • 1

Top 50 recent answers are included