Powered by OpenAIRE graph
Found an issue? Give us feedback
image/svg+xml Jakob Voss, based on art designer at PLoS, modified by Wikipedia users Nina and Beao Closed Access logo, derived from PLoS Open Access logo. This version with transparent background. http://commons.wikimedia.org/wiki/File:Closed_Access_logo_transparent.svg Jakob Voss, based on art designer at PLoS, modified by Wikipedia users Nina and Beao Systems Engineeringarrow_drop_down
image/svg+xml Jakob Voss, based on art designer at PLoS, modified by Wikipedia users Nina and Beao Closed Access logo, derived from PLoS Open Access logo. This version with transparent background. http://commons.wikimedia.org/wiki/File:Closed_Access_logo_transparent.svg Jakob Voss, based on art designer at PLoS, modified by Wikipedia users Nina and Beao
Systems Engineering
Article . 2026 . Peer-reviewed
License: Wiley Online Library User Agreement
Data sources: Crossref
addClaim

To Thrust or Not to Thrust, That Is the Question

Authors: Alejandro Salado;

To Thrust or Not to Thrust, That Is the Question

Abstract

ABSTRACT A discussion during the INCOSE International Symposium 2025 revealed a persistent misunderstanding regarding functional allocation and encapsulation in hierarchical system models. In particular, this was illustrated by the question of whether thrust is produced by an airplane or by its engine. While thrust itself is not the focus of this paper, the question serves as a concrete and instructive example of a deeper conceptual issue: the conflation of system‐level behavior with subsystem‐level allocation, and the improper interpretation of encapsulation across hierarchical levels. This paper addresses the thrust attribution question by first examining it through constructs from general systems theory, emphasizing system boundaries, black‐box behavior, and encapsulation. The argument is then formalized using Wymore's mathematical modeling framework for open systems. The paper concludes by discussing implications for systems engineering practice and analyzing why such misunderstanding may persist in mature engineering domains despite well‐established theoretical foundations.

  • BIP!
    Impact byBIP!
    citations
    The total number of citations received by all articles of the researcher of interest.
    0
    popularity
    This indicator reflects the "current" impact/attention (the "hype") of an article in the research community at large, based on the underlying citation network.
    Average
    influence
    This indicator reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically).
    Average
    impulse
    This indicator reflects the initial momentum of an article directly after its publication, based on the underlying citation network.
    Average
Powered by OpenAIRE graph
Found an issue? Give us feedback
citations
The total number of citations received by all articles of the researcher of interest.
BIP!Citations provided by BIP!
popularity
This indicator reflects the "current" impact/attention (the "hype") of an article in the research community at large, based on the underlying citation network.
BIP!Popularity provided by BIP!
influence
This indicator reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically).
BIP!Influence provided by BIP!
impulse
This indicator reflects the initial momentum of an article directly after its publication, based on the underlying citation network.
BIP!Impulse provided by BIP!
0
Average
Average
Average
Upload OA version
Are you the author of this publication? Upload your Open Access version to Zenodo!
It’s fast and easy, just two clicks!