Editing Ada (programming language) (section)

== History ==
In the 1970s the [[United States Department of Defense|US Department of Defense]] (DoD) became concerned by the number of different programming languages being used for its embedded computer system projects, many of which were obsolete or hardware-dependent, and none of which supported safe modular programming. In 1975, a [[working group]], the [[High Order Language Working Group]] (HOLWG), was formed with the intent to reduce this number by finding or creating a programming language generally suitable for the department's and the [[Ministry of Defence (United Kingdom)|UK Ministry of Defence]]'s requirements. After many iterations beginning with an original [[Straw man proposal|straw-man proposal]]<ref>{{Cite web|url=http://iment.com/maida/computer/requirements/strawman.htm|title=DoD – Strawman Requirements – April 1975|website=iment.com|access-date=Apr 4, 2023}}</ref> the eventual programming language was named Ada. The total number of high-level programming languages in use for such projects fell from over 450 in 1983 to 37 by 1996.

HOLWG crafted the '''<span class="anchor" id="Steelman language requirements">Steelman language requirements</span>''' , a series of documents stating the requirements they felt a programming language should satisfy. Many existing languages were formally reviewed, but the team concluded in 1977 that no existing language met the specifications. The requirements were created by the [[United States Department of Defense]] in ''The Department of Defense Common High Order Language program'' in 1978. The predecessors of this document were called, in order, "Strawman", "Woodenman", "Tinman" and "Ironman".<ref>Department of Defense (June 1978), [https://web.archive.org/web/20200914235620/https://dwheeler.com/steelman/steelman.htm Requirements for High Order Computer Programming Languages: "Steelman"]</ref> The requirements focused on the needs of [[embedded systems|embedded]] computer applications, and emphasised reliability, maintainability, and efficiency. Notably, they included [[exception handling]] facilities, [[run-time checking]], and [[parallel computing]].

It was concluded that no existing language met these criteria to a sufficient extent,<ref>SoftTech Inc. (1976), [[iarchive:DTIC ADA037637/mode/2up|"Evaluation of ALGOL 68, Jovial J3B, Pascal, Simula 67, and TACPOL Versus TINMAN - Requirements for a Common High Order Programming Language."]] - See also: [[ALGOL 68]], [[JOVIAL]] J3B, [[Pascal (programming language)|Pascal]], [[Simula]] 67, and TACPOL (Defense Technical Information Center - DTIC ADA037637, Report Number 1021-14)</ref> so a contest was called to create a language that would be closer to fulfilling them. The design that won this contest became the Ada programming language. The resulting language followed the Steelman requirements closely, though not exactly.

[[File:Ada Lovelace portrait.jpg|thumb|225x225px|Watercolour painting of Ada Lovelace]]
Requests for proposals for a new programming language were issued and four contractors were hired to develop their proposals under the names of Red ([[Intermetrics]] led by Benjamin Brosgol), Green ([[Honeywell]], led by [[Jean Ichbiah]]), Blue ([[SofTech, Inc.|SofTech]], led by John Goodenough)<ref>{{cite web|url=http://www.sei.cmu.edu/about/people/jbg.cfm |title=John Goodenough &#124; SEI Staff Profile |publisher=Sei.cmu.edu |access-date=2014-01-27}}</ref> and Yellow ([[SRI International]], led by Jay Spitzen).<!-- Though Intermetrics and Bull have previous links, I am including them for parallelism. --> In April 1978, after public scrutiny, the Red and Green proposals passed to the next phase. In May 1979, the Green proposal, designed by Jean Ichbiah at Honeywell, was chosen and given the name Ada—after Augusta Ada King, Countess of Lovelace, usually known as [[Ada Lovelace]]. This proposal was influenced by the language [[LIS (programming language)|LIS]] that Ichbiah and his group had developed in the 1970s. The preliminary Ada reference manual was published in ACM SIGPLAN Notices in June 1979. The Military Standard reference manual was approved on December 10, 1980 (Ada Lovelace's birthday), and given the number MIL-STD-1815 in honor of Ada Lovelace's birth year. In 1981, [[Tony Hoare]] took advantage of his [[Turing Award]] speech to criticize Ada for being overly complex and hence unreliable,<ref>{{cite journal |last=C.A.R. |first=Hoare |author-link=Tony Hoare |date=1981 |title=The Emperor's Old Clothes |url=http://zoo.cs.yale.edu/classes/cs422/2011/bib/hoare81emperor.pdf |url-status=live |journal=Communications of the ACM |publisher=[[Association for Computing Machinery]] |volume=24 |issue=2 |pages=75–83 |doi=10.1145/358549.358561 |s2cid=97895 |archive-url=https://web.archive.org/web/20160304012013/http://zoo.cs.yale.edu/classes/cs422/2011/bib/hoare81emperor.pdf |archive-date=2016-03-04 |doi-access=free}}</ref> but subsequently seemed to recant in the foreword he wrote for an Ada textbook.<ref>{{cite book |last1=Watt |first1=D.A. |last2=Wichmann |first2=B.A. |last3=Findlay |first3=W. |title=Ada: Language and Methodology |publisher=Prentice-Hall |date=1987}}</ref>

Ada attracted much attention from the programming community as a whole during its early days. Its backers and others predicted that it might become a dominant language for general purpose programming and not only defense-related work.<ref name="sward" /> Ichbiah publicly stated that within ten years, only two programming languages would remain: Ada and [[Lisp (programming language)|Lisp]].<ref name="SIGAda-Rosen">{{cite journal |last=Rosen |first=J-P. |title=The Ada Paradox(es) |journal=Ada Letters |publisher=ACM SIGAda |volume=24 |issue=2 |date=August 2009 |pages=28–35|doi=10.1145/1620593.1620597 |s2cid=608405}}</ref>  Early Ada compilers struggled to implement the large, complex language, and both compile-time and run-time performance tended to be slow and tools primitive.<ref name="sward" />   Compiler vendors expended most of their efforts in passing the massive, language-conformance-testing, government-required [[Ada Compiler Validation Capability]] (ACVC) validation suite that was required in another novel feature of the Ada language effort.<ref name="SIGAda-Rosen" />

The first validated Ada implementation was the NYU Ada/Ed translator,<ref>{{cite web |url=http://oai.dtic.mil/oai/oai?verb=getRecord&metadataPrefix=html&identifier=ADA136759 |title=Ada Compiler Validation Summary Report: NYU Ada/ED, Version 19.7 V-001 |author=SofTech Inc. |place=Waltham, MA |date=1983-04-11 |access-date=2010-12-16 |archive-url=https://web.archive.org/web/20120312080046/http://oai.dtic.mil/oai/oai?verb=getRecord&metadataPrefix=html&identifier=ADA136759 |archive-date=2012-03-12 }}</ref> certified on April 11, 1983. NYU Ada/Ed is implemented in the high-level set language [[SETL]].<ref>{{cite book |last1=Dewar |first1=Robert B. K. |last2=Fisher |first2=Gerald A. Jr. |last3=Schonberg |first3=Edmond |last4=Froelich |first4=Robert |last5=Bryant |first5=Stephen |last6=Goss |first6=Clinton F. |last7=Burke |first7=Michael |title=Proceeding of the ACM-SIGPLAN symposium on Ada programming language – SIGPLAN '80 |chapter=The NYU Ada translator and interpreter |volume=15 |issue=11 |pages=194–201 |date=November 1980 |isbn=0-89791-030-3 |doi=10.1145/948632.948659|s2cid=10586359}}</ref> Several commercial companies began offering Ada compilers and associated development tools, including [[Alsys]], [[TeleSoft]], [[DDC-I]], [[Advanced Computer Techniques]], [[Tartan Laboratories]], [[Irvine Compiler]], [[TLD Systems]], and [[Verdix]].<ref name="adaic-1992">{{cite news |title=Ada Validated Compilers List |publisher=Ada Information Clearinghouse |date=July 1, 1992 |pages=1–36}}</ref> Computer manufacturers who had a significant business in the defense, aerospace, or related industries, also offered Ada compilers and tools on their platforms; these included [[Concurrent Computer Corporation]], [[Cray Research, Inc.]], [[Digital Equipment Corporation]], [[Harris Computer Systems]], and [[Siemens Nixdorf Informationssysteme AG]].<ref name="adaic-1992" />

In 1991, the US Department of Defense began to require the use of Ada (the ''Ada mandate'') for all software,<ref>{{cite web|url=http://archive.adaic.com/pol-hist/policy/mandate.txt |title=The Congressional Ada Mandate |author=Ada Information Clearinghouse |date=1994 |access-date=2015-06-07 |archive-url=https://web.archive.org/web/20160304073005/http://archive.adaic.com/pol-hist/policy/mandate.txt |archive-date=2016-03-04}}</ref> though exceptions to this rule were often granted.<ref name="sward" />  The Department of Defense Ada mandate was effectively removed in 1997, as the DoD began to embrace [[commercial off-the-shelf]] (COTS) technology.<ref name="sward">{{cite conference |contribution=The rise, fall and persistence of Ada |first=Ricky E. |last=Sward |date=November 2010 |title=SIGAda '10: Proceedings of the ACM SIGAda annual international conference on SIGAda |pages=71–74 |url=http://dl.acm.org/citation.cfm?id=1879063.1879081&coll=DL&dl=GUIDE&CFID=551420221&CFTOKEN=60383966 | doi=10.1145/1879063.1879081|isbn=978-1-4503-0027-8|url-access=subscription }}</ref> Similar requirements existed in other [[North Atlantic Treaty Organization|NATO]] countries: Ada was required for NATO systems involving [[command and control]] and other functions, and Ada was the mandated or preferred language for defense-related applications in countries such as Sweden, Germany, and Canada.<ref>{{cite book |url=http://apps.dtic.mil/dtic/tr/fulltext/u2/a217657.pdf |archive-url=https://web.archive.org/web/20191215065214/http://www.dtic.mil/dtic/tr/fulltext/u2/a217657.pdf |url-status=live |archive-date=December 15, 2019 |first=Nicholas J. |last=Babiak |title=Ada, the New DoD Weapon System Computer Language – Panacea or Calamity |publisher=[[Air University (United States Air Force)]] |date=1989 |pages=39–40}}</ref>

By the late 1980s and early 1990s, Ada compilers had improved in performance, but there were still barriers to fully exploiting Ada's abilities, including a tasking model that was different from what most real-time programmers were used to.<ref name="SIGAda-Rosen" />

Because of Ada's [[Safety-critical system|safety-critical]] support features, it is now used not only for military applications, but also in commercial projects where a software bug can have severe consequences, e.g., [[avionics]] and [[air traffic control]], commercial rockets such as the [[Ariane (rocket family)|Ariane 4 and 5]], [[satellite]]s and other space systems, railway transport and banking.<ref name="Ada_usage" />
For example, the [[Primary Flight Control System]], the [[Aircraft flight control systems|fly-by-wire]] system software in the [[Boeing 777]], was written in Ada, as were the fly-by-wire systems for the aerodynamically unstable [[Eurofighter Typhoon]],<ref>{{cite web |date=16 June 1999 |title=Agile thinking |url=https://www.flightglobal.com/agile-thinking/26933.article |url-status=live |archive-url=https://web.archive.org/web/20210415054346/https://www.flightglobal.com/agile-thinking/26933.article |archive-date=15 April 2021 |access-date=13 Feb 2024 |website=FlightGlobal}}</ref> [[Saab JAS 39 Gripen|Saab Gripen]],<ref>{{Cite web |last=Frisberg |first=Bo |title=Usage of Ada in the Gripen Flight Control System |url=https://www.sigada.org/conf/sa98/papers/frisberg.pdf |url-status=live |archive-url=https://web.archive.org/web/20240115002036/https://www.sigada.org/conf/sa98/papers/frisberg.pdf |archive-date=15 Jan 2024 |access-date=13 Feb 2024 |website=The Special Interest Group on Ada}}</ref> [[Lockheed Martin F-22 Raptor]] and the DFCS replacement flight control system for the [[Grumman F-14 Tomcat]]. The Canadian Automated Air Traffic System was written in 1 million lines of Ada ([[Source lines of code|SLOC]] count). It featured advanced [[distributed processing]], a distributed Ada database, and object-oriented design. Ada is also used in other air traffic systems, e.g., the UK's next-generation Interim Future Area Control Tools Support ({{proper name|iFACTS}}) air traffic control system is designed and implemented using [[SPARK (programming language)|SPARK]] Ada.<ref>{{cite web|last=AdaCore|title=GNAT Pro Chosen for UK's Next Generation ATC System|url=http://www.adacore.com/2007/06/19/adacore-gnat-pro-chosen-for-uk-next-generation/|access-date=2011-03-01|archive-url=https://web.archive.org/web/20101224163518/http://www.adacore.com/2007/06/19/adacore-gnat-pro-chosen-for-uk-next-generation/|archive-date=2010-12-24}}</ref>
It is also used in the [[France|French]] [[Transmission Voie-Machine|TVM]] in-[[cab signalling]] system on the [[TGV]] high-speed rail system, and the metro suburban trains in Paris, London, Hong Kong and New York City.<ref name="Ada_usage" /><ref>{{cite web|last=AdaCore|title=Look Who's Using Ada|url=http://www.adacore.com/home/ada_answers/lookwho/|access-date=2011-03-01|archive-url=https://web.archive.org/web/20101224102110/http://www.adacore.com/home/ada_answers/lookwho|archive-date=2010-12-24}}</ref>

The Ada 95 revision of the language went beyond the Steelman requirements, targeting general-purpose systems in addition to embedded ones, and adding features supporting [[object-oriented programming]].<ref>David A. Wheeler (1997), [https://web.archive.org/web/20200914235617/https://dwheeler.com/steelman/steeltab.htm "Ada, C, C++, and Java vs. The Steelman"]. Originally published in ''Ada Letters'' July/August 1997</ref>