Search Results

Bosch adds 10,000 software engineers

Ford, Bosch demo automated-parking project in Detroit

ZF builds ‘middleware’ to address vehicle software escalation

SAE EDGE Research Reports provide examinations significant topics facing mobility industry today including Connected Automated Vehicle Technologies Electrification Advanced Manufacturing

SAE EDGE Research Reports provide examinations significant topics facing mobility industry today including Connected Automated Vehicle Technologies Electrification Advanced Manufacturing

SAE EDGE Research Reports provide examinations significant topics facing mobility industry today including Connected Automated Vehicle Technologies Electrification Advanced Manufacturing

. ----------------- This standard defines standards for loadable software parts and software transport media. It describes the principles and rules to be applied to any part of a data load system, to ensure compatibility and interoperability. ...It includes part numbering, content, labeling and formatting of loadable software parts and software transport media.

This document describes a secure internet facility for sending all types of aviation software using the world wide web (www). Software suppliers may use this document as a starting point for the construction of a secure web server utility. ...It provides sufficient flexibility and is compatible with numerous software distribution models. The file management structure is consistent with other ARINC standards for loadable software, and references ARINC 665 and ARINC 667 in particular. ...The file management structure is consistent with other ARINC standards for loadable software, and references ARINC 665 and ARINC 667 in particular.

This document defines the aircraft industry's standards for Loadable Software Parts (LSPs) and Media Set Parts (MSPs). It describes the common principles and rules to be applied to any part of a data load system to ensure compatibility and inter-operability of software parts. ...It describes the common principles and rules to be applied to any part of a data load system to ensure compatibility and inter-operability of software parts. It includes part numbering, content, labeling, and formatting of an LSP, and a Media Set containing LSPs. ...Supplement 5 refers to a companion document, ARINC Report 645: Common Terminology and Functions for Software Distribution and Loading.

This document defines the aircraft industry's standards for Loadable Software Parts (LSPs) and Media Set Parts (MSPs). It describes the common principles and rules to be applied to any part of a data load system to ensure compatibility and inter-operability.

This standard is applicable to all airborne software. As such, the software development needs to perform certain verification activities to comply to the standard objectives. ...This paper identifies approaches that may be followed to apply machine learning techniques for automation and a framework to incorporate this into the existing peer review process performed for airborne software. This paper also discusses the challenges in automating review activity to improve quality, reduce cost and adhere to standards (such as DO178) at the same time. ...Development of any safety critical software applications such as in the aerospace industry needs to comply to specific standards (DO-178) to meet airworthiness requirements.

This standard is a top-level design guide for managing the development and maintenance of avionics software. It provides guidance for the design and development of avionics software for traditional ARINC 700-series equipment and IMA. ...This standard emphasizes the airline desire for user-modifiable software.

Topics include software acquisition, software receiving, software distribution and necessary documentation. The FLS management process described in ARINC 667 is compatible with published FAA/JAA guidance on this subject. ...This document describes effective methods to manage and distribute operation flight software programs, aeronautical data bases and other forms of software used within an airline organization. ...The FLS management process described in ARINC 667 is compatible with published FAA/JAA guidance on this subject. Software suppliers, airline users and regulators will find this document to be a practical and effective guide.

Topics include software acquisition, software receiving, software distribution and necessary documentation. The FLS management process described in ARINC 667 is compatible with published FAA/EASA guidance on this subject. ...This document describes effective methods to manage and distribute operation flight software programs, aeronautical data bases and other forms of software used within an airline organization. ...The FLS management process described in ARINC 667 is compatible with published FAA/EASA guidance on this subject. Software suppliers, airline users and regulators will find this document to be a practical and effective guide.

It is not intended to become the only possible CAN software loading alternative. It is intended for those avionics devices that are software loadable. ...The purpose of the standard is to provide a simple and efficient protocol for loading software parts to line replaceable units (LRUs) on a CAN bus, as an alternative to ARINC Report 615A or ARINC Report 615.

As a starting point, this document provides guidance on: Which standard to use in specific situations The use of and how integrity checks should be applied Common terminology in airborne software management Since airplanes started using software controlled hardware, there has been a need to standardize processes and terminology. ...This document provides airlines, airframe manufacturers, aircraft equipment suppliers, and others with information that is specific to data, software, and ground tools used in aviation configuration and data management. As a starting point, this document provides guidance on: Which standard to use in specific situations The use of and how integrity checks should be applied Common terminology in airborne software management Since airplanes started using software controlled hardware, there has been a need to standardize processes and terminology. ...This document is the centroid to which other software standards are related.

This document provides airlines, airframe manufacturers, aircraft equipment suppliers, and others with information that is specific to data, software, and ground tools used in aviation configuration and data management.

This standard provides aircraft manufacturers, regulatory agencies, and airlines a format standard for aircraft configuration reporting, and facilitates automated comparison of configuration data reports (e.g., authorized versus as flying, etc.).

The purpose of this standard is to provide a method for packaging aircraft software parts for distribution using contemporary media or by electronic distribution. This project intends to standardize and provide guidance for the storage of floppy based software, currently packaged in media set parts. ...This project intends to standardize and provide guidance for the storage of floppy based software, currently packaged in media set parts. This standard format can be then stored or distributed on a single physical media member (CD-ROM), or by electronic crate.

The purpose of this standard is to provide a method for packaging aircraft software parts for distribution using contemporary media or by electronic distribution. This project intends to standardize and provide guidance for the storage of floppy based software, currently packaged in media set parts. ...This project intends to standardize and provide guidance for the storage of floppy based software, currently packaged in media set parts. This standard format can be then stored or distributed on a single physical media member (CD-ROM), or by electronic crate.