Abstract : This report describes the full scope of the Department of Defense (DoD) Radio Frequency Identification (RFID) activities with the purpose of identifying RFID-related issues specific to the Defense Logistics Agency (DLA). It summarizes DoD Components' status in implementing DoD RFID policy requirements, new DoD uses of active RFID, and progress in the use of passive RFID in the DoD supply chain. The report also addresses relevant standards and RFID training activities. There are several issues for DLA relating to the use of both active and passive RFID. These range from programmatic concerns regarding the need for a common RFID system architecture to practical concerns about the performance impact of reduced power levels. The report recommends actions that may allow potential benefits of emerging RFID technology to streamline DLA operations.

: This study reports on a programming language survey commissioned by the Assistant Secretary of Defense for C3I to determine how many programming languages are being used in the DoD today as compared to 20 years ago when the DoD began development of the Ada language. The sample population for this survey consisted of weapons systems taken from the 1994 Presidential Budget requests for RDT&E programs exceeding $15 million and Procurement budgets exceeding $25 million. The current DoD list of major Automated Information Systems was used as the survey sample for non-weapons systems. The survey found that over 80% of the applications in the sample were written in third generation languages. Moreover, it identified 37 third generation languages in contrast to an estimate of at least 450 general purpose languages and dialects in 1974. In weapons systems modernization, Ada is the most commonly used language.

: This paper reports on the examination of ten commercial tools identified for the static and dynamic analysis of Ada code. It provides software development managers with information that may help them gain an understanding of the types of tools that are commercially available, the functionality of these tools, and how they can aid the development of Ada software. During the course of the assessment, the tools were applied to a series of Ada programs in order to assess their functionality. Each tool was then described in terms of its functionality, ease of use, and documentation and support. Problems encountered during the examination and other pertinent observations were also recorded. Significant findings from this study include the following: (1) some of the examined tools could be brought into immediate use to improve the cost-effectiveness of testing for SDI software development efforts, (2) the coverage analyzers provide reporting data that can support the management of SDI testing efforts, and (3) many of the tools can be used in conjunction to overcome the limitations of particular tools.

: This paper provides a top-level description of an initiative designed to develop critically needed software testing capabilities prior to a Strategic Defense System (SDS) Milestone II decision. It identifies several SDI software testing requirements and examines the state of the art and practice in this field. Deficiencies were found between needed Strategic Defense System (SDS) capabilities and the expected available technology. Aspects of SDS software testing that should be addressed are described, including the ability to assure the correctness of SDS software, the types of software to be tested, and the ability to perform required testing within cost and schedule constraints. The document contains several detailed example project descriptions, and provides a brief overview of the software testing technology horizon.

: The purpose of IDA Paper P-2266 is to document the goals and proposed contents of a software test and evaluation (T and E) policy for the Strategic Defense Initiative Organization (SDIO). Such a policy would enable SDIO to obtain consistent results from software T and E, obtain the maximum benefit from available T and E technology, and provide support for a Full-Scale Development decision. In general, the software T and E policy will be the mechanism for defining the activities and responsibilities of the various T and E participants in achieving the necessary change in practices and attitudes to ensure effective T and E. Findings, conclusions, and recommendations are listed.