Effectively defining "shall not" requirements

Jeffrey Voas, Phillip A. Laplante

Research output: Contribution to journalReview article

2 Citations (Scopus)

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

Fingerprint

Hazards
Testing

All Science Journal Classification (ASJC) codes

  • Software
  • Hardware and Architecture
  • Computer Science Applications

Cite this

Voas, Jeffrey ; Laplante, Phillip A. / Effectively defining "shall not" requirements. In: IT Professional. 2010 ; Vol. 12, No. 3. pp. 46-52.
@article{92ce682ce1f04263922a446c01cffd34,
title = "Effectively defining {"}shall not{"} requirements",
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.",
author = "Jeffrey Voas and Laplante, {Phillip A.}",
year = "2010",
month = "5",
day = "1",
doi = "10.1109/MITP.2009.87",
language = "English (US)",
volume = "12",
pages = "46--52",
journal = "IT Professional",
issn = "1520-9202",
publisher = "IEEE Computer Society",
number = "3",

}

Effectively defining "shall not" requirements. / Voas, Jeffrey; Laplante, Phillip A.

In: IT Professional, Vol. 12, No. 3, 5196658, 01.05.2010, p. 46-52.

Research output: Contribution to journalReview article

TY - JOUR

T1 - Effectively defining "shall not" requirements

AU - Voas, Jeffrey

AU - Laplante, Phillip A.

PY - 2010/5/1

Y1 - 2010/5/1

N2 - 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.

AB - 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.

UR - http://www.scopus.com/inward/record.url?scp=77952840631&partnerID=8YFLogxK

UR - http://www.scopus.com/inward/citedby.url?scp=77952840631&partnerID=8YFLogxK

U2 - 10.1109/MITP.2009.87

DO - 10.1109/MITP.2009.87

M3 - Review article

VL - 12

SP - 46

EP - 52

JO - IT Professional

JF - IT Professional

SN - 1520-9202

IS - 3

M1 - 5196658

ER -