Difference between revisions of "System Assurance (glossary)"
| Line 2: | Line 2: | ||
====Source(s)==== | ====Source(s)==== | ||
| − | + | NATO. February 2010. Engineering for system assurance in NATO programs. Washington, DC: NATO Standardization Agency, DoD 5220.22M-NISPOM-NATO-AEP-67. | |
| − | |||
| − | |||
===Discussion=== | ===Discussion=== | ||
Revision as of 17:53, 31 August 2011
…the justified confidence that the system functions as intended and is free of exploitable vulnerabilities, either intentionally or unintentionally designed or inserted as part of the system at any time during the life cycle... This confidence is achieved by system assurance activities, which include a planned, systematic set of multi-disciplinary activities to achieve the acceptable measures of system assurance and manage the risk of exploitable vulnerabilities. (NATO February 2010, p. 1)
Source(s)
NATO. February 2010. Engineering for system assurance in NATO programs. Washington, DC: NATO Standardization Agency, DoD 5220.22M-NISPOM-NATO-AEP-67.
Discussion
This area is for the Glossary Term Owner to provide discussion on the context and uses of the term. This is not where you should provide comments. Please use the “Discussion” tab (above) to provide feedback if you are not the term owner.
Please note that if there is more than one definition, it is very important to provide information on the context of the different terms and to explain to the user why it is not possible to identify only one definition. For example, is this an emerging concept for which there is still much research to be done? Or have two different definitions emerged as the result of two different disciplines interacting with systems engineering?