Effectively defining "shall not" requirements

Jeffrey Voas, Phillip Laplante

Research output: Contribution to journalReview article

2 Scopus citations

Abstract

The authors review how to define a set of "negative requirements," or hazards, starting with elicitation and discovery of shall-not requirements through system integration and testing using a process called hazard mining.

Original languageEnglish (US)
Article number5196658
Pages (from-to)46-52
Number of pages7
JournalIT Professional
Volume12
Issue number3
DOIs
StatePublished - May 1 2010

All Science Journal Classification (ASJC) codes

  • Software
  • Hardware and Architecture
  • Computer Science Applications

Fingerprint Dive into the research topics of 'Effectively defining "shall not" requirements'. Together they form a unique fingerprint.

  • Cite this