Systems Engineering Pathology: Comprehensive Characterization of Systems Engineering Dysfunction (original) (raw)

Selected systems engineering process deficiencies and their consequences

Acta Astronautica, 2007

The systems engineering process is well established and well understood. While this statement could be argued in the light of the many systems engineering guidelines and that have been developed, comparative review of these respective descriptions reveal that they differ primarily in the number of discrete steps or other nuances, and are at their core essentially common. Likewise, the systems engineering textbooks differ primarily in the context for application of systems engineering or in the utilization of evolved tools and techniques, not in the basic method. Thus, failures in systems engineering cannot credibly be attributed to implementation of the wrong systems engineering process among alternatives. However, numerous systems failures can be attributed to deficient implementation of the systems engineering process. What may clearly be perceived as a system engineering deficiency in retrospect can appear to be a well considered system engineering efficiency in real timean efficiency taken to reduce cost or meet a schedule, or more often both. Typically these efficiencies are grounded on apparently solid rationale, such as reuse of heritage hardware or software. Over time, unintended consequences of a systems engineering process deficiency may begin to be realized, and unfortunately often the consequence is system failure. This paper describes several actual cases of system failures that resulted from deficiencies in their systems engineering process implementation, including the Ariane 5 and the Hubble Space Telescope.

Eight deadly defects in systems engineering and how to fix them

2007

Any organization desirous to adopt or improve systems engineering needs to be aware that research into the nature of systems engineering has identified a number of defects in the current systems engineering paradigm. This paper discusses eight of these defects and ways to fix or compensate for them.

A road map for implementing systems engineering

Sandia National …, 1997

Studies by academia, industry, and government indicate that applying a sound systems engineering process to development programs is an important tool for preventing cost and schedule overruns and performance deficiencies. There is an enormous body of systems engineering ...

HOW TO DEVELOP EFFECTIVE SYSTEM ENGINEERS

Proceedings of the American Society for Engineering Management 2020 International Annual Conference, 2020

System engineering (SE) is a structured systematized methodology that deals with designing, managing, and optimizing systems performance. System engineers use the perspective of system thinking to make the successful use and retirement of engineering systems. Since the role of system engineers ranges widely from technical support to customer interaction, system design to management, there is a demand to develop a cadre of effective systems engineers. However, two critical questions are not well-defined in the extant body of SE literature: (1) What are the fundamental attributes of systems engineering that would influence the effectiveness of individual systems engineers? (2) What are the corresponding leading indicators for appraising the performance of an individual systems engineer? To respond to these questions, this paper proposes a new instrument to evaluate the performance of the system engineers and subsequently identifies their strengths and weakness within the complex system domain. The implication of this study would assist systems engineers in strengthening their system skills and reflects a state that can be improved through training, workshops, and education to prepare them to face the complex situations originating from the problem domain.

5.5.3 Systems Engineering Management

INCOSE International Symposium, 2004

Organizations may have sophisticated and detailed systems engineering process models yet struggle to implement them effectively in the face of conflicting internal priorities, legacy practices and slowly changing cultures. Taking experiences from a number of sources this paper identifies a range of current systems engineering issues and suggests that it is the interface of systems engineering with other business activities that is a cause of many implementation problems. By taking a systems view of the business (a systems-make-systems approach), one can use systems engineering principles to address these problems. A broader remit for Systems Engineering Management is recommended.

Principles for Successful Systems Engineering

Procedia Computer Science, 2012

This paper summarizes several iterations in developing a compact set of four key principles for successful systems engineering, which are 1) Stakeholder Value-Based System Definition and Evolution 2) Incremental Commitment and Accountability 3) Concurrent Multidiscipline System Definition and Development, and 4) Evidence-Based and Risk-based Decisionmaking. It provides a rationale for the principles, including short example case studies of failed projects that did not apply the principles, and of successful projects that did. It will compare the principles with other sets of principles such as the Lean Systems Engineering and the Hitchins set of principles for successful systems and systems engineering.

Applying systems analysis to program failure in organizations

Innovative Higher Education, 1986

Certain systems analysis techniques can be applied to examinations of program failure in continuing education to locate weaknesses in planning and implementing stages. Since failures can be the result of human errors and environmental conditions (and frequently a combination of both), a systems design to determine causes must include techniques that can detect both individual and nonhuman factors. Questions to guide an analysis and various procedures are recommended. Unexamined failures may lead to "tossing the baby out with the bathwater," when analysis, in fact, could be the initial step toward successful future implementation.

Overcoming barriers to systems engineering process improvement

Systems Engineering, 2000

Neither systems engineering nor process improvement is new. Since 1992, INCOSE papers and others have been reporting success in documenting and improving processes. A considerable body of process improvement literature is available, particularly related to improvement of software development processes. Even systems engineering process improvement is gaining in popularity, judging from the increasing number of INCOSE papers detailing various efforts. Yet the nature of systems engineering poses challenges over and above those seen in other process improvement efforts. This paper focuses on identifying and resolving typical barriers to improving the systems engineering process.

9.2.1 The Many Faces of Systems Engineering

INCOSE International Symposium, 2014

This article "The Many Faces of Systems Engineering" is based on a qualitative study that included, at its core, dozens of in-depth interviews with prominent experts in the field. We have conversed with lead systems engineers, high ranking executives, academic experts and experienced consultants. Roughly one half of the study's participants are Israelis, with the other half hailing from a multitude of other countries. We felt it was important to present a wide spectrum of perspectives on this field, as it pertains to the different features of various industries and organizations. The main findings of this study are: • Systems engineering is a profession in the making that links the classical engineering disciplines with managerial and organizational systems. • since the early 1970's, the need to create integration, both between the various engineering disciplines and between engineering disciplines in general and nonengineering systems grew constantly .