Difference between revisions of "The ROI of Systems Engineering"
Jump to navigation
Jump to search
(Created page with '<blockquote>Boehm, B., R. Valerdi, and E.C. Honour. 2008. "The ROI of Systems Engineering: Some Quantitative Results for Software-Intensive Systems." ''Systems Engineering'', 11(...') |
m (Text replacement - "SEBoK v. 2.9, released 20 November 2023" to "SEBoK v. 2.10, released 06 May 2024") |
||
(20 intermediate revisions by 6 users not shown) | |||
Line 1: | Line 1: | ||
<blockquote>Boehm, B., R. Valerdi, and E.C. Honour. 2008. "The ROI of Systems Engineering: Some Quantitative Results for Software-Intensive Systems." ''Systems Engineering'', 11(3): 221-234.</blockquote> | <blockquote>Boehm, B., R. Valerdi, and E.C. Honour. 2008. "The ROI of Systems Engineering: Some Quantitative Results for Software-Intensive Systems." ''Systems Engineering'', 11(3): 221-234.</blockquote> | ||
+ | ==Usage== | ||
+ | This source is considered a primary reference for the [[Economic Value of Systems Engineering]] article. | ||
==Annotation== | ==Annotation== | ||
− | + | The return on investment investigation is a core part of the rationale for doing Systems engineering as a part of the problem solving approach in an organization – and this work provides real statistical evidence of the efficacy of the approach. This article focuses on software intensive systems, but the results are generally valid. | |
− | |||
+ | <center>'''SEBoK v. 2.10, released 06 May 2024'''</center> | ||
[[Category:Primary Reference]] | [[Category:Primary Reference]] |
Latest revision as of 22:59, 2 May 2024
Boehm, B., R. Valerdi, and E.C. Honour. 2008. "The ROI of Systems Engineering: Some Quantitative Results for Software-Intensive Systems." Systems Engineering, 11(3): 221-234.
Usage
This source is considered a primary reference for the Economic Value of Systems Engineering article.
Annotation
The return on investment investigation is a core part of the rationale for doing Systems engineering as a part of the problem solving approach in an organization – and this work provides real statistical evidence of the efficacy of the approach. This article focuses on software intensive systems, but the results are generally valid.