The Scope of Systems Engineering

Systems engineering is the application of Systems Thinking for improving the features and functions within a scenario in a controlled way. The basic narrative on the Scope of Systems Engineering defines the fundamental steps that must be followed in a logical sequence. Generally, systems engineering is not just running through this sequence once. Instead, systems engineering is an iterative process to achieve a feasible and optimum solution progressively by running through this logical sequence in total or in specific parts again and again. In this iterative process, the Scope of Systems Engineering captures the feedforward path. The front-loading process is described by the basic narrative on the Problem Processing Cycle considering all input information and information fed back from previous iterations. A few general principles are applicable throughout the process:

• System design follows a top-down principle as defined by the Steps A to H starting from the whole progressing to the details.
• System integration follows a bottom-up principle as defined by the Steps H to K concentrating on the assurance that the engineered system elements provide the required characteristics what is denoted as verification, and that the considered scenarios feature the intended and improved objectives what is denoted as validation.
• The consideration of alternatives is essential in all steps A to K to avoid a premature fixation on the understanding of the system environment and a particular system solution.

Due to the third principle, the Scope of Systems Engineering applies primarily and directly to conceptual design stages before Step H – Development, Adaptation and/or Procurement of System Elements – is commenced. In an economic approach, earlier iterations are kept brief considering a wider range of alternatives progressing to later iterations concentrating on more promising solutions until an optimum solution is selected for implementation.

In conceptional stages, the system integration activities are reduced to their preparation and should be supported by virtualisation strategies. For this reason, system models enabling a virtual system integration are recommended. They should be generated and maintained throughout conceptual and full-scale development to ease actual system integration in full-scale system development, and as an overall development risk mitigation measure.

So far, systems engineering has been introduced as deeply rooted in systems thinking and the employment of human specific cognitive capabilities. It makes no difference who applies systems engineering. The Scope of Systems Engineering may be adopted by individuals and groups of people independently of the grade of complexity and the need for multidisciplinary cooperation.

There is another strong argument why enterprises must consider systems engineering. Although there is no explicit legal requirement to apply systems engineering, all enterprises are well advised to implement systems engineering along the logical sequence defined by the Scope of Systems Engineering in order to satisfy their legal obedience regarding liability and safety laws and regulations. Without performing sound systems engineering all claims for being an actor on the market aware of societal responsibilities remain meaningless promises. The basic narrative on the System Life Cycle provides further guidance how to integrate and apply systems engineering in an enterprise context. The basic narrative on the Systems Engineering Value Stream details systems engineering with respect to full-scale development when systems engineering is further constraint by manifold organisational considerations.

The following pages in the page sequence addresses the Stages A to K one after another. The figure above may be used to navigate between these pages. If clicked the SVG image is displayed in a separate window. Then the hyperlinks defined in the SVG become active to jump between the pages.