| U.S. Department of Defence, Requirements for High Order Computer Programming Languages "STEELMAN", U.S. Department of Defence, 1978. |
....review a few existing subsets of the language. Finally, a brief conclusion is drawn. 2. Requirements of Programming Language A study by Bentley [7] summarises some of the well known requirements of programming language for the development of high integrity systems including works by [14] 16] [48], 49] and [21] It carries out an assessment on Java against all the requirements, producing a series of rationales. A subset of the language is also proposed, but unfortunately only sequential features are included. The outcome of the study is compatible to a large extent with our objective in ....
....in order to be considered for use in implementing high integrity software. Appropriate justifications are made regarding each requirement. Readers are encouraged to refer to the references if in any doubt about rationales and specifics. L.1.1. 1 Type safety Strong typing rules References [48], 16] 49] 21] 15] 22] 37] 33] Rationale Strongly typed languages help reduce errors in programs at compile time. Moreover, type safety is often considered to be sufficient for ensuring the minimum nontrivial level of program safety, i.e. control flow safety, memory safety, and stack ....
[Article contains additional citation context not shown here]
U.S. Department of Defence, Requirements for High Order Computer Programming Languages "STEELMAN", U.S. Department of Defence, 1978.
....move on to review a few existing subsets of the language. 2. Requirements of Programming Language A study by Bentley [Bentley1999] summarises some of the well known requirements of programming language for the development of high integrity systems including works by [Carr 1990] Cullyer 1991] USDoD1978] USDoD1990] and [Hutcheon 1992] It carries out an assessment on Java against all the requirements, producing a series of comprehensive rationales. A subset of the language is also proposed, but only sequential features are included. The outcome of the study is compatible to a large extent ....
.... with type checking across the module boundaries Well understood: will the designers and programmers understand the language sufficiently to write safety critical software 5 These questions, however, are high level and do not cover some detailed issues like those in the Steelman requirements [USDoD1978] The Steelman requirements [USDoD1978] are both extensive and technically detailed. It was established by the U.S. Department of Defence after a number of reviews and refinements by military and civil communities in order to evaluate existing languages. This eventually led to the development ....
[Article contains additional citation context not shown here]
U.S. Department of Defence, Requirements for High Order Computer Programming Languages "STEELMAN", U.S. Department of Defence, 1978. 35
....Ada programming language arose from a US Department of Defence (DoD) initiative started in the mid 1970 s to develop a High Order Language suitable for embedded systems software. The original Ada language proposal, which was one of the four responses to the Ironman Steelman requirements documents [5], was refined to a proposed standard by 1980 [6] and standardised in 1983 [7] Our analysis of the requirements and standards documents shows that the designers had four principle high level design goals for Ada 83: program reliability and maintenance, support for programming in the large, ....
US Department of Defence, "Requirements for High Order Computer Programming Languages: Steelman", June 1978.
....language arose from a US Department of Defence (DoD) initiative started in the mid 1970 s to develop a High Order Language (HOL) suitable for embedded systems software. The original Ada language proposal, which was one of the four responses to the Ironman Steelman requirements documents [47], was refined to a proposed standard [28,48] by 1980 and standardised in 1983 [49] Our analysis of the requirements and standards documents shows that the designers had four principle high level design goals for Ada 83: program reliability and maintenance, support for programming in the ....
US Department of Defence, "Requirements for High Order Computer Programming Languages: Steelman", June 1978.
....persistence in Ada is not a new one. Proposed and actual examples include Green s proposed extensions to Ada[21] APPL A[34] PGRAPHITE[40] the work of Millan and Mulatero[27] and Intermetrics proposed ODMG Ada95 binding[31] Our analysis of the Ada requirements and standards documents [22, 35, 36, 37, 38] suggests that the Ada designers had four principle high level design goals for the language: program reliability and maintenance, support for programming in the large, support for a wide range of application domains, and program execution efficiency. In this paper, we focuses on ....
U.S. Department of Defense. Requirements for High Order Computer Programming Languages: Steelman. United States Department of Defence, June 1978.
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC