\\..&& = article title <<..>> = subheads {..} = italics * = bullet (except for two in calendar) Except for old header text, all mandatory returns, both
and

, are done with double carriage returns. AdaIC News to go electronic-only AdaIC News Fall 1997 Ada Information Clearinghouse The Official Source for Ada Information Vol. XV, No. 2 ISSN 1064-1505 No Charge AdaIC Sponsored by the Ada Joint Program Office and operated by IIT Research Institute +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ \\In This Issue&& URL -- http://sw-eng.falls-church.va.us/ * Paige Memo Gives Guidance -- Transitioning to engineering-review process, p. 2 * Ada 95 Java demo -- distributed processing on the Web, p. 4 * Guide to the COE -- plug and play for the warfighter, p. 6 * Usage and reader surveys -- Let us know what you're doing and what you think! pp. 11 & 12 \\Ada 95: More Platforms, More Vendors, More Choices, and More on the Way&& \\14 Vendors, 87 Compilers on Major Systems&& When the Ada Joint Program Office (AJPO) first considered the transition to Ada 95, it concluded that it was vital for the most widely used platforms to get validated support as early as possible. To a significant extent, that was accomplished last year. By the spring of 1996, five vendors had validated 14 compilers -- covering the Patriot missile system, and major platforms from Digital Equipment Corp., Silicon Graphics, Inc., Hewlett-Packard, Windows NT and 95, and the IBM RS/6000. Since then, those five vendors and 9 others coming on board have been working to spread the range of hosts and targets, and to increase the choices available for important platforms. By the summer of 1997, the number of vendors had grown to 14, and they were offering 87 validated compilers. The vendors are listed in Table 1; as you can see in Figure 1, much of the increase reflects a greater range of options in popular host platform families, with 18 compilers for PC/80x86 platforms and 34 for Sun platforms. Additionally, there is now a validated compiler hosted on the Macintosh. Coverage has also increased for targets (Table 2): supported platforms now include Motorola MVME chips, Lockheed Martin RAD 6000, Siemens Nixdorf RM 200 processors, and a number of simulators. <> Strictly speaking, compiler validation is necessary only for producing the executable code that will be fielded in a DOD project. For those of you doing work on your own, or preliminary work prior to producing fielded code, there's always been the freely available GNU Ada 95 Translator (the GNAT compiler) and it has been ported to several platforms. (See Table 3 for list of GNAT's known ports.) Also, the Public Ada Library includes the AVLAda9X Ada 95 compiler for MS-DOS. The Ada Information Clearinghouse -- 800/232-4211 -- can give you information on obtaining these compilers. <

> On which platforms are compilers hosted? DEC 8 IBM 4 Macintosh 1 Motorola 1 PowerMaxion 2 Siemens Nixdorf 1 SGI 7 Sun 34 <> Who's offering compilers? Vendor # of compilers Ada Core Technologies (ACT) 6 ACT/Digital Equipment Corp. 1 ACT/On-Line Applications 1 ACT/Siemens Nixdorf 1 ACT/Silicon Graphics, Inc. 5 ACT/Tenon Intersystems 1 Aonix (Thomson) 12 Concurrent 2 Green Hills 17 Intermetrics 5 Irvine 10 OC Systems 2 R.R. Software 6 Rational 18 <
> For which platforms are compilers targeted? DEC 6 HP 10 Heurikon 6 IBM 4 LockMar RAD6000 2 Macintosh 1 Motorola 14 PC/80x86 15 PowerMaxion 2 PowerStack 1 Raytheon EWCC 1 SGI 7 Siemens Nixdorf 1 Simulators 4 Sun 14 <
> Where has the GNU Ada 95 Translator (GNAT) compiler been ported? NOTE: Not all are validated Alpha Digital Unix 4.x Alpha OpenVMS 7.x Alpha Windows NT HP HPUX 10.x SGI IRIX SNI Sinix Sparc Solaris Sparc SunOS 4.1.x PowerPC AIX 4.x PowerPC MachTen 80x86 Linux 80x86 Windows 95 80x86 Windows NT 80x86 IBM OS/2 80x86 DOS 80x86 Solaris 2.5.1 80x86 SCO UNIX 80x86 FreeBSD 80x86 NetBSD 80x86 Nextstep DECstation Ultrix m68k Nextstep m68k SunOS m68k MachTen m68k Amiga DOS {cross compiler (bare machine) targets:} ERC32 Sparc V7 / RTEMS PowerPC / RTEMS 1750a i960 VxWorks m68k VxWorks \\70 Organizations Offering 100 Tools&& Searching for an Ada binding? Or perhaps an Ada 95 development environment that will run under Windows 95? The Ada Information Clearinghouse (AdaIC) Products and Tools database is a good place to begin your search. The AdaIC has maintained an on-line catalog of Ada products and tools on the AdaIC Internet site for several years. This database can be accessed through the World Wide Web at http://archive.adaic.com/tools. <<80% more than last year>> There are currently over 100 tools, compilers, and bindings listed for Ada 95 in the AdaIC's Products and Tools database. This represents an 80% increase over the past year, providing further evidence of the growth of the Ada 95 market. These tools were developed by over 70 companies, organizations, and universities located in the United States and abroad. Items listed in the database include products and tools used throughout a typical Ada development lifecycle. They are grouped in three main categories: implementation tools -- which include development environments, metric analyzers, bindings, and code translators; analysis and design tools -- which include database modeling, design analysis, and requirement tracing; and maintenance-support tools -- which include configuration-management and maintenance-analysis tools. You can conduct a specialized search for the various products and tools through any of these categories. A search can also be conducted by vendor name or product name. In addition, the database entries will link you to vendor Web sites and to more detailed product descriptions when available. <> Table 1 provides a breakdown by category of the number of products and tools currently listed in the AdaIC's Products and Tools Database. As you can see from the Table, the database lists a large number of development environments (which include editor, debuggers, compilers); bindings and repositories are also well represented. Many tools have more than one application since developers have created products that include several tools in one package. Several of the tools listed in the database can be downloaded through the AdaIC. Among these tools are Ada 95 bindings for POSIX, OS/2 API, DCE, and Win32, and development-environment tools such as the Ada Compiler Evaluation System (ACES) and WebAda. <> If you are searching for a particular product or tool and you cannot locate it in the AdaIC's Products and Tools database, please contact the AdaIC and we will try to find out if it exists in the marketplace or if one is under development. You can list your company's product or tool in the AdaIC's Products and Tools database by filling out a submission form -- found on the AdaIC Web site at http://archive.adaic.com/docs/flyers/forms/tool_entry_form.shtml or send e-mail detailing the product along with your company's point-of-contact, phone number, fax, e-mail, and address to: adainfo@sw-eng.falls-church.va.us. <
> What kind of tools are available? Tool Category # of Ada 95 tools Development environments 43 Bindings 28 Interface/graphics/animation builders 14 Source-code translators 13 Libraries/repositories 11 Metric-analyzer tools 7 Documentation generators 7 Design-analysis tools 7 Cross-compilation/development tools 7 Reverse-engineering tools 6 Project-management tools 4 Simulation testing tools 3 Data-conversion/file-translation tools 1 DBMS tools 1 \\Memorandum Gives Guidance&& <> ASSISTANT SECRETARY OF DEFENSE 6000 DEFENSE PENTAGON WASHINGTON, DC 20301-6000 COMMAND, CONTROL, COMMUNICATIONS, AND INTELLIGENCE April 29, 1997 Memorandum for Secretaries of the Military Departments Chairman of the Joint Chiefs of Staff Under Secretaries of Defense Director, Defense Research and Engineering Assistant Secretaries of Defense Inspector General of the Department of Defense Assistants to the Secretary of Defense Director, Administration and Management Director, Operational Test and Evaluation Directors of the Defense Agencies Directors of the DOD Field Activities SUBJECT: Use of the Ada Programming Language Last year, I asked the National Academy of Sciences' National Research Council Computer Science and Telecommunications Board to study the Department of Defense (DOD) software policies. After carefully reviewing and considering the Board's final report, I have directed my staff to undertake the necessary actions to revise the policy contained in DOD Directive 3405.1, "Computer Programming Language Policy," to eliminate the mandatory requirement for use of the Ada programming language in favor of an engineering approach to selection of the language to be used. Additionally, DOD 5000.2-R, "Mandatory Procedures for Major Defense Acquisition Programs (MDAPs) and Major Automated Information System (MAIS) Acquisition Programs," will be revised consistent with those changes. In the interim, pending formal coordination of the necessary revisions, programming language selections should be made in the context of the system and software engineering factors that influence overall life-cycle costs, risks, and potential for interoperability. As appropriate, these selections may be reviewed during milestone/system approval processes. Among the factors that should be considered and appropriately documented in the decision process are: * system/software requirements, including performance, interoperability, reliability, safety, and security requirements; * system/software architecture, including partitioning into components; * extent of compliance with/incorporation of other related direction (e.g., use of standards such as the Joint Technical Architecture, open systems, and commercial-off-the-shelf software) and the impact thereof; * selection of software development and support methodologies and processes; * use of software development and support tools and generators; * long-term maintenance implications, including evolvability and supportability; and * integration of software issues and decisions with other planning considerations to include cost, schedule, acquisition strategy and staffing. Ada should be one of the languages considered in this decision process; however, Ada waiver requests are no longer required when another language is selected. My point of contact for this action is Ms. Linda Brown, who is assigned to my Deputy Assistant Secretary of Defense for Command, Control and Communications, (703) 604-1590, e-mail: Linda.Brown@osd.pentagon.mil, or Mr. Samuel Worthington, (703) 604-1584. /s/ Emmett Paige, Jr. \\Letter from the AJPO&& <> I continue to applaud Mr. Paige's bold decision to end the Ada Mandate and implement the remaining recommendations of the National Research Council (NRC) report. If you have not yet read the NRC report, I would urge you to do so. You can link to an on-line version via the AdaIC Web page (http://archive.adaic.com/docs/present/nrc/). <> The NRC's solid explanation of and support for Ada's reliability and suitability for warfighting software must not be ignored. Ada should be used where it makes engineering sense. In military applications, reliability makes engineering sense. For military systems with twenty-year-plus lifecycles, a maintainable language is essential. Ada will prevail where engineering factors are part of the decision process. <> Make no mistake, war is about killing people and breaking things. Military weapons systems are designed to be lethal and must be reliably controlled. Unreliable military software is frightening. We often hear of Ada's strong typing. An implicit type conversion that results in a 1 degree rounding error will, at a range of 40 kilometers, put ordnance 700 meters off target. In a close combat situation, a 700-meter error can result in friendly casualties. Reliability is important. I don't want to have to tell a Gold Star Mother that her son or daughter was killed by friendly fire due to a software error. The fact that this software was procured using "best commercial practices" and was determined to be "good enough" for military use is likely to be of small comfort. Military software is a life-or-death proposition. People who don't understand this should not be in the business. I would stress that during my tenure at the AJPO I have never received any engineering-based complaint about Ada. The solid work done by the Ada vendor community has done an effective job of silencing critics who have complained about Ada compilers. One objection that is often parroted is the complaint about "lack of tools." I have been unable to get the complainants to state exactly what "tools" are lacking. The Ada Resource Association has also aggressively sought to find out. The reality is that high-level languages require fewer tools than low-level languages. Another complaint is that there are "no Ada programmers." It is well known that there is currently a serious shortage of skilled software personnel. Any hard-skill computer scientist can pick up Ada very quickly. <> Contrary to many people's perception, Ada is a very easy language to learn. At Tri-Ada '97, hard data will be presented to demonstrate this. A controlled experiment conducted at the United States Military Academy shows that students can go further, faster in Ada than in Pascal, a language specifically designed for educational use. I would like to encourage everyone in the Ada community to attend Tri-Ada '97. Noted Ada author Norman Cohen has done an outstanding job putting together a very strong technical program. Given the policy changes this year, results from the educational community, and progress in industry, this year promises to be one of the most productive Tri-Ada's ever, covering each of Tri-Ada's three constituent groups: government, industry, and education. <> Our biggest challenge comes from the "magazine management crowd" who base what should be engineering decisions on what they read in popular computer trade journals. Unfortunately, some of these journals continue to publish wildly inaccurate information about Ada and the Ada Program. That being said, I would like to thank the reporters who have taken the time to contact the AJPO to check facts or ask questions. As a former journalist myself and a currently active researcher, I have great respect for journalists who take the time to go to primary sources for their information, and I thank them for their trouble. I also appreciate the many members of the Ada community who have brought these erroneous articles to my attention and have taken it upon themselves to fight some of this misinformation that has grown into a mythology of its own. <> As of this writing, I am preparing to return to the faculty of the United States Military Academy. Once again, the future of the AJPO is in doubt. Decisions still have to be made regardingthe funding of the NRC recommendations for DOD support to the Ada infrastructure. In this respect, the Ada program is no different than most other Defense programs these days. Given current funding constraints, many critical programs are living a day-to-day existence. <> In my view, maintaining a consistent, fair, and stable compiler validation process remains one of our highest priorities. Another critical mission is U.S. representation on the various national and international standards bodies. I see these tasks continuing uninterrupted regardless of funding constraints. <> The Ada community is a great community, and the greatest aspect of this assignment has been interacting with the many selfless Ada volunteers. The government and contract personnel of the AJPO have made this a delightful assignment. I would particularly like to thank Rear Admiral John A. Gauss for his inspiring leadership, keen insights, and for the freedom and support he gave me while serving at the AJPO. <> Inside the Beltway, there is no stopping a catchy analogy. Ada is often compared to Betamax VCRs. The analogy being that there is no question of the technical superiority of the Beta format over VHS, yet Beta format VCRs failed to capture the consumer market. Like many analogies, this does not go far enough. In fact, Beta format VCRs continue to be used by video professionals specifically because of the technical superiority of the Beta format. Just because Blockbuster doesn't stock Beta format videotapes doesn't impact on the engineering decisions made by video professionals. Military software is not the same as consumer software. You cannot buy "off-the-shelf" fire-control systems. Ada was designed to build software to military specifications. Where reliability counts and where software engineering considerations factor into project management, Ada will continue to thrive. John A. Hamilton, Jr. Lieutenant Colonel, U.S. Army Chief, Ada Joint Program Office \\Ada 95 Demo Combines Java Bytecode and Distributed Processing on the Web&& To support the warfighter, the Department of Defense (DOD) must move increasingly into systems of communications, data processing, and personal interaction that are seamlessly integrated in real time across great distances and across disparate hardware and software systems. The Defense Information Infrastructure Common Operating Environment (DII COE) is intended to provide a framework for that integration. In the general marketplace, the World Wide Web has shown the resources that can be accessed over the Internet; Sun's Java programming language is designed to permit the Web's processing power to grow even faster. Java bytecode runs on the huge number of enduser platforms, not the limited number of Web hosts. Looking, then, at the variety of needs and technologies, the Ada 95 programming language is uniquely positioned to meet those needs and to maximize use of those technologies. Ada 95's Annex E provides the mechanism for distributed processing. Java's semantic similarity to Ada made it straightforward to develop a compiler that produces bytecode indistinguishable from that provided by Java. (See {AdaIC News}, Winter 1996-1997. "Ada Java Compiler Released", which describes the Appletmagic compiler developed by Intermetrics, Inc.) One natural combination, therefore, is endusers/clients running Java bytecode generated from Ada 95 source code, and a host/distributed server using Ada 95's Annex E distribution mechanism internally. Both these technologies have been discussed within the DII community. Until recently, though, neither had been demonstrated in live software, nor had the two been combined in a single client/server demonstration. To meet this need, the Ada Joint Program Office (AJPO) sponsored a successful demonstration project -- the GCCS Ada 95 Client Demo Applet. Developed by CACI, Inc., it is now available on the Web. You can link to it via http://archive.adaic.com/. The prototype client/server pair demonstrates the use of two new technologies within a context similar to that of the DII COE. For a bare-bones example, developers chose the sort of application that might be built on top of the DII Global Command and Control System/Global Combat Support System COE (DII GCCS/GCSS COE). For this demo's prototype client/server pair, they chose to simulate a hypothetica command, control, communications, computers, and intelligence (C4I) application. The prototype has been successfully demonstrated on Sun Sparcstation server hardware with no COE present, and on PC (Windows 95 and NT), Macintosh, and Sun client hardware. At CACI, the server ran on three Sun Workstations as a single distributed Ada 95 program. The client software was written in Ada 95 and compiled with the Intermetrics AppletMagic(tm) compiler. The generated Java bytecode runs on any Java Virtual Machine (JVM) -- for example, a Java-enabled Web browser such as Netscape 3.x, the Microsoft Internet Explorer 3.x, or a JVM Applet Viewer. Suitable hardware could be a Sun, a Macintosh, a PC running Windows NT 4.0, or a PC running Windows 95). <> The client/server pair provides basic functionality in simulating simplified information on enemy troop locations and troop types with which a commander might be presented during a battle. This information is gathered from three "sensors" (implemented as simple software simulations) in near real-time and displayed as standard military icons on a simulated texture map. The system allows multiple clients to connect to the server simultaneously. All clients observe the same battlefield. Each receives the same set of sensor observations, so all client displays will be identical. The client software initially displays a login screen. Once the user presses the login button, the client connects to the server and begins the download and display of the data. The client software displays an icon representing each observed enemy on a pseudo-map. The icons are color coded to correspond with each sensor (ground => blue, air => red, satellite => yellow). Each type of unit is represented by the standard military icons. As each "sensor" observes the units, the new data is sent to the client. The client applet then continuously updates the display with the new data. Once the user selects "quit" from the menu or closes the map window, the client disconnects from the server. The user is then presented with the login screen again. <> The prototype has successfully shown some of the benefits of the JVM for the DII environment: * {Client neutrality:} The client software will run (without change) on Sun/Solaris, Macintosh/System 7.5.5, PC/Windows NT 4.0, and PC/Windows 95 environments. (Observed differences in client software behavior for identical .class files appear to be due to differences in JVM implementations. In this respect, the behavior of the Ada 95 client is no different than a Java client -- it runs identically on different machines within the known differences/bugs present on those JVM implementations.) * {No physical distribution and/or installation of client software:} The demonstration application will run on any machine preconfigured with a Java-enabled Web browser. There is no need to supply users with a disk containing client software; and, therefore, no user-run installation of client software. It has also shown a strong advantage of the Ada 95 Annex E distributed-programming approach: * {Scalability:} The server software is able to be configured and run on anywhere from 1 to 5 Sun systems. Repartitioning the distributed server system does not require any changes to the software. It requires only a simple edit of the .cfg file and re-running of the partitioning tool. Of course, the ability to distribute the server over multiple machines affords corresponding performance gains with no Ada 95 source-code modifications. (Instant update of clients is one other benefit of Java bytecode and the Ada 95 Distributed Annex, but is not currently demonstrated at this time: If the demonstration application is updated from v1.0 to v.1.1, then all clients automatically run the latest version the next time they launch their Web browser.) <> All new software written for the prototype was written in Ada 95. The server software was compiled with the GNU Ada Translator (GNAT v3.09) from Ada Core Technologies and the GNAT implementation of the Distributed Systems Annex (GLADE 1.01) for Sun Sparc running Solaris 2.5. The client software was compiled using Intermetrics AppletMagic compiler v1.38 for Macintosh. The client software makes extensive use of the standard Java toolkits and libraries via the Ada 95 bindings supplied with AppletMagic. Once the sensor server has been launched, one or more clients may connect to it. Both the HTML server (providing the Web page and the downloadable Java-bytecode client applet) and the Sensor Server application must be hosted on the same machine. This is due to a "limitation" of the security software that is part of the Java Virtual Machine. A Web-based applet (client) is allowed to open up a network connection only to the same host machine from which the applet was downloaded (that is, the HTML server). <> The technical success of this prototype opens up the possibility for further investigation of the areas in which these technologies may be applied. It demonstrates Ada 95's ability to provide these benefits to the DII. \\{AdaIC News} to go electronic-only&& This, the Fall issue, is the next-to-the-last issue of the {AdaIC News} that will be published and mailed to subscribers in hardcopy form. Beginning in 1998, the {AdaIC News} will be available only on the Internet and World Wide Web, with summaries available through electronic mail. <> {On the Web:} The current and past issues of the newsletter are available on the Ada Information Clearinghouse's Web site at http://archive.adaic.com/news/Newsletter/ {Via e-mail:} The AdaIC is establishing a separate e-mail list for those wishing to receive a summary of the AdaIC automatically each quarter. To subscribe, send an e-mail message to listproc@sw-eng.falls-church.va.us with subscribe adaicnews as the body of the text. (No signatures please.) {Dial-up:} For those with a modem but not Internet or Web access, the AdaIC Web site can also be reached by direct dial-up. The telephone number is 703/681-2845. Contact the AdaIC for access instructions. <> {This} issue will be the last hardcopy version mailed to readers outside the United States. The upcoming (Winter 1997-1998) issue will be the last one sent to U.S. readers, and is scheduled to be mailed around the turn of the year. {If you have any questions, please feel free to contact the AdaIC.} Ada Information Clearinghouse P.O. Box 1866 Falls Church, VA 22041 tel: 703/681-2466; 800/232-4211 fax: 703/681-2869 Web: http://archive.adaic.com e-mail: adainfo@sw-eng.falls-church.va.us \\AJPO Summer Intern&& The Ada Joint Program Office welcomed a summer intern, Cadet Stephen Hamilton, a Computer Science major from the U.S. Military Academy. While at the AJPO, he significantly increased the AJPO's multimedia technical presentation capabilities. He also increased the AJPO's understanding of the impact of supporting the teaching of Ada at West Point. Cadet Hamilton, like all cadets at West Point and the Air Force Academy, has received AJPO-supported Ada instruction. He is a strong supporter of Ada -- and his own performance shows its benefits. \\Plug and Play for the Warfighter&& The Defense Information Infrastructure Common Operating Environment (DII COE) provides a foundation for building open systems. It is a "plug and play" open architecture designed around a client/server model. The DII COE model is analogous to the Microsoft Windowsr paradigm. It provides a standard environment, a set of standard off-the-shelf components, and a set of programming standards that describe how to add new functionality to the environment. The DII COE is designed to run on PCs and workstations; it extends the Windows paradigm, which allows applications to coexist, by providing the capability for mission applications to share data and services/functions at the server level. Thus, the DII COE allows for true integration of open systems. This article provides an introduction to the DII COE. It includes background on the COE; information on currently available versions of the COE; and instructions for ordering a copy; as well as pointers to the wealth of resources available to software developers who are interested in using the COE. <> The DII COE concept originated in the early to mid 1990s with a simple observation about the Department of Defense's (DOD's) command and control (C2) systems: Certain functions (mapping, track management, communications interfaces, etc.) are so fundamental that they are required for virtually every C2 systems. In "old" DOD software development environments, developers were building these common functions from scratch for every system. Each developer implemented the functions differently, which led to incompatibility between the systems. Thus, while most of the production systems used by the DOD had similar functions, they could not easily interoperate with each other. Also, the DOD was investing a great deal of time and money in rebuilding the same functions. In planning for building the replacement for one of the most critical C2 systems, the World-Wide Military Command and Control System (WWMCCS), the DOD evaluated several architectures with the goal of selecting a system architecture that would be able to easily take advantage of emerging commercial products and standards. The Global Command and Control System (GCCS), which has replaced the WWMCCS, is built upon an open architecture that both meets the DOD's unique functional needs (the GCCS systems architecture) and provides for interoperabilty with other systems (the GCCS COE technical architecture). The open/technical architecture developed for GCCS provided the baseline for the DII COE. Longer term development of the COE is being managed by the Defense Information Systems Agency's Joint Interoperability and Engineering Organization (DISA/JIEO); development is being driven by the requirements of major efforts such as: GCCS; Command, Control, Computers, Communications and Intelligence (C4I) for the Warrior; logistics support systems for the DOD's Global Combat Support System (GCSS), and financial support systems for electronic commerce/electronic data interchange (EC/EDI). <> The DII COE concept encompasses the following: * an architecture and approach for building interoperable systems; * an infrastructure for supporting mission area applications; * a rigorous definition of the runtime execution environment; * a rigorous set of requirements for achieving COE compliance; * an automated toolset for enforcing COE principles and measuring COE compliance; * an automated process for software integration; * a collection of implemented, reusable software components; * an approach and methodology for software reuse; * a collection of application program interfaces (APIs) for accessing COE components. Figure 1 on the previous page provides a view of the DII COE and the relationship to COE-based systems. The shaded box illustrates the two types of reusable software that the applications may access through APIs: COE components and the operating system. <> The DII COE is being designed to be hardware independent; it will operate on a range of operating systems running under standards-based systems. DISA is developing DII COE implementations based on user requirements. Currently, DISA has developed versions of the COE for Windows NT 3.5.1 and 4.0, and for a variety of flavors of Unix, including Solaris and HP. Also, beta versions are available for IBM AIX and Digital Unix. To obtain your copy of the COE, see the sidebar at the right. <> The DII COE listserv provides a moderated forum for COE developers. Messages are sent and received through the user's ordinary e-mail service. For those who do not wish to subscribe to the listserv, messages may be viewed through an organized archive on the CSEIC Web site at: http://sw-eng.falls-church.va.us/cseic/listserv/maillist.html To subscribe to the DII COE Listserv, send a message to: listproc@sw-eng.falls-church.va.us In the body of the message, write: subscribe diicoe \\Saving money, code, with the COE&& Software developers are proving that cost savings can be achieved by using the COE. Col David L. Chadwick, Commander, Marine Corps Tactical Systems Support Activity (MCTSSA) returned $5 million to the General Fund after completing a successful reengineering project. In this case, the activity reengineered and segmented three legacy systems (6-22 years old) that had a total of 200,000 source lines of C/C++ code. The reengineering process of the systems involved three major steps: 1) stripping out any COE-redundant configuration items; 2) parsing remaining code into segments; and 3) converting all relational database management system calls to SQL calls. (MCTSSA's success has already been covered in the general press; see {Government Computer News}, vol. 15, no. 11, 5/27/96.) \\DOD Policy/Guidance for COE Usage&& All of the DOD's emerging C4I systems and system upgrades will be segmented for the DII COE, according to an August 22, 1996, DOD policy memo issued by Paul G. Kaminski, Under Secretary of Defense (Acquisition and Technology (USD (A&T)), and Emmett Paige, Jr., Assistant Secretary of Defense (Command, Control, Communications and Intelligence) (ASD (C3I)). This memorandum mandates the use of the DOD's Joint Technical Architecture (JTA), which references the DII COE as, "the specific COE implementation that will continue to evolve in compliance with all applicable JTA specifications, standards, and source references." The JTA, which is being coordinated by DISA, identifies a common set of mandatory information technology standards and guidelines to be used in all C4I systems and the interfaces of C4I systems with other key assets. (Note: The DII COE is a specific implementation of the COE technical architecture specified by the JTA.) \\Online with COE&& <> DISA has developed a wealth of technical documentation and information about the COE. The Computer Systems Engineering Information Clearinghouse (CSEIC) has organized DII COE information and provides a full-text-search tool for general COE documentation on its DII COE home page (http://sw-eng.falls-church.va.us/coe/docs/). General COE documentation is also available in HTML, PDF, and MS Word format. DISA has also established a hotline (1-800/738-7379) where users and prospective users can get general as well as technical information. <> Software developers may request a copy of the DII COE by sending electronic mail to the appropriate sponsor: * {Army:} chslib@doim6.monmouth.army.mil * {Navy/USMC:} navy_coe@smtp-gw.spawar.navy.mil * {Air Force:} sullivang@hanscom.af.mil * {DISA/Other:} Complete the form found on the World Wide Web at: http://164.117.48.247/Tango/tango.acgi$/CMDBTango/POCSearch.qry?function=form This can also be found under configuration management on DISA's COE Web site: http://spider.osfl.disa.mil/dii/ * {GCSS Developers:} gcssdctf@slidell.disa.mil * {Intel:} hardgetl@emh-497ig.bolling.af.mil \\Tri-Ada '97 to Emphasize Ada Diversity, Present Expert Speakers&& The 12th Annual Tri-Ada Conference will be held November 9-13, 1997 at the Adam's Mark Hotel in Saint Louis, Mo. Hosted by the Association of Computing Machinery's Special Interest Group on Ada (ACM SIGAda), Tri-Ada is a major forum for bringing together professionals in the fields of software engineering, object technology, software quality, reuse, testing, education and training, and acquisition. The theme for this year's conference is "Cost-Effective, Quality Software Systems: Preparing for the Next Century". Tri-Ada '97 will be a week of technical papers, keynote presentations, experience reports, workshops, interactive panels, exhibits, posters, demonstrations, educational symposia, birds-of-a-feather sessions, along with an exceptional tutorial program and opportunities to mingle. This year's conference will emphasize the diversity of Ada applications and support throughout government, industry, and academic domains, nationally and internationally. A wide range of panels and tutorials are scheduled for Tri-Ada '97. Among the panels will be future directions for Ada bindings and related standards; AdaSAGE and software reuse; Ada and Java; and the future of programming languages in the next century. Tutorials range from CORBA, to Java for Ada 95 programmers, to Ada 95 object-oriented programming guidelines, among others. Tri-Ada '97 will also present some of the leading experts in software engineering. Scheduled speakers include former Assistant Secretary of Defense for C3I, Emmett Paige, Jr.; John B. Goodenough, Chief Technical Officer of the Software Engineering Institute; Edward F. Miller of Software Research, Inc.; and two former AJPO Chiefs, LTC John A. Hamilton and Charles B. Engle. In addition to their tradition of refereed papers, panel sessions, and excellent tutorials, Tri-Ada '97 is seeking to expand conference activities to include tracks for government attendees, and sessions for the less experienced programmers. Once again, Tri-Ada will serve as the largest Ada exhibition in the world. Over 100 companies will be demonstrating their latest tools and compilers for Ada 95. At Tri-Ada '96 in Philadelphia, over 600 attendees attended technical sessions, visited exhibits, and exchanged idea with other Ada professionals from around the world. For most up to date information about Tri-Ada '97, visit the Tri-Ada '97 Web site at http://www.acm.org/sigada/Tri-Ada/ta97.htm or call 1-800/338-5365. \\WAdaS '97 Plans for Future&& The 14th Annual Washington Ada Symposium (WAdaS '97) was held June 23-26 at the McLean Hilton in McLean, Va. The conference, sponsored by the Washington, D.C. chapter of SIGAda, was highlighted by speeches by LTC John A. Hamilton, Jr., USA, Chief of the Ada Joint Program Office (AJPO); former AJPO Chief Dr. Charles B. Engle; Ada 95 designer S. Tucker Taft; and GNU Ada 95 Translator (GNAT) expert Robert Dewar. WAdaS '97 provided two days of tutorials and workshops followed by the two-day conference. In addition, ACM SIGAda held their day long Long-Range Planning Meeting in conjunction with the conference. The final two days of WAdaS were devoted to speeches and conference sessions. LTC Hamilton's keynote address provided the audience with an up-to-the-minute status on Ada and the future of the AJPO. Dr. Engle's speech gave attendees a view from the outside on Ada and the Ada community. Mr. Taft discussed the business and technical case for building critical systems in Ada 95; and Dr. Dewar gave his views on the Ada compiler industry and the future of Ada. In addition to the daily speeches, sessions were held on the following topics: Ada 95 Early Adopters, Ada 95 and Java, Ada and Education, ASIS, Ada Common Environment, and Ada 95 and Distributed Systems. Also held during the conference portion of WAdaS was a mini-exhibition. Several Ada vendors set up exhibit booths and displayed their latest products. This year's exhibitors included the AdaIC, SIGAda, Rational Software, Inc., AAI Corporation, Ada Core Technologies, Objective Interface Systems, Green Hills Software, OC Systems, Mark V Systems, Aonix, DDC-I, Lockheed Martin Idaho Technologies Company, and NASA Goddard Flight Dynamics Division. If you would like to obtain a copy of the proceedings from WAdaS '97, contact the Ada Information Clearinghouse at 1-800-232-4211 or e-mail to: adainfo@sw-eng.falls-church.va.us. \\Software Engineering Calendar&& Call the AdaIC for further information on these conferences, seminars, and work-shops, or check out the Web page at http://archive.adaic.com. And let us know if your organization is sponsoring an event! (Report of a product, service, or event is for information purposes only and does not constitute an endorsement by the Ada Information Clearinghouse or the Ada Joint Program Office.) <> November 2-5 San Francisco, CA 714/778-3230 <> November 2-5 Monterey, CA 408/756-6196 <> 12th IEEE International Conference; Formerly the Knowledge-Based Software Engineering Conference [KBSE] November 3-5 Hyatt Regency Lake Tahoe; Incline Village, NV 402/472-8394 <> November 9-13 Adam's Mark Hotel; Saint Louis, MO 919/419-8242, ext. 15 <> Co-operation and Business opportunities for Eastern/Western European Countries in the IT field. Practical Improvement of Software Processes and Products November 10-12 Hotel Flamenco; Budapest, Hungary +353 1 286 1583 <> November 16-21 San Jose, CA 510/294-2628 <> November 17 San Jose Convention Center; San Jose, CA 603/646-2417; 847/467-4129 <> December 1-3 Research Triangle Park, NC e-mail: mark@cs.clemson.edu; conte@eos.ncsu.edu; alexe@eos.ncsu.edu <> December 2-5 Hong Kong e-mail: apsec@comp.hkbu.edu.hk <<22nd Annual Software Engineering Workshop>> December 3-4 Goddard Space Flight Center; Greenbelt, MD 301/286-6347 <> December 8-9 Radisson Plaza Hotel; Alexandria, VA 703/768-0400 <> December 18-21 Bangalore, India fax: 213/740-4418; e-mail: balki@serc.iisc.ernet.in <> January 19-23 908/582-7691 <> February 27-March 1 Atlanta, GA 405/744-5221 <> March 1-5 412/624-6094 <> March 5 Clearwater Beach, FL 630/979-0042 <> March 9-12 Hyatt Regency Hotel; Chicago, IL 412/268-3007 <> March 24-26 Washington Convention Center; Washington, DC 800/791-3673 <> on Research in Computational Molecular Biology March 28-April 1 212/241-5777 <> March 30-April 3 The Maaleh Hachamisha Kibbutz Hotel; Jerusalem, Israel +972-2-6520574 <> April 6-10 Colorado Springs, CO <> April 19-24 http://www.stsc.hill.af.mil/stc/ <> April 19-25 Kyoto, Japan +81-6-850-6570,6571 <> April 1-5 University of Geneva; Geneva, Switzerland http://www.ippsxx.org/ipps97/index.html <<5th International Conference on Software Reuse>> June 2-5 Victoria, British Columbia, Canada E-mail: edwards@vtops.cs.vt.edu <> June 7-9 612/625-7338 <> June 15-19 804/982-2200 <> October 18-22 604/361-2695 *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. \\Ada usage survey form&& Please mail or fax to: Ada Information Clearinghouse P.O. Box 1866 Falls Church, VA 22041 Fax: 703/681-2869 You can help us keep our information resources up to date by filling out this form and mailing it or faxing it to the AdaIC. Please complete and mail back to the Ada Information Clearinghouse. Date of Survey: The Project: Acronym: Project Name: Project URL: Project Description: Developing Organization: Name: URL: Address: City, State, Zip: Point of Contact: Code/Building: Phone Number: Fax Number: E-Mail: Sponsoring Organization: Name: URL: Address: City, State, Zip: Contract Number (if applicable): Point of Contact: Code/Building: Phone Number: Fax Number: E-Mail: Project background: ___ No previous system existed ___ Old system existed in different language ___ Modification/upgrade of existing system Software system to be used within: (check one) ___ Army ___ Navy ___ Marine Corps ___ Air Force ___ Coast Guard ___ Other DOD ___ Non-DOD Government ___ Commercial ___ Academia ___ Outside U.S. Software Functions: (check all that apply) ___ Automated Test Equipment ___ Avionics ___ Command and Control ___ Communications/Telecommunications ___ Financial ___ Intelligence ___ Logistics System ___ Management Information System ___ Process Control ___ Robotics ___ Scientif Data Processing ___ Simulation ___ Systems Software ___ Training ___ Weapons System Your affiliation to the project: (check the one most applicable) ___ Manager ___ Developer ___ End-User Lessons Learned/Comments: System Technologies: (check all that apply) ___ Artificial Intelligence ___ Batch Processing ___ Client/Server ___ Database ___ Expert System ___ Graphics/Animation/Image Processing ___ High Reliability/Dependability ___ Interactive Processing ___ Multi-Media ___ Neural Network ___ Real-Time ___ Security ___ Other: Host System Hardware Architecture: ___ Mainframes ___ Minicomputers ___ Workstations ___ Microcomputers Operating Systems and Environments: Target System Hardware Architecture: ___ Mainframes ___ Minicomputers ___ Workstations ___ Microcomputers Operating Systems and Environments: Compiler used: Tool(s) used: Definition of SLOC (Source Lines of Code): ___ Non-commented, non-blank lines ___ All lines (includes commented lines) ___ Terminal semicolons ___ Other: Total number of SLOC Completed: Predicted: Breakdown of developing languages (Total = 100%) Ada: Other languages: Breakdown of software source (Total = 100%) Externally developed commercial packages (COTS): Externally developed government packages (GOTS): Internally developed new packages: Internally developed reusable packages: Division of project labor # of people Average years experience Project Manager/Task Leader System Engineer/System Analyst Software Designer/Data Analyst Programmer/Test Engineer Q&A Personnel/Configuration Management Personnel Estimated program costs To Date: $____________ Overall: $ Software Development Expenditure (Total = 100%) In-house development: In-house maintenance: Outsource/Contract development: Outsource/Contract maintenance: Project Lifecycle Status: (check one) ___ Requirement ___ Design ___ Code/Test ___ Integration/Test ___ Final Delivery/Maintenance Development Approach: (check one) ___ Classic Method/"Waterfall" Model ___ Spiral Method/"Fountain" Model Milestones: (include date and description) Project Start: System Design: Implementation Complete: Build, Release, or Version Delivery: Project Complete: System Development Techniques: Analysis & Design Methods: System Development Standard: (check one) ___ DOD-STD-2167A ___ DOD-STD-2168 ___ DOD-STD-7935A ___ Mil-STD-499A ___ Mil-STD-498 ___ None ___ Other: Government Contract-Contractor CMM Maturity Level and Method ___ ISO 9000 certification The contractor CMM Maturity level (1-5) was: The CMM Maturity level was determined through: (check one) ___ Formal internal assessment ___ Independent external assessment ___ Government Software Capability Evaluation ___ Other: If old system exists, describe transitional method to new system: (check one) ___ switch to new system and terminate old system simultaneously ___ begin operating the new system one module at a time ___ run old system and new system simultaneously until all the bugs are corrected from new system Will your organization be developing more Ada projects in the future? ___ Yes ___ No ___ Unknown If reused software was utilized, how has it affected the development schedule? ___ Lengthened ___ Shortened ___ No Effect \\Reader survey&& Tell us what you think! 1. In general, the AdaIC News is? ___ very valuable ___ valuable ___ somewhat valuable ___ not valuable ___ negative ___ no opinion 2. How many people other than yourself regularly read your copy of the AdaIC News? ___ none ___ 1-5 ___ 6-10 ___ 11+ 3. How many times have you passed along a copy or an article to others who don't regularly see the AdaIC News? ___ several times in the past year ___ occasionally ___ seldom ___ never 4. What do you think of the AdaIC News's size? ___ too short ___ about right ___ too long 5. And its coverage of topics? ___ under reports important areas, for example, _____________________________________ ___ over reports certain areas, for example, ________________________________________ ___ about right 6. Are there any other general comments you'd like to pass along? ___________________________________________________________________ ___________________________________________________________________ ___________________________________________________________________ 7. What would you like to see added to the newsletter or databases? ___________________________________________________________________ ___________________________________________________________________ ___________________________________________________________________ Mail to: Ada Information Clearinghouse P.O. Box 1866 Falls Church, VA 22041 This is a good time to check to see that your address is correct in our database! \\AdaIC News&& The Ada Information Clearinghouse (AdaIC) publishes information on the Ada community's events, working groups, research, publications, and concerns. The AdaIC provides its services free of charge to the governmental, academic, and commercial software communities. This service is sponsored by the Defense Information Systems Agency's Ada Joint Program Office (DOD/DISA/JIEO/CFCSE/AJPO), which facilitates the implementation of the DOD's software initiative (Ada) throughout the Services, and maintains the integrity of the language. IIT Research Institute operates the AdaIC at the AJPO offices in Falls Church, VA. Ada Information Clearinghouse P.O. Box 1866 Falls Church, VA 22041 Phone: 703/681-2466 1-800-AdaIC-11 (232-4211) DSN: 761-2466 Fax: 703/681-2869 adainfo@sw-eng.falls-church.va.us http://sw-eng.falls-church.va.us/ Ada Joint Program Office Defense Information Systems Agency Code JEXH 5600 Columbia Pike, Suite 364 Falls Church, VA 22041 Tel: 703/681-2466 DSN: 761-2466 The views, opinions, and findings contained in this report are those of the author(s) and should not be construed as an official Agency position, policy, or decision, unless so designated by other official documentation. Copyright 1997. IIT Research Institute. All rights assigned to the U.S. Government (Ada Joint Program Office). Permission to reprint this newsletter, in whole or in part, is granted, provided the Ada Information Clearinghouse is acknowledged as the source. If this newsletter is reprinted as part of a published document, please send the AdaIC a courtesy copy of the publication. The AdaIC is sponsored by the Ada Joint Program Office. AdaIC News Idaho National Engineering & Environmental Laboratory Lockheed Martin Idaho Technologies Company P.O. Box 1625 Idaho Falls, ID 83415-3779 OFFICIAL BUSINESS ADDRESS CORRECTION REQUESTED To change your address, please mail this panel with the updated information to the AdaIC at P.O. Box 1866, Falls Church, VA 22041 U.S.A. Or send e-mail to adainfo@sw-eng.falls-church.va.us