Eric Honour
Research Subjects
Research Interests
Eric Honour has a total of 5 co-authors. Here are the top co-authors by number of shared publications:
- Tyson R. Browning
Neeley School of Business, Texas Christian University
2 shared publications Barry Boehm
Center for Systems & Software Engineering, University of Southern California, Los Angeles, CA 90089
1 shared publicationMarkus Hoppe
Technische Universitaet Muenchen Institute of Astronautics Boltzmannstr. 15 85748 Garching Germany
1 shared publication- Ricardo Valerdi
Department of Systems and Industrial Engineering, The University of Arizona, Tucson, AZ 85721, USA
1 shared publication - Viktor Lévárdy
Technische Universitaet Muenchen Institute of Astronautics Boltzmannstr. 15 Garching 85748 Germany
1 shared publication
Latest Publications
- 30 March 2018
- Published by Wiley in Systems Engineering
- Vol. 21 (3) , 148-151
A historical perspective on systems engineering
With 20 years of the Systems Engineering journal completed, this short article considers its impact on the discipline of systems engineering (SE) as a whole. It reviews the founding principles of this journal and assesses how well it has advanced those principles. In a broader sense, it also reviews 70 years of existence of the SE discipline and then looks ahead for its promises. After several decades of rapid growth, SE appears to have partially stagnated in the 1990s and 2000s in the face of process control pressures. The use of first principles has dwindled. Resurgence in the field, however, has been coincident with the time frame of this journal, as first principles are being redeveloped and new methods are arising. This journal successfully acts as a stimulus for that resurgence.
- 30 March 2018
- Published by Wiley in Systems Engineering
- Vol. 21 (3) , 148-151
A historical perspective on systems engineering
With 20 years of the Systems Engineering journal completed, this short article considers its impact on the discipline of systems engineering (SE) as a whole. It reviews the founding principles of this journal and assesses how well it has advanced those principles. In a broader sense, it also reviews 70 years of existence of the SE discipline and then looks ahead for its promises. After several decades of rapid growth, SE appears to have partially stagnated in the 1990s and 2000s in the face of process control pressures. The use of first principles has dwindled. Resurgence in the field, however, has been coincident with the time frame of this journal, as first principles are being redeveloped and new methods are arising. This journal successfully acts as a stimulus for that resurgence.
ENGINEERING THE VIRTUAL OR COLLABORATIVE SOS
The largest, most complex, and most prevalent systems of systems (SoS) are virtual or collaborative in nature. In such a SoS, there is no central authority to perform systems engineering. Yet, the virtual or collaborative SoS does grow, adapt, and evolve in response to the needs of the many stakeholders. Changes in the SoS happen because of many changes in the constituent systems (CS), with each change occurring when the CS owners deem it useful to change. The systems engineering activities in the CS can be used to guide and affect the SoS through a collaborative and competitive environment in which each CS systems engineer seeks to optimize the SoS behavior for their own purposes. This requires a different approach to the systems engineering activities, in which greater emphasis is on the higher‐level analysis, architecting, and quantification. This paper describes the modified systems engineering approach, showing how to engineer the SoS from within the scope of a CS.
ENGINEERING THE VIRTUAL OR COLLABORATIVE SOS
The largest, most complex, and most prevalent systems of systems (SoS) are virtual or collaborative in nature. In such a SoS, there is no central authority to perform systems engineering. Yet, the virtual or collaborative SoS does grow, adapt, and evolve in response to the needs of the many stakeholders. Changes in the SoS happen because of many changes in the constituent systems (CS), with each change occurring when the CS owners deem it useful to change. The systems engineering activities in the CS can be used to guide and affect the SoS through a collaborative and competitive environment in which each CS systems engineer seeks to optimize the SoS behavior for their own purposes. This requires a different approach to the systems engineering activities, in which greater emphasis is on the higher‐level analysis, architecting, and quantification. This paper describes the modified systems engineering approach, showing how to engineer the SoS from within the scope of a CS.
- 1 June 2011
- Published by Wiley in INCOSE International Symposium
- Vol. 21 (1) , 1233-1245
10.4.1 Sizing Systems Engineering Activities to Optimize Return on Investment
- 1 June 2011
- Published by Wiley in INCOSE International Symposium
- Vol. 21 (1) , 1233-1245
10.4.1 Sizing Systems Engineering Activities to Optimize Return on Investment
- 1 July 2010
- Published by Wiley in INCOSE International Symposium
- Vol. 20 (1) , 1422-1439
11.4.2 Systems Engineering Return on Investment
Research work continues into Systems Engineering Return on Investment (SE‐ROI) following prior work on Value of Systems Engineering and Systems Engineering Effectiveness. This paper presents major results in the form of statistically proven relationships between systems engineering (SE) activities and the technical, schedule and cost success of programs. It has been found that all defined SE activities correlate positively with program success as measured in three of four success metrics used (cost overrun, schedule overrun and perceptive success). When the effect of program characterization parameters is included, the correlation is strong with optimum levels of SE activities as much as 25% of a program cost. The paper presents quantified values for the relationships, indicating appropriate levels of each SE activity that correlate to optimum levels of success. Results show a surprising lack of correlation between SE activities and the technical quality of the product system, for which some possible explanations are provided.
- 1 July 2010
- Published by Wiley in INCOSE International Symposium
- Vol. 20 (1) , 1422-1439
11.4.2 Systems Engineering Return on Investment
Research work continues into Systems Engineering Return on Investment (SE‐ROI) following prior work on Value of Systems Engineering and Systems Engineering Effectiveness. This paper presents major results in the form of statistically proven relationships between systems engineering (SE) activities and the technical, schedule and cost success of programs. It has been found that all defined SE activities correlate positively with program success as measured in three of four success metrics used (cost overrun, schedule overrun and perceptive success). When the effect of program characterization parameters is included, the correlation is strong with optimum levels of SE activities as much as 25% of a program cost. The paper presents quantified values for the relationships, indicating appropriate levels of each SE activity that correlate to optimum levels of success. Results show a surprising lack of correlation between SE activities and the technical quality of the product system, for which some possible explanations are provided.
- 1 April 2008
- Published by Wiley in Systems Engineering
- Vol. 11 (3) , 221-234
The ROI of systems engineering: Some quantitative results for software‐intensive systems
This paper presents quantitative results on the return on investment of systems engineering (SE‐ROI) from an analysis of the 161 software projects in the COCOMO II database. The analysis shows that, after normalizing for the effects of other cost drivers, the cost difference between projects doing a minimal job of software systems engineering— as measured by the thoroughness of its architecture definition and risk resolution— and projects doing a very thorough job was 18% for small projects and 92% for very large software projects as measured in lines of code. The paper also presents applications of these results to project experience in determining ‘‘how much up front systems engineering is enough’’ for baseline versions of smaller and larger software projects, for both ROI‐driven internal projects and schedule‐driven outsourced systems of systems projects. © 2008 Wiley Periodicals, Inc. Syst Eng
- 1 April 2008
- Published by Wiley in Systems Engineering
- Vol. 11 (3) , 221-234
The ROI of systems engineering: Some quantitative results for software‐intensive systems
This paper presents quantitative results on the return on investment of systems engineering (SE‐ROI) from an analysis of the 161 software projects in the COCOMO II database. The analysis shows that, after normalizing for the effects of other cost drivers, the cost difference between projects doing a minimal job of software systems engineering— as measured by the thoroughness of its architecture definition and risk resolution— and projects doing a very thorough job was 18% for small projects and 92% for very large software projects as measured in lines of code. The paper also presents applications of these results to project experience in determining ‘‘how much up front systems engineering is enough’’ for baseline versions of smaller and larger software projects, for both ROI‐driven internal projects and schedule‐driven outsourced systems of systems projects. © 2008 Wiley Periodicals, Inc. Syst Eng
- 10 March 2008
- Published by Wiley in Systems Engineering
- Vol. 11 (3) , 187-202
Measuring the life‐cycle value of enduring systems
A goal of systems development is to produce enduringly valuable product systems— i.e., systems that are valuable when delivered to their users and which continue to be attractive to their stakeholders over time. However, quantifying the life‐cycle value (LCV) provided by a system has proven elusive. In this paper, we propose an approach to quantifying a system's LCV based on the key parameters that have perceived value to the system's stakeholders. For this, we draw upon insights from the management, marketing, product development, value engineering, and systems engineering literature. We then demonstrate our proposed approach with an example of a cellular telephone system. By designing systems for maximum LCV, systems architects and engineers will provide dramatically increased value to their organizations and other stakeholders. However, to provide maximum LCV, a system may need to be designed to facilitate adaptability to changing circumstances and stakeholder preferences. We conclude the paper with discussions of some of the major difficulties in measuring LCV and some of the opportunities for further research in this area. © 2008 Wiley Periodicals, Inc. Syst Eng
- 10 March 2008
- Published by Wiley in Systems Engineering
- Vol. 11 (3) , 187-202
Measuring the life‐cycle value of enduring systems
A goal of systems development is to produce enduringly valuable product systems— i.e., systems that are valuable when delivered to their users and which continue to be attractive to their stakeholders over time. However, quantifying the life‐cycle value (LCV) provided by a system has proven elusive. In this paper, we propose an approach to quantifying a system's LCV based on the key parameters that have perceived value to the system's stakeholders. For this, we draw upon insights from the management, marketing, product development, value engineering, and systems engineering literature. We then demonstrate our proposed approach with an example of a cellular telephone system. By designing systems for maximum LCV, systems architects and engineers will provide dramatically increased value to their organizations and other stakeholders. However, to provide maximum LCV, a system may need to be designed to facilitate adaptability to changing circumstances and stakeholder preferences. We conclude the paper with discussions of some of the major difficulties in measuring LCV and some of the opportunities for further research in this area. © 2008 Wiley Periodicals, Inc. Syst Eng
- 1 July 2005
- Published by Wiley in INCOSE International Symposium
- Vol. 15 (1) , 1530-1545
10.4.1 Measuring the Lifecycle Value of a System
- 1 July 2005
- Published by Wiley in INCOSE International Symposium
- Vol. 15 (1) , 1530-1545
10.4.1 Measuring the Lifecycle Value of a System
- 1 June 2004
- Published by Wiley in INCOSE International Symposium
- Vol. 14 (1) , 1660-1674
8.2.3 Verification, Validation & Testing Strategy and Planning Procedure
- 1 June 2004
- Published by Wiley in INCOSE International Symposium
- Vol. 14 (1) , 1660-1674
8.2.3 Verification, Validation & Testing Strategy and Planning Procedure