Effectively defining "shall not" requirements

Jeffrey Voas; Phillip Laplante

doi:10.1109/MITP.2009.87

Effectively defining "shall not" requirements

Jeffrey Voas, Phillip Laplante

Research output: Contribution to journal › Review article › peer-review

4 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 language	English (US)
Article number	5196658
Pages (from-to)	46-52
Number of pages	7
Journal	IT Professional
Volume	12
Issue number	3
DOIs	https://doi.org/10.1109/MITP.2009.87
State	Published - May 2010

All Science Journal Classification (ASJC) codes

Software
Hardware and Architecture
Computer Science Applications

Access to Document

10.1109/MITP.2009.87

Cite this

@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 Phillip Laplante",

year = "2010",

month = may,

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",

}

TY - JOUR

T1 - Effectively defining "shall not" requirements

AU - Voas, Jeffrey

AU - Laplante, Phillip

PY - 2010/5

Y1 - 2010/5

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

AN - SCOPUS:77952840631

SN - 1520-9202

VL - 12

SP - 46

EP - 52

JO - IT Professional

JF - IT Professional

IS - 3

M1 - 5196658

ER -

Effectively defining "shall not" requirements

Abstract

All Science Journal Classification (ASJC) codes

Access to Document

Other files and links

Fingerprint

Cite this