Skip to content
Free planNo credit card requiredStart writing
AI for Research home
AI for Research home
Dashboard
Sign inGet started

Search 250 million research papers

Read the abstract, see who wrote it and who cites it, and get the citation in APA, MLA, Chicago or Harvard.

About 1,992 papers for “Avionics software”

Software for Avionics.

Defense Technical Information Center (DTIC) · 1983

The objectives of this Meeting were as follows: Provide an overview of the software elements associated with embedded computer resources; Address current issues related to software requirements, design, development, verification, and validation, Identify software life-cycle considerations such as costs, management, and maintenance, and Discuss trends in software technology and identify the key features contributing to more efficient and more economic software programs in the NATO countries.

Cited by 0

Reengineering an avionics software system

Raghava G. Gowda, Bryce Eldridge, M. Bohler · 2002

This paper deals with the experiences in reengineering an existing system and developing an object-oriented design for the current system. The subsystem under study is the terrain following algorithm (TFA) or the vertical steering subsystem, a component of the guidance system of the operational flight program (OFP). The OFF is a major subsystem of the integrated test bed (ITB) facility used to support the development, test, and evaluation of advanced avionics systems in the avionics directorate at Wright-Patterson air force base. The techniques used in this reengineering process included structure charts, object-oriented structured design (OOSD) notation, and visibility diagrams for Ada packages. For developing an object-oriented design, the object modeling technique (OMT) by Rumbaugh et al. was used. Some of the CASE tools used for reengineering were Software Through Pictures, Rational Rose, and OMTool.

Cited by 0

Software reliability and advanced avionics

Gerard E. Migneault · 1980

This paper proposes that software is becoming the most safety critical element of the highly reliable avionics systems which will be needed in civil transport aircraft of the future.

Cited by 9

Avionics Software Support Cost Model.

Defense Technical Information Center (DTIC) · 1983

This report describes the work performed to develop the Avionics Software Support Cost Model (ASSCM). ASSCM is an interactive model which projects annual software support costs of various proposed avionics software configurations during the early design phase of system development. It bases cost projections on a unique algorithm designed to use as much historical data as possible. The algorithm also relies on subjective information contained from a large group of individuals familiar with support software and its costs. (Author)

Cited by 0

Automated maintenance of avionics software

Joseph Loyall, S.A. Mathisen, Peter Hurley et al. · 2002

Maintenance of avionics software is an increasing burden for the Air Force because of the growing size and complexity of software on aircraft. As software becomes larger and more complex, maintainers have more difficulty understanding and modifying it. The test burden and need for support hardware and software, which also must be maintained, also increases. TASC has developed a prototype tool that provides automated support for the avionics software maintenance process. The prototype improves the software maintainer's understanding of an operational flight program and reduces the manual effort necessary to perform regression testing. It indicates the possible effects of a software modification, aids in test selection and creation, performs test execution and result checking, and measures test coverage.< <ETX xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink">&gt;</ETX>

Cited by 7

Avionics Simulation, Development and Software Engineering

Blanche, Jim, Glaese, John, Kissel, Ralph et al. · NASA Technical Reports Server (NASA)

This monthly report summarizes the work performed under contract NAS8-00114 for Marshall Space Flight Center in the following tasks: 1) Purchase Order No. H-32831D, Task Order 001A, GPB Program Software Oversight; 2) Purchase Order No. H-32832D, Task Order 002, ISS EXPRESS Racks Software Support; 3) Purchase Order No. H-32833D, Task Order 003, SSRMS Math Model Integration; 4) Purchase Order No. H-32834D, Task Order 004, GPB Program Hardware Oversight; 5) Purchase Order No. H-32835D, Task Order 005, Electrodynamic Tether Operations and Control Analysis; 6) Purchase Order No. H-32837D, Task Order 007, SRB Command Receiver/Decoder; and 7) Purchase Order No. H-32838D, Task Order 008, AVGS/DART SW and Simulation Support

Cited by 0Open access

Software model checking for avionics systems

Darren Cofer, Michael W. Whalen, Steven P. Miller · 2008

The adoption of model-based development tools is changing the cost-benefit equation for the industrial use of formal methods. The integration of formal methods such as model checking into software development environments makes it possible to fight increasing cost and complexity with automation and rigor. This paper describes how formal analysis tools can be inserted into a model-based development process to decrease costs and increase quality of safety-critical avionics software.

Cited by 9

Developing Generic Software for Spacecraft Avionics

Joseph F. Smith · NASA Technical Reports Server (NASA) · 2003

A proposed approach to the development of software for spacecraft avionics is based partly on a concept of generic software that could be tailored to satisfy requirements for specific missions. The proposed approach would stand in contrast to the conventional approach of first defining avionics requirements for a specific mission, then developing software specific to those requirements. The proposed approach might also be adaptable to programming computers that control and monitor other complex equipment systems that range in scale from automobiles to factories. The concept of a spacecraft avionics functional model (SAFM) is a major element of the proposed approach. An SAFM would be, essentially, a systematic and hierarchical description of the functionality required of the avionics software (and hardware) for a given mission. Although the initial input information used to start the construction of an SAFM would typically amount to a high-level description, the SAFM would thereafter be decomposed to a low level. The resulting low-level version of the model would be used to develop a set of generic requirements that could be expected to include a large fraction of all requirements for a large fraction of all missions. The generic requirements would be used to develop software modules that could be included in, or excluded from, the final flight software to satisfy the requirements of a specific mission.

Cited by 0Open access

Power, Avionics and Software - Phase 1.0:

William D. Ivancic, O. Scott Sands, Casey J. Bakula et al. · NASA Technical Reports Server (NASA) · 2014

This report describes Power, Avionics and Software (PAS) 1.0 subsystem integration testing and test results that occurred in August and September of 2013. This report covers the capabilities of each PAS assembly to meet integration test objectives for non-safety critical, non-flight, non-human-rated hardware and software development. This test report is the outcome of the first integration of the PAS subsystem and is meant to provide data for subsequent designs, development and testing of the future PAS subsystems. The two main objectives were to assess the ability of the PAS assemblies to exchange messages and to perform audio testing of both inbound and outbound channels. This report describes each test performed, defines the test, the data, and provides conclusions and recommendations.

Cited by 0