|
Simulation and Software Development for Capabilities Based Warfare: An Analysis of Harmonized Systems Engineering Processes |
|||
|
SISO 2005 Spring Simulation Interoperability Workshop (05S-SIW-106) |
|||
|
As the Navy shifts toward a capability-based vice platform-based military, the lines separating the development of systems, software, and simulation become blurred. An ever-closer connection between system software development and system modeling and simulation can make it difficult to distinguish a line of divergence between their respective engineering processes. However, multiple approaches and processes have already been codified for architecting Navy systems, software, and simulations. Correlating the systems engineering (SE) processes used to develop these Navy products is important for understanding capability composition and complete interoperability.
Three examples of the different system engineering processes were chosen for analysis: the Federation Development and Execution Process (FEDEP), Department of Defense Architecture Framework (DoDAF) and Model Driven Architecture (MDA). FEDEP is an IEEE standard for interoperable simulation development, DoDAF is the U.S. Department of Defense common approach for architecture description and MDA is the Object Management Group‘s (OMG) process for software centric development. Each represents a different perspective of the systems engineering process and the associated products.
It is important to understand how these processes can be aligned, and the relationships between their respective SE products, particularly in their early stages. A better understanding of the processes’ connections will enable a cleaner development process of modeling for interoperability. This paper will describe connections among MDA, DoDAF, and FEDEP and discuss ways to leverages those connections to move forward with a capabilities-based systems engineering process for the Navy. |
|||
|
Sarah Trbovich VisiTech, Ltd.
Richard Reading VisiTech, Ltd. |
|||
| © 2005 VisiTech, Ltd. |