Premium
Obstacles to the flow of requirements verification
Author(s) -
Marchant Alan B.
Publication year - 2008
Publication title -
systems engineering
Language(s) - English
Resource type - Journals
SCImago Journal Rank - 0.474
H-Index - 50
eISSN - 1520-6858
pISSN - 1098-1241
DOI - 10.1002/sys.20127
Subject(s) - computer science , systems engineering , process (computing) , verification , requirements management , software engineering , requirements analysis , task (project management) , functional verification , requirements engineering , requirements elicitation , non functional requirement , system requirements , formal verification , risk analysis (engineering) , engineering , software , software system , programming language , medicine , software construction , operating system
Abstract The process of developing technical requirements and subsequently documenting adherence to those requirements is a primary task for Systems Engineering. Disciplined validation and verification of requirements helps assure that the product system will be successful as designed and gives the program a fighting chance to achieve its goals. But commitment and adherence to a process of thorough validation and verification is not always sufficient. Unforeseen technical constraints and logical inconsistencies often spring up at the last minute to block requirements verification for complex systems. By recognizing weaknesses in the structure and definition of requirements that are likely to interfere with the verification flow, the systems engineer can create a more manageable hierarchy of requirements and more effectively redirect the verification process when difficulties arise. © 2008 Wiley Periodicals, Inc. Syst Eng