Ada9X Project Report Mapping Document, Draft, Office of the Under Secretary of Defense for Acquisition, Washington, D.C. 20301, U.S.A, February 1991.  Home/Search   Document Not in Database   Summary   Related Articles   Check

.... requirements began with a Workshop in June 1989 [8] included additional workshops and solicitation of revision requests from users world wide (over 750 were received) and culminated in the publishing of a requirements document in December 1990 [9] and an associated rationale in May 1991 [10]. The requirements document established 41 Requirements and 22 Study Topics, and directed the mapping revision team to attempt to satisfy all of the Requirements and as many of the Study Topics as possible. In recognition of the specialized needs of particular application areas, the document ....

Ada 9X Project Office, Office of the Under Secretary of Defense for Acquisition, Washington, DC. Ada 9X Requirements Rationale, May 1991.

....Ada 83 to Ada 9X. The determination of essential requirements began with a Workshop in June 1989 [8] included additional workshops and solicitation of revision requests from users world wide (over 750 were received) and culminated in the publishing of a requirements document in December 1990 [9] and an associated rationale in May 1991 [10] The requirements document established 41 Requirements and 22 Study Topics, and directed the mapping revision team to attempt to satisfy all of the Requirements and as many of the Study Topics as possible. In recognition of the specialized needs of ....

Ada 9X Project Office, Office of the Under Secretary of Defense for Acquisition, Washington, DC. Ada 9X Requirements, December 1990.

....for the revised language; the mapping of these requirements onto language changes followed by the adoption of the revised language by all major standards organizations; and the transition in use from Ada 83 to Ada 9X. The determination of essential requirements began with a Workshop in June 1989 [8], included additional workshops and solicitation of revision requests from users world wide (over 750 were received) and culminated in the publishing of a requirements document in December 1990 [9] and an associated rationale in May 1991 [10] The requirements document established 41 ....

Ada 9X Project Office, Office of the Under Secretary of Defense for Acquisition, Washington, DC. Ada 9X Requirements Workshop, June 1989.

....ANSI sponsored the revised standard, with the DOD managing the development through the Ada Joint Program Office (AJPO) The AJPO established the Ada 9X Project Office, and named Christine Anderson as the project manager in October 1988. The Ada 9X Project Plan was released in January, 1989 [7]. The plan stated the goal of the revision process clearly and succinctly: The overall goal of the Ada 9X Project is to revise ANSI MIL STD 1815A to reflect current essential requirements with minimum negative impact and maximum positive impact to the Ada community. According to the plan, the ....

Ada 9X Project Office, Office of the Under Secretary of Defense for Acquisition, Washington, DC. Ada 9X Project Plan, January 1989.

....revision effort. However, in some cases, they are a necessary consequence of changes to the semantics of existing language features, in order to correct problems in Ada 83. In early 1992, the Ada 9X Mapping Team compiled a list of incompatibilities [1] for the then existing Mapping Specification [2,3]. Since that time, refinements of the Mapping Specification have steadily reduced the number of incompatibilities. Still, some incompatibilities will remain. In this article, we provide practical guidelines to Ada 83 programmers, so that their Ada 83 code will be upward compatible with the Ada 9X ....

Ada 9X Mapping Document, Volume II, Mapping Specification, Annexes, Version 4.0., Office of the Under Secretary of Defense for Acquisition, US Department of Defense, March 1992.

....revision effort. However, in some cases, they are a necessary consequence of changes to the semantics of existing language features, in order to correct problems in Ada 83. In early 1992, the Ada 9X Mapping Team compiled a list of incompatibilities [1] for the then existing Mapping Specification [2,3]. Since that time, refinements of the Mapping Specification have steadily reduced the number of incompatibilities. Still, some incompatibilities will remain. In this article, we provide practical guidelines to Ada 83 programmers, so that their Ada 83 code will be upward compatible with the Ada 9X ....

Ada 9X Mapping Document, Volume II, Mapping Specification, Version 4.0., Office of the Under Secretary of Defense for Acquisition, US Department of Defense, December 1991.

....has been a central design goal of the Ada 9X revision effort. However, in some cases, they are a necessary consequence of changes to the semantics of existing language features, in order to correct problems in Ada 83. In early 1992, the Ada 9X Mapping Team compiled a list of incompatibilities [1] for the then existing Mapping Specification [2,3] Since that time, refinements of the Mapping Specification have steadily reduced the number of incompatibilities. Still, some incompatibilities will remain. In this article, we provide practical guidelines to Ada 83 programmers, so that their Ada ....

....will not have a detrimental effect on the produced Ada code. For ease of reference, we first enumerate the guidelines and then explain them in more detail. We do not attempt to provide any comprehensive rationale for the underlying language changes; for such information, we refer the reader to [1] and its future revisions or replacements. 2. THE GUIDELINES AT A GLANCE Most of the upward incompatibilities imply that some legal Ada 83 programs are no longer legal in Ada 9X. Any Ada 9X compiler is guaranteed to identify and reject all such incompatible situations, safeguarding users against ....

[Article contains additional citation context not shown here]

Ada 9X Mapping Document, Volume I, Mapping Rationale, Version 4.1., Office of the Under Secretary of Defense for Acquisition, US Department of Defense, March 1992.

....October 1978. Hil82a] Paul N. Hilfinger. Abstraction Mechanisms and Language Design. MIT Press, 1982. Hil82b] Paul N. Hilfinger. Implementation Strategies for Ada Tasking Idioms. In Proceedings of the AdaTEC Conference on Ada, 1982. Hil90] Paul N. Hilfinger. Tasking Idioms and Enhancements in Ada 9X. Draft Version 1, November 1990. BIBLIOGRAPHY 197 Burke. The NYU Ada Translater and Interpreter. In ACMSIGPLAN Symposium on the Ada Programming Languages, pages 194 201, November 1980. SIGPLAN Notices 15(11) DFSS89] Robert Dewar, Susan Flynn, Edmond Schonberg, and Norman Shulman. Distributed Ada on Shared Memory ....

....Shulman. Distributed Ada on Shared Memory Multiprocessors. In Distributed Ada, pages 229 241, December 1989. Dri90a] Kenneth W. Dritz. Personal communication, August 1990. Dri90b] Kenneth W. Dritz. Tutorial on Parallel Programming in Ada. Presented at the Eighth Annual National Conference on Ada Technology, Atlanta, Georgia, March 1990. Ell86] J.R. Ellis. Bulldog: A Compiler for VLIW Architectures. 1985 ACM Doctoral Disseration Awards. MIT Press, 1986. EN90] Kemal Ebcioglu and Toshio Nakatani. A New Compilation Technique for Parallelizing Loops with Unpredictable Branches on a VLIW Architecture. In David Gelernter, Alexandru ....

[Article contains additional citation context not shown here]

Ada 9x Project Report. Ada 9x Requirements. Technical report, Office of the Under Secretary of Defense Acquisition, December 1990.

....Chapter 4 describes techniques for constructing Ada applications that wish to present multiple, simultaneous transactions to a DBMS. 4. SQL Decimal Support in the SAMeDL. The lack of support for decimal arithmetic and decimal representations in Ada has been the subject of much discussion [1]. Chapter 5 presents a suggested implementation of decimal support. Interested readers are advised to examine the decimal support being prepared as part of the Ada9X revision project [2] This chapter discusses the steps needed to add decimal support, in the form of base domains, to the ....

Ada 9X Project Report - Requirements Workshop. Office of the Undersecretary of Defense for Acquisition, June 1989.

....is a list of the one or more Requirement Summary sections of this rationale containing an indication of how the requirement has been met. Note that a detailed analysis of how the requirements themselves relate back to the original Revision Requests is contained in the Requirements Rationale [DoD 91] General R2.1 A(1) Incorporate Approved Commentaries 1.5 R2.1 A(2) Review Other Presentation Suggestions 1.5 R2.1 B(1) Maintain Format of Existing Standard 1.5 R2.1 C(1) Machine Readable Version of the Standard 1.5 R2.2 A(1) Reduce Deterrents to Efficiency 3.11, 8.5, 9.8 ....

Ada 9X Requirements Rationale. Office of the Under Secretary of Defense for Acquisition, Washington, D.C., 1991.

....is now called Ada.Text IO.Editing. The description has been recast to avoid dependence on the COBOL standard. F. 2) Ada 95 Rationale: Appendices Requirements: Z 1 Appendix Z Requirements This appendix lists the various requirements and study topics discussed in the Requirements document [DoD 90] and generally indicates how they have been met (by refererence to other parts of this rationale) or else notes why they proved to be inappropriate. Z.1 Analysis The requirements are listed here in exactly the order of the requirements document; against each requirement is a list of the one or ....

....B.5 Z.2 Conclusion The above analysis shows that all the formal Requirements have been thoroughly met and it is only the Study Topics for parallel processing where compromises have been made. We can therefore conclude that Ada 95 clearly meets the spirit of the Requirements as expressed in [DoD 90] Ada 95 Rationale References: 1 ....

Ada 9X Requirements. Office of the Under Secretary of Defense for Acquisition, Washington, D.C., 1990.

No context found.

Ada9X Project Report Mapping Document, Draft, Office of the Under Secretary of Defense for Acquisition, Washington, D.C. 20301, U.S.A, February 1991.

No context found.

Ada 9X Documents, Ada 9X Project Report, Real-Time Systems Annex, Office of the Under Secretary of Defense for Acquisition, US Department od Defense, February 1993.

No context found.

Ada 9X Project Plan. Office of the Under Secretary of Defense for Acquisition, Washington, D.C., 1989.

No context found.

Ada Board's Recommended Ada 9X Strategy. Office of the Under Secretary of Defense for Acquisition, Washington, D.C., 1988.

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