AdaIC Sponsored by the Ada Joint Program Office and operated by IIT Research Institute
In This Issue
NRC Study Recommends New Software Review Process, Changes in Ada Mandate
On November 1, 1996, the National Research Council (NRC) at the National Academy of Science (NAS) released its report Ada and Beyond: Software Policies for the Department of Defense. The report was the work of the NRC’s “Committee on the Past and Present Contexts for the Use of Ada in the Department of Defense”, created by the NRC’s Computer Science and Telecommunications Board to review current language policy in the Department of Defense (DoD), and to examine the role of Ada in DoD software development. The study was requested by the Office of the Assistant Secretary of Defense for Command, Control, Communications, and Intelligence (ASD C3I).
The committee concluded that “vigorous support of Ada would benefit warfighting systems, and recommends that the Department of Defense should continue to use and promote Ada in such systems.” However, the committee found “significant problems with the two primary components of the Defense Department’s current strategy for Ada. First, the current programming language policy requires the use of Ada for all new defense software, which the committee finds to be overly broad in scope. Second, the Defense Department’s plan to discontinue investments in both Ada technology and user-community support will weaken the Ada infrastructure, and will work against any requirement to use Ada in the future.” The committee recommended that DoD take the following steps regarding Ada:
- 1. “Continue to require Ada for its warfighting software and drop the Ada requirement for its other software.”
- 2. “Provide roughly $15 million per year for Ada infrastructure support, or drop the requirement to use Ada entirely.”
- 3. “Make programming language decisions in the context of a Software Engineering Plan Review process.”
The committee’s rationale for these recommendations was:
- 1. “In commercially dominated areas, using Ada is generally less cost-effective than using other languages. Requiring Ada’s use in commercially dominated applications would place DOD systems at a competitive disadvantage.
- 2. “In warfighting applications, Ada’s technical capabilities for building real-time, high-assurance custom software are generally superior to those of other programming languages. DOD’s investments in Ada to date have provided DOD systems with a competitive advantage in these areas.”
- 3. “The commercial marketplace alone will not sustain a robust Ada infrastructure.”
- 4. “A relatively modest ($15 million per year) DOD investment at the margin would be sufficient to sustain a robust Ada infrastructure for warfighting applications.”
- 5. “DOD’s inventory of more than 50 million lines of Ada warfighting software will become a liability without a robust Ada infrastructure.”
- 6. “DOD’s current Ada waiver process can be effectively replaced by adoption of the commercially established practice of architecture review boards, a process that can also strengthen DOD’s overall software engineering capability.”
The committee also concluded that “currently available data are insufficient, on their own, to accurately determine the impact of programming language choice on the outcome of defense programs.” Based on “the limitations of available data”, the committee also recommended that DoD “institute a corporate effort to collect software metrics to guide future policy and management decisions”.
Among the environmental factors cited by the committee for changing Ada policies were the shift from custom-made to commercial off-the-shelf (COTS) software, and the increased reliance on product-line architectures that enable software assets to be reused across families of applications. The committee concluded that in “warfighting applications areas such as weapon control and electronic warfare, there is little commercial development, and the Defense Department has established a strong community of warfighting software developers whose production factors are oriented to Ada. However, for the numerous defense applications in which the market is dominated by commercial solutions, such as finance and logistics, production factors have been built around programming languages other than Ada, putting solutions at a disadvantage.”
For further information
The release summarizing the report and the slides used in the public presentation can be found on the Ada Information Clearinghouse’s World Wide Web site at http://archive.adaic.com/docs/present/nrc/ Information on obtaining the full report will be available on the NRC’s Web site at http://www2.nas.edu/cstbweb.
For further information, contact:
CSTB, National Research Council;
210 Constitution Avenue, N.W.;
Washington, DC 20418;
Tel: 202/334-2605; Fax: 202/334-2318;
Ada Joint Program Office — The Phoenix
In the previous newsletter, I discussed the closing of Ada Joint Program Office (AJPO). I explained the rationale and the process by which the office would be closed. Much has happened since I wrote those words — and I am happy to report that the AJPO will not be closing after all! In this newsletter, I will explain what has transpired, and then I will end with a final discussion of some additional items that I think may interest you.
The AJPO remains open
The decision to close the AJPO was predicated upon the view that it had completed its mission, i.e., Ada 95 was an approved international standard, and its infrastructure was in place. This was a reasonable view. However, as part of the closing of the office, much work went into defining exactly what the AJPO did and how it did it. A consequence of this effort was that it became apparent that the AJPO was still needed to support and expand the infrastructure of the Ada effort. This realization caused the Defense Information Systems Agency (DISA) to decide to continue the office in its present form. Consequently, the AJPO will remain open until at least FY99. The budget for FY97 was increased to compensate for the office remaining open the full fiscal year. There will be no closing in June of 1997!
This has had many ramifications. First, the AJPO had handed off its oversight of Ada compiler validation to the National Institute for Standards and Technology (NIST) effective 1 October 1996. This was a planned part of the phase out of the office and occurred on time. However, NIST has since decided to phase out its validation activities for all languages. And since the AJPO will remain open, it seems prudent to keep this capability within the AJPO. As a result, effective with the introduction of the Ada Compiler Validation Capability (ACVC) 2.1 on 1 April 1997, the AJPO will once again assume responsibility and authority for all validations. The Ada Validation Office at the Institute for Defense Analyses has already been funded to continue its role in this effort. Additionally, many of the other transfers of AJPO responsibility mentioned in the previous newsletter have been halted. Those that already occurred have been reversed. The AJPO will continue as before.
The NRC Study
This change of plans was made before the public announcement of the results of the National Research Council (NRC) study of Ada policy. Dr. Barry Boehm headed this group of distinguished experts in studying the Ada policy within the Department of Defense (DoD) on behalf of the Assistant Secretary of Defense for C3I, the Hon. Emmett Paige, Jr. The positive findings of this committee independently supported the decision to keep the AJPO open.
The Boehm study made several key findings. One was that there is no better language for high-assurance (high-reliability) software than Ada. As a result, they have recommended that all warfighting software continue to be written in Ada. Further, enforcement of this requirement should be more rigorous!
On the other hand, systems without a high-reliability requirement (are there any?), specifically information systems, should be written in whatever language is best for the application — meaning that Ada will compete just like any other language for this section of the market, and the selection will be made on the basis of criteria decided by the program manager.
Another finding of the Boehm study was that the Ada infrastructure needs to be supported by the DoD since the commercial share of the market for Ada is limited. The committee recommended that the DoD provide $15 million per year to support this infrastructure, which would go to the AJPO to support the Ada community and vendors. This infrastructure support would include the creation and updating of bindings and tools to make Ada more competitive with other commercial languages. It would also continue to fund many of the successful initiatives started by the AJPO in recent years. They also took the more assertive step of saying that if DoD did not want to support the infrastructure for Ada at this level, it ought to abandon Ada altogether.
The Boehm study also made several very important findings in the area of software engineering and acquisition reform for the DoD. I suggest that if these findings are of interest to you, then you should obtain a copy of the report; it is available for downloading over the World Wide Web. (For further details on the report itself, and on obtaining copies of the documents available, see “NRC Study Recommends New Software Review Process, Changes in Ada Mandate” beginning on page 1.)
Finally, I have some personal news that may be of interest. Effective 22 November 1996, I regretfully submitted my resignation as the Chief of the AJPO. This has been a very enjoyable labor of love for me, and I will miss the people and the staff of the AJPO. The support staff of Jay Lynagh, Joan McGarity, and Gary Shupe are impossible to over praise. They are dedicated civil servants who work very hard behind the scenes to make things happen. I will miss their support. In addition, the staff of IIT Research Institute (IITRI) are very professional and are also unsung “heroes” on the Ada front. Each is a dedicated professional with a “can do” attitude. Finally, there is the cadre at DISA. From DISA Director Lt Gen Edmonds, through his deputy RADM Gauss, and the new Senior Executive Service (SES) executive Joanne Arnette, I could not have asked for more supportive bosses in the chain of command. I will miss them all. Most importantly, I will miss the support of the Ada community and ACM SIGAda, all of whom have always been there to help me do this job.
I am moving on to newer responsibility because of an opportunity too great to miss. I will be the Vice President, North America, for Q-Labs, a software-engineering-services provider. Q-Labs is a subsidiary of Ericsson and has a worldwide customer base.
If you should need to contact me, my new phone number is 301/864-1177; or you can send e-mail to firstname.lastname@example.org.
Thanks again for all of your support. I am sad to leave, but very excited by this new opportunity. Stay in touch!
Charles B. Engle Jr.
Chief, Ada Joint Program Office
22 November 1996
Ada Java Compiler Released
At the TRI-Ada ’96 Conference (Dec. 3-7, in Philadelphia), Intermetrics, Inc., announced the mass-market release of AppletMagic, its tool that converts Ada 95 source code to Java bytecode for execution by any Java-capable World Wide Web browser. AppletMagic simplifies the development of complex, high-reliability applets and can be used as a supplement or an alternative to the Java language.
The Ada Joint Program Office (AJPO) provided partial funding for development of AppletMagic through its Ada Technology Insertion Program-Partnerships (ATIP-P) program. Priced at $99, with a reduced price of $40 for academic use, AppletMagic includes a development environment, class libraries, multimedia training, and Ada language documentation.
Netscape Navigator, Microsoft Explorer, and other Web browsers contain Java bytecode interpreters that execute applets downloaded from Web sites. Because the applets can now be generated by AppletMagic as well as any other Java development environment, the developer can program either in Ada 95 or in Java, or can mix the two; the end user can’t tell the difference.
Tucker Taft, principal designer of Ada 95, and Intermetrics’ technical leader for AppletMagic, said: “The combination of Ada 95 and Java technologies is a ‘best of both worlds’ solution. Ada provides compile-time advantages such as enumeration types, generic templates, in, in-out, and out parameter modes, etc., while the Java execution technology contributes runtime flexibility through automatic garbage collection, dynamic linking and platform independence”.
(As part of the TRI-Ada program, Taft spoke on “Exploiting Java Technology with Ada”.)
Bill Carlson, Vice President for Products and Technology, said: “With Java support on nearly every desktop, and Java-based network appliances and embedded computers popping up everywhere, we’re very excited about making Ada’s software engineering strengths and legacy of reusable software available as an applet development tool.”
AppletMagic is available on CD-ROM for Windows 95 and Windows NT, and can be purchased online. Users seeking more information can visit the AppletMagic site at http://www.appletmagic.com. Headquartered in Cambridge, Mass., Intermetrics, Inc., is a software-development, systems-integration and systems-services company. Further information about Intermetrics can be found at its home page at http://www.intermetrics.com.
Ada 95 at Work
In this issue, we’re listing some of the Ada 95 projects recently added to the Ada Usage Database. If you’d like to submit information on your own project, see the survey form on pages 15-16. If you’d like to check out more such projects, they’re searchable on-line on the AdaIC Web site: http://archive.adaic.com/projects/.
Includes all functionality presented in the CORBA 2.0 specifications; supports numerous extensions. [PC: Commercial]
Ada 95 Bindings for Global Command and Control System (GCCS)
Combining ProtoTech and STARS technology to provide a set of Ada 95 bindings for the GCCS common core services (about 9000 functions in 1000 header files).
Ada 95 GUI Binding and Tools for Windows 95 (Claws) Specifically designed for Ada 95 and Win32; will not be tied to the underlying C API routines. A Windows 95 visual applications builder for the Ada 95 programming language. [PC: Commercial]
Ada 95/POSIX Avionics Open Systems Demonstration Program (OSAT) JSF AV-8B
Avionics flight test demonstration, technology risk reduction program for the Joint Strike Fighter (JSF, formerly JAST). Calculates weapon release ballistics and related cockpit display information. [Workstation/AV-8B (Harrier) Mission Computer: DoD]
Research project to investigate, formulate, and generate “Graphical Representations of Algorithms, Structures, and Processes for Ada”. Has potential to replace pretty-printed Ada source code. [Workstation: Non-DoD Gov’t]
MIL-STD-1553B Bindings for Ada 95
Bindings for the standard on multiplex serial data bus applications are offered as thick and thin. [DoD]
Ada 95 and Trustworthy Systems
Study to produce a document advising how to use Ada 95 for the development of critical applications. [Canadian]
Ada Binding for ODMG-93
Approach allows Ada programmers to use a single language to access object-oriented database functionality regardless of vendor. [Workstation: Air Force]
Ada Computer-Aided Programming System (AdaCAPS)
Interactive development environment (IDE) that works with GNAT (GNU-NYU Ada 95 Translator) under DOS. [PC: Academic]
GNAT Ada 95 Graphics Package (GNA95GP)
2D graphics package/instructional tool; when fully implemented, also to be graphics programming tool. [PC: Academic]
Tasking runtime system of the GNU NYU Ada 95 Translator (GNAT) compiler. [Workstation: Academic]cont’d from previous page
Ada Sound: Structured Music Synthesis System in Ada 95
Proposed to develop new music synthesis system to remedy deficiencies with using outdated computer music languages, and to exploit parallel computers. [PC: Academic]
Ada Upgrade for VisualAge
Enables users to develop software applications by visually connecting software “parts” written in Ada 95 and C++. Users able to add new Ada 95 parts to the VisualAge palette. [Workstation/PC: Commercial]
AdaIDE for GNAT Ada 95
Windows-3.1-based interface program for GNAT Ada 95 program development; multi-document interface (MDI) program based on the Microsoft example in Visual BASIC 3.0. [PC: Academic]
Canadian Space Agency RadarSat Remote Sensing Satellite Payload Computer Unit
Will control payload subsystems, store information, and download it to the ground station in sync with the satellite’s orbits. [Canadian]
Computer Aided Instruction
Includes advanced CBT features; integrated with the resident Ada environment; to provide Ada 95 training over Internet. [Commercial/ATIP-P]
DACS/ASIS-95 and Test Coverage Tools
1) Implementation of the Ada 95 Semantic Interface Specification (ASIS 95) for the DDC-I Ada 95 Compiler System (DACS-95) front end. 2) Ada 95 test coverage environment based on ASIS 95. [Commercial]
Java class Decompiler written in Ada 95. Version 1.0 provides similar output as javap program in Sun JDK distribution; future versions to allow translation to other languages. Ada 95 translation under development. For GNAT. [Commercial]
FIRM: An Ada Binding to ODMG-93 1.2
Functionality Integrated Resource Manager (FIRM), an ODBMS to support real-time avionics applications. [Air Force]
Foggy Bottom Transit Authority (FoBTA)
Computer-controlled HO-scale model of an urban rapid transportation system. [Workstation or PC: Academic]
Little Boxes: An Ada 95 Toolkit for Structured Diagrams
Proposed to design and implement a library of reusable Ada modules that would provide much of the infrastructure for programs that incorporate structured diagrams. [Academic]
Mapping HRT-HOOD Designs to Ada 95 Hierarchical Libraries
Uses subroutine renaming feature and child library feature of Ada 95 to improve the mapping/translations of designs into Ada. [European]
Mutants: An Ada 95 Generic Toolkit for Genetic Algorithms
Proposed to develop a library of components to simplify the construction of systems that use “genetic” methods of problem solving. [Academic]
NMR Spectrometer Control Software
Redesign of software to control a nuclear magnetic resistance spectrometer. [Workstation: Commercial]
OLE Automation Controller in Ada 95
For Microsoft Object Linking and Embedding (OLE) toolset for Microsoft WindowsNT/95 developer. Implemented an OLE automation controller that accessed an OLE server that provided access to CORBA objects. [PC: Air Force]
Object-Oriented Ada 95 Library
Tool to support teaching software engineering, software reuse, other Ada-related courses. [PC: Academic]
Project Armada 1995
Projects for last year students at Uppsala University: extend GNAT’s gnatdist to include all categorization pragmas and load balancing; enhance existing communication subsystem GARLIC; implement a distributed simulator. [Academic]
SemWeb — Semantic Webs
Provides browser and editor to support modeling and creation of Web sites; also provides Ada class libraries that define API for dynamically creating files in HTML, etc. [PC: Commercial]
Simulations of Tuberculosis Control Programs
Implements the simulations. [Commercial]
Stony Brook Ada 95
Ada 95 development system for DOS, 32-bit DOS extended, Win16, and Win32 applications development. [PC: Commercial]
Thor Ada 95 Microprocessor
Developing embedded computing system for Swedish Odin satellite to handle onboard attitude-control functions in space. Space-tested, first 32-bit microprocessor in space using Ada. [Swedish]
Academic Ada - Texbook and Special CD-ROM Edition of Ada 95 Compiler Released
Addison Wesley Computer & Engineering Publishing Group and Aonix (formerly Thomson Software Products) have teamed to release a compiler/textbook package aimed at the student market and also available for any academic, experimental, or personal use without restriction — so long as the use is non-commercial. (A full commercial license is available separately from Aonix.)
The package became available through bookstores in mid-December 1996. It includes both the textbook, Ada 95, Problem Solving and Program Design, Second Edition, by Michael B. Feldman and Elliot B. Koffman, and a CD-ROM version of the compiler, a “Special Edition” of Aonix’s Ada 95 compiler ObjectAda.
Development of the compiler was sponsored by the Ada Joint Program Office (AJPO), and the combined package was used for the first time in a summer-school Computer Science class taught at the Air Force Academy. At the conclusion of the course, the students favorably evaluated the compiler and textbook as easy to use and understand, and the package is now in regular use at both the Air Force Academy and West Point.
This Special Edition of ObjectAda is available for student and academic use on PCs and workstations running Windows95 and WindowsNT. No site license is needed, and the combined package is offered at the same price as the book alone except for an additional charge of around $5 for packaging.
The CD-ROM includes:
- Textbook: Ada 95: Problem Solving and Program Design, Second Edition, an introductory computer-science textbook for Ada 95.
- Compiler: “A fast, disk-efficient” Ada 95 compiler. ObjectAda was the first validated Ada 95 compiler for Windows. Maximum 2,000 lines of code per Ada source file; maximum 20 task objects per program; maximum 35 program units per program.
- Debugger: A multi-window, source-level, symbolic debugger with high-level support for Ada 95 features, including tagged types and protected types.
- Library Manager: A source-based library manager that “minimizes persistent storage on disk, and eliminates traditional Ada library setup and complexity.”
- On-Line Help: On-line, hypertext help and user guide, linked to the textbook and tools.
- Specifications: As noted, the CD-ROM will operate on personal computers and workstations running Windows95 and WindowsNT. Disk space is about 100 megabytes; recommended memory is 12 megabytes; recommended processor is 100-MHz Pentium, but it will run on a ‘486.
- ISBN: Book/CD-ROM package, ISBN 0-201-30485-6; book alone ISBN 0-201-87009-6 (softcover, 814 pages, 1996).
For further information Instructors wishing to receive a complimentary examination copy of the textbook (ISBN 87009) for adoption consideration may send their request via e-mail to email@example.com; within the USA, call 1-800/447-2226. Information is also available at Addison Wesley’s World Wide Web site: http://www.awl.com/cseng/author-index.htm (under Feldman).
For additional information on the full commercial site license available through Aonix, contact 1-800-97-AONIX (972-6649).
Ten Companies Announce New Software Tools Supporting Ada 95
Ten Ada Technology Insertion Program-Partnership (ATIP-P) companies have announced availability of new products; they bring to the commercial marketplace a variety of tools that enhance the usability of Ada 95.
The new products result from Ada Joint Program Office (AJPO) investments to stimulate wider adoption of the Ada programming language within government and the academic, industrial, and research communities. The 50/50 government-industry partnerships for ATIP-P were spearheaded by the Idaho National Engineering Laboratory (INEL). Following (in alphabetical order by company) are descriptions of the new products, their availability, and the points of contact for further information.
AdaMentor 95 AdaMentor 95 is a comprehensive computer-based training course in Ada 95, based on the textbook by John G. P. Barnes Programming in Ada 95. Delivered over the Internet, it supports several innovative features reminiscent of the traditional classroom — such as peer and instructor interaction, an interactive and nonlinear presentation of materials that includes direct links to hypertext reference documents, quizzes throughout the course, and direct access to a validated compiler and linker for solving in-course exercises. It supports both individual self-administered training and organizations providing structured training to a geographically dispersed group under the mentoring of an experienced instructor.
Availablity: The AdaMentor 95 training course was announced at the Tri-Ada’96 conference in Philadelphia, Dec. 4, 1996, and is available for online registration at http://www.adasoft.com/. Optional proficiency assessment testing is planned for early 1997.
Contact: Jerry Horsewood
Cherry Lane Business Park
8750-9 Cherry Lane
Laurel, MD 20707
tel: 301/725-7014; fax: 301/725-0980
AppletMagic is an Ada 95 compiler that generates Java bytecodes. The compiler allows users to construct portable Java applets or applications using Ada 95 — the Ada 95 code being translated to bytecodes. Once translated, the Ada95-Java applets execute in the context of a World Wide Web (WWW) browser that supports Java (e.g., Netscape 2.0.x) and are used to enhance WWW pages with animation and other active and interactive features. The compiler produces portable Java bytecodes in the same kind of class files as Sun’s Java compiler, supporting interoperability between Java and Ada 95, including the extension of Java object classes with Ada 95 tagged records, and vice versa.
Availbility: Trial versions have been available on WWW site http://www.inmet.com/javadir/download/. Copies are usable for a limited time, after which they no longer function. A non-limited version may then be purchased. A commercial CD-ROM for Windows 95 is also available. Trial versions are available for Sparc Solaris, Windows 95/NT, and MacOS.
Contact: For information on how to order AppletMagic, visit Intermetrics’ WWW site: http://www.appletmagic.com/. (Also see “Ada Java Compiler Released” elsewhere in this issue.)
DACS/ASIS-95 and Test Coverage Tools (TCI)
DDC-I, Inc., offers an implementation for the DDC-I Ada 95 Compiler System (DACS) frontend conforming with the latest version of the Ada Semantic Interface Specification (ASIS 95) and an Ada 95 test coverage environment. An open-systems solution, the ASIS interface will be common among all DACS-95 compilers. It gives programmatic read-only access to semantic Ada 95 information through the compiler-independent ASIS 95 standard. DACS/ASIS-95 can be used to build Ada 95 tools — including restructuring, browsing and navigation tools, coding-style and standards-compliance tools, data-flow and dependency-tree analysis tools, language translations and document-generation tools, quality-assessment test tools, and safety- and security-compliance tools. The DACS-95 Test Coverage Tools set is an Ada 95 test-coverage environment, based on ASIS 95, which supports automatic test generation for structured analysis, coverage analysis (condition and decision coverage), nonintrusive verification, and support for embedded testing. A state-of-the-art test tool set for coverage testing, DACS-95 Test Coverage Tools are useful for unit and component testing and can be used to measure metric test completion.
Availability: Both DACS/ASIS-95 and DACS-95 Test Coverage Tools will be available in the second quarter of 1997.
Contact: Jennifer Sanchez, DDC-I
400 North 5th Street
Phoenix, AZ 85004
tel: 602/275-7172; fax: 602/252/6054
SemWeb (Semantic Webs)
SemWeb provides a browser and editor to support the modeling and creation of Web sites using semantic networks. It also provides Ada class libraries that define an application programming interface (API) for dynamically creating files in HyperText Mark-up Language (HTML) and other WWW languages and formats. The SemWeb products were created to provide WWW sites with higher quality, semantic-based information and capabilities. The cost of maintaining a Web site is dramatically reduced through the use of formal modeling and the generation of Web sites from these descriptions. And novel, large, and complex Web-based servers can be implemented reliably through the use of Ada class libraries that generate HTML and other WWW standard formats based on the semantic network representing a site.
Availability: First quarter of 1997.
Contact: William Loftus
WPL Laboratories, Inc.
410 Lancaster Avenue, Suite 6
Haverford, PA 19041
Stony Brook Ada 95
Stony Brook Ada 95 is a complete Ada 95 development system for DOS, 32-bit extended, WIN 16, and WIN32 applications development. The Stony Brook compiler is intended to deliver increased developer productivity and superior code generation, and to achieve faster compilation times than any other optimizing compiler, for any language. The company reports that its compilers “produce high-quality code, as good as that of the best compiler, for any language, on the supported platforms.”
Availability: Stony Brook Ada 95 is presently in beta test. The initial release, featuring complete implementation, will be available March 1997.
Contact: Richard Gogesch
Stony Brook Software
187 East Wilbur Road, Suite 4
Thousand Oaks, CA 91360
Ada 95 Upgrade for VisualAge
The Ada 95 Upgrade for VisualAge makes the features and power of IBM’s award-winning VisualAge C++ available to Ada 95. This upgrade for VisualAge enables users to develop software applications by visually connecting software parts written in Ada 95 and C++. The Ada 95 code is automatically generated for connecting software parts, and users are able to add new Ada 95 parts to the VisualAge palette. VisualAge ships with the IBM OpenClass Library, which is made up of a large collection of visual and nonvisual parts. The Ada 95 Upgrade for VisualAge support mixed-language ?
Availability: The Ada 95 Upgrade for VisualAge became available January 1, 1997.
Contact: Ralph Crafts
OC Systems, Inc.
9990 Lee Highway, Suite 270,
Fairfax, VA 22030
Orbix Ada allows developers to create distributed applications based on the Object Management Group’s (OMG’s) Common Object Request Broker Architecture (CORBA) standard. Orbix includes all the functionality presented in the CORBA 2.0 specification — including Interface Definition Language (IDL) compiler, dynamic invocation interface, and InterORB interoperability protocol. Orbix supports numerous extensions to CORBA, to better enable the design and construction of advanced CORBA-based applications. Orbix for Windows provides a gateway between Microsoft’s Object Linking and Embedding (OLE) 2.0 and CORBA by way of a specially enhanced IDL compiler that generates a complete program that acts as an OLE automation server. Orbix supports major platforms using multiple programming languages, including Ada 95, C++, and Java.
Availability: Orbix Ada version 1.1 is now available for Solaris, SGI, AIX, DEC Alpha, HP-UX, and Windows NT on a variety of Ada 95 compilers. The latest version adds support for tasking and full CORBA type Any, using newly implemented Orbix libraries built 100% in Ada 95.
Contact: Phil Carrasco
Objective Interface Systems, Inc.
1892 Preston White Drive
Reston, VA 20191-5448
GNAT Ada 95 for Apple Macintosh
McKee Consulting offers a GNU Ada Translator (GNAT) Ada 95 compiler and environments for the Macintosh, running Tenon Intersystems MachTen Unix. MachTen is a POSIX-conformant Unix with a full Internet protocol suite and a software-development environment based on the GNU compiler. The product includes:
- GNAT (v.3.07 or later) for the Macintosh Power PC (PPC); Target: PowerMac, running MachTen (4.03) or MacOS (7.5.1 or later);
- GNAT (v.3.05 or later) for the Macintosh 68020/30/40 (68k); Target: 8020/30/40, running Tenon’s MachTen Unix (2.3);
- Ada language bindings to the Macintosh Toolbox (API);
- example code for using the compiler and the toolbox; and
- Installation scripts, system tuning guide, user documentation.
Availability: GNAT Ada 95 was released to GNAT Internet sites in April 1996. MachTen was recently released on CD, with GNAT and McKee tools bundled.
Contact: Gary McKee
P.O. Box 3009
Littleton, CO 80161-3009
e-mail: firstname.lastname@example.org or: email@example.com
Claw for Microsoft Windows NT or Windows 95
The Claw binding is an object-oriented frontend environment offering a framework and resources for Ada programmers to create applications for the Microsoft Windows NT or Windows 95 operating systems. Windows programmers can now use Ada 95, the only internationally standard object-oriented programming language. Claw is a thick binding for Ada 95, and allows programming in the base language without additional commands or modifications to the code. Claw allows Ada 95 to be more effective on the world’s most popular operating system by providing all of the capabilities needed to make development of Ada 95 graphical user interface (GUI) applications easy. The tutorial documents the use of Claw with and without the GUI-construction tools.
Availability: See http://www.rrsoftware.com/claw.htm for further information.
Contact: Ian Goldberg
RR Software, Inc.
P.O. Box 1512
Madison, WI 53701-1512
MIL-STD-15553B Bindings for Ada 95
Noetic Software, Inc., offers thick and thin Ada 95 bindings for MIL-STD-1553B (multiplex serial data bus) applications, developed to implement hardware/bus initialization, bus control, remote terminal, and bus-monitor operations. Also available are thin bindings for a low-level interface to the ILD-DDC ACE (BU61589) MIL-STD-1553B hardware. These bindings allow for an easy transition of existing applications to Ada 95 and a greater potential for software reuse among all MIL-STD-1553B applications. The standard interface reduces costs and time investments associated with training developers in the creation and use of 1553B applications.
Availability: Became available in October 1996.
Contact: Michael Kiernan
Noetic Software, Inc.
2300 Computer Avenue,
Willow Grove, PA 19090
AdaIC Web Pages Redesigned
The AdaIC World Wide Web pages were recently redesigned with three goals in mind: to create a more consolidated directory of information that maximizes access to the AdaIC's most frequently accessed documents, reports, and programs; to increase the visibility and use of information within the databases for AdaIC Catalog of Education and Training (CREASE), compilers, products and tools, library, projects and usage, and Internet links databases; and to reduce the size of graphics on all main and sub pages.
From the main page, users may go to a browsable directory of information on a particluar Ada subject area either by clicking on one of the green header boxes or by selecting from the pull-down navigational window. Links are provided under each of the Ada subject areas, for users looking for quick and direct access to some of the AdaIC's most frequently accessed files and pages.
A wealth of database information
The AdaIC maintains databases that track Ada education and training, products and tools, projects, compilers, publications, and other Internet resources. In order to more easily access the wealth of information in these databases, users may now execute both keyword searches and search on particular fields. Many titles, organizations, and tools are contained within scrollable lists for browsing, and search results contain links to the actual search item when available.
Graphics & bandwidth
In order to speed up the load time of the AdaIC Web pages, the graphics on the main and sub pages were reduced in size. Thus, the graphics can still serve as visual navigational clues, without impeding access to the actual information.
We encourage all our users to try out the new AdaIC site and let us know what you think! http://archive.adaic.com.
Services Building Track Records in Systematic Reuse: Services provide input to annual reuse report
In one sense, software reuse is a given throughout the world of software development. Virtually everyone agrees that it is vital to holding down costs and increasing quality, and virtually everyone has reused code from earlier efforts. In another sense, it is new territory, with lessons to be learned and old habits to be changed every day.
The difference is that ad hoc, opportunistic reuse is only the very beginning of reuse. To be successful, reuse must be systematic; it must be an established process working throughout development; it must be based on the domains where development actually takes place, whether avionics or financial accounting or any other; and it must build libraries of proven resources than can be easily accessed when needed.
This is what is meant by “reuse” at the Department of Defense (DoD) Software Reuse Initiative (SRI) at the Defense Information Systems Agency (DISA). In SRI’s terms, this is a product-line approach — one that is systematic, process-driven, domain-specific, architecture-centric, and library-based.
Much work has already taken place along these lines. Now, those efforts must be given the widest possible circulation. One step in that process began on June 14, 1996, when Hon. Emmett Paige, Assistant Secretary of Defense for Command, Control, Communications, and Intelligence (ASD C3I), requested that the Services provide input to the SRI’s annual report to Congress.
The Services — accomplishments and plans
The Service inputs have provided status updates on their programs, shown the accomplishments of the past year, and indicated plans for the future. While differing in particulars, the three Services are each working towards the same general goals.
Army — guidance, tools, and project experience
The Army’s input notes that the Army Reuse Initiative is not a program as such, but is more a paradigm or process of addressing and leveraging potential reusable components. The common functions and software identified are key to the Army’s Technical Architecture. Implementation of this approach is a business decision that considers cost, schedule, and functional requirements against the benefits offered by software reuse and the integration and interoperability offered by a common architecture.
Important among centralized activities, the Army has been providing general guidance documents to support increased reuse. On Apr. 26, 1996, the Secretary of the Army signed the United States Army Software Reuse Policy. The Army is assigning domain managers to domains that align with the current Program Executive Officer’s (PEO’s) organization. The Army is also staffing an updated software-reuse strategy and implementation plan.
In concurrent action with the publishing of the software-reuse policy, the Director of Information Systems for Command, Control, Communications, and Computers (DISC4) drafted an updated Army Software Reuse Strategy and Army Software Implementation Plan. These two draft documents were reviewed and modified by an Army working group of software-reuse experts. Both documents were submitted Army-wide for comments and adoption in the last quarter of FY96.
The Army has also been moving ahead on tools and practical support for developers. For instance, the Army Reuse Center (ARC) incorporated a new commercial off-the-shelf (COTS) search-and-retrieval engine into the Army’s Reuse Library to provide an interactive Web interface to the Defense Software Repository System. The tool also allows greater access to the ARC through the Internet and only requires the user to have a Web Browser. The new tool provides greater interoperability with other reuse libraries.
Also, the Army is capitalizing on the lessons learned in a Communication-Electronics Command (CECOM) pilot project with the Software Technology for Adaptable Reliable Systems (STARS) program. In particular, a follow-on pilot is addressing the business-issue barriers to implementing reuse technology when contracted to private industry. Additionally, many significant software reuse initiatives were executed outside of a centralized Army effort, and some of these are described in the Army report.
Navy — achieving success within a practical framework
The Department of the Navy (DON) views software reuse as an essential part of the software development and acquisition process: As is true of other software development and acquisition practices, encouraging reuse makes sense in some instances, while in others it is simply not practicable.
From a Navy perspective, reuse is a practice or a decision point during the acquisition and development (including reengineering) process when the use of existing software assets is considered before new development is begun. The decision point exists for both government and contract developers because success in both communities is measured in terms of cost, schedule, and performance.
As part of the software development and acquisition process, the Navy has found that software reuse has not been implementable at the “enterprise” level. The primary factor readily limiting reuse at this level is that funding is provided on a program basis. There has been little incentive for one program to incur the additional expense of providing reusable components for another program.
The Navy’s success with software reuse is attributable to a Navy-wide awareness effort centered around the DON Software Reuse Plan, the DON Software Reuse Guide, and the support and funding provided by the SRI. Other factors, such as fiscal constraints, profit motives, maintenance costs, emphasis on architecture development, interoperability concerns, improved communications among programs, and the active involvement of the Program Executive Officers (PEOs) and Program Managers (PMs), have also contributed to the increased emphasis on reuse. The Navy finds that the momentum associated with these “natural” forces will likely sustain software reuse. It is Navy policy not to mandate software reuse but to consider software reuse prior to any new development and/or reengineering effort. This is consistent with DOD 5000.2-R, Part 4.3.5 (1 and 2).
Air Force — Reuse support from conferences to tools
In its input to the annual reuse report, the Air Force highlighted several activities and products during the last year to support the DoD SRI — including participation in DoD planning and review meetings; planning, coordination, and execution of workshops, conferences, and conference sessions; and the publication of reuse-related documents that support program managers and engineers in the adoption and integration of reuse practices.
Besides supporting development and review of SRI documents (including the Reuse Vision and Strategy, the SRI Strategic Plan, and the SRI Operational and Management Plan), the Air Force has developed three guidance documents of its own: the USAF SRI Goals and Objectives, the USAF SRI Strategic Plan, and the USAF SRI Implementation Plan. The Goals and Objectives is complete, the Strategic Plan is undergoing final USAF review, and the Implementation Plan is planned to be released for USAF field review by the end of September.
Two important building blocks in the Air Force’s internal effort have been the Comprehensive Approach to Reusable Defense Software (CARDS) and Portable, Reusable, Integrated Software Modules (PRISM) programs.
Under the USAF CARDS Partnerships program, the Air Force developed the Reuse Methodology Fusion Framework — which aids program managers and engineers in the selection and integration of reuse methods into various software lifecycle processes. The CARDS Partnerships program also developed the Reuse Readiness Technology Transition Framework — which aids DOD organizations in assessing their current software lifecycle processes and environments and planning the adoption of reuse technology, concepts, methods, processes, and tools.
The USAF CARDS program coordinated and supported the SRI/MITRE, Inc., workshop on DoD Domain Scoping held in September 1995. The results of these efforts were presented at the 1995 and 1996 Software Technology Conference held in Salt Lake City. In addition, the CARDS program planned and coordinated Reuse 95 and Reuse 96 — focused conferences on state-of-the-art reuse practices.
The Air Force continues to pursue an active agenda in software reuse. While it notes funding constraints, current plans include continuing current efforts aimed at:
- encouraging implementation of software reuse within the various mission domains in the Air Force via the creation and implementation of organizational reuse plans;
- baselining the DOD SRI Technology Roadmap (two-lifecycle model — domain engineering/application engineering) and identifying and addressing (or coordinating) filling gaps in this lifecycle process; and
- initiating a Command Center Product Line (CCPL) contract as a test case for product-line engineering, including: architecture group, product-line engineering centers, and product-line asset support.
For further information
When SRI products such as the 1996 SRI Annual Report are made available for release to the public, they will be announced via the “Software Engineering News Brief” service, which is sent weekly by e-mail. To be added to the distribution list, send e-mail to:
The body of the message should say:
Information will also be available via this newsletter and the ReuseIC’s Web site: (http://sw-eng.falls-church.va.us/ReuseIC/).
Additional information can be obtained through the ReuseIC at 1-800-REUSE-79 (738-7379).
In the Department of Defense’s (DoD’s) efforts to control software costs and improve reliability, extensive, systematic software reuse has been shown to be one of the most promising strategies available.
The Software Reuse Initiative (SRI) was dedicated to bringing that promise to reality — working to coordinate software-reuse efforts, to maximize the use of resources to develop the necessary infrastructure, and to turn the focus from libraries to adoption of a reuse-driven, product-line approach to systems acquisition, development, and lifecycle support.
In August, Mr. Anthony Valletta, Deputy Assistant Secretary of Defense (C3IA) and Chair of the Software Reuse Executive Steering Committee (RESC), declared the SRI a success. The SRI’s Annual report will provide a look at the accomplishments that produced that success.
Under the DoD SRI Strategic Plan, the SRI had five Strategic Thrusts:
- 1. Implement a product-line approach: The SRI provided a focus for implementing changes in the way the DoD has done business. By effecting DoD infrastructure changes and by using product-line management and engineering principles, the SRI promoted asset management and product integration. The SRI encouraged that product-line management, engineering and product integrity emphasis be placed on “best of breed” architectures that have become core elements for migration systems.
- 2. Develop a reuse-based software systems engineering paradigm: The SRI provided the base technology in the form of successful reuse practices and supporting integrated environments for product-line approach and asset management. The SRI also provided a technology roadmap for the reuse-based paradigm — one that identifies central technology for insertion and investment. Lessons learned from their use have supported the continued evolution of the products.
- 3. Remove barriers to reuse: The SRI provided business support in the form of a tailored business model, as well as the incentives leading towards the institution of reuse. Lessons learned from their use have supported their continued evolution, and the policy and procedure change requirements for the DoD infrastructure.
- 4. Quicken technology transfer: The SRI provided technology framework products and services together with required education and training to stimulate initial adoption of the product-line approach. In some cases, partner programs were used to speed adoption of reuse technology. Lessons learned from their use have supported the continued evolution of the products.
- 5. Make successes apparent: The SRI used marketing and outreach programs to promote reuse and disseminate information. Benchmarking was used to prove the effectiveness of reuse. This information has promoted and supported the practice of reuse and the product-line approach.
The SRI accomplished its near-term goals and provided the DoD with the ability to adapt to future technologies.
Year by year, funding resources are becoming more constrained across the DoD. The reality of the current resource environment dictates that reuse efforts must take place as part of the overall program/systems development efforts and priorities. This has led to a reevaluation of the approach to achieving software reuse. With the success of the SRI’s DoD-wide initiatives, redirection of reuse activities was an obvious response. The availability of SRI products and experience opened the way for DoD to pursue software reuse in the context of overall software-management priorities and fiscal constraints.
Beginning in Fiscal Year 1997, DoD is redirecting its reuse efforts away from a large consolidated program and onto program- and system-specific activities that can be successfully funded. The priority is shifting to smaller scale, program- and domain-specific efforts that support mission requirements and that can be realistically funded within existing Service and Agency priorities.
One SRI activity that will remain in place without much visible change is the Reuse Information Clearinghouse. The ReuseIC will be part of a consolidated Software Engineering Information Center; its site on the World Wide Web will remain at http://sw-eng.falls-church.va.us/ReuseIC/.
For the future, the Services and Agencies will continue to plan, budget, and implement software reuse in context of mission-related programs and other software management priorities. With the basic reuse infrastructure established and initial successes accomplished, the legacy of the SRI will be further lessons learned, technology maturation, additional product-line opportunities and usage, and the identification and exploitation of opportunities for cross-product-line and inter-service reuse.
A future, where the product-line approach is the DoD approach of choice for new and evolving domains and the returns on DoD reuse investments are significant, is one that is well within reach because of the efforts of the Software Reuse Initiative.
For further information
When SRI products such as the 1996 Annual Report are made available for release to the public, they will be announced via the “Software Engineering News Brief” service, which is sent weekly by e-mail. To be added to the distribution list, send e-mail to:
The body of the message should say:
Information will also be available via this newsletter and the ReuseIC’s Web site: (http://sw-eng.falls-church.va.us/reuseic/). Additional information can be obtained through the ReuseIC at 1-800-REUSE-SW (738-7379).
Perhaps the main reason that the Ada programming language was developed is quite non-technical: to save money. Software engineering has goals: modifiability, efficiency, reliability, understandability, portability, reusability. Whatever their technical merits, the reason we pay attention to those goals is because failure to meet them costs money. Lots of it.
And the cost is not merely a matter of how much it costs to develop a program on day one. The point that concerned the Department of Defense (DoD) in adopting Ada was lifecycle costs — the cost of modifying, maintaining, and improving a system over the course of years.
To some extent, Ada’s advantages over the long haul are simply common sense: To the extent a program is modular, for instance, it will be easier to modify; to the extent it is readable, it will be easier to maintain. Ada encourages these characteristics far more than most other languages. Lifecycle costs, then, are bound to be less when using Ada.
Backing up those common-sense advantages with hard evidence, you can find several files of interest on the Ada Information Clearinghouse’s (AdaIC) World Wide Web site.
- One is a study conducted by the MITRE Corporation, “Ada in the Maintenance Arena”, by Michael J. Schrank, Glenn W. Boyce, Jr., and Dr. Carolyn K. Davis.
- Another is Dr. Stephen F. Zeigler’s paper “Comparing Development Costs of C and Ada”, previously mentioned in the Spring/Summer issue of this newsletter.
The MITRE study
The MITRE study points out that software-maintenance costs have increased to the point where they consume 60-80% of many software budgets. The study indicates that U.S. corporations are spending $30 billion annually on software maintenance and may employ as much as 90% of all software resources.
An example the study gives from the world of embedded systems is the Air Force’s F-16 aircraft. Development costs were $85 million, but estimated maintenance costs are $250 million. MITRE’s experience in this area comes from “an ongoing effort to evaluate military [software-maintenance organizations] from the system-level, software, and cost perspectives”. Part of this effort has included development of maintenance cost estimates for each of the maintenance activities. “Using this baseline of information,” the report notes, “we are able to project the potential savings that can be attributed to the use of Ada.”
The report’s case for Ada cost savings does require making certain assumptions. One is the expectation that the amount of delivered source lines of code will be reduced. The authors point out, however, that reports indicate that developers must be experienced in Ada to increase development productivity — which many Ada supporters regard as a given.
A second assumption requires that one be able to compare equal functionality in analyzing multiple languages. This issue is addressed by reference to the “function point” (FP) data collected by T. Capers Jones — which compares different languages’ line counts in terms of the functionality they provide, rather than assuming that one line in one language is as meaningful as one line in any other. The FP data indicates that Ada will obtain equal functionality with fewer source lines of code (SLOC) than C and other high-level languages such as FORTRAN and Jovial. “For Ada, the SLOC per FP is 71; for C, the SLOC per FP is 128; and for other higher order languages (HOLs), the SLOC per FP is 105.”
The study authors also calculated comparative costs for an average annual maintenance effort within a ten-year “maintenance horizon” (using a parametric tool, Lockheed-Martin’s Programmed Review of Information for Costing and Evaluation (PRICE) Software (PRICE-S)). Their analysis showed average annual maintenance costs to be lower for Ada than for C and for all other HOLs in general.
(The MITRE study can be found on the AdaIC Web site at http://archive.adaic.com/docs/reports/schrank/main.htm).
What improvement would C or other languages need?
The report then asks what sort of a boost C or other languages would need to come up to Ada. As an example, the study shows the effects of increasing C and other languages’ productivity factor by 50% and increasing quality by 25%. For other HOLs in general, the combination would bring support costs down to those of Ada. For C, though, that same improvement would still not be enough. Moreover, “[w]ith these increases in productivity and code quality for other HOLs and C,” the report says, “Ada would still maintain its cost advantage since many of the techniques used to achieve the increases in productivity and code quality in other languages could also be applied to Ada.”
However, the report also points out that Ada itself must be supported by investment. The report concludes that very few large Ada programs have entered the maintenance phase. When they do, just “handing over the product and the tools is simply not sufficient”. Training in a product’s design methodology, software-engineering practices, and proper tool usage are “vital to preserving the quality of software product.”
Successful maintenance, the report says in closing, “cannot occur without considerable advance planning on the part of all organizations associated with the maintenance and support of software.
The Zeigler study
The evidence available to the MITRE study indicated that few major Ada systems in the DoD have moved into the maintenance phase. To gain evidence from the maintenance perspective, we can look at long-term figures for a commercial product — specifically the Verdix Ada Development System (VADS), on which work began in 1983. The project was started in C because suitable Ada compilers were not yet available. Later, however, both C and Ada were used.
Quite unintentionally, the use of both languages provided a head-to-head comparison of C and Ada. Both the staff and the tools they used kept the comparison fair. The VADS tools, supporting both C and Ada, were used for their own development, and the staff was equally proficient in both languages.
All that was needed was for someone to go back over the update/maintenance records of the Verdix system. This analysis was performed by Dr. Stephen F. Zeigler, who worked on the effort first for Verdix, now for Rational Software Corp. (which later purchased Verdix). The data from the VADS effort reveals that over the lifecycle, Ada’s cost effectiveness is twice that of C’s, or better.
One other notable conclusion was that, within a six-month timeframe, Ada is no more difficult to learn than C is; and as developers continue to learn Ada, their code will improve in quality. In contrast, the study finds that the fix rates of C users do not substantially improve after the first six months. “We can observe that those people who code primarily in Ada can expect fewer bugs and general improvement, while C users can expect harder going,” the study reported.
(The Zeigler study can be found on the AdaIC Web site at http://www.adaic.com/whyada/ada-vs-c/cada_art.html.)
We need your help in identifying who is using Ada 95 either to develop new systems or to reengineer systems that have been developed in other languages. We are tracking this information for two primary reasons:
- to maintain a knowledge base of how Ada is being used and for what applications it is most frequently used;
- to develop a set of metrics that future developers can use to predict the productivity and cost of systems developed in ada.
Data collected by means of this survey will be available to you for browsing on the AdaIC World Wide Web site (http://archive.adaic.com/projects/). In addition, we are supplying this data to the National Software Data and Information Repository (NSDIR) for inclusion in their comprehensive database of software-development projects.
Please take a few minutes to complete the enclosed survey, and return it to the AdaIC at your earliest convenience. Thank you for your assistance! Please return completed forms to:
Ada Information Clearinghouse
P.O. Box 1866
Falls Church, VA 22041
Financial risk is frequently a concern when an organization transitions to an Ada-based development environment. Responding to this, the Ada Joint Program Office (AJPO) has established a resource library of Ada software tools for use by government organizations desiring to move to the new technology.
The library, administered by the Idaho National Engineering Laboratory (INEL), will make available Ada 95 bindings, compilers, application systems, and other innovations in return for evaluations of the products’ technical features and customer support. The tools will be on loan for an appropriate period (say, six months), and thereafter will be made available to others interested — as also will be the evaluations.
The library will thus leverage the AJPO’s investment in promoting the development and spread of the Ada programming language. Ada 95 tools will be variously applied and reapplied in the field, and all involved will benefit from real-use evaluation and lessons learned. Organizations interested in obtaining additional information on the tools loaner program and the Ada95 tools available should contact the Idaho National Engineering Laboratory:
These Newsbits have been extracted from the AdaIC’s “Software Engineering News Briefs” – a regular news feature that is sent out electronically on a weekly basis. To be added to the distribution list, please send e-mail to: firstname.lastname@example.org. In the body of the message, write: subscribe newslist.
The Software Engineering World Wide Web site, home page for both the Ada and Reuse Information Clearinghouses, has been judged among the “Top 5% of the Web” by the Point Web Reviews (part of the Lycos company’s search activities on the Web). Sites are chosen based upon their content, presentation, and experience.
“Discovering Ada” — Enhanced CD-ROM now available at no charge to Services, academia
The “Discovering Ada” CD-ROM, Version 2.0, is now available. “Discovering Ada” is an interactive, multimedia Ada 95 tutorial, produced by Intermetrics, Inc. It is intended to help Ada 83 and non-Ada programmers familiarize themselves with Ada 95. For Version 2.0, Intermetrics has corrected bugs reported in Version 1.0, added a tutorial on Web Applets in Ada 95 and syntax reference diagrams, and included the Ada 95 Rationale.
The Ada Joint Program Office (AJPO) has a number of copies of Version 2.0 available for free distribution to the Service Academies, to other colleges and universities, and to program managers; distribution is via the Ada Information Clearinghouse (AdaIC). Interested parties should contact the AdaIC by phone at 1-800-AdaIC-11 (232-4211), or via e-mail at email@example.com.
Version 2.0 was made available commercially in December through Intermetrics. For more information on commercial distribution, contact Paige Conrad, Intermetrics, Inc., 617/661-1840, firstname.lastname@example.org.
Trade group considering candidate bindings for Ada Common Environment
The Ada Common Environment Working Group of the Ada Resource Association (ARA) is currently reviewing candidates for adoption as “Ada Common Environment Bindings”. In October, the trade group sought nominations for the X Window System (X11), Microsoft Win32, Open Database Connectivity (ODBC), and Microsoft Foundation Classes (MFC). In November, the group started an 8-week period with the goal of selecting suitable candidates. One binding from each area will be designated as “ARA Common” and will be recognized by member companies of the Ada Common Environment Working Group.
The call for participation noted that nominated bindings must be existing implementations — “freely distributable, though not necessarily in the public domain. Bindings that do not rely heavily on vendor-specific language features are a plus.”
[Steven W. North, Secretary, ACE WG, c/o OC Systems, Inc., 9990 Lee Highway, Suite 270, Fairfax, VA 22030-1720; e-mail: email@example.com]
The 11th Annual Symposium of the DoD’s Ada Software Engineering Education and Training (ASEET) Team will be held at Monmouth Univ., Monmouth, N.J., 10-13 June 1997. The theme is “The Ada95 Tool Chest for the Year 2000”; the deadline for abstracts (2-4 pages) is 15 Mar. 1997.
[Major David Cook, AFIT/LSS, 2950 P Street, Wright-Patterson AFB, OH 45433-7765; Tel: 937/252-0503, x4204; Fax: 937/656-4550; DSN 785-; e-mail: firstname.lastname@example.org. After 1 Mar., further information at ASEET Web site: http://pr.erau.edu/~binguee]
Ada-Europe ’97 — International Conference on Reliable Software Technologies
The 1997 Ada-Europe Conference will be held June 2-6, 1997 in London’s Tower Hotel. It aims to bring together users and vendors of software engineering tools, and those who research and teach related techniques, to discuss and exchange new developments and to share good practice. Participation in the Conference is invited from all those in the software-engineering community — users, vendors, educators and researchers. Find the call for papers and additional information at: http://www.sis.port.ac.uk/adauk/Ada-Europe/Conference/1997.
[Ada-Europe Conference Administrator: Helen Byard, c/o Ada UK, P.O. Box 322, York YO1 3GY, UK-England; tel: +44 1904 412740; fax: +44 1904 426702; e-mail: email@example.com. Conference Chairman: Bill Taylor, e-mail: firstname.lastname@example.org. For further information, send e-mail to: email@example.com]
Ada and Reuse News Briefs combined and expanded
The bi-weekly news services for Ada News and Reuse News have been combined, and the news service’s scope has been expanded. News briefs now provide information on the following Defense Information Systems Agency (DISA) initiatives: Ada, software reuse, I-CASE, DII, COE. News summaries will be issued weekly.
[Ada Information Clearinghouse, Reuse Information Clearinghouse; e-mail: firstname.lastname@example.org]
New and improved Ada jobs page on-line
The Ada Information Clearinghouse (AdaIC) has unveiled its new and improved Ada Jobs Web page. The page is located on the AdaIC Web site at http://www.adaic.com/jobs/. The new page saves time and effort by allowing readers to post their own Ada jobs listings, instead of first having to submit the information to the AdaIC. By posting a listing and then clicking the “reload” button, readers can view their messages immediately.
In addition to current Ada employment opportunities, postings can include links to recruiters’ pages, images, and articles related to the Ada job market. [For further information, contact the AdaIC at 1-800/AdaIC-11 (232-4211).]
24th Annual ACM SIGACT-SIGPLAN Symposium on Principles of Programming Languages
January 15-17, 1997
La Sorbonne, Paris, France
Workshop on Domain-Specific Languages
(in association with POPL ’97)
January 18, 1997
SIGCSE ’97 Conference and Exhibit Special Interest Group on Computer Science Education of the Association for Computing Machinery
February 27-March 1, 1997
Fairmont Hotel, San Jose, CA
ACM97 — The Next 50 Years of Computing
March 3-5, 1996
San Jose, CA
March 13-19, 1997
March 18-20, 1997
Washington, D.C., Convention Center
Eighth Annual Workshop on Institutionalizing Software Reuse (WISR8)
March 23-26, 1997
Joint Workshop on Parallel and Distributed Real-Time Systems
Fifth International Workshop on Parallel and Distributed Real-Time Systems (WPDRTS) and Third Workshop on Object-Oriented Real-Time Systems (OORTS)
April 1-3, 1997
SEI Conference on Risk Management
Managing Uncertainty in a Changing World
April 7-9, 1997
Hotel Cavalier, Virginia Beach, VA
8th International Real-Time Ada Workshop (IRTAW 8)
April 8-11, 1997
Ravenscar, North Yorkshire, England
The 9th Annual Software Technology Conference (STC)
April 27-May 2, 1997
Salt Lake City, Utah
ICSE-19: 19th International Conference on Software Engineering
April 27-May 3, 1997
First International Conference SQE 97 Software Quality Engineering including Symposium on Software Engineering Education
May 5-7, 1997
Wessex Institute of Technology, Southampton, UK
1997 International Conference on Software Engineering
May 17-24, 1997
Sheraton Boston Hotel and Towers, Boston, MA
Ada Europe ’97 — International Conference on Reliable Software Technologies
June 2-6, 1997
June 2-5, 1997
Georgia World Congress Center, Atlanta, GA
11th Annual ASEET Symposium
June 10-13, 1997
Monmouth University, Monmouth, NJ
SEKE ’97 — The Ninth International Conference on Software Engineering and Knowledge Engineering
June 18-20, 1997
*Washington Ada Symposium (WAdaS ’97)
June 23-25, 1997
McLean Hilton, McLean, VA
*Object World West ‘97
July 23-25, 1997
Moscone Center, San Francisco, CA
15th International Conference on Artificial Intelligence (IJCAI-97)
Aug 23-29, 1997
Sixth European Software Engineering Conference (ESEC’97)
September 22-25, 1997
OOPSLA ’97: Conference on Object Oriented Programming Systems Languages and Applications
October 12-17, 1997
Call the AdaIC for further information on the following Ada conferences, seminars, and workshops. Let us know if your organization is sponsoring an Ada event!* The AdaIC will have an exhibit.
We sometimes have free passes to conference exhibit areas where the AdaIC will have an exhibit. Feel free to call and ask for available passes.