<div class="description">
<p>Fail early, fail often, but ensure that when failure occurs, a learning period is part of the systems development process. Understanding the reasons a system can fail during the development process is key to maximizing mission effectiveness. Would it not be valuable to have a process that allows the designers to recognize when a system is failing to meet the user's requirements early in the development process? Furthermore, would it not be useful for that process to be iterative, to allow the impacts of changes to be seen in real-time, as the concept is defined and the system is designed? What would it be worth to have the ability to accomplish this inside the engineering safety net of Model-Based Systems Engineering? This research shows an alternative process to classic systems engineering and optimization analysis, where system design decisions are statically and dynamically modeled in a Model-Based Systems Engineering environment and what if types of changes are answered and analyzed using embedded simulation. This research demonstrates the process with the use case of a highly relevant real world problem of countering the threat of small commercial unmanned systems to the security of naval installations.
</p>
<br>Subjects: Model-based system engineering; analysis of alternatives; concept Development; Simulation; trade-space; system engineering</div>
<div class="fn value">
Moulds, Thomas E.</div>
Internet Archive identifier