The use of architectures for the design, development, and documentation of system-of-systems engineering has become a common practice in recent years.At the same time, acquisition guidance has been recently reformed to move from the bottom-up approach of the Requirements Generation System (RGS) to the top-down approach mandated by the Joint Capabilities Integration and Development System (JCIDS), which requires the use of DoDAF to support acquisition.Defense agencies have had difficulty adjusting to these new policies, and are struggling to determine how to meet new acquisition requirements.This research has developed the Architecture-based Technology Evaluation and Capability Tradeoff (ARCHITECT) Methodology to respond to these challenges and address concerns raised about the defense acquisition process.The methodology integrates existing tools and techniques for systems engineering and system of systems engineering with several new modeling and simulation tools and techniques developed as part of this research to fill gaps noted in prior CBAs. Additional criteria for the methodology were developed by leveraging lessons learned from similar fields, including management science and cognitive psychology.A suppression of enemy air defenses (SEAD) mission is used to demonstrate the application of ARCHITECT and to show the plausibility of the approach. Overall, it is shown that the ARCHITECT methodology results in an improvement over current CBAs in the criteria developed here.
【 预 览 】
附件列表
Files
Size
Format
View
Architect: the architecture-basedtechnology evaluation and capabilitytradeoff method