{"id":262921,"date":"2019-02-06T22:22:41","date_gmt":"2019-02-07T03:22:41","guid":{"rendered":"https:\/\/www.nasa.gov\/?migration=converted-node-439250"},"modified":"2023-07-26T15:08:45","modified_gmt":"2023-07-26T19:08:45","slug":"2-0-fundamentals-of-systems-engineering","status":"publish","type":"reference","link":"https:\/\/www.nasa.gov\/reference\/2-0-fundamentals-of-systems-engineering\/","title":{"rendered":"SEH 2.0 Fundamentals of Systems Engineering"},"content":{"rendered":"<div id=\"\" class=\" hds-module hds-module-full wp-block-nasa-blocks-secondary-navigation\"><div class=\"hds-secondary-navigation-wrapper z-top width-100 padding-0\"><div id=\"\" class=\"hds-secondary-navigation width-full border-bottom-1px text-center hds-color-mode-dark hds-module hds-module-full wp-block-nasa-blocks-hdsnav\"><button type=\"button\" class=\"hds-secondary-nav-mobile-button display-flex tablet:display-flex desktop:display-none width-full flex-align-center bg-carbon-90 border-color-carbon-80 color-spacesuit-white\" aria-expanded=\"false\" aria-controls=\"hds-secondary-nav-track\"><span>Systems Engineering Handbook<\/span><svg width=\"16\" height=\"16\" alt=\"\" enable-background=\"new 0 0 400 400\" viewBox=\"0 0 400 400\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\"><path d=\"m4.2 122.2 195.1 195.1 196.5-196.6-37.9-38-157.8 157.8-156.8-156.8z\" \/><\/svg><\/button><div class=\"hds-secondary-nav-track grid-container grid-container-extrawide padding-0 tablet:padding-x-3 desktop:padding-x-2 \"><div class=\"hds-secondary-navigation-menu-items\"><nav><ul class=\"usa-nav__primary usa-accordion flex-justify-center margin-0\"><li class=\"usa-nav__primary-item \"><a class=\"usa-nav__link\" href=\"https:\/\/www.nasa.gov\/reference\/systems-engineering-handbook\/\">Home<\/a><\/li><li class=\"usa-nav__primary-item \"><a class=\"usa-nav__link\" href=\"https:\/\/www.nasa.gov\/reference\/1-0-introduction\/\">1.0 Introduction<\/a><\/li><li class=\"usa-nav__primary-item usa-current\"><a class=\"usa-nav__link\" href=\"https:\/\/www.nasa.gov\/reference\/2-0-fundamentals-of-systems-engineering\/\">2.0 Fundamentals of Systems...<\/a><\/li><li class=\"usa-nav__primary-item\"><button type=\"button\" class=\"usa-accordion__button usa-nav__link\" aria-expanded=\"false\" aria-controls=\"basic-nav-section-one\"><span>More<\/span><svg class=\"hds-desktop-submenu-toggle-icon display-none tablet:display-none desktop:display-block\" width=\"16\" height=\"16\" alt=\"\" enable-background=\"new 0 0 400 400\" viewBox=\"0 0 400 400\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\"><path d=\"m4.2 122.2 195.1 195.1 196.5-196.6-37.9-38-157.8 157.8-156.8-156.8z\" \/><\/svg><svg class=\"hds-mobile-submenu-toggle-icon display-block tablet:display-block desktop:display-none\" width=\"16\" height=\"16\" viewBox=\"0 0 16 16\" fill=\"none\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\"><circle cx=\"8\" cy=\"8\" r=\"7.5\" fill=\"#0B3D91\" stroke=\"white\"\/><rect x=\"4\" y=\"7.6001\" width=\"8\" height=\"0.8\" fill=\"white\"\/><rect class=\"hds-mobile-submenu-toggle-icon-line-vertical\" x=\"7.59998\" y=\"12\" width=\"8\" height=\"0.8\" transform=\"rotate(-90 7.59998 12)\" fill=\"white\"\/><\/svg><\/button><ul id=\"basic-nav-section-one\" class=\"usa-nav__submenu\" hidden><li class=\"usa-nav__submenu-item \"><a class=\"usa-nav__link\" target=\"_self\" href=\"https:\/\/www.nasa.gov\/reference\/3-0-nasa-program-project-life-cycle\/\">3.0 NASA Program\/Project Life...<\/a><\/li><li class=\"usa-nav__submenu-item \"><a class=\"usa-nav__link\" target=\"_self\" href=\"https:\/\/www.nasa.gov\/reference\/4-0-system-design-processes\/\">4.0 System Design Processes<\/a><\/li><li class=\"usa-nav__submenu-item \"><a class=\"usa-nav__link\" target=\"_self\" href=\"https:\/\/www.nasa.gov\/reference\/5-0-product-realization\/\">5.0 Product Realization<\/a><\/li><li class=\"usa-nav__submenu-item \"><a class=\"usa-nav__link\" target=\"_self\" href=\"https:\/\/www.nasa.gov\/reference\/6-0-crosscutting-technical-management\/\">6.0 Crosscutting Technical Management<\/a><\/li><li class=\"usa-nav__submenu-item \"><a class=\"usa-nav__link\" target=\"_self\" href=\"https:\/\/www.nasa.gov\/reference\/system-engineering-handbook-appendix\/\">Appendix<\/a><\/li><li class=\"usa-nav__submenu-item \"><a class=\"usa-nav__link\" target=\"_self\" href=\"https:\/\/www.nasa.gov\/wp-content\/uploads\/2018\/09\/nasa_systems_engineering_handbook_0.pdf?emrc=4096b9\">PDF Version 508 Compliant<\/a><\/li><\/ul><\/ul><\/nav><\/div><\/div><\/div><\/div><\/div>\n\n<div id=\"\" class=\"hds-encyclopedia-intro-banner bg-carbon-05 width-full maxw-full hds-module hds-module-full wp-block-nasa-blocks-encyclopedia-intro-banner\">\t<div class=\"padding-y-0 padding-x-3 desktop:padding-y-0 desktop:padding-x-5\">\n\t\t<div class=\"grid-row flex-align-center\">\n\t\t\t<div class=\"desktop:grid-col-2\"><\/div>\n\t\t\t<div class=\"desktop:grid-col-5 padding-y-4\">\n\t\t\t\t<h1 class=\"display-48 font-weight-extrabold margin-bottom-1\">\n\t\t\t\t\tSEH 2.0 Fundamentals of Systems Engineering\t\t\t\t<\/h1>\n\t\t\t\t\t\t\t\t<div class=\"display-flex flex-align-center\">\n\t\t\t\t\t<div class=\"display-flex flex-align-center label-inter color-carbon-60 margin-right-2 desktop:margin-right-3\">\n\t\t\t\t\t\t<svg class=\"square-2 margin-right-1\" viewBox=\"0 0 600 600\" aria-hidden=\"true\"><path d=\"M293 .1C131.3 3.5-.5 136.4.1 300.1c-.7 162.7 132 301.1 302.2 299.9 165.8-1.1 299.2-136.6 297.6-303.2C598.3 132.5 462.9-3.5 293 .1zm8.9 570.6C151.5 571.8 30.6 451.1 29.2 302.4c-1.4-149.6 119.7-273.2 270.9-273 144.2-.2 266.7 114.2 270.4 263.7 3.8 153.2-117.9 276.5-268.6 277.6z\"\/><path d=\"M444.1 450.4c-67.3.1-134.5.1-201.8.1-15.9 0-31.8.1-47.7-.1-7-.1-12.6-4.5-14.4-11-1.9-6.6.4-13.4 6.9-16.6 3.8-1.9 8.5-2.7 12.7-2.8 81.6-.2 163.2-.1 244.7 0 3.9 0 5.6-.6 5.5-5.1-.1-96.5-.1-193.1 0-289.6 0-4.4-1.5-5.3-5.5-5.3-15.7.2-31.5.1-47.2.1-6.8 0-6.8 0-6.8 6.6v167.5c0 1.8-.2 3.5-.3 5.3-.5.2-1.1.5-1.6.7-14.6-14.7-29.2-29.4-45.1-45.4l-44.1 44.1V120.7c-1.7-.2-3-.5-4.2-.5-28.5 0-56.9-.4-85.4.1-34.3.6-59.6 26-59.7 60.1-.3 85.1-.1 170.2-.1 255.3 0 8.3 2.2 16 6.7 23 9.2 14.5 22.7 21.3 39.7 21.4 35.3.1 70.6 0 105.9 0 47.5 0 95.1 0 142.6.1 3.6 0 5.1-.8 4.9-4.8-.3-6.3-.4-12.7 0-19.1.5-4.8-1.2-5.9-5.7-5.9z\"\/><\/svg>\n\t\t\t\t\t\t<span>Encyclopedia<\/span>\n\t\t\t\t\t<\/div>\n\t\t\t\t\t<div class=\"label-inter color-carbon-60\">Updated Feb 6, 2019<\/div>\n\t\t\t\t<\/div>\n\t\t\t<\/div>\n\t\t\t<div class=\"desktop:grid-col-5 desktop:padding-left-5 padding-top-3\">\n\t\t\t\t<div class=\"hds-media-wrapper margin-left-auto margin-right-auto\"><figure class=\"hds-media-inner hds-cover-wrapper hds-media-ratio-fit \"><img decoding=\"async\" loading=\"lazy\" alt=\"\" style=\"transform: scale(1); transform-origin: 50% 50%; object-position: 50% 50%; object-fit: cover;\" src=\"\/wp-content\/plugins\/nasa-blocks\/assets\/images\/encyclopedia-intro-banner\/encyclopedia-intro-banner-example-01.jpg\" ><\/figure><\/div>\t\t\t<\/div>\n\t\t<\/div>\n\t<\/div>\n\t<\/div>\n\n\n<p>At NASA, \u201csystems engineering\u201d is defined as a methodical, multi-disciplinary approach for the design, realization, technical management, operations, and retirement of a system. A \u201csystem\u201d is the combination of elements that function together to produce the capability required to meet a need. The elements include all hardware, software, equipment, facilities, personnel, processes, and procedures needed for this purpose; that is, all things required to produce system-level results. The results include system-level qualities, properties, characteristics, functions, behavior, and performance. The value added by the system as a whole, beyond that contributed independently by the parts, is primarily created by the relationship among the parts; that is, how they are interconnected. It is a way of looking at the \u201cbig picture\u201d when making technical decisions. It is a way of achieving stakeholder functional, physical, and operational performance requirements in the intended use environment over the planned life of the system within cost, schedule, and other constraints. It is a methodology that supports the containment of the life cycle cost of a system. In other words, systems engineering is a logical way of thinking.<\/p>\n\n\n\n<p>Systems engineering is the art and science of developing an operable system capable of meeting requirements within often opposed constraints. Systems engineering is a holistic, integrative discipline, wherein the contributions of structural engineers, electrical engineers, mechanism designers, power engineers, human factors engineers, and many more disciplines are evaluated and balanced, one against another, to produce a coherent whole that is not dominated by the perspective of a single discipline.<\/p>\n\n\n\n<p>Systems engineering seeks a safe and balanced design in the face of opposing interests and multiple, sometimes conflicting constraints. The systems engineer should develop the skill for identifying and focusing efforts on assessments to optimize the overall design and not favor one system\/subsystem at the expense of another while constantly validating that the goals of the operational system will be met. The art is in knowing when and where to probe. Personnel with these skills are usually tagged as \u201csystems engineers.\u201d They may have other titles\u2014lead systems engineer, technical manager, chief engineer\u2014but for this document, the term \u201csystems engineer\u201d is used.<\/p>\n\n\n\n<p>The exact role and responsibility of the systems engineer may change from project to project depending on the size and complexity of the project and from phase to phase of the life cycle. For large projects, there may be one or more systems engineers. For small projects, the project manager may sometimes perform these practices. But whoever assumes those responsibilities, the systems engineering functions should be performed. The actual assignment of the roles and responsibilities of the named systems engineer may also therefore vary. The lead systems engineer ensures that the system technically fulfills the defined needs and requirements and that a proper systems engineering approach is being followed. The systems engineer oversees the project\u2019s systems engineering activities as performed by the technical team and directs, communicates, monitors, and coordinates tasks. The systems engineer reviews and evaluates the technical aspects of the project to ensure that the systems\/subsystems engineering processes are functioning properly and evolves the system from concept to product. The entire technical team is involved in the systems engineering process.<\/p>\n\n\n\n<p>The systems engineer usually plays the key role in leading the development of the concept of operations (ConOps) and resulting system architecture, defining boundaries, defining and allocating requirements, evaluating design tradeoffs, balancing technical risk between systems, defining and assessing interfaces, and providing oversight of verification and validation activities, as well as many other tasks. The systems engineer typically leads the technical planning effort and has the prime responsibility in documenting many of the technical plans, requirements and specification documents, verification and validation documents, certification packages, and other technical documentation.<\/p>\n\n\n\n<p>In summary, the systems engineer is skilled in the art and science of balancing organizational, cost, and technical interactions in complex systems. The systems engineer and supporting organization are vital to supporting program and Project Planning and Control (PP&C) with accurate and timely cost and schedule information for the technical activities. Systems engineering is about tradeoffs and compromises; it uses a broad crosscutting view of the system rather than a single discipline view. Systems engineering is about looking at the \u201cbig picture\u201d and not only ensuring that they get the design right (meet requirements) but that they also get the right design (enable operational goals and meet stakeholder expectations).<\/p>\n\n\n\n<p>Systems engineering plays a key role in the project organization. Managing a project consists of three main objectives: managing the technical aspects of the project, managing the project team, and managing the cost and schedule. As shown in <a href=\"#Fig2-0-1\"><strong>Figure 2.0-1<\/strong><\/a>, these three functions are interrelated. Systems engineering is focused on the technical characteristics of decisions including technical, cost, and schedule and on providing these to the project manager. The Project Planning and Control (PP&C) function is responsible for identifying and controlling the cost and schedules of the project. The project manager has overall responsibility for managing the project team and ensuring that the project delivers a technically correct system within cost and schedule. Note that there are areas where the two cornerstones of project management, SE and PP&C, overlap. In these areas, SE provides the technical aspects or inputs whereas PP&C provides the programmatic, cost, and schedule inputs.<\/p>\n\n\n\n<p>This document focuses on the SE side of the diagram. The practices\/processes are taken from NPR 7123.1, NASA Systems Engineering Processes and Requirements. Each process is described in much greater detail in subsequent chapters of this document, but an overview is given in the following subsections of this chapter.<a><\/a><\/p>\n\n\n<div id=\"\" class=\"hds-media hds-module wp-block-image\"><div class=\"margin-left-auto margin-right-auto nasa-block-align-inline\"><div class=\"hds-media-wrapper margin-left-auto margin-right-auto\"><figure class=\"hds-media-inner hds-cover-wrapper hds-media-ratio-none \"><a href=\"https:\/\/www.nasa.gov\/wp-content\/uploads\/2019\/02\/seh_diagram_20-1.jpg\"><img fetchpriority=\"high\" decoding=\"async\" width=\"1072\" height=\"815\" src=\"https:\/\/www.nasa.gov\/wp-content\/uploads\/2019\/02\/seh_diagram_20-1.jpg?w=1072\" class=\"attachment-2048x2048 size-2048x2048\" alt=\"Project Management\" style=\"transform: scale(1); transform-origin: 50% 50%; object-position: 50% 50%; object-fit: cover;\" block_context=\"nasa-block\" srcset=\"https:\/\/www.nasa.gov\/wp-content\/uploads\/2019\/02\/seh_diagram_20-1.jpg 1072w, https:\/\/www.nasa.gov\/wp-content\/uploads\/2019\/02\/seh_diagram_20-1.jpg?resize=300,228 300w, https:\/\/www.nasa.gov\/wp-content\/uploads\/2019\/02\/seh_diagram_20-1.jpg?resize=768,584 768w, https:\/\/www.nasa.gov\/wp-content\/uploads\/2019\/02\/seh_diagram_20-1.jpg?resize=1024,779 1024w, https:\/\/www.nasa.gov\/wp-content\/uploads\/2019\/02\/seh_diagram_20-1.jpg?resize=400,304 400w, https:\/\/www.nasa.gov\/wp-content\/uploads\/2019\/02\/seh_diagram_20-1.jpg?resize=600,456 600w, https:\/\/www.nasa.gov\/wp-content\/uploads\/2019\/02\/seh_diagram_20-1.jpg?resize=900,684 900w\" sizes=\"(max-width: 1072px) 100vw, 1072px\" loading=\"eager\" \/><\/a><\/figure><figcaption class=\"hds-caption padding-y-2\"><div class=\"hds-caption-text p-sm margin-0\"><strong>Figure 2.0-1\u00a0<\/strong>Systems Engineering in Context of Overall Project Management<\/div><\/figcaption><\/div><\/div><\/div>\n\n\n<h3 class=\"wp-block-heading\">2.1    The Common Technical Processes and the SE Engine<\/h3>\n\n\n\n<p>There are three sets of common technical processes in NPR 7123.1, NASA Systems Engineering Processes and Requirements: system design, product realization, and technical management. The processes in each set and their interactions and flows are illustrated by the NPR systems engineering \u201cengine\u201d shown in <a href=\"#Fig2-1-1\"><strong>Figure 2.1-1<\/strong><\/a>. The processes of the SE engine are used to develop and realize the end products. This chapter provides the application context of the 17 common technical processes required in NPR7123.1. The system design processes, the product realization processes, and the technical management processes are discussed in more detail in Chapters <strong><a href=\"\/seh\/4-design-process\">4.0<\/a><\/strong>, <strong><a href=\"\/seh\/5-realization\">5.0<\/a><\/strong>, and <strong><a href=\"\/seh\/6-crosscutting\">6.0<\/a><\/strong>, respectively. Processes 1 through 9 indicated in <a href=\"#Fig2-1-1\"><strong>Figure 2.1-1<\/strong><\/a> represent the tasks in the execution of a project. Processes 10 through 17 are crosscutting tools for carrying out the processes.<\/p>\n\n\n<div id=\"\" class=\"hds-media hds-module wp-block-image\"><div class=\"margin-left-auto margin-right-auto nasa-block-align-inline\"><div class=\"hds-media-wrapper margin-left-auto margin-right-auto\"><figure class=\"hds-media-inner hds-cover-wrapper hds-media-ratio-none \"><a href=\"https:\/\/www.nasa.gov\/wp-content\/uploads\/2019\/02\/seh_figure_21-1_se_engine_1080x750.jpg\"><img loading=\"lazy\" decoding=\"async\" width=\"1080\" height=\"750\" src=\"https:\/\/www.nasa.gov\/wp-content\/uploads\/2019\/02\/seh_figure_21-1_se_engine_1080x750.jpg?w=1080\" class=\"attachment-2048x2048 size-2048x2048\" alt=\"Figure 2.1-1 SE Engine Diagram\" style=\"transform: scale(1); transform-origin: 50% 50%; object-position: 50% 50%; object-fit: cover;\" block_context=\"nasa-block\" srcset=\"https:\/\/www.nasa.gov\/wp-content\/uploads\/2019\/02\/seh_figure_21-1_se_engine_1080x750.jpg 1080w, https:\/\/www.nasa.gov\/wp-content\/uploads\/2019\/02\/seh_figure_21-1_se_engine_1080x750.jpg?resize=300,208 300w, https:\/\/www.nasa.gov\/wp-content\/uploads\/2019\/02\/seh_figure_21-1_se_engine_1080x750.jpg?resize=768,533 768w, https:\/\/www.nasa.gov\/wp-content\/uploads\/2019\/02\/seh_figure_21-1_se_engine_1080x750.jpg?resize=1024,711 1024w, https:\/\/www.nasa.gov\/wp-content\/uploads\/2019\/02\/seh_figure_21-1_se_engine_1080x750.jpg?resize=400,278 400w, https:\/\/www.nasa.gov\/wp-content\/uploads\/2019\/02\/seh_figure_21-1_se_engine_1080x750.jpg?resize=600,417 600w, https:\/\/www.nasa.gov\/wp-content\/uploads\/2019\/02\/seh_figure_21-1_se_engine_1080x750.jpg?resize=900,625 900w\" sizes=\"(max-width: 1080px) 100vw, 1080px\" \/><\/a><\/figure><figcaption class=\"hds-caption padding-y-2\"><div class=\"hds-caption-text p-sm margin-0\"><strong>Figure 2.1-1<\/strong>\u00a0The Systems Engineering Engine (NPR 7123.1)<\/div><\/figcaption><\/div><\/div><\/div>\n\n\n<ul>\n<li><strong>System Design Processes:<\/strong> The four system design processes shown in <a href=\"#Fig2-1-1\"><strong>Figure 2.1-1<\/strong><\/a> are used to define and baseline stakeholder expectations, generate and baseline technical requirements, decompose the requirements into logical and behavioral models, and convert the technical requirements into a design solution that will satisfy the baselined stakeholder expectations. These processes are applied to each product of the system structure from the top of the structure to the bottom until the lowest products in any system structure branch are defined to the point where they can be built, bought, or reused. All other products in the system structure are realized by implementation or integration.<\/li>\n\n\n\n<li><strong>Product Realization Processes:<\/strong> The product realization processes are applied to each operational\/mission product in the system structure starting from the lowest level product and working up to higher level integrated products. These processes are used to create the design solution for each product (through buying, coding, building, or reusing) and to verify, validate, and transition up to the next hierarchical level those products that satisfy their design solutions and meet stakeholder expectations as a function of the applicable life cycle phase.<\/li>\n\n\n\n<li><strong>Technical Management Processes:<\/strong> The technical management processes are used to establish and evolve technical plans for the project, to manage communication across interfaces, to assess progress against the plans and requirements for the system products or services, to control technical execution of the project through to completion, and to aid in the decision-making process.<\/li>\n<\/ul>\n\n\n\n<p>The processes within the SE engine are used both iteratively and recursively. As defined in NPR 7123.1, \u201citerative\u201d is the \u201capplication of a process to the same product or set of products to correct a discovered discrepancy or other variation from requirements,\u201d whereas \u201crecursive\u201d is defined as adding value to the system \u201cby the repeated application of processes to design next lower layer system products or to realize next upper layer end products within the system structure. This also applies to repeating application of the same processes to the system structure in the next life cycle phase to mature the system definition and satisfy phase success criteria.\u201d The technical processes are applied recursively and iteratively to break down the initializing concepts of the system to a level of detail concrete enough that the technical team can implement a product from the information. Then the processes are applied recursively and iteratively to integrate the smallest product into greater and larger systems until the whole of the system or product has been assembled, verified, validated, and transitioned.<\/p>\n\n\n\n<p>For a detailed example of how the SE Engine could be used, refer to the NASA Expanded Guidance for SE document at <a href=\"https:\/\/nen.nasa.gov\/web\/se\/doc-repository\" rel=\"noopener\">https:\/\/nen.nasa.gov\/web\/se\/doc-repository<\/a>.<\/p>\n\n\n\n<p>AS9100 is a widely adopted and standardized quality management system developed for the commercial aerospace industry. Some NASA Centers have chosen to certify to the AS9100 quality system and may require their contractors to follow NPR 7123.1. <a href=\"#Table2-1-1\"><strong>Table 2.1-1<\/strong><\/a> shows how the 17 NASA SE processes align with AS9100.<\/p>\n\n\n<div id=\"\" class=\"hds-media hds-module wp-block-image\"><div class=\"margin-left-auto margin-right-auto nasa-block-align-inline\"><div class=\"hds-media-wrapper margin-left-auto margin-right-auto\"><figure class=\"hds-media-inner hds-cover-wrapper hds-media-ratio-none \"><a href=\"https:\/\/www.nasa.gov\/wp-content\/uploads\/2019\/02\/seh_table_2-1_1_se-processes-as9100.jpg\"><img loading=\"lazy\" decoding=\"async\" width=\"1080\" height=\"750\" src=\"https:\/\/www.nasa.gov\/wp-content\/uploads\/2019\/02\/seh_table_2-1_1_se-processes-as9100.jpg?w=1080\" class=\"attachment-2048x2048 size-2048x2048\" alt=\"Table 2.1-1 Alignment of the 17 SE Processes to AS9100\" style=\"transform: scale(1); transform-origin: 50% 50%; object-position: 50% 50%; object-fit: cover;\" block_context=\"nasa-block\" srcset=\"https:\/\/www.nasa.gov\/wp-content\/uploads\/2019\/02\/seh_table_2-1_1_se-processes-as9100.jpg 1080w, https:\/\/www.nasa.gov\/wp-content\/uploads\/2019\/02\/seh_table_2-1_1_se-processes-as9100.jpg?resize=300,208 300w, https:\/\/www.nasa.gov\/wp-content\/uploads\/2019\/02\/seh_table_2-1_1_se-processes-as9100.jpg?resize=768,533 768w, https:\/\/www.nasa.gov\/wp-content\/uploads\/2019\/02\/seh_table_2-1_1_se-processes-as9100.jpg?resize=1024,711 1024w, https:\/\/www.nasa.gov\/wp-content\/uploads\/2019\/02\/seh_table_2-1_1_se-processes-as9100.jpg?resize=400,278 400w, https:\/\/www.nasa.gov\/wp-content\/uploads\/2019\/02\/seh_table_2-1_1_se-processes-as9100.jpg?resize=600,417 600w, https:\/\/www.nasa.gov\/wp-content\/uploads\/2019\/02\/seh_table_2-1_1_se-processes-as9100.jpg?resize=900,625 900w\" sizes=\"(max-width: 1080px) 100vw, 1080px\" \/><\/a><\/figure><figcaption class=\"hds-caption padding-y-2\"><div class=\"hds-caption-text p-sm margin-0\"><strong>Table 2.1-1<\/strong>\u00a0Alignment of the 17 SE Processes to AS9100<\/div><\/figcaption><\/div><\/div><\/div>\n\n\n<h3 class=\"wp-block-heading\">2.2    An Overview of the SE Engine by Project Phase<\/h3>\n\n\n<div id=\"\" class=\"hds-media hds-module wp-block-image\"><div class=\"margin-left-auto margin-right-auto nasa-block-align-inline\"><div class=\"hds-media-wrapper margin-left-auto margin-right-auto\"><figure class=\"hds-media-inner hds-cover-wrapper hds-media-ratio-none \"><a href=\"https:\/\/www.nasa.gov\/wp-content\/uploads\/2019\/02\/seh_figure_2-2_1_se-project-lifecycle.png\"><img loading=\"lazy\" decoding=\"async\" width=\"1080\" height=\"648\" src=\"https:\/\/www.nasa.gov\/wp-content\/uploads\/2019\/02\/seh_figure_2-2_1_se-project-lifecycle.png?w=1080\" class=\"attachment-2048x2048 size-2048x2048\" alt=\"Figure 2.2-1 Project LIfecycle\" style=\"transform: scale(1); transform-origin: 50% 50%; object-position: 50% 50%; object-fit: cover;\" block_context=\"nasa-block\" srcset=\"https:\/\/www.nasa.gov\/wp-content\/uploads\/2019\/02\/seh_figure_2-2_1_se-project-lifecycle.png 1080w, https:\/\/www.nasa.gov\/wp-content\/uploads\/2019\/02\/seh_figure_2-2_1_se-project-lifecycle.png?resize=300,180 300w, https:\/\/www.nasa.gov\/wp-content\/uploads\/2019\/02\/seh_figure_2-2_1_se-project-lifecycle.png?resize=768,461 768w, https:\/\/www.nasa.gov\/wp-content\/uploads\/2019\/02\/seh_figure_2-2_1_se-project-lifecycle.png?resize=1024,614 1024w, https:\/\/www.nasa.gov\/wp-content\/uploads\/2019\/02\/seh_figure_2-2_1_se-project-lifecycle.png?resize=400,240 400w, https:\/\/www.nasa.gov\/wp-content\/uploads\/2019\/02\/seh_figure_2-2_1_se-project-lifecycle.png?resize=600,360 600w, https:\/\/www.nasa.gov\/wp-content\/uploads\/2019\/02\/seh_figure_2-2_1_se-project-lifecycle.png?resize=900,540 900w\" sizes=\"(max-width: 1080px) 100vw, 1080px\" \/><\/a><\/figure><figcaption class=\"hds-caption padding-y-2\"><div class=\"hds-caption-text p-sm margin-0\"><strong>Figure 2.2-1<\/strong>\u00a0Miniature Version of the Poster-Size NASA Project Life Cycle Process Flow for Flight and Ground Systems Accompanying this Handbook<\/div><\/figcaption><\/div><\/div><\/div>\n\n\n<p><a href=\"#Fig2-2-1\"><strong>Figure 2.2-1<\/strong><\/a> conceptually illustrates how the SE engine is used during each phase of a project (Pre-Phase A through Phase F). The life cycle phases are described in <a href=\"#Table2-2-1\"><strong>Table 2.2-1<\/strong><\/a>.<strong> <a href=\"#Fig2-2-1\">Figure 2.2-1<\/a> <\/strong>is a conceptual diagram. For full details, refer to the poster version of this figure, which is located at <a href=\"https:\/\/nen.nasa.gov\/web\/se\/doc-repository\" rel=\"noopener\">https:\/\/nen.nasa.gov\/web\/se\/doc-repository<\/a>.<\/p>\n\n\n\n<p>The uppermost horizontal portion of this chart is used as a reference to project system maturity, as the project progresses from a feasible concept to an as-deployed system; phase activities; Key Decision Points (KDPs); and major project reviews. The next major horizontal band shows the technical development processes (steps 1 through 9) in each project phase. The SE engine cycles five times from Pre-Phase A through Phase D. Note that NASA\u2019s management has structured Phases C and D to \u201csplit\u201d the technical development processes in half in Phases C and D to ensure closer management control. The engine is bound by a dashed line in Phases C and D. Once a project enters into its operational state (Phase E) and closes out (Phase F), the technical work shifts to activities commensurate with these last two project phases. The next major horizontal band shows the eight technical management processes (steps 10 through 17) in each project phase. The SE engine cycles the technical management processes seven times from Pre-Phase A through Phase F.<\/p>\n\n\n<div id=\"\" class=\"hds-media hds-module wp-block-image\"><div class=\"margin-left-auto margin-right-auto nasa-block-align-inline\"><div class=\"hds-media-wrapper margin-left-auto margin-right-auto\"><figure class=\"hds-media-inner hds-cover-wrapper hds-media-ratio-none \"><a href=\"https:\/\/www.nasa.gov\/wp-content\/uploads\/2019\/02\/seh_figure_2-2_1_se_phases.png\"><img loading=\"lazy\" decoding=\"async\" width=\"1080\" height=\"956\" src=\"https:\/\/www.nasa.gov\/wp-content\/uploads\/2019\/02\/seh_figure_2-2_1_se_phases.png?w=1080\" class=\"attachment-2048x2048 size-2048x2048\" alt=\"Table 2.2-1 Project LIfecycle Phases\" style=\"transform: scale(1); transform-origin: 50% 50%; object-position: 50% 50%; object-fit: cover;\" block_context=\"nasa-block\" srcset=\"https:\/\/www.nasa.gov\/wp-content\/uploads\/2019\/02\/seh_figure_2-2_1_se_phases.png 1080w, https:\/\/www.nasa.gov\/wp-content\/uploads\/2019\/02\/seh_figure_2-2_1_se_phases.png?resize=300,266 300w, https:\/\/www.nasa.gov\/wp-content\/uploads\/2019\/02\/seh_figure_2-2_1_se_phases.png?resize=768,680 768w, https:\/\/www.nasa.gov\/wp-content\/uploads\/2019\/02\/seh_figure_2-2_1_se_phases.png?resize=1024,906 1024w, https:\/\/www.nasa.gov\/wp-content\/uploads\/2019\/02\/seh_figure_2-2_1_se_phases.png?resize=400,354 400w, https:\/\/www.nasa.gov\/wp-content\/uploads\/2019\/02\/seh_figure_2-2_1_se_phases.png?resize=600,531 600w, https:\/\/www.nasa.gov\/wp-content\/uploads\/2019\/02\/seh_figure_2-2_1_se_phases.png?resize=900,797 900w\" sizes=\"(max-width: 1080px) 100vw, 1080px\" \/><\/a><\/figure><figcaption class=\"hds-caption padding-y-2\"><div class=\"hds-caption-text p-sm margin-0\"><strong>Table 2.2-1<\/strong>\u00a0Project Life Cycle Phases<\/div><\/figcaption><\/div><\/div><\/div>\n\n\n<h3 class=\"wp-block-heading\">2.3    Example of Using the SE Engine<\/h3>\n\n\n\n<p>In Pre-Phase A, the SE engine is used to develop the initial concepts; clearly define the unique roles of humans, hardware, and software in performing the missions objectives; establish the system functional and performance boundaries; develop\/identify a preliminary\/draft set of key high-level requirements, define one or more initial Concept of Operations (ConOps) scenarios; realize these concepts through iterative modeling, mock-ups, simulation, or other means; and verify and validate that these concepts and products would be able to meet the key high-level requirements and ConOps. The operational concept must include scenarios for all significant operational situations, including known off-nominal situations. To develop a useful and complete set of scenarios, important malfunctions and degraded-mode operational situations must be considered. The importance of early ConOps development cannot be underestimated. As system requirements become more detailed and contain more complex technical information, it becomes harder for the stakeholders and users to understand what the requirements are conveying; i.e., it may become more difficult to visualize the end product. The ConOps can serve as a check in identifying missing or conflicting requirements.<\/p>\n\n\n\n<p>During Phase A, the recursive use of the SE engine is continued, this time taking the concepts and draft key requirements that were developed and validated during Pre-Phase A and fleshing them out to become the set of baseline system requirements and ConOps. During this phase, key areas of high risk might be simulated to ensure that the concepts and requirements being developed are good ones and to identify verification and validation tools and techniques that will be needed in later phases.<\/p>\n\n\n\n<p>Note that this Pre-Phase A initial concepts development work is not the formal verification and validation program that is performed on the final product, but rather it is a methodical run through ensuring that the concepts that are being developed in this Pre-Phase A are able to meet the likely requirements and expectations of the stakeholders. Concepts are developed to the lowest level necessary to ensure that they are feasible and to a level that reduces the risk low enough to satisfy the project. Academically, this process could proceed down to the circuit board level for every system; however, that would involve a great deal of time and money. There may be a higher level or tier of product than circuit board level that would enable designers to accurately determine the feasibility of accomplishing the project, which is the purpose of Pre-Phase A.<\/p>\n\n\n\n<p>During Phase B, the SE engine is applied recursively to further mature requirements and designs for all products in the developing product tree and perform verification and validation of concepts to ensure that the designs are able to meet their requirements. Operational designs and mission scenarios are evaluated and feasibility of execution within design capabilities and cost estimates are assessed.<\/p>\n\n\n\n<p>Phase C again uses the left side of the SE engine to finalize all requirement updates, finalize the ConOps validation, develop the final designs to the lowest level of the product tree, and begin fabrication.<\/p>\n\n\n\n<p>Phase D uses the right side of the SE engine to recursively perform the final implementation, integration, verification, and validation of the end product, and at the final pass, transition the end product to the user.<\/p>\n\n\n\n<p>The technical management processes of the SE engine are used in Phases E and F to monitor performance; control configuration; and make decisions associated with the operations, sustaining engineering, and closeout of the system. Any new capabilities or upgrades of the existing system reenter the SE engine as new developments.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">2.4    Distinctions between Product Verification and Product Validation<\/h3>\n\n\n\n<p>From a process perspective, the Product Verification and Product Validation processes may be similar in nature, but the objectives are fundamentally different:<\/p>\n\n\n\n<ul>\n<li>Verification of a product shows proof of compliance with requirements\u2014that the product can meet each \u201cshall\u201d statement as proven though performance of a test, analysis, inspection, or demonstration (or combination of these).<\/li>\n\n\n\n<li>Validation of a product shows that the product accomplishes the intended purpose in the intended environment\u2014that it meets the expectations of the customer and other stakeholders as shown through performance of a test, analysis, inspection, or demonstration.<\/li>\n<\/ul>\n\n\n\n<p>Verification testing relates back to the approved requirements set and can be performed at different stages in the product life cycle. The approved specifications, drawings, parts lists, and other configuration documentation establish the configuration baseline of that product, which may have to be modified at a later time. Without a verified baseline and appropriate configuration controls, later modifications could be costly or cause major performance problems.<\/p>\n\n\n\n<p>Validation relates back to the ConOps document. Validation testing is conducted under realistic conditions (or simulated conditions) on end products for the purpose of determining the effectiveness and suitability of the product for use in mission operations by typical users. Validation can be performed in each development phase using phase products (e.g., models) and not only at delivery using end products.<\/p>\n\n\n\n<p>It is appropriate for verification and validation methods to differ between phases as designs advance. The ultimate success of a program or project may relate to the frequency and diligence of validation efforts during the design process, especially in Pre-Phase A and Phase A during which corrections in the direction of product design might still be made cost-effectively. The question should be continually asked, \u201cAre we building the right product for our users and other stakeholders?\u201d The selection of the verification or validation method is based on engineering judgment as to which is the most effective way to reliably show the product\u2019s conformance to requirements or that it will operate as intended and described in the ConOps.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">2.5    Cost Effectiveness Considerations<\/h3>\n\n\n\n<p>The objective of systems engineering is to see that the system is designed, built, and can be operated so that it accomplishes its purpose safely in the most cost-effective way possible considering performance, cost, schedule, and risk. A cost-effective and safe system should provide a particular kind of balance between effectiveness and cost. This causality is an indefinite one because there are usually many designs that meet the cost-effective condition.<\/p>\n\n\n\n<p>Design trade studies, an important part of the systems engineering process, often attempt to find designs that provide the best combination of cost and effectiveness. At times there are alternatives that either reduce costs without reducing effectiveness or increase effectiveness without increasing cost. In such \u201cwin-win\u201d cases, the systems engineer\u2019s decision is easy. When the alternatives in a design trade study require trading cost for effectiveness, the decisions become harder.<\/p>\n\n\n\n<p><strong>The Systems Engineer\u2019s Dilemma<\/strong><\/p>\n\n\n\n<p>At each cost-effective solution:<\/p>\n\n\n\n<ul>\n<li>To reduce cost at constant risk, performance must be reduced.<\/li>\n\n\n\n<li>To reduce risk at constant cost, performance must be reduced.<\/li>\n\n\n\n<li>To reduce cost at constant performance, higher risks must be accepted.<\/li>\n\n\n\n<li>To reduce risk at constant performance, higher costs must be accepted.<\/li>\n<\/ul>\n\n\n\n<p>In this context, time in the schedule is often a critical resource, so that <em>schedule<\/em> behaves like a kind of cost.<\/p>\n\n\n\n<p><a href=\"#Fig2-5-1\"><strong>Figure 2.5-1<\/strong><\/a> shows that the life cycle costs of a program or project tend to get \u201clocked in\u201d early in design and development. The cost curves clearly show that late identification of and fixes to problems cost considerably more later in the life cycle. Conversely, descopes taken later versus earlier in the project life cycle result in reduced cost savings. This figure, obtained from the Defense Acquisition University, is an example of how these costs are determined by the early concepts and designs. The numbers will vary from project to project, but the general shape of the curves and the message they send will be similar. For example, the figure shows that during design, only about 15% of the costs might be expended, but the design itself will commit about 75% of the life cycle costs. This is because the way the system is designed will determine how expensive it will be to test, manufacture, integrate, operate, and sustain. If these factors have not been considered during design, they pose significant cost risks later in the life cycle. Also note that the cost to change the design increases as you get later in the life cycle. If the project waits until verification to do any type of test or analysis, any problems found will have a significant cost impact to redesign and reverify.<\/p>\n\n\n<div id=\"\" class=\"hds-media hds-module wp-block-image\"><div class=\"margin-left-auto margin-right-auto nasa-block-align-inline\"><div class=\"hds-media-wrapper margin-left-auto margin-right-auto\"><figure class=\"hds-media-inner hds-cover-wrapper hds-media-ratio-none \"><a href=\"https:\/\/www.nasa.gov\/wp-content\/uploads\/2019\/03\/seh_figure_2-5_1_cost_impacts.jpg\"><img loading=\"lazy\" decoding=\"async\" width=\"1080\" height=\"971\" src=\"https:\/\/www.nasa.gov\/wp-content\/uploads\/2019\/03\/seh_figure_2-5_1_cost_impacts.jpg?w=1080\" class=\"attachment-2048x2048 size-2048x2048\" alt=\"Figure 2.5-1 Cost Impacts\" style=\"transform: scale(1); transform-origin: 50% 50%; object-position: 50% 50%; object-fit: cover;\" block_context=\"nasa-block\" srcset=\"https:\/\/www.nasa.gov\/wp-content\/uploads\/2019\/03\/seh_figure_2-5_1_cost_impacts.jpg 1080w, https:\/\/www.nasa.gov\/wp-content\/uploads\/2019\/03\/seh_figure_2-5_1_cost_impacts.jpg?resize=300,270 300w, https:\/\/www.nasa.gov\/wp-content\/uploads\/2019\/03\/seh_figure_2-5_1_cost_impacts.jpg?resize=768,690 768w, https:\/\/www.nasa.gov\/wp-content\/uploads\/2019\/03\/seh_figure_2-5_1_cost_impacts.jpg?resize=1024,921 1024w, https:\/\/www.nasa.gov\/wp-content\/uploads\/2019\/03\/seh_figure_2-5_1_cost_impacts.jpg?resize=400,360 400w, https:\/\/www.nasa.gov\/wp-content\/uploads\/2019\/03\/seh_figure_2-5_1_cost_impacts.jpg?resize=600,539 600w, https:\/\/www.nasa.gov\/wp-content\/uploads\/2019\/03\/seh_figure_2-5_1_cost_impacts.jpg?resize=900,809 900w\" sizes=\"(max-width: 1080px) 100vw, 1080px\" \/><\/a><\/figure><figcaption class=\"hds-caption padding-y-2\"><div class=\"hds-caption-text p-sm margin-0\"><strong>Figure 2.5-1<\/strong>\u00a0Life-Cycle Cost Impacts from Early Phase Decision-Making<\/div><\/figcaption><\/div><\/div><\/div>\n\n\n<p>The technical team may have to choose among designs that differ in terms of numerous attributes. A variety of methods have been developed that can be used to help uncover preferences between attributes and to quantify subjective assessments of relative value. When this can be done, trades between attributes can be assessed quantitatively. Often, however, the attributes are incompatible. In the end, decisions need to be made in spite of the given variety of attributes. There are several decision analysis techniques (<a href=\"https:\/\/www.nasa.gov\/seh\/6.8-decision-analysis\">Section 6.8<\/a>) that can aid in complex decision analysis. The systems engineer should always keep in mind the information that needs to be available to help the decision-makers choose the most cost-effective option.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">2.6    Human Systems Integration (HSI) in the SE Process<\/h3>\n\n\n\n<p>As noted at the beginning of NPR 7123.1, the \u201csystems approach is applied to all elements of a system (i.e., hardware, software, human systems integration. In short, the systems engineering approach must equally address and integrate these three key elements: hardware, software, and human systems integration).\u201d Therefore, the human element is something that integration and systems engineering processes must address. The definition of \u201csystem\u201d in NPR 7123.1 is inclusive; i.e., a system is \u201cthe combination of elements that function together to produce the capability required to meet a need. The elements include all hardware, software, equipment, facilities, personnel, processes, and procedures needed for this purpose.\u201d For additional information and guidance on his, refer to Section 2.6 of the NASA Expanded Guidance for Systems Engineering at <a href=\"https:\/\/nen.nasa.gov\/web\/se\/doc-repository\" target=\"_blank\" rel=\"noopener\">https:\/\/nen.nasa.gov\/web\/se\/doc-repository<\/a>.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">2.7    Competency Model for Systems Engineers<\/h3>\n\n\n\n<p><a href=\"#Table2-7-1\"><strong>Table 2.7-1<\/strong><\/a> provides a summary of the Competency Model for Systems Engineering. For more information on the NASA SE Competency model refer to: <a href=\"http:\/\/appel.nasa.gov\/competency-model\/.\" target=\"_blank\" rel=\"noopener\">http:\/\/appel.nasa.gov\/competency-model\/.<\/a><\/p>\n\n\n\n<p>There are four levels of proficiencies associated with each of these competencies:<\/p>\n\n\n\n<ul>\n<li>Team Practitioner\/Technical Engineer<\/li>\n\n\n\n<li>Team Lead\/Subsystem Lead<\/li>\n\n\n\n<li>Project Systems Engineer<\/li>\n\n\n\n<li>Chief Engineer<\/li>\n<\/ul>\n\n\n<div id=\"\" class=\"hds-media hds-module wp-block-image\"><div class=\"margin-left-auto margin-right-auto nasa-block-align-inline\"><div class=\"hds-media-wrapper margin-left-auto margin-right-auto\"><figure class=\"hds-media-inner hds-cover-wrapper hds-media-ratio-none \"><a href=\"https:\/\/www.nasa.gov\/wp-content\/uploads\/2019\/04\/seh_table_2-7_1_competency_mode_p1.jpg\"><img loading=\"lazy\" decoding=\"async\" width=\"1080\" height=\"1195\" src=\"https:\/\/www.nasa.gov\/wp-content\/uploads\/2019\/04\/seh_table_2-7_1_competency_mode_p1.jpg?w=1080\" class=\"attachment-2048x2048 size-2048x2048\" alt=\"Table 2.7-1 Competency Mode\" style=\"transform: scale(1); transform-origin: 50% 50%; object-position: 50% 50%; object-fit: cover;\" block_context=\"nasa-block\" srcset=\"https:\/\/www.nasa.gov\/wp-content\/uploads\/2019\/04\/seh_table_2-7_1_competency_mode_p1.jpg 1080w, https:\/\/www.nasa.gov\/wp-content\/uploads\/2019\/04\/seh_table_2-7_1_competency_mode_p1.jpg?resize=271,300 271w, https:\/\/www.nasa.gov\/wp-content\/uploads\/2019\/04\/seh_table_2-7_1_competency_mode_p1.jpg?resize=768,850 768w, https:\/\/www.nasa.gov\/wp-content\/uploads\/2019\/04\/seh_table_2-7_1_competency_mode_p1.jpg?resize=925,1024 925w, https:\/\/www.nasa.gov\/wp-content\/uploads\/2019\/04\/seh_table_2-7_1_competency_mode_p1.jpg?resize=362,400 362w, https:\/\/www.nasa.gov\/wp-content\/uploads\/2019\/04\/seh_table_2-7_1_competency_mode_p1.jpg?resize=542,600 542w, https:\/\/www.nasa.gov\/wp-content\/uploads\/2019\/04\/seh_table_2-7_1_competency_mode_p1.jpg?resize=813,900 813w\" sizes=\"(max-width: 1080px) 100vw, 1080px\" \/><\/a><\/figure><\/div><\/div><\/div>\n\n<div id=\"\" class=\"hds-media hds-module wp-block-image\"><div class=\"margin-left-auto margin-right-auto nasa-block-align-inline\"><div class=\"hds-media-wrapper margin-left-auto margin-right-auto\"><figure class=\"hds-media-inner hds-cover-wrapper hds-media-ratio-none \"><a href=\"https:\/\/www.nasa.gov\/wp-content\/uploads\/2019\/04\/seh_table_2-7_1_competency_model_p2.jpg\"><img loading=\"lazy\" decoding=\"async\" width=\"1080\" height=\"1273\" src=\"https:\/\/www.nasa.gov\/wp-content\/uploads\/2019\/04\/seh_table_2-7_1_competency_model_p2.jpg?w=1080\" class=\"attachment-2048x2048 size-2048x2048\" alt=\"Table 2.7-1 Competency Model\" style=\"transform: scale(1); transform-origin: 50% 50%; object-position: 50% 50%; object-fit: cover;\" block_context=\"nasa-block\" srcset=\"https:\/\/www.nasa.gov\/wp-content\/uploads\/2019\/04\/seh_table_2-7_1_competency_model_p2.jpg 1080w, https:\/\/www.nasa.gov\/wp-content\/uploads\/2019\/04\/seh_table_2-7_1_competency_model_p2.jpg?resize=255,300 255w, https:\/\/www.nasa.gov\/wp-content\/uploads\/2019\/04\/seh_table_2-7_1_competency_model_p2.jpg?resize=768,905 768w, https:\/\/www.nasa.gov\/wp-content\/uploads\/2019\/04\/seh_table_2-7_1_competency_model_p2.jpg?resize=869,1024 869w, https:\/\/www.nasa.gov\/wp-content\/uploads\/2019\/04\/seh_table_2-7_1_competency_model_p2.jpg?resize=339,400 339w, https:\/\/www.nasa.gov\/wp-content\/uploads\/2019\/04\/seh_table_2-7_1_competency_model_p2.jpg?resize=509,600 509w, https:\/\/www.nasa.gov\/wp-content\/uploads\/2019\/04\/seh_table_2-7_1_competency_model_p2.jpg?resize=764,900 764w, https:\/\/www.nasa.gov\/wp-content\/uploads\/2019\/04\/seh_table_2-7_1_competency_model_p2.jpg?resize=1018,1200 1018w\" sizes=\"(max-width: 1080px) 100vw, 1080px\" \/><\/a><\/figure><\/div><\/div><\/div>\n\n<div id=\"\" class=\"hds-media hds-module wp-block-image\"><div class=\"margin-left-auto margin-right-auto nasa-block-align-inline\"><div class=\"hds-media-wrapper margin-left-auto margin-right-auto\"><figure class=\"hds-media-inner hds-cover-wrapper hds-media-ratio-none \"><a href=\"https:\/\/www.nasa.gov\/wp-content\/uploads\/2019\/04\/seh_table_2-7_1_competency_model_p3.jpg\"><img loading=\"lazy\" decoding=\"async\" width=\"1080\" height=\"915\" src=\"https:\/\/www.nasa.gov\/wp-content\/uploads\/2019\/04\/seh_table_2-7_1_competency_model_p3.jpg?w=1080\" class=\"attachment-2048x2048 size-2048x2048\" alt=\"Table 2.7-1 Compentency Model\" style=\"transform: scale(1); transform-origin: 50% 50%; object-position: 50% 50%; object-fit: cover;\" block_context=\"nasa-block\" srcset=\"https:\/\/www.nasa.gov\/wp-content\/uploads\/2019\/04\/seh_table_2-7_1_competency_model_p3.jpg 1080w, https:\/\/www.nasa.gov\/wp-content\/uploads\/2019\/04\/seh_table_2-7_1_competency_model_p3.jpg?resize=300,254 300w, https:\/\/www.nasa.gov\/wp-content\/uploads\/2019\/04\/seh_table_2-7_1_competency_model_p3.jpg?resize=768,651 768w, https:\/\/www.nasa.gov\/wp-content\/uploads\/2019\/04\/seh_table_2-7_1_competency_model_p3.jpg?resize=1024,868 1024w, https:\/\/www.nasa.gov\/wp-content\/uploads\/2019\/04\/seh_table_2-7_1_competency_model_p3.jpg?resize=400,339 400w, https:\/\/www.nasa.gov\/wp-content\/uploads\/2019\/04\/seh_table_2-7_1_competency_model_p3.jpg?resize=600,508 600w, https:\/\/www.nasa.gov\/wp-content\/uploads\/2019\/04\/seh_table_2-7_1_competency_model_p3.jpg?resize=900,763 900w\" sizes=\"(max-width: 1080px) 100vw, 1080px\" \/><\/a><\/figure><\/div><\/div><\/div>\n\n\n<p><\/p>\n","protected":false},"excerpt":{"rendered":"<p>At NASA, \u201csystems engineering\u201d is defined as a methodical, multi-disciplinary approach for the design, realization, technical management, operations, and retirement of a system. A \u201csystem\u201d is the combination of elements that function together to produce the capability required to meet a need. The elements include all hardware, software, equipment, facilities, personnel, processes, and procedures needed [...]<\/p>\n","protected":false},"author":93,"featured_media":268632,"template":"","meta":{"nasa_hds_core_meta_l10n":"en-US","nasa_hds_core_meta_article_editor":"","nasa_hds_core_meta_article_contacts":[],"nasa_hds_core_meta_article_topic":"","nasa_hds_core_meta_linked_locations":[],"nasa_hds_core_meta_article_related_articles":[],"hds_migrate_meta_pr_release_id":"","hds_migrate_meta_pr_release_type":"","nasa_hds_core_meta_location_x":"","nasa_hds_core_meta_location_y":"","nasa_hds_core_meta_gallery_images":[]},"categories":[],"news-tags":[],"internal-terms":[12700],"coauthors":[],"parsely":{"version":"1.1.0","meta":{"@context":"https:\/\/schema.org","@type":"WebPage","headline":"SEH 2.0 Fundamentals of Systems Engineering","url":"https:\/\/www.nasa.gov\/reference\/2-0-fundamentals-of-systems-engineering\/","mainEntityOfPage":{"@type":"WebPage","@id":"https:\/\/www.nasa.gov\/reference\/2-0-fundamentals-of-systems-engineering\/"},"thumbnailUrl":"https:\/\/www.nasa.gov\/wp-content\/uploads\/2019\/02\/seh_diagram_20-1.jpg?w=150&h=150&crop=1","image":{"@type":"ImageObject","url":"https:\/\/www.nasa.gov\/wp-content\/uploads\/2019\/02\/seh_diagram_20-1.jpg"},"articleSection":"General","author":[{"@type":"Person","name":"Garrett Shea"}],"creator":["Garrett Shea"],"publisher":{"@type":"Organization","name":"NASA","logo":"https:\/\/www.nasa.gov\/wp-content\/themes\/nasa\/assets\/images\/nasa-logo.svg"},"keywords":[],"dateCreated":"2019-02-07T03:22:41Z","datePublished":"2019-02-07T03:22:41Z","dateModified":"2023-07-26T19:08:45Z"},"rendered":"<meta name=\"parsely-title\" content=\"SEH 2.0 Fundamentals of Systems Engineering\" \/>\n<meta name=\"parsely-link\" content=\"https:\/\/www.nasa.gov\/reference\/2-0-fundamentals-of-systems-engineering\/\" \/>\n<meta name=\"parsely-type\" content=\"index\" \/>\n<meta name=\"parsely-image-url\" content=\"https:\/\/www.nasa.gov\/wp-content\/uploads\/2019\/02\/seh_diagram_20-1.jpg?w=150&h=150&crop=1\" \/>\n<meta name=\"parsely-pub-date\" content=\"2019-02-07T03:22:41Z\" \/>\n<meta name=\"parsely-section\" content=\"General\" \/>\n<meta name=\"parsely-author\" content=\"Garrett Shea\" \/>","tracker_url":"https:\/\/cdn.parsely.com\/keys\/nasa.gov\/p.js"},"read_time":18,"featured_image":{"id":268632,"file":"https:\/\/www.nasa.gov\/wp-content\/uploads\/2019\/02\/seh_diagram_20-1.jpg","title":"seh_diagram_20-1","alt":"Project Management","caption":""},"_links":{"self":[{"href":"https:\/\/www.nasa.gov\/wp-json\/wp\/v2\/reference\/262921"}],"collection":[{"href":"https:\/\/www.nasa.gov\/wp-json\/wp\/v2\/reference"}],"about":[{"href":"https:\/\/www.nasa.gov\/wp-json\/wp\/v2\/types\/reference"}],"author":[{"embeddable":true,"href":"https:\/\/www.nasa.gov\/wp-json\/wp\/v2\/users\/93"}],"version-history":[{"count":18,"href":"https:\/\/www.nasa.gov\/wp-json\/wp\/v2\/reference\/262921\/revisions"}],"predecessor-version":[{"id":401290,"href":"https:\/\/www.nasa.gov\/wp-json\/wp\/v2\/reference\/262921\/revisions\/401290"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.nasa.gov\/wp-json\/wp\/v2\/media\/268632"}],"wp:attachment":[{"href":"https:\/\/www.nasa.gov\/wp-json\/wp\/v2\/media?parent=262921"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.nasa.gov\/wp-json\/wp\/v2\/categories?post=262921"},{"taxonomy":"news-tags","embeddable":true,"href":"https:\/\/www.nasa.gov\/wp-json\/wp\/v2\/news-tags?post=262921"},{"taxonomy":"internal-terms","embeddable":true,"href":"https:\/\/www.nasa.gov\/wp-json\/wp\/v2\/internal-terms?post=262921"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/www.nasa.gov\/wp-json\/wp\/v2\/coauthors?post=262921"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}