|
Planning future Multi-Domain Battle (MDB) missions requires extensive, complex, and real-time collaboration and coordination between many Warfighting Functions and Domains such as Electronic Warfare (EW), Positioning, Navigation and Timing (PNT), Network Operations, and Cyber Operations. This collaboration and coordination requires synchronization of the associated domain processes and activities. Large Infrastructure projects for Command and Control (C2) are designed to integrate and align these processes through Information Technology (IT) services, such as decision aids, collaboration tools, and communication tools. New acquisition initiatives are driving infrastructure development to support the rapid fielding of capabilities through a modular software development approach. State-of-the-Art Shared Infrastructure Services can be developed using Agile Software Development (ASD) methods such as Scrum, Kanban, or Extreme Programming. However, the integration of these IT services cannot be easily planned since they are developed at the technology (i.e., software implementation) level according to the selected ASD method. Engineering the Infrastructure as Code (IaC) results in a gap between doctrinal processes and required system functionality since developers quickly code and configure small functional modular units at the technology level, while bypassing the traditional top-down waterfall flow from requirements to design. Furthermore, IaC does not explicitly require consulting a systems architecture. To improve the alignment of configured IT infrastructure services with doctrinal processes, this paper seeks to determine the extent to which agile Development Operations (DevOps) process can implement C2 doctrine while supporting dynamically-changing mission requirements and an operational environment. This paper proposes an automated Systems Engineering workflow to realize IT infrastructure services using Model-Driven Architecture (MDA) and a military DevOps.
|
