Search NASA⌕ Search

SEARCH · Search NASA

Results for “ENGINES - PERFORMANCE”

Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 433 records · Page 24
All sourcesNASA NTRSDOE OSTI
NASA NTRS2001

Improving System Engineering Excellence at NASA's Marshall Space Flight Center

NASA's Marshall Space Flight Center (MSFC) management feels that sound system engineering practices are essential for successful project management, NASA studies have concluded that recent project failures could be attributed in part to inadequate systems engineering. A recent survey of MSFC project managers and system engineers' resulted in the recognition of a need for training in Systems Engineering Practices, particularly as they relate to MSFC projects. In response to this survey, an internal pilot short-course was developed to reinforce accepted practices for system engineering at MSFC. The desire of the MSFC management is to begin with in-house training and offer additional educational opportunities to reinforce sound system engineering principles to the more than 800 professionals who are involved with system engineering and project management. A Systems Engineering Development Plan (SEDP) has been developed to address the longer-term systems engineering development needs of MSFC. This paper describes the survey conducted and the training course that was developed in response to that survey.

Takada, Pamela Wallace↗
NASA NTRS1995

Optimal Trajectories and Control Strategies for the Helicopter in One-Engine-Inoperative Terminal-Area Operations

Engine failure represents a major safety concern to helicopter operations, especially in the critical flight phases of takeoff and landing from/to small, confined areas. As a result, the JAA and FAA both certificate a transport helicopter as either Category-A or Category-B according to the ability to continue its operations following engine failures. A Category-B helicopter must be able to land safely in the event of one or all engine failures. There is no requirement, however, for continued flight capability. In contrast, Category-A certification, which applies to multi-engine transport helicopters with independent engine systems, requires that they continue the flight with one engine inoperative (OEI). These stringent requirements, while permitting its operations from rooftops and oil rigs and flight to areas where no emergency landing sites are available, restrict the payload of a Category-A transport helicopter to a value safe for continued flight as well as for landing with one engine inoperative. The current certification process involves extensive flight tests, which are potentially dangerous, costly, and time consuming. These tests require the pilot to simulate engine failures at increasingly critical conditions, Flight manuals based on these tests tend to provide very conservative recommendations with regard to maximum takeoff weight or required runway length. There are very few theoretical studies on this subject to identify the fundamental parameters and tradeoff factors involved. Furthermore, a capability for real-time generation of OEI optimal trajectories is very desirable for providing timely cockpit display guidance to assist the pilot in reducing his workload and to increase safety in a consistent and reliable manner. A joint research program involving NASA Ames Research Center, the FAA, and the University of Minnesota is being conducted to determine OEI optimal control strategies and the associated optimal,trajectories for continued takeoff (CTO), rejected takeoff (RTO), balked landing (BL), and continued landing (CL) for a twin engine helicopter in both VTOL and STOL terminal-area operations. This proposed paper will present the problem formulation, the optimal control solution methods, and the key results of the trajectory optimization studies for both STOL and VTOL OEI operations. In addition, new results concerning the recently developed methodology, which enable a real-time generation of optimal OEI trajectories, will be presented in the paper. This new real-time capability was developed to support the second piloted simulator investigation on cockpit displays for Category-A operations being scheduled for the NASA Ames Vertical Motion Simulator in June-August of 1995. The first VMS simulation was conducted in 1994 and reported.

Chen, Robert T. N.↗
NASA NTRS2002

Rocket Engine Oscillation Diagnostics

Rocket engine oscillating data can reveal many physical phenomena ranging from unsteady flow and acoustics to rotordynamics and structural dynamics. Because of this, engine diagnostics based on oscillation data should employ both signal analysis and physical modeling. This paper describes an approach to rocket engine oscillation diagnostics, types of problems encountered, and example problems solved. Determination of design guidelines and environments (or loads) from oscillating phenomena is required during initial stages of rocket engine design, while the additional tasks of health monitoring, incipient failure detection, and anomaly diagnostics occur during engine development and operation. Oscillations in rocket engines are typically related to flow driven acoustics, flow excited structures, or rotational forces. Additional sources of oscillatory energy are combustion and cavitation. Included in the example problems is a sampling of signal analysis tools employed in diagnostics. The rocket engine hardware includes combustion devices, valves, turbopumps, and ducts. Simple models of an oscillating fluid system or structure can be constructed to estimate pertinent dynamic parameters governing the unsteady behavior of engine systems or components. In the example problems it is shown that simple physical modeling when combined with signal analysis can be successfully employed to diagnose complex rocket engine oscillatory phenomena.

Nesman, Tom↗
NASA NTRS2003

Enhancement and Extension of Porosity Model in the FDNS-500 Code to Provide Enhanced Simulations of Rocket Engine Components

In the past, the design of rocket engines has primarily relied on the cold flow/hot fire test, and the empirical correlations developed based on the database from previous designs. However, it is very costly to fabricate and test various hardware designs during the design cycle, whereas the empirical model becomes unreliable in designing the advanced rocket engine where its operating conditions exceed the range of the database. The main goal of the 2nd Generation Reusable Launching Vehicle (GEN-II RLV) is to reduce the cost per payload and to extend the life of the hardware, which poses a great challenge to the rocket engine design. Hence, understanding the flow characteristics in each engine components is thus critical to the engine design. In the last few decades, the methodology of computational fluid dynamics (CFD) has been advanced to be a mature tool of analyzing various engine components. Therefore, it is important for the CFD design tool to be able to properly simulate the hot flow environment near the liquid injector, and thus to accurately predict the heat load to the injector faceplate. However, to date it is still not feasible to conduct CFD simulations of the detailed flowfield with very complicated geometries such as fluid flow and heat transfer in an injector assembly and through a porous plate, which requires gigantic computer memories and power to resolve the detailed geometry. The rigimesh (a sintered metal material), utilized to reduce the heat load to the faceplate, is one of the design concepts for the injector faceplate of the GEN-II RLV. In addition, the injector assembly is designed to distribute propellants into the combustion chamber of the liquid rocket engine. A porosity mode thus becomes a necessity for the CFD code in order to efficiently simulate the flow and heat transfer in these porous media, and maintain good accuracy in describing the flow fields. Currently, the FDNS (Finite Difference Navier-Stakes) code is one of the CFD codes which are most widely used by research engineers at NASA Marshall Space Flight Center (MSFC) to simulate various flow problems related to rocket engines. The objective of this research work during the 10-week summer faculty fellowship program was to 1) debug the framework of the porosity model in the current FDNS code, and 2) validate the porosity model by simulating flows through various porous media such as tube banks and porous plate.

Cheng, Gary↗
NASA NTRS1999

Aerospace Systems Design in NASA's Collaborative Engineering Environment

Past designs of complex aerospace systems involved an environment consisting of collocated design teams with project managers, technical discipline experts, and other experts (e.g. manufacturing and systems operations). These experts were generally qualified only on the basis of past design experience and typically had access to a limited set of integrated analysis tools. These environments provided less than desirable design fidelity, often lead to the inability of assessing critical programmatic and technical issues (e.g., cost risk, technical impacts), and generally derived a design that was not necessarily optimized across the entire system. The continually changing, modern aerospace industry demands systems design processes that involve the best talent available (no matter where it resides) and access to the best design and analysis tools. A solution to these demands involves a design environment referred to as collaborative engineering. The collaborative engineering environment evolving within the National Aeronautics and Space Administration (NASA) is a capability that enables the Agency's engineering infrastructure to interact and use the best state-of-the-art tools and data across organizational boundaries. Using collaborative engineering, the collocated team is replaced with an interactive team structure where the team members are geographically distributed and the best engineering talent can be applied to the design effort regardless of physical location. In addition, a more efficient, higher quality design product is delivered by bringing together the best engineering talent with more up-to-date design and analysis tools. These tools are focused on interactive, multidisciplinary design and analysis with emphasis on the complete life cycle of the system, and they include nontraditional, integrated tools for life cycle cost estimation and risk assessment. NASA has made substantial progress during the last two years in developing a collaborative engineering environment. NASA is planning to use this collaborative engineering infrastructure to provide better aerospace systems life cycle design and analysis, which includes analytical assessment of the technical and programmatic aspects of a system from "cradle to grave." This paper describes the recent NASA developments in the area of collaborative engineering, the benefits (realized and anticipated) of using the developed capability, and the long-term plans for implementing this capability across the Agency.

Monell, Donald W.↗
NASA NTRS1947

The Combination of Internal-Combustion Engine and Gas Turbine

While the gas turbine by itself has been applied in particular cases for power generation and is in a state of promising development in this field, it has already met with considerable success in two cases when used as an exhaust turbine in connection with a centrifugal compressor, namely, in the supercharging of combustion engines and in the Velox process, which is of particular application for furnaces. In the present paper the most important possibilities of combining a combustion engine with a gas turbine are considered. These "combination engines " are compared with the simple gas turbine on whose state of development a brief review will first be given. The critical evaluation of the possibilities of development and fields of application of the various combustion engine systems, wherever it is not clearly expressed in the publications referred to, represents the opinion of the author. The state of development of the internal-combustion engine is in its main features generally known. It is used predominantly at the present time for the propulsion of aircraft and road vehicles and, except for certain restrictions due to war conditions, has been used to an increasing extent in ships and rail cars and in some fields applied as stationary power generators. In the Diesel engine a most economical heat engine with a useful efficiency of about 40 percent exists and in the Otto aircraft engine a heat engine of greatest power per unit weight of about 0.5 kilogram per horsepower.

Zinner, K.↗
NASA NTRS2004

[The Engineering and Technical Services Directorate at the Glenn Research Center]

My name is James Moon and I am a senior at Tennessee State University where my major is Aeronautical and Industrial Technology with a concentration in industrial electronics. I am currently serving my internship in the Engineering and Technical Services Directorate at the Glenn Research Center (GRC). The Engineering and Technical Service Directorate provides the services and infrastructure for the Glenn Research Center to take research concepts to reality. They provide a full range of integrated services including engineering, advanced prototyping and testing, facility management, and information technology for NASA, industry, and academia. Engineering and Technical Services contains the core knowledge in Information Technology (IT). This includes data systems and analysis, inter and intranet based systems design and data security. Including the design and development of embedded real-time s o h a r e applications for flight and supporting ground systems, Engineering and Technical Services provide a wide range of IT services and products specific to the Glenn Research Center research and engineering community. In the 7000 Directorate I work directly in the 7611 organization. This organization is known as the Aviation Environments Technical Branch. My mentor is Vincent Satterwhite who is also the Branch Chief of the Aviation Environments Technical Branch. In this branch, I serve as the Assistant program manager of the Engineering Technology Program. The Engineering Technology Program (ETP) is one of three components of the High School L.E.R.C.I.P. This is an Agency-sponsored, eight-week research-based apprenticeship program designed to attract traditionally underrepresented high school students that demonstrate an aptitude for and interest in mathematics, science, engineering, and technology.

Moon, James↗
NASA NTRS2007

Integration of On-Line and Off-Line Diagnostic Algorithms for Aircraft Engine Health Management

This paper investigates the integration of on-line and off-line diagnostic algorithms for aircraft gas turbine engines. The on-line diagnostic algorithm is designed for in-flight fault detection. It continuously monitors engine outputs for anomalous signatures induced by faults. The off-line diagnostic algorithm is designed to track engine health degradation over the lifetime of an engine. It estimates engine health degradation periodically over the course of the engine s life. The estimate generated by the off-line algorithm is used to update the on-line algorithm. Through this integration, the on-line algorithm becomes aware of engine health degradation, and its effectiveness to detect faults can be maintained while the engine continues to degrade. The benefit of this integration is investigated in a simulation environment using a nonlinear engine model.

Kobayashi, Takahisa↗
NASA NTRS2008

An Object-oriented Computer Code for Aircraft Engine Weight Estimation

Reliable engine-weight estimation at the conceptual design stage is critical to the development of new aircraft engines. It helps to identify the best engine concept amongst several candidates. At NASA Glenn (GRC), the Weight Analysis of Turbine Engines (WATE) computer code, originally developed by Boeing Aircraft, has been used to estimate the engine weight of various conceptual engine designs. The code, written in FORTRAN, was originally developed for NASA in 1979. Since then, substantial improvements have been made to the code to improve the weight calculations for most of the engine components. Most recently, to improve the maintainability and extensibility of WATE, the FORTRAN code has been converted into an object-oriented version. The conversion was done within the NASA s NPSS (Numerical Propulsion System Simulation) framework. This enables WATE to interact seamlessly with the thermodynamic cycle model which provides component flow data such as airflows, temperatures, and pressures, etc. that are required for sizing the components and weight calculations. The tighter integration between the NPSS and WATE would greatly enhance system-level analysis and optimization capabilities. It also would facilitate the enhancement of the WATE code for next-generation aircraft and space propulsion systems. In this paper, the architecture of the object-oriented WATE code (or WATE++) is described. Both the FORTRAN and object-oriented versions of the code are employed to compute the dimensions and weight of a 300- passenger aircraft engine (GE90 class). Both versions of the code produce essentially identical results as should be the case. Keywords: NASA, aircraft engine, weight, object-oriented

Tong, Michael T.↗
NASA NTRS2008

Development Status of the CECE Cryogenic Deep Throttling Demonstrator Engine

As one of the first technology development programs awarded by NASA under the U.S. Space Exploration Policy (USSEP), the Pratt & Whitney Rocketdyne (PWR) Deep Throttling, Common Extensible Cryogenic Engine (CECE) program was selected by NASA in November 2004 to begin technology development and demonstration toward a deep throttling, cryogenic engine supporting ongoing trade studies for NASA's Lunar Lander descent stage. The CECE program leverages the maturity and previous investment of a flight-proven hydrogen/oxygen expander cycle engine, the PWR RLI0, to develop and demonstrate an unprecedented combination of reliability, safety, durability, throttlability, and restart capabilities in a high-energy, cryogenic engine. The testbed selected for the deep throttling demonstration phases of this program was a minimally modified RL10 engine, allowing for maximum current production engine commonality and extensibility with minimum program cost. Two series of demonstrator engine tests, the first in April-May 2006 and the second in March-April 2007, have demonstrated in excess of 10:1 throttling of the hydrogen/oxygen expander cycle engine. Both test series have explored a combustion instability ("chug") environment at low throttled power levels. These tests have provided an early demonstration of an enabling cryogenic propulsion concept with invaluable system-level technology data acquisition toward design and development risk mitigation for future CECE Demonstrator engine tests.

Source record↗
NASA NTRS2010

SSME Engine Controller Development and Evolution

The SSME engine controller is a redundant, micro-processor based control unit. The controller along with its embedded software provides closed loop control of the engine s thrust and mixture ratio during flight as well as configuring the engine state and operations during non-flight activities such as checkouts, and pre-start engine conditioning. It processes orbiter commands into engine actions and provides engine state and health information to the orbiter for immediate action, telemetry and recording. In addition the controller includes functions which continually monitor and manage engine health, and can activate a variety of fault mitigation actions to insure safe engine operation. The objective of this paper is to provide a description of the SSME engine controller as well as its developmental history and lessons learned

Abrams, Russ↗
NASA NTRS2009

TRW - Lunar Descent Engine

As we went through the program, what we determined, and what we all agreed on, was that the thrust coefficient (Cf) of the nozzle, after you get past a certain point, is really an engineering parameter. It s not a fundamental parameter that is going to be highly variable. Once we knew what the contour of the nozzle was, and once we knew what its characteristic was out to 2:1, we could calculate what the 48:1 thrust coefficient was going to be. In every case that we made a test, the calculation was precise. We weren't looking for a problem out at 48:1. Once we crushed the nozzle and said, "Yeah, we can land on the boulder," and once we had the thermal profile of that columbium nozzle, we did not require a lot of effort there. The real characterization was done in throttling over the 10:1 with the injector and controlling the mixture ratio on that - the whole head-end assembly - out to 2:1. I think everybody at NASA and Grumman agreed that flying like you test is great, particularly if you are using an aircraft engine. But, in this case, the thrust coefficient of the nozzle was not an issue. We had the tandem configuration of the service module, the command module, and the LEM sitting out there, and we were to fire the LEM. On Apollo 5, we were firing the LEM to show how it would work. There was a problem. I can t remember where the problem was, but something caused a problem before that engine had finished its burn. It was not in the engine, but there was some other problem, and NASA made a controlled shutdown. Then, they came to us and asked, "Hey, we re up there. We want to finish this test program. Is it okay if we restart that engine again in space with this tandem configuration?" We said, "As long as it has been more than forty minutes since you shut down, our analysis says that you will be okay in terms of the thermal characteristics of the inside of that chamber." They restarted it and pushed that system around in orbit on Apollo 5. It turned out, that when it came to Apollo 13, we went back into the record, and said, "Hey, we have pushed this system around up there on Apollo 5, and we have also restarted this tandem configuration." The requirements on Apollo 13 were to put it back into play. The spacecraft was out of free return to the earth at the time of the accident. It would not have come back. NASA said, "Okay, we ll use the descent engine to put the spacecraft in a free trajectory; it will go around the moon and be on free trajectory back to Earth." Then, as it came around the far side of the moon, the guys found out that they had an oxygen problem. As you remember, things were getting pretty bad in there. They said, "We ve got to get it back as fast as we can. Is it okay if we re-fire the engine? Now, we re in a free trajectory, so we want to put as much delta-v (or change in velocity) in as we can. Can we re-fire right now?" We said, "Yes, the data says it has been this period of time." We could re-fire the engine, run the rest of the duty cycle up as far as we needed while preserving enough fluids to make the final correction as the spacecraft got near Earth, and restart the engine. It was pretty fortuitous that we could give them those answers.

Elverum, Gerard W.↗
NASA NTRS2010

CECE: Expanding the Envelope of Deep Throttling Technology in Liquid Oxygen/Liquid Hydrogen Rocket Engines for NASA Exploration Missions

As one of the first technology development programs awarded by NASA under the Vision for Space Exploration, the Pratt & Whitney Rocketdyne (PWR) Deep Throttling, Common Extensible Cryogenic Engine (CECE) program was selected by NASA in November 2004 to begin technology development and demonstration toward a deep throttling, cryogenic engine supporting ongoing trade studies for NASA s Lunar Lander descent stage. The CECE program leverages the maturity and previous investment of a flight-proven hydrogen/oxygen expander cycle engine, the PWR RL10, to develop and demonstrate an unprecedented combination of reliability, safety, durability, throttlability, and restart capabilities in high-energy, cryogenic, in-space propulsion. The testbed selected for the deep throttling demonstration phases of this program was a minimally modified RL10 engine, allowing for maximum current production engine commonality and extensibility with minimum program cost. Four series of demonstrator engine tests have been successfully completed between April 2006 and April 2010, accumulating 7,436 seconds of hot fire time over 47 separate tests. While the first two test series explored low power combustion (chug) and system instabilities, the third test series investigated and was ultimately successful in demonstrating several mitigating technologies for these instabilities and achieved a stable throttling ratio of 13:1. The fourth test series significantly expanded the engine s operability envelope by successfully demonstrating a closed-loop control system and extensive transient modeling to enable lower power engine starting, faster throttle ramp rates, and mission-specific ignition testing. The final hot fire test demonstrated a chug-free, minimum power level of 5.9%, corresponding to an overall 17.6:1 throttling ratio achieved. In total, these tests have provided an early technology demonstration of an enabling cryogenic propulsion concept with invaluable system-level technology data acquisition toward design and development risk mitigation for future lander descent main engines.

Giuliano, Victor J.↗
NASA NTRS2015

Combustion Stability Verification for the Thrust Chamber Assembly of J-2X Developmental Engines 10001, 10002, and 10003

The J-2X engine, a liquid oxygen/liquid hydrogen propellant rocket engine available for future use on the upper stage of the Space Launch System vehicle, has completed testing of three developmental engines at NASA Stennis Space Center. Twenty-one tests of engine E10001 were conducted from June 2011 through September 2012, thirteen tests of the engine E10002 were conducted from February 2013 through September 2013, and twelve tests of engine E10003 were conducted from November 2013 to April 2014. Verification of combustion stability of the thrust chamber assembly was conducted by perturbing each of the three developmental engines. The primary mechanism for combustion stability verification was examining the response caused by an artificial perturbation (bomb) in the main combustion chamber, i.e., dynamic combustion stability rating. No dynamic instabilities were observed in the TCA, although a few conditions were not bombed. Additional requirements, included to guard against spontaneous instability or rough combustion, were also investigated. Under certain conditions, discrete responses were observed in the dynamic pressure data. The discrete responses were of low amplitude and posed minimal risk to safe engine operability. Rough combustion analyses showed that all three engines met requirements for broad-banded frequency oscillations. Start and shutdown transient chug oscillations were also examined to assess the overall stability characteristics, with no major issues observed.

Morgan, C. J.↗
NASA NTRS2020

Building the RS-25 Engine for NASA’s Next Generation of Exploration.

NASA is aggressively pursuing a human lunar return to the Moon with the Artemis Program. The Space Launch System (SLS) is critical to the transportation architecture, providing both crew and cargo capability. To accelerate SLS development, NASA settled on space shuttle heritage propulsion technologies. Early missions will use repurposed RS-25 engines from the Shuttle Program adapted to SLS requirements. For future missions, however, NASA and engine contractor Aerojet Rocketdyne are restarting RS-25 production with a goal of using the latest manufacturing technologies to produce an RS-25 variant that will cost at least 30 percent less than the shuttle-era engines developed and flown for almost 30 years. The prospect of restarting the production line on these engines after many years and modifying the engine to reduce cost and better match the needs of the SLS vehicle presented unique challenges and opportunities for NASA and Aerojet Rocketdyne. NASA and AR are now deep into the process of adapting 16 RS-25 engines for the first four SLS Artemis flights and building the first RS-25 “Restart” engines for future Artemis missions. In addition to navigating programmatic, technical, and logistical challenges with the current RS-25 production work, NASA and AR have partnered to pursue new methods of building this engine through advanced manufacturing techniques to further reduce the cost and schedule required to build each RS-25 engine to contribute to the long-term affordability of the SLS vehicle. This presentation will discuss the goals for the restart program, the challenges, and results to date.

Jessica Jean Wood↗
DOE OSTI2020

Opposed-piston engine in a light-duty truck

An opposed-piston engine is configured to fit in an engine compartment of a light-duty truck without compromising engine operations or the integrity of the engine compartment. The opposed-piston engine includes an air handling system and can be configured so that a cylinder assembly of the engine is tilted. The tilt of the cylinder assembly can allow for all of the components of the engine's air handling system to be located on one side of the opposed-piston engine. The air handling system of the opposed-piston engine can be configured with a cobra-head shaped intake duct assembly.

Warlick, Jr., Richard D.↗
NASA NTRS2020

COMDES-MELT: A Turbofan Engine Icing Risk Analysis Tool, User’s Manual

The computational tool COMDES-MELT was developed to predict the susceptibility of turbofan engines to ice accretion when flying in an ice crystal environment. COMDES-MELT is a first-generation computational tool that can estimate the conditions at which the accretion of ice can occur, location within the turbofan engine compression system, and at which engine operating points within the flight trajectory. This is accomplished by tracking the parameters of static wet bulb temperature, ice particle melt ratio, and the ice-water to airflow rates ratio as ice crystals are ingested into the engine compression system. It has been used successfully to predict engine operating points for simulation in an altitude wind tunnel with ice crystal ingestion. These engine tests occur in a simulated ice crystal cloud environment. This predictive analysis has been used to generate the test matrix in preparation for tests in the Propulsion Systems Laboratory, an altitude test facility at the NASA Glenn Research Center. Furthermore, due to the speed of the code during an engine icing test, adjustments to the test matrix can be provided to the test engineer in real time to focus on a particular area of ice accretion susceptibility. The use of the COMDES-MELT code will be examined in this manual.

Turbofan engine↗
NASA NTRSDate not supplied

NASA Aeronautics Research Mission Directorate System Security Engineering Approaches

System security engineering (SSE) is a set of formal engineering methods and is considered a subset of systems engineering. It is a relatively new development in systems engineering with the initial NIST (National Institute of Standards) standard published in November of 2016 with updates in 2018, and 2022. The guiding principles in our methodology are based in NIST Special Publication 800-160 Vol. 1 “Systems Security Engineering: Considerations For A Multidisciplinary Approach In The Engineering Of Trustworthy Secure Systems” and integrate methodologies from common IT (Information Technology) threat modeling approaches utilizing MBSE (Model-Based Systems Engineering). The presentation will discuss how our teams utilize SSE and MBSE (Model-Based Systems Engineering) to develop secure architectures for systems under development in our NASA aeronautics research environment. This includes the activities to develop Protection Needs (PN) that, in turn result in security requirements in the design context and policies for the future state operational context for system protection. The process of applying SSE to analyze project architectures and ConOps (Concept of Operations) is intended to ensure the transferred research is both secure and securable in a “real-world” setting.

Systems Security Engineering↗