Systems-Engineering (SE) is an Engineering Process, encompassing and managing all relevant System Stakeholders Requirements; as well as all design Solutions; and necessary technology, economic, and political areas.
The fundamental purposes of Systems-Engineering are to:

• optimize the System Solution at the highest Level of Stakeholder concerns,
• synchronize all contributing disciplines to contribute efficiently to the final System characteristics,
• consider the entire System Life-Cycle needs,

• manage risks for the entire System and the entire System life.

Alternative Names

Concept Number: *223
English Master: Systems-Engineering
Synonyms, Variations & Acronyms: SE


An INCOSE Definition
“Systems-Engineering integrates all the disciplines and specialty groups into a team effort forming a structured development Process that proceeds from Concept to production to operation. Systems-Engineering considers both the business and the technical needs of all customers with the Goal of providing a Quality Product that meets the user needs.”
(http://www.incose.org/ whatis.html)
Blanchard”s Department of Defence (DoD) Definition
Systems-Engineering is the “Process that shall:

1. Transform operational needs and Requirements into an integrated System design Solution through concurrent consideration of all life-cycle needs (i.e., development, manufacturing, test and evaluation, verification, deployment, operations, support, training and disposal);

2. Ensure the compatibility, interoperability, and integration of all Functional and physical interfaces and ensure that System definition and design reflect the Requirements for all System elements (i.e., hardware, software, facilities, people, data); and

3. Characterize and manage technical risks.” [BLANCHARD98]
An FAA (the USA Federal Aviation Authority) Definition
Systems-Engineering is:
“A hybrid methodology that combines Policy, analysis, design, and management. It ensures that a Complex man-made System or Product, selected from the range of options available, is the one most likely to satisfy the customer”s objectives in the Context of long-term future operation or market environments.
Systems-Engineering is applied throughout the System or Product Life-Cycle as a comprehensive, possibly iterative, interleaved, or recursive, technical Process to:
a. Translate an operational need into a configured System or Product meeting the operational need
b. Integrate the technical contributions of all available Development Resources, including all technical disciplines into a coordinated effort that meets established program Cost, schedule and performance objectives. This involves a “holistic view” (the design of the whole as distinguished from the design of the parts). Such a view is multi-disciplinary in nature, rather than disciplinary or interdisciplinary;
c. Ensure the compatibility of all Function and physical interfaces (internal and external)
d. Ensure that System or Product definition and design reflect the Requirements in System or Product elements (outcome, hardware, software, facilities, people, and data).
e. Characterize [identify, define, and classify] technical risks, develop Risk abatement approaches, and reduce technical risks by prevention and mitigation of Impacts when risks are realized.”
e. Characterize [identify, define, and classify] technical risks, develop Risk abatement approaches, and reduce technical risks by prevention and mitigation of Impacts when risks are realized.”


Illustration: none






1. The Systems-Engineering Process is a conscious attempt to avoid sub-optimal Engineering. Without Systems-Engineering, the success of the resulting System is more accidental than predictable. Systems-Engineering is necessary because there are so many possible places for Product development to go wrong. For example, sub-optimal results might be caused by setting Requirements for too narrow a list of Stakeholders, or by using too narrow a set of Design-Ideas to solve the problem of satisfying all project Requirements. Another frequent problem, especially in well-established large companies, is for groups to produce optimal components yet produce a very sub-optimal Complete System.

2. Systems-Engineering includes a broad application of disciplines such as Requirements-Engineering, Quality-Control, project management, test Engineering, and any of the many other disciplines that might be found useful for satisfying Stakeholders. Architecture-Engineering, a subset of Systems-Engineering, is by contrast, directed only towards the design aspects.





Systems-Engineer *574



This Concept entered by Kay Dudman.

Created by system. Last Modification: Thursday 11 of July, 2019 20:57:04 CEST by Admin (Kai).

Concept Search