Guidelines for Choosing a Computer Language:|
Support for the Visionary Organization
Changes to the 2nd Edition of This Document
This document has been updated because of two important new developments since the publication of the 1st edition. One was the change in software policy of the Department of Defense (DoD) to include the use of a Software Engineering Plan Review (SEPR) as an integral part of choosing a language for a software project [Paige 97]. The second was the increasing popularity of Java that has dictated the addition of Java as a default language in the SASEA process. The SEPR concept is consistent with the basic tenets of the SASEA process [NRC 97], and, indeed, SASEA could become an important part of the SEPR process. Hence, some minor changes have been made to the specific language characteristics and software engineering factors in Table 2 and Table 3 to clarify their consistency with the SEPR requirements.
In the process of updating the document, the described decision process also got the SASEA name. It is so much easier and clearer when references are to a named process.
The appendices have been rearranged to make it easier to add new language appendices in the future. Now all language appendices are at the end. In the process, the letters I and O have been deleted as appendix letters since they are often confused with numerals.
|< Previous Page||Search||Contents||Tables||Next Page >|