Software Control For an APM System
Matthew S. Aldrich
Abstract
Matthew S. Aldrich
Abstract
An APM system, like many every day products, has software programs that enable it to function safely, efficiently, and consistently. These software programs require configuration control processes. Software configuration control processes are essential for an APM, as numerous software programs must be logged, version tracked, and tested for safety and correct operation. Software can be controlled on several operational levels: Source Code, final installable executables, full or partial system backups, proprietary development packages, and/or programmed hardware ready for installation. The actual requirement will depend on many factors. This paper will explore the software control methods of version tracking, escrow accounts, and archiving for the implementation and operational phases of a system (software development will not be discussed in detail). The implications of each aspect of the software control process will be related to what system components benefit the most from their application. Selected industry standards for the software in APM systems and the software development industry in general are listed at the end of this paper.
A significance statement is not available in the OpenAlex record.
A contribution statement is not available in the OpenAlex record.
Method details are not available in the OpenAlex metadata.
Findings are not separately available in the OpenAlex metadata.
Limitations are not available in the OpenAlex metadata.
Application details are not available in the OpenAlex metadata.
An APM system, like many every day products, has software programs that enable it to function safely, efficiently, and consistently. These software programs require configuration control processes. Software configuration control processes are essential for an APM, as numerous software programs must be logged, version tracked, and tested for safety and correct operation. Software can be controlled on several operational levels: Source Code, final installable executables, full or partial system backups, proprietary development packages, and/or programmed hardware ready for installation. The actual requirement will depend on many factors. This paper will explore the software control methods of version tracking, escrow accounts, and archiving for the implementation and operational phases of a system (software development will not be discussed in detail). The implications of each aspect of the software control process will be related to what system components benefit the most from their application. Selected industry standards for the software in APM systems and the software development industry in general are listed at the end of this paper.
Key concepts: Software construction, Computer science, Backporting, Software development, Package development process, Software system, Avionics software, Software