Difference between revisions of ""‐ilities""
(Created page with ""‐ilities" is the developmental, operational, and support requirements a program must address (named because they typically end in "ility"—availability, maintainabilit...") |
(→Definitions) |
||
| Line 3: | Line 3: | ||
==Definitions== | ==Definitions== | ||
According to the [[ INCOSE Systems Engineering Handbook (4th edition)]], | According to the [[ INCOSE Systems Engineering Handbook (4th edition)]], | ||
| − | :[["‐ilities"]]. The developmental, operational, and support requirements a program must address (named because they typically end in "ility" | + | :[["‐ilities"]]. The developmental, operational, and support requirements a program must address (named because they typically end in "ility" -- availability, maintainability, vulnerability, reliability, supportability, etc.). |
[[Category: Systems Engineering]][[Category: Articles]] | [[Category: Systems Engineering]][[Category: Articles]] | ||
Latest revision as of 21:25, 25 November 2020
"‐ilities" is the developmental, operational, and support requirements a program must address (named because they typically end in "ility"—availability, maintainability, vulnerability, reliability, supportability, etc.).
Definitions
According to the INCOSE Systems Engineering Handbook (4th edition),
- "‐ilities". The developmental, operational, and support requirements a program must address (named because they typically end in "ility" -- availability, maintainability, vulnerability, reliability, supportability, etc.).
