"Software Engineering" Inspires Innovation in Tactical Methods
■ Xia Zehua, Xu Zicheng
Technology drives transformation, and transformation calls for innovation. Today, the wave of intelligentization (智能化) sweeps across the full-domain battlefield; the form of warfare is accelerating its evolution, the dimensions of competition are continuously expanding, and various battlefield spaces are interwoven with one another. Innovation in tactical methods (战法创新) has become an important lever for tipping the scales of victory and defeat in war and for forging full-domain war-winning capabilities. Analogous to the application of tactical methods on a complex battlefield, software engineering is a systematic discipline that works deeply within complex, large-scale information environments. Its principles of responsive development, incremental delivery, and closed-loop quality control share a degree of consistency with the laws governing tactical method innovation under conditions of intelligentization. We can draw on relevant concepts from software engineering to empower the full chain of tactical method generation, implementation, and evaluation, and inject endogenous momentum into the generation and qualitative improvement of combat effectiveness.
Advancing "Responsive" Tactical Method Generation. Responsive development is a software development model capable of adapting to the contemporary complex information environment. This model is centered on dynamic adjustment and oriented by actual requirements; it possesses the qualities of flexible combination and rapid iteration, and can precisely meet users' core needs in response to dynamic changes in the external environment. As the saying goes, "water shapes its flow according to the terrain; troops win victory according to the enemy" (水因地而制流，兵因敌而制胜). The generation of tactical methods must adapt to the battlefield environment and match the requirements for achieving victory. Drawing on the responsive development model of software engineering, we can achieve tactical method designs that are deeply aligned with complex battlefield situations, precisely matched to the differentiated requirements of different operational missions and different operational environments, and that realize effective coupling of operational resources with tactical plans, firmly grasping battlefield initiative. In terms of implementation pathways: on one hand, we must build a situation-driven linkage mechanism (态势驱动联动机制) that aggregates battlefield data through a full-domain perception network, makes advance assessments of the direction of the battle situation and core operational requirements, and uses intelligent algorithms to match and combine tactical methods, ensuring that the diverse tactical plans produced genuinely approach actual combat conditions and improve the unit's combat effectiveness. On the other hand, we must improve the iterative update mechanism, streamline redundant processes in tactical method design, compress the cycle for plan optimization, and conduct routine fine-tuning and refinement of tactical method details, allowing tactical plans to evolve in step with the battlefield situation and remain consistently aligned with actual combat requirements.
Advancing "Incremental" Tactical Method Implementation. In software engineering, incremental delivery is primarily applied to large-scale, extended-cycle software projects. Its incremental character is mainly reflected in the project team's practice of decomposing the overall research and development objective—which is large in volume and complex in structure—layer by layer into a number of phased sub-tasks that are strongly interrelated, graduated in difficulty, and independently verifiable, and then completing "version development—feature supplementation—performance debugging" in an orderly manner according to a preset rhythm, ultimately delivering the product in stages. The process from conception to implementation of a tactical method is likewise a long-cycle, systematic undertaking, encompassing multiple links such as command system integration, operational force adaptation, supporting equipment coordination, and personnel quality cultivation. The incremental delivery model of software engineering can provide inspiration for smoothly advancing the integration of new tactical methods into existing operational systems. We must scientifically decompose the implementation levels of tactical methods: centering on the overall objective of tactical method application, and following the progressive implementation levels of "theoretical demonstration—unit trial training—full-domain promotion," we should clarify the construction standards, work priorities, and assessment dimensions for each level, and coordinate all construction work step by step. We can promote a "versioned" iterative implementation model: in combination with the differences in service branch characteristics and operational scenarios, release a basic version of the tactical method, then supplement functions and refine details based on feedback from frontline application, gradually upgrading and optimizing the tactical method, and smoothly completing the transition from old to new tactical methods.
Advancing "Closed-Loop" Tactical Method Evaluation. The closed-loop evaluation mechanism runs throughout the full cycle of software research, development, and use. Its function is to comprehensively detect a software system's operational stability, functional integrity, and scenario adaptability through diverse means, forming a positive cycle in which research and development, application, testing and evaluation, and optimization are interlocked, continuously improving the operational effectiveness of the software system. "Running water does not stagnate; a door hinge does not rot" (流水不腐，户枢不蠹). Tactical methods are not immutable, and tactical method innovation cannot be achieved overnight. Ensuring that tactical method innovation never stops depends on the construction of a normalized "closed-loop" tactical method evaluation mechanism. First, we must build a three-dimensional evaluation indicator system: grounded in the overall picture of system-of-systems (体系化) confrontation, and centered on multiple indicators such as decision-making operational efficiency, operational resource allocation, degree of achievement of specialized tasks, and system compatibility, we should build a multi-layered, comprehensive quantitative evaluation indicator framework to ensure that tactical method evaluation has a basis on which to rely. Second, we must improve the full-cycle data collection mechanism: open up data transmission links across all levels and all operational units, collect core data on various tactical methods during exercises and training activities, and allow the effectiveness of tactical method application to be presented directly before decision-makers. Third, we must establish a two-way interactive optimization mechanism: rely on intelligent algorithms to complete data analysis and effectiveness assessment, generate objective and precise evaluation reports, and build a feedback channel that reaches directly to tactical method research and development departments, enabling tactical methods to undergo targeted optimization at the level of top-level design, forming a "ceaselessly self-renewing" (生生不息) closed loop of tactical method upgrading.