Joint architecting, design, and simulation of operational-functional requirements and scenarios on the one hand and system functionality and technological requirements on the other hand is a common challenge in systems engineering. We propose a model-based systems engineering approach that addresses this challenge. The confusion between operational and functional behavior stems from systems engineers' inherent tendency to adopt a system-centric perspective and employ modeling techniques that are inadequate for the task at hand. Functional models provide a biased perspective on the overarching operational context, while business-process-oriented models provide partial coverage of the system's architecture — its structure-behavior combination. The problem intensifies when the operational scenario is indefinite and dependent on responsive system behavior and when the operational scenario consists of the utilization of functionality in multiple systems. Operational mission management in various domains utilizes planning, execution, and control functionality in several systems, and copes with the operational-functional distinction.
['Yaniv Mordecai', 'Dov Dori']
Model-based operational-functional unified specification for mission systems