Rethinking nonfunctional software requirements

Manfred Broy

doi:10.1109/MC.2015.139

Rethinking nonfunctional software requirements

Manfred Broy

TUM Emeriti of Excellence

Research output: Contribution to specialist publication › Article

22 Scopus citations

Abstract

Categorizing software requirements based on functional and architectural views in terms of logical and probabilistic behavior models could help mitigate weaknesses in the elicitation and structuring of requirements.

Original language	English
Pages	96-99
Number of pages	4
Volume	48
No	5
Specialist publication	Computer
DOIs	https://doi.org/10.1109/MC.2015.139
State	Published - 1 May 2015

Keywords

Software Technologies
categorization of requirements
requirements engineering
software engineering
system requirements
systems engineering

Access to Document

10.1109/MC.2015.139

Cite this

@misc{8082a2f0a6ae4de3b3d0300428d5d0e9,

title = "Rethinking nonfunctional software requirements",

abstract = "Categorizing software requirements based on functional and architectural views in terms of logical and probabilistic behavior models could help mitigate weaknesses in the elicitation and structuring of requirements.",

keywords = "Software Technologies, categorization of requirements, requirements engineering, software engineering, system requirements, systems engineering",

author = "Manfred Broy",

note = "Publisher Copyright: {\textcopyright} 1970-2012 IEEE.",

year = "2015",

month = may,

day = "1",

doi = "10.1109/MC.2015.139",

language = "English",

volume = "48",

pages = "96--99",

journal = "Computer",

issn = "0018-9162",

publisher = "IEEE Computer Society",

}

TY - GEN

T1 - Rethinking nonfunctional software requirements

AU - Broy, Manfred

PY - 2015/5/1

Y1 - 2015/5/1

N2 - Categorizing software requirements based on functional and architectural views in terms of logical and probabilistic behavior models could help mitigate weaknesses in the elicitation and structuring of requirements.

AB - Categorizing software requirements based on functional and architectural views in terms of logical and probabilistic behavior models could help mitigate weaknesses in the elicitation and structuring of requirements.

KW - Software Technologies

KW - categorization of requirements

KW - requirements engineering

KW - software engineering

KW - system requirements

KW - systems engineering

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

U2 - 10.1109/MC.2015.139

DO - 10.1109/MC.2015.139

M3 - Article

AN - SCOPUS:84930613355

SN - 0018-9162

VL - 48

SP - 96

EP - 99

JO - Computer

JF - Computer

ER -

Rethinking nonfunctional software requirements

Abstract

Keywords

Access to Document

Other files and links

Fingerprint

Cite this