Four critical areas are addressed by Agile engineers:
Requirements definition of critical operational/system parameters
Leveraging DoD Architecture Framework (DoDAF) products for architecture development
Critical C4ISR operational thread assessment
Operational scenario design/development
Agile engineers work closely with TRADOC, and other customer communities, to stay abreast of, and influence as appropriate, emerging doctrine concepts. As a general rule, Agile engineers access all applicable elements of doctrine, training, leader development, organization, materiel, soldier, personnel, and facilities (DTLOMS-PF) to provide the warfighter with an integrated C4ISR solution. Areas frequently requiring focused attention are:
Size, weight and power (SWAP) considerations
Derivation, or refinement, of information exchange requirements (IERs)
Tactical Operations Center (TOC) interoperability requirements, including TOC-to higher/lower echelon C3 interoperability.
Agile engineers leverage and create DoDAF products as required to develop “As Is” and “To Be” operational and system architectures for follow-on tradeoff analyses, network enhancements and future technology insertions.
Agile engineers assess critical communication/data exchange threads across any given architecture to determine important interoperability challenges that may need new or emerging technology insertions to address user requirements. Early detection and assessment of critical threads enables Agile engineers to properly define and develop cost effective solutions prior to system deployment.
Agile use these various architecture products to provide a common baseline for follow-on communications/network design, linkage to operational mission requirements, modeling/simulation guidance, and test activity planning and execution. A properly designed operational scenario focuses engineering efforts to properly support the warfighter.