Giovanni Gentili wrote:
Why we must restrict the use case to a single vocabulary
or analyze all the possibile vocabularies?
I think it's be better to "generalize" the problem
and find a unique solution for human/machine.
The issue when trying to abstract problems is that you can end up doing
"architecture astronautics"; you concentrate on making generic ways to
build solutions to weakly constrained problems without any attention to
the details of those problems that make them unique. The solutions that
are so produced often have the theoretical capacity to solve broad
classes of problem, but are often found to be poor at solving any
specific individual problem.
By looking at actual use cases we can hope to retain enough detail in
the requirements that we satisfy at least some use cases well, rather
than wasting out time building huge follies that serve no practical
purpose to anyone.
