Premium
7.7.1 Getting the right requirements right
Author(s) -
Kasser Joseph
Publication year - 2012
Publication title -
incose international symposium
Language(s) - English
Resource type - Journals
ISSN - 2334-5837
DOI - 10.1002/j.2334-5837.2012.tb01385.x
Subject(s) - requirements analysis , requirements management , requirements engineering , non functional requirement , computer science , requirements elicitation , system requirements , functional requirement , software requirements specification , software requirements , system requirements specification , software , engineering management , systems engineering , engineering ethics , software engineering , engineering , software system , software development , software design , programming language , software construction , operating system
Research has shown that there is an on‐going consensus that: good requirements are critical to the success of a project the current requirements paradigm produces poorly written requirements and ways of producing better requirements have been around for more than 20 years. So, instead of producing yet another paper on how to write better requirements, this paper begins by posing the following question: why do systems and software engineers continue to produce poor requirements when ways to write good requirements have been documented in conference papers and textbooks? The paper then documents findings from research into the problem via the systems thinking perspectives and hypothesises that there are two requirements paradigms; the original A paradigm and the current B paradigm which is inherently flawed. The paper then dissolves the problem of poor requirements by applying technology to reduce the need for most of the requirements written today.