基于COTS的航空电子软件开发

介绍了商用货架产品(COTS)在航空电子软件开发中应用的优点和缺点,和基于COTS的航电软件构架;并给出了一个开发过程和部分开发工具。最后通过一个实例说明基于COTS的航电软件开发是实际可行的。     

Open systems architecture solutions for military avionics testing

Raytheon makes extensive use of open systems architecture methods in developing special test equipment (STE) for testing military avionics equipment. Such use has resulted in significant cost and schedule savings in the development of production test equipment for radar and infrared systems. With open systems architectures, a test system can be assembled using COTS products. This brings economies of scale to test equipment, which is normally built in very low quantities. Therefore, the potential cost savings due to COTS usage is proportionately greater in STE than in the higher volume avionics systems that are tested. A second major benefit of using COTS products is that test system development schedule cycle time is greatly reduced. This paper describes the application of Open Systems Architectures (OSA) to avionics testing. The following major architectures are surveyed: VME bus, VXI bus, IEEE GPIB, IEEE 1149.1 JTAG test bus, 1553 Military Bus, Fibre Channel, and COTS Test Applications Software. We describe how the benefits of OSA have been extended at Raytheon into achieving vertical test commonalities. The flexibility of OSA can be exploited to provide an overall optimum test solution, taking all levels of test into account. For example, test systems can be tailored with COTS products to provide integrated methods for avionics tests at the module, unit, and system levels. Test systems can be configured to maximize the reuse of COTS hardware over all test levels. Test software can also be programmed to optimize such reuse over levels of test. Additional test verticality synergies derived from such OSA usage are described, including: test false alarm avoidance; test cones of tolerance optimization; and efficient test of field returns     

Reconfigurable COTS test systems

Automatic Test Equipment (ATE) systems are used to qualify, accept, and troubleshoot electronic products. ATE systems may be in the form of large general-purpose systems that can test a wide variety of products or the more commonly used custom, turnkey systems that are designed for specific test application(s) and requirements. Turnkey ATE systems are labor-intensive; as a result, even a relatively simple turnkey tester is costly and may take months (or even years) to develop, integrate, and deploy. The main reason for this aspect of turnkey ATE systems is that even though the instrumentation may be off-the-shelf components, most everything else is custom and requires design, development, extensive debug and integration. Time and again, systems integrators have tried to find a solution that would combine the cost effectiveness of COTS systems with the flexibility of custom ATE. This paper suggests a solution to this problem and that it is feasible to combine COTS testers with custom requirements. This solution, called CreATE, provides a flexible architecture using COTS components (including instruments, cabling and interfacing products)     

The cost of COTS

Fairchild Defense, a division of Orbital Sciences Corporation, has been a pioneer in the use of Commercial-Off-The-Shelf (COTS) hardware, software, and tools in military equipment. Fairchild has developed a cost and schedule effective approach to the use of COTS elements. This paper discusses Fairchild's experience with the use of COTS in military equipment and special considerations imposed because of the military environment     

基于HLA的航天飞行任务联合仿真系统设计

简要说明了HLA的基本特点,描述了一个已经实现的航天测控仿真系统,并将其结构思想与HLA进行了对照。在此基础上,提出了一个依据HLA标准,对航天员座舱仿真、火箭和飞船仿真、测控网仿真等进行集成的航天飞行任务联合仿真系统框架,分析了各个仿真联邦成员的功能需求和信息接口,并着重介绍了针对任务要求的时间管理、数据通信等关键RTI机制的设计和实现方法,以及参照FEDEP模型和借助商业成品软件工具的系统开发策略。     

Integrating system engineering software tools

System engineering projects typically involve the use of a variety of design, analysis, simulation, and management software tools that are home-grown or commercial-off-the-shelf (COTS). Very often, these applications are hosted on dissimilar computing platforms in a network environment. An application deployed on one platform may not be easily ported to another platform, and it usually cannot be readily accessed by software on the other platform. Enhancing the inter-operation among software applications or tools will greatly increase the effectiveness of the system engineering process. The middleware technology currently being developed by the computer industry promises to provide the needed software interface for integrating tools across a heterogeneous computer network. This paper discusses the experience of applying the middleware technology to software tools used in system engineering     

Next generation space avionics: layered system implementation

Advances in electronics over the past decade have produced major improvements in the power and flexibility of computer systems. Unfortunately current avionics systems for space applications typically have not leveraged these COTS advantages. A decade ago, the state-of-the-art for avionics systems made a step change to the Integrated Modular Avionics (IMA) used in the Boeing 777. This next generation avionics architecture is not based upon traditional Byzantine redundancy structures, but on a truth-based scheme where each element knows when an internal failure occurs and removes itself from the system. IMA utilizes a lock-step microprocessor design that communicates to a COTS Backplane for input/output, and to a Virtual Backplane/spl trade/ (a reliable high-speed serial bus) for intra-system communication. The system functions are implemented using a time and space partitioned operating system. The entire system provides the simplicity of a simplex system, implements the highest level of reliability providing complete flexibility to reconfigure both software applications and hardware interfaces, allows for rapid prototyping using low-cost COTS hardware, and is easily expandable beyond the initial point implementation. As the only 5/sup th/ generation avionics architecture, the concepts incorporated into Honeywell's IMA are ideally suited to be the backbone of the next generation Space Exploration Program avionics architectures.     

Sustainment of legacy automatic test systems: lessons learned on TPS transportability

Sustainment of legacy automatic test systems (ATS) saves cost through the re-use of software and hardware. The ATS consists of the automatic test equipment (ATE), the test program sets (TPSs), and associated software. The associated software includes the architecture the TPSs run on, known as the control software or test station test executive. In some cases, to sustain the legacy ATS, it is more practical to develop a replacement ATE with the latest instrumentation, often in the form of commercial off-the-shelf (COTS) hardware and software. The existing TPSs, including their hardware and test programs, then need to be transported, or translated, to the new test station. In order to understand how to sustain a legacy ATS by translating TPSs, one must realize the full architecture of the legacy ATS to be replaced. It must be understood that TPS transportability does not only include translating the original TPS from an existing language (such as ATLAS) to a new language (such as "C") to run on a new test station, but includes transporting the run-time environment created by the legacy ATS. This paper examines the similarities and differences of legacy ATE and modern COTS ATE architectures, how the ATS testing philosophy impacts the ease of TPS transportability from legacy ATE to modern-day platforms, and what SEI has done to address the issues that arise out of TPS transportability.     

Development of a TPS reuse library using COTS tools

In the past, functional test requirements (FTR) or test requirement documents (TRD) and test program sets (TPS) were standalone items developed by individual engineers. In some cases, one engineer would write the FTR/TRD and another would develop the TPS. Commercial ATLAS FTRs are prepared in ARINC 616 and 626 ATLAS. Military TRDs are written in IEEE ATLAS 716 versions. Previous test reuse attempts have not been successful because additional software, like browsers, is required to support these efforts. It was difficult to justify writing new software; for example, browsers to manage the application software. Today, commercial-off-the-shelf (COTS) tools are in place to browse and view information from circuit diagrams to documents to source code. These tools can develop hierarchies to organize the information. These COTS tools are available throughout Boeing on many types of workstations and personal computers on every engineer's desk. This paper discusses how a reusable test library (RTL) is being developed using commercial-off-the-shelf (COTS) tools, such as Mosaic, to address commercial and military test applications. It describes each of the tools and the process to develop TPSs using the reuse library. It defines the metrics and benefits achieved     

Technology roll lessons learned on embedded avionics platforms

Open system architectures based on commercial off-the-shelf (COTS) building block components offer the ability to leverage the latest technology into fielded products while minimizing the impact to the operational flight software, typically the most costly component of an avionics development or upgrade. Our team has developed a layered hardware and software approach based on industry standard hardware and software interfaces to abstract the application (operational) software developers from the underlying technology rolls to the hardware and operating system software that naturally occur as part of the commercial marketplace, A technology roll is defined as the replacement of a current product with a subsequent generation of a product from the same product family. In this article, we describe the components and the layered architecture of our open system architecture approach. We discuss specific system, hardware, and software technology insertions that incorporate the latest available technology and how these changes have been abstracted from the application software. The article concludes by discussing lessons Learned from the use of these common components and corresponding technology rolls across various platforms     

IMA aircraft improvements

Integrated modular avionics (IMA) is being suggested as the means by which new capabilities can be deployed on aircraft at an affordable cost. RTCA SC-200 is presently considering the guidance document for IMA. All of the functionality that IMA offers can be achieved through a conventional federated architecture; however, the cost, size, and weight penalties of the federated solution make it economically infeasible. IMA is seen as the way forward. It is assuming greater importance as the aircraft industry transitions to commercial-off-the-shelf (COTS) technology with its attendant obsolescence and reliability concerns. IMA may be one of the most cost-effective ways by which rapid obsolescence can be managed. Ironically, this move to COTS is also the greatest threat to IMA systems. IMA achieves reductions in size, cost, and weight by providing a set of flexible hardware and software resources that can be statically or dynamically mapped to a set of required avionics functional capabilities. This introduces a number of new complexities such as mixed criticalities and reconfiguration. We do not address these issues herein. Rather we discuss the mechanisms by which electronics degrades and how a classical safety assessment of a reconfigurable IMA system can be ified by this degradation. We argue that, with the advent of COTS, it is no longer justifiable to consider that electronics has an effectively constant failure rate. Physical considerations suggest that electronics failure occurs when environmental and operating stress causes the accumulation of damage to the underlying structures to exceed the threshold strength of the constituent materials and interfaces. Finally, we suggest how finite-life electronics effects may be mitigated.     

Continuing challenges in lithium battery development

In these days of emphasizing standardization, Acquisition Reform, Non-Developed Items (NDI) and Commercial-Off-The-Shelf (COTS) technologies, we are facing new challenges associated with these trends. Program managers are pressured to use a standard or COTS battery, while simultaneously, the new systems being developed have increasingly complex and demanding power requirements. Hardware must be developed with shorter schedules, and policies of Acquisition Reform limit the amount of control the government has over the development of a given item. In this paper, we review battery development efforts that have resulted in unexpected problems. Relevant data from both current and past test programs are presented. Recommendations are provided concerning how to best avoid duplication of effort, while ensuring that the final product will have the best chances of succeeding     

Graph-tree-based software control flow checking for COTS processors on pico-satellites

 This paper proposes a generic high-performance and low-time-overhead software control flow checking solution, graph-tree-based control flow checking (GTCFC) for space-borne commercial- off-the-shelf (COTS) processors. A graph tree data structure with a topology similar to common trees is introduced to transform the control flow graphs of target programs. This together with design of IDs and signatures of its vertices and edges allows for an easy check of legality of actual branching during target program execution. As a result, the algorithm not only is capable of detecting all single and multiple branching errors with low latency and time overheads along with a linear-complexity space overhead, but also remains generic among arbitrary instruction sets and independent of any specific hardware. Tests of the algorithm using a COTS-processor-based onboard computer (OBC) of in-service ZDPS-1A pico-satellite products show that GTCFC can detect over 90% of the randomly injected and all-pattern-covering branching errors for different types of target programs, with performance and overheads consistent with the theoretical analysis; and beats well-established preeminent control flow checking algorithms in these dimensions. Furthermore, it is validated that GTCGC not only can be accommodated in pico-satellites conveniently with still sufficient system margins left, but also has the ability to minimize the risk of control flow errors being undetected in their space missions. Therefore, due to its effectiveness, efficiency, and compatibility, the GTCFC solution is ready for applications on COTS processors on pico-satellites in their real space missions.     

Use of service history for certification credit for COTS [avionic software]

Much has been written in the last ten years about how the use of commercial-off-the-shelf (COTS) components would revolutionize the aerospace industry avionics, communication, navigation, surveillance/air traffic management (CNS/ATM) as well as global air traffic management (GATM). Civil aviation authorities around the world have been faced with numerous requests to certify aircraft containing increasing percentages of COTS components, much of it never designed or intended for use in the safety critical environment of an aircraft. Product service history is one method for demonstrating that such software is acceptable for use. In theory, product service history would seem to be a fairly simple concept, both to understand and to apply. However, in practice, such use has proven extremely problematic, as questions of how to measure the historic performance and the relevance of the provided data have surfaced. This paper elaborates a research effort funded by the United States Federal Aviation Administration to collect, analyze, and synthesize what is known and understood about applying product service history. The effort is limited to the topic of software product service history as applied in the certification of airborne systems and equipment.     

Replacement strategy for aging avionics computers

With decreasing defense dollars available to purchase new military aircraft, the inventory of existing aircraft will have to last many more years than originally anticipated. As the avionics computers on these aging aircraft get older, they become more expensive to maintain due to parts obsolescence. In addition, expanding missions and changing requirements lead to growth in the embedded software which, in turn, requires additional processing and memory capacity. Both factors, parts obsolescence and new processing capacity, result in the need to replace the old computer hardware with newer, more capable microprocessor technology. New microprocessors, however, are not compatible with the older computer instruction set architectures. This generally requires the embedded software in these computers to be rewritten. A significant savings-estimated in the billions of dollars-could be achieved in these upgrades if the new computers could execute the old embedded code along with any new code to be added. This paper describes a commercial-off-the-shelf (COTS)-based form, fit, function, and interface (F³I) replacement strategy for legacy avionics computers that can reuse existing avionics code “as is” while providing a flexible framework for incremental upgrades and managed change. It is based on a real-time embedded software technology that executes legacy binary code on the latest generation COTS microprocessors. This technology promises performance improvements of 5-10 times that of the legacy avionics computer that it replaces. It also promises a 4× decrease in cost and schedule over rewriting the code and provides a “known good” starting point for incremental upgrades of the embedded flight software. Code revalidation cost and risk are minimized since the structure of the embedded code is not changed, allowing the replacement computer to be retested at the “blackbox” level using existing qualification tests     

The problem with aviation COTS

Commercial Off the Shelf (COTS) has become a byword for acquisition reform, but there are significant risks associated with the use of COTS products in military systems. These risks are especially acute for aviation systems. This paper explains how COTS can negatively affect military acquisitions and gives ideas on how to plan and resolve COTS caused problems     

设计模式探析及其在测控软件中的应用

针对测控领域中复用程度低和开发周期长的问题,提出在该领域软件进一步推广和使用设计模式的思路。分析当前测控软件在实际开发过程中遇到的突出症结,并结合具体工程实践描述在测控软件领域引入设计模式的作用和影响,以单态模式为例分析引入设计模式对软件体系架构造成的深刻改变和潜在风险,给出测控软件领域中运用设计模式的建议。通过分析不同应用场景表明,灵活运用设计模式能够解决航天测控软件中常见的突出问题。     

一种基于HPC和COTS技术的软件雷达硬件体系结构设计

利用HPC系统强大的运算能力和高速数据传输带宽，通过网络互连所构成的网络拓扑结构，再结合基于具有可靠的工作性能和较低的成本，并且具有标准化、同类器件可替换的COTS技术的产品作为计算节点，构建了一种标准化、模块化的软件雷达硬件体系结构。     

Embedded information system re-engineering

Currently fielded embedded information systems face readiness challenges imposed by evolving missions and extended service lifespans. The ability to overcome these challenges is constrained by such factors as shrinking budgets, limited computational capacity and diminished manufacturing sources effects that impact both hardware and software options. Wholesale redevelopment is often cost prohibitive, particularly since large portions of embedded applications continue to fulfil mission requirements. Solutions must preserve prior investments while providing efficient pathways for continued technology refresh. A technology solution for affordable modernization of legacy system software is being development. The Embedded Information System Re-engineering (EISR) project is developing an automation-assisted JOVIAL-to-C re-engineering capability that permits simultaneous modernization of both the structure and source language of legacy embedded applications. Engineers will be able to apply the proven labor-saving visualization and analysis features of modern CASE tools to legacy JOVIAL applications. EISR will thus allow the DoD to recapture previous investments in proven legacy algorithms and mission capabilities while permitting the full exploitation of COTS economies of scale. This paper describes in brief the goals and objectives of the EISR project, and provides the current status of the EISR capability.