Categorizing software requirements based on functional and architectural views in terms of logical and probabilistic behavior models could help mitigate weaknesses in the elicitation and structuring of requirements.
No takes yet. Share an insight, caveat, or question.
Manfred Broy (2015) studied this question.
Synapse has enriched 5 related papers. Consider them for comparative context: