Software is the primary mechanism for deployment of DoD capability. Software challenges cut across the defense enterprise. An enterprise strategy is needed to align resources to meet growing challenges/threats.

关键词：电子信息；软件；防护；策略

查看摘要 索取原文[13页]

This research seeks to utilize a software defined radio for the detection and spatial identification of radio frequency identification tags. A software defined radio (SDR) is a hardware platform that provides the ability to broadcast and receive across multiple bands of the radio frequency (RF) spectrum, depending on the RF front end and software profile loaded on it. The focus of the research will be on the spatial identification (SID) of passive radio frequency identification tags (RFID). The research is applicable to many areas of day-to-day operations both within the DoD and industry. Flight line safety tracking of equipment and personnel, as well as perimeter defense, are two areas that may benefit from this technology. One dual-purpose, civilian and military, application would be the tracking and locating of inventory within a warehouse. The research developed and implemented a SID process, and proved its suitability to quickly identify and locate target tags within range. A profile of the system's capabilities and limitations in a laboratory environment was developed, including range, sensitivity, and accuracy.

关键词：电子信息；软件；无线电；空间技术

查看摘要 索取原文[136页]

Software-defined radios (SDRs) provide researchers with a powerful and flexible wireless communications experimentation platform. GNU Radio is the most popular open-source software toolkit for deploying SDRs, and is frequently used with the Universal Software Radio Peripheral (USRP). There is significant complexity involved in setting up GNU Radio with the USRP; therefore, in this report, we describe the key steps to take (and pitfalls to avoid) in order to successfully establish such an SDR testbed.

关键词：电子信息；软件；无线电；测试

查看摘要 索取原文[20页]

This final report contains the findings from the trustworthy composition of pre-designed software components project. Since DoD software is often developed at multiple vendor sites, individual components may be verified and delivered to an integrator--but the integration might fail because of behavioral incompatibility of the component interfaces. This work proposed behavioral types of interfaces by extracting the polychronous model from source code, and then using the theory of polychronous composition to check if the composition satisfied all of the requirements. The computation of composition properties (type inference) required novel development of a specialized Boolean theory for Prime Implicates, which provided a huge computational improvement through highly efficient generation of Prime Implicates.

关键词：电子信息；软件；嵌入式；预设计

查看摘要 索取原文[93页]

Adoption of commercial off-the-shelf (COTS) products in safety critical systems has been seen as a promising acquisition strategy to improve mission affordability and, yet, has come with significant barriers and challenges. Attempts to integrate COTS software components into NASA human rated flight systems have been, for the most part, complicated by verification and validation (V&V) requirements necessary for flight certification per NASA s own standards. For software that is from COTS sources, and, in general from 3rd party sources, either commercial, government, modified or open source, the expectation is that it meets the same certification criteria as those used for in-house and that it does so as if it were built in-house. The latter is a critical and hidden issue. This paper examines the longstanding barriers and challenges in the use of 3rd party software in safety critical systems and cover recent efforts to use COTS software in NASA s Multi-Purpose Crew Vehicle (MPCV) project. It identifies some core artifacts that without them, the use of COTS and 3rd party software is, for all practical purposes, a nonstarter for affordable and timely insertion into flight critical systems. The paper covers the first use in a flight critical system by NASA of COTS software that has prior FAA certification heritage, which was shown to meet the RTCA-DO-178B standard, and how this certification may, in some cases, be leveraged to allow the use of analysis in lieu of testing. Finally, the paper proposes the establishment of an open source forum for development of safety critical 3rd party software.

关键词：电子信息；软件；飞行系统；认证；安全系统

查看摘要 索取原文[14页]

Flight controllers in NASA s mission control centers work day and night to ensure that missions succeed and crews are safe. The IT goals of NASA mission control centers are similar to those of most businesses: to evolve IT infrastructure from basic to dynamic. This paper describes Mission Control Technologies (MCT), an application platform that is powering mission control today and is designed to meet the needs of future NASA control centers. MCT is an extensible platform that provides GUI components and a runtime environment. The platform enables NASA's IT goals through its use of lightweight interfaces and configurable components, which promote standardization and incorporate useful solution patterns. The MCT architecture positions mission control centers to reach the goal of dynamic IT, leading to lower cost of ownership, and treating software as a strategic investment.

关键词：电子信息；软件；应用程序；飞行控制软件

查看摘要 索取原文[9页]

Why APPs are important to the military: (1) Information is presented in a manner that users want to see, (2) Speed of building and deploying tool, and (3) Community comfort with development and use of APPs. To streamline its operations in a rapidly advancing world, the Army is creating an online APP marketplace in the hopes of empowering its soldiers and boosting efficiency.

关键词：电子信息；软件；国防部；应用商店

查看摘要 索取原文[11页]

Indiana University's SWIM activities have primarily been in three areas. All are completed, but we are continuing to work on two of them because refinements are useful to both DoE laboratories and the high performance computing community.

关键词：电子信息；软件；科学组件

查看摘要 索取原文[4页]

NASA has always been in the business of balancing new technologies and techniques to achieve human space travel objectives. NASA s historic Software Production Facility (SPF) was developed to serve complex avionics software solutions during an era dominated by mainframes, tape drives, and lower level programming languages. These systems have proven themselves resilient enough to serve the Shuttle Orbiter Avionics life cycle for decades. The SPF and its predecessor the Software Development Lab (SDL) at NASA s Johnson Space Center (JSC) hosted flight software (FSW) engineering, development, simulation, and test. It was active from the beginning of Shuttle Orbiter development in 1972 through the end of the shuttle program in the summer of 2011 almost 40 years. NASA s Kedalion engineering analysis lab is on the forefront of validating and using many contemporary avionics HW/SW development and integration techniques, which represent new paradigms to NASA s heritage culture in avionics software engineering. Kedalion has validated many of the Orion project s HW/SW engineering techniques borrowed from the adjacent commercial aircraft avionics environment, inserting new techniques and skills into the Multi-Purpose Crew Vehicle (MPCV) Orion program. Using contemporary agile techniques, COTS products, early rapid prototyping, in-house expertise and tools, and customer collaboration, NASA has adopted a cost effective paradigm that is currently serving Orion effectively. This paper will explore and contrast differences in technology employed over the years of NASA s space program, due largely to technological advances in hardware and software systems, while acknowledging that the basic software engineering and integration paradigms share many similarities.

关键词：电子信息；软件；航空飞船；载人飞船

查看摘要 索取原文[27页]

Software can currently be acquired in three different methods. The first is to have software custom built/developed to match a particular specification/requirement. We shall refer to this option as 'make.' The second is to purchase a software product from a vendor/supplier. We shall refer to this option as 'buy'. The third is to rent/outsource the use of a software product or a software development environment from a third-party supplier. We shall refer to this option as 'rent.' It seems that what is lacking is some guidance to help acquirers decide which of these three software acquisition approaches to consider and, eventually, to select. This lack of objective, quantitative guidance (including risks associated with each option decisions needed for each option, etc.) causes acquirers to sometimes make ill-informed decisions about which acquisition method to use. This paper identifies some of the differences between these three acquisition models as mapped against several life cycle phases and project activities, and then identifies risks associated with the 'rent' option.

关键词：电子信息；软件；采集模型

查看摘要 索取原文[22页]