Waterfall model
In the military aspect of the software development cycle is generally longer, consider a wide range of aspects, and waterfall model in the project at all stages of very little feedback, not conducive to the robustness of the software.
Rapid prototyping
Military users are generally internal personnel, the funds are more abundant, there is no need to first make models. And the prototype has the possibility of leaking, unfavorable to military development.
Fast Incremental
Military requirements of the project is interlocking, the overall requirements will be relatively strong, not very suitable for such a little delivery, and do not need a little bit of production.
Spiral Model
Spiral model every step has risk analysis, this is very important, the military is the most important security, state secrets can not be leaked, so compared to the previous way, the spiral model is very obvious advantage is very large, but the shortcomings and rapid increase the same, there is no need for phased delivery.
Object-oriented model
The object-oriented model makes each function modular, each part uses different objects, the object has a class relationship, so it will have good confidentiality characteristics, for military development, security is not the most important, he can take the spiral each step of the advantages of risk analysis, for programmers, modular design is more conducive to programming , there is no need to consider the complexities of the linkages between the various parts.
In summary, the choice of object-oriented model is better.
What kind of development model do you think it is appropriate to use some military software systems?