Executable architecture analysis modeling

ABSTRACT

The Executable Architecture Analysis (EAAM) capability allows DoD the ability to assess the readiness of new systems to operate on the net-centric battlefield of the future through evaluation of operational and design baseline architectures.

In a large modern enterprise, a rigorously defined framework is necessary to capture a vision of the entire system in all its dimensions and complexity, to include all the system of systems. The Department of Defense Architecture Framework (DoDAF) currently prescribes products that provide "static" representations of information. These static products, while capturing enormous amounts of information about the operational, system, and technical architectures, fail to support detailed dynamic "behavioral" analysis of how the systems are supposed to interact with each other. A major issue for these communities is not only how to accurately document Command and Control (C2) and related IT capabilities using architectures, but also how to conduct a useful analysis of these capabilities to determine the performance and effectiveness of the systems providing the required capability. Part of the solution is to enhance DoDAF with a method or capability to support these communities with measurable and repeatable environments which virtually reproduce the test environment and play back segments of test events supporting sensitivity analysis of conditions with replaceable battlespace components. This enables decision makers to make concise and effective decisions associated with transformation and process re-engineering. The EAAM approach offers the DoD and DHS a number of new capabilities to plan, organize, maintain, and conduct operational architecture testing for NCOW transformation.

REFERENCES

• 1: Joshua J. Yi , Lieven Eeckhout , David J. Lilja , Brad Calder , Lizy K. John , James E. Smith, The Future of Simulation: A Field of Dreams, Computer, v.39 n.11, p.22-29, November 2006 [doi>10.1109/MC.2006.404]
• 2: DOD Architecture Framework, V1.0, Vol. I and II, 15 August 2003.
• 3: Else, Steven. "as-is," "could be" and possible transition consideration, center for Government Transformation, 2005.
• 4: Pawlowski, T., Barr, P., Ring, S., Williams, M., Segarra, S., "Executable Architecture Methodology for Analysis, FY03 Report," MITRE Technical Report 03W-0000081, February, 2004.
• 5: Garcia, J, Browning, J., "Innovations in Process Modeling as Applied to JFCOM Joint Experimentation Directorate Division Experiment Management Teams" Spring SIW 06S-SIW-015, March 2006.
• 6: Charles, Philipp, Turner, Phil "Capabilities based acquisition ... from theory to reality" CHIPS, summer, 2004.

INDEX TERMS

Keywords:
DODAF, executable architectures, open standards