They are called requirement engineers :).
Spot on regards the what and the how. Additionally to specify the what, i always document the rationale WHY. We can see this in sentence patterns for specifying use cases, epics, etc.
Spot on regards the what and the how. Additionally to specify the what, i always document the rationale WHY. We can see this in sentence patterns for specifying use cases, epics, etc.
It’s key to remember that the requirements of a Thing are the WHAT and not the HOW. Keep the requirements separate from the Design, then the requirements can stay pretty short and sweet.
It takes a very specific type of engineer or analyst to be able to think at this level of abstraction and not jump into solutionineering (design) when trying to establish exactly what the stakeholders want the system to do.
[0] https://www.incose.org/incose-member-resources/working-group...
[1] https://www.incose.org/docs/default-source/working-groups/re...