When Not to Use Ada
- Ada may not be appropriate
- - When some other language has lower lifecycle costs
- - For some R&D applications where the intent is for concept development only and the system will not be fielded
- - For some prototype applications, however the prototype must not be carried into E&D for subsequent fielding
- - When a compiler does not exist for the hardware platform
- - When timing and/or sizing constraints make Ada a technical infeasibility
From the Script: SLIDE 39 - When Not to Use Ada
Ada may not be appropriate:
- When some other language has lower lifecycle costs. Remember the maintenance phase!
- For some R&D applications where the intent is for concept development only and the system will not be fielded.
- For some prototype applications. However, the prototype must not be carried into E&D for subsequent fielding.
- When a compiler does not exist for the hardware platform.
- When timing and/or sizing constraints make Ada technically infeasable. Many programmers have been surprised at what a mature Ada compiler can achieve that seemed impossible.
- For other circumstances, Ada is a proven performer. There is a Language Selection monograph available that can help you decide if Ada is the best choice for a project.
The Ada policy has resulted in a popular belief that Ada is a "DOD language." This has, at times, discouraged use of Ada in the commercial sector. Keep in mind that this policy is not a “Use Ada for Ada’s sake” but “Use Ada because it is a good idea.”