Criteria

Text:
Content:
Display:

Results

Viewing 1 to 30 of 97
CURRENT
2018-01-18
Standard
AS5652A
This SAE Aerospace Standard (AS) contains requirements for a digital time division command/response multiplex data bus, for use in systems integration that is functionally similar to MIL-STD-1553B with Notice 2 but with a star topology and some deleted functionality. Even with the use of this document, differences may exist between multiplex data buses in different system applications due to particular application requirements and the options allowed in this document. The system designer must recognize this fact and design the multiplex bus controller (BC) hardware and software to accommodate such differences. These designer selected options must exist to allow the necessary flexibility in the design of specific multiplex systems in order to provide for the control mechanism, architectural redundancy, degradation concept, and traffic patterns peculiar to the specific application requirements.
CURRENT
2017-11-21
Standard
ARP1210E
This SAE Aerospace Recommended Practice (ARP) describes a class of digital computer programs for use by organizations other than the engine supplier for reduction of engine test data relating to the interface of the engine in the airframe or test facility. This ARP also is intended as a guide for the preparation of such computer programs.
2017-10-16
WIP Standard
SAE6906
The standard would include requirements for HSI management [planning, execution, coordination (internal and external) documentation, administration and quality control], including collaboration among HSI domains, coordination between HSI and other disciplines to optimize total system performance, optimize human performance, and minimize personnel-driven risks and customer ownership costs.
CURRENT
2017-10-11
Standard
AS6089
This document was prepared by the SAE AS-1A2 Committee to establish techniques for validating the Network Controller (NC) complies with the NC requirements specified in AS5653, Revision B. Note that this verification document only verifies the specific requirements from AS5653 and does not verify all of the requirements invoked by documents that are referenced by AS5653. The procuring authority may require further testing to verify the requirements not explicitly defined in AS5653 and in this verification document.
HISTORICAL
2017-07-19
Standard
J1939DA_201707
This document is intended to supplement the J1939 documents by offering the J1939 information in a form that can be sorted and search for easier use.
CURRENT
2017-07-06
Standard
ARIR667-2
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. 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. Software suppliers, airline users and regulators will find this document to be a practical and effective guide.
CURRENT
2017-06-12
Standard
AS7106/1A
This document has been declared "CANCELLED" as of June 2017. By this action, this document will remain listed in the Numerical Section of the Aerospace Standards Index. Cancelled specifications are available from SAE.
CURRENT
2017-05-26
Standard
J3117_201705
This document covers un-shielded balanced single twisted pair data cable intended for use in surface vehicle cables for 100 Mbps Ethernet applications. The tests in this document are intended to qualify cables for normal operation in an automotive environment while maintaining the necessary electrical properties for reliable data transmission.
HISTORICAL
2017-04-27
Standard
J1939DA_201704
This document is intended to supplement the J1939 documents by offering the J1939 information in a form that can be sorted and search for easier use. The J1939 Digital Annex, introduced in August 2013, offers key J1939 technical data in an Electronic Spreadsheet that can be easily searched, sorted, and adapted to other formats. J1939DA contains all of the SPNs (parameters), PGNs (messages), and other J1939 data previously published in the SAE J1939 top level document. J1939DA also contains all of the SLOTs, Manufacturer ID Codes, NAME Functions, and Preferred Addresses previously published in the SAE J1939 top level and the J1939-71 document. J1939DA contains the complete technical details for all of the SPNs and PGNs previously published in the SAE J1939-71 document. It also includes the supporting descriptions and figures previously published in the SAE J1939-71 document.
CURRENT
2017-03-30
Standard
AS47643
This document establishes techniques for validating that an Aircraft Station Interface (ASI) complies with the interface requirements delineated in MIL-STD-1760 Revision E.
CURRENT
2017-02-01
Standard
AS9115A
The requirements of 9100 apply with the following clarification for software. This standard supplements the 9100 standard requirements for deliverable software and contains quality management system requirements for organizations that design, develop, and/or produce deliverable software and services for the aviation, space, and defense industry. This includes, as required, support software that is used in the development and maintenance of deliverable software and services. The deliverable software may be stand-alone, embedded, mobile application, or loadable into a target computer. This deliverable software may also be part of services (e.g., cloud environment, web hosted solutions or platforms).
CURRENT
2016-11-08
Standard
AS9162
This document identifies the basic elements and provides a standard for structuring operator self-verification programs within the aviation, space, and defense industry for producers of commercial and military aircraft and weapons platforms, space vehicles, and all related hardware, software, electronics, engines, and composite components. The requirements specified in this standard are complementary (not alternative) to contractual and applicable statutory and regulatory requirements. Should there be a conflict between the requirements of this standard and applicable statutory or regulatory requirements, the latter shall take precedence.
CURRENT
2016-08-01
Standard
ARP4868C
The SAE Aerospace Standard document AS681 is the parent document of this SAE Aerospace Recommended Practice (ARP). AS681 applies to Engine programs written to conform to this document. This ARP specifies a set of functions and their expected behaviors that constitute a function based Application Program Interface (API) for gas turbine engine customer programs. The functions specified in this API are delivered by the Supplier as part of the Engine model. This document defines generic language independent functions and specific appendices for implementations in C and Fortran. The function based API specified in this ARP represents an alternative to the Fortran COMMON block structure, as specified in AS4191, historically used to communicate with an engine program. The customer may request emulation of the AS4191 interface if desired.
CURRENT
2016-07-29
Standard
ARIS844P1
ARINC Specification 844, prepared in two parts, defines the requirements of a Target Data Loader (TDL) from the target hardware point of view. Both parts are based on two data loading standards: Part 1 clarifies ARINC Report 615-3: Airborne Computer High Speed Data Loader, Part 2 clarifies ARINC Report 615-4: Airborne Computer High Speed Data Loader. ARINC Report 615 was originally written from the data loader point of view. It is important that a target designer have a general understanding of the operation of a data loader in its modern implementation. Equally important is the need for data loader manufacturers to understand the standardized implementation requirements and supported subset of ARINC 615 features that are defined in ARINC 844, Parts 1 and 2. Therefore, ARINC Specification 844 is expected to provide value to both data loader and target implementers.
CURRENT
2016-07-29
Standard
ARIS844P2
ARINC Specification 844, prepared in two parts, defines the requirements of a Target Data Loader (TDL) from the target hardware point of view. Both parts are based on two data loading standards: Part 1 clarifies ARINC Report 615-3: Airborne Computer High Speed Data Loader, Part 2 clarifies ARINC Report 615-4: Airborne Computer High Speed Data Loader. ARINC Report 615 was originally written from the data loader point of view. It is important that a target designer have a general understanding of the operation of a data loader in its modern implementation. Equally important is the need for data loader manufacturers to understand the standardized implementation requirements and supported subset of ARINC 615 features that are defined in ARINC 844, Parts 1 and 2. Therefore, ARINC Specification 844 is expected to provide value to both data loader and target implementers.
CURRENT
2016-07-14
Standard
ARIR665-4
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. It includes part numbering, content, labeling, and formatting of an LSP, and a Media Set containing LSPs.
CURRENT
2016-06-27
Standard
ARP9005A
This document contains recommended practices for the effective control of non-deliverable software. It addresses practices for control during the development, production, release maintenance, and retirement of non-deliverable software, as well as for software procured from outside manufacturers and incorporated in the production, evaluation, test, acceptance or calibration of processes. For the purposes of this document, the terms software and non-deliverable software are considered synonymous.
CURRENT
2016-06-16
Standard
IEEEEIA12207_1
This guide provides guidance for recording life cycle data resulting from the life cycle processes of IEEE/EIA 12207.0.
CURRENT
2016-06-16
Standard
IEEEEIA12207_2
This guide provides implementation consideration guidance for the normative clauses of IEEE/EIA 12207.0. The guidance is based on software industry experience with the life cycle processes presented in IEEE/EIA 12207.0.
CURRENT
2016-06-16
Standard
EQB2
Program Managers have considered the subject of effectiveness quantification from three diverse points of view. The first viewpoint, in conjunction with the system effectiveness analyst, is to quantify everything and to consider everything quantifiable into a figure of merit. The result is a numerical decision aid that usually has some undesirable attributes such as oversimplification, non-sensitivity to critical parameters, hidden calculations, and difficulty in exercise of the model. This technique is characterized by mathematical models, computer programs, and attempted optimizations. The second viewpoint, in conjunction with the controller, is to consider the effectiveness as specified and concentrate on cost reduction, This has a danger of formulating all technical problems in terms of cost or economic considerations. This technique is characterized by closely controlled work packages.
CURRENT
2016-06-16
Standard
EIA408
This standard applies to the interconnection of data terminal equipment and numerical control equipment at the tape reader interface. The data terminal would typically be connected to a remote data source/sink such as a computer. This standard is applicable for the interchange of signals when used in conjunction with electronic equipment, each interchange circuit of which has a single return (signal ground) that can be interconnected at the interface point.
CURRENT
2016-06-16
Standard
RS274D
This standard is intended to serve as a guidein the coordination of system design, to minimize the variety of program manuscripts required, to promote uniformity of programming techniques, and to foster interchangeability of input data between numerically controlled machines of the same classification by type, process function, size, and accuracy. It is intended that simple numerically controlled machines be programmed usinga simple format, which is systematically expandable for morec omplex machines.
CURRENT
2016-05-31
Standard
CRB1
Expert systems are a wave of the information processing future. As time goes on they will become more and more part of the mainstream. However, a necessary prerequisite to moving them into widespread use is to reduce the methodologies for expert system development closer to the more generally accepted software engineering techniques. This report offers a step towards that goal. It describes an alternative software life cycle model for expert system development. Since the field of Artificial Intelligence is so broad, this report limits the software to be considered. Systems that would be of the greatest interest to DoD over the next 5 to 7 years would be expert systems that have the following attributes: - may reason with uncertainty - are not necessarily rule-based - are non-learning systems. For these systems, a developmental cycle is articulated, and each phase of the cycle described.
CURRENT
2016-05-31
Standard
CRB2
This paper originated with a software quality panel workshop at the EIA Computer Resources Workshop. The panel group initially focused on requirements for nondeliverable software. It was felt that the requirements for deliverable software were well covered by Department of Defense standards but non-deliverable software issues were not adequately covered. After much discussion, including attempts to define nondeliverable by examples of software types, a surprising unanimous conclusion was reached by the participants. That is: the states of "deliverable" and "non-deliverable" had no bearing on the quality of the software, and thereby also had no bearing on the quality assurance requirements that should be applied for that software. Rather, the only rational application of quality assurance was primarily dependent on the impact that the software had, or could have, on the end product (ยก.e. the ultimate mission).
2016-03-03
WIP Standard
EIA649_1A
This document is used for placing Configuration Management Requirements on Defense Contracts after being tailored by the Acquirer. When effectively and consistently applied, Configuration Management (CM) provides a positive impact on product quality, cost, and schedule. The planning and execution of Configuration Management (CM) is an essential part of the product development and life cycle management process. It provides control of all configuration documentation, physical parts and software representing or comprising the product. Configuration Management's overarching goal is to establish and maintain consistency of a product's functional and physical attributes with its requirements, design and operational information throughout its life cycle. When effectively and consistently applied, Configuration Management (CM) provides a positive impact on product quality, cost, and schedule.
2016-03-03
WIP Standard
EIA649C
When effectively and consistently applied, Configuration Management (CM) provides a positive impact on product quality, cost, and schedule. This standard is intended to assist in establishing, performing, or evaluating CM systems. CM is an integrated system of processes that ensure consistency of a product's performance, functional and physical attributes with its requirements, design, and operational information. The essence of CM, as portrayed in this consensus standard, is the common application of CM functions and their underlying fundamental principles, which have universal applicability across the broad spectrum of commercial and government enterprises. The standard provides an understanding of what to do, why a customer/suppler should do it, and when it is necessary to tailor the application of CM functions. This standard fulfills the important function of providing a rational basis upon which to apply good judgment in both planning for and executing CM across the enterprise.
CURRENT
2015-12-11
Standard
ARIS828-4
ARINC 828-4 defines a common Electronic Flight Bag (EFB) interface that can support EFB installations and the associated software applications. Supplement 4 defines two new connectors that will provide power and Ethernet to the EFB, thus enabling a smaller and lighter footprint for EFB installation provisions.
CURRENT
2015-10-28
Standard
J2534/1_201510
This SAE Recommended Practice describes a standardized interface that connects between a standard personal computer (PC) and vehicle. The purpose of this interface is to enable the reprogramming of emission-related control modules, in 2004 and later model year vehicles. The interface shall consist of the necessary hardware and/or software to support the requirements defined in this document. It is expected that vehicle manufacturers will provide the software application that will control the Pass-Thru Interface, to perform the actual reprogramming. The goal of this document is to ensure that reprogramming software from any vehicle manufacturer is compatible with interface supplied by any tool manufacturer. A common interface for all vehicle manufacturers reduces the tool costs for aftermarket garages, while allowing each vehicle manufacturer to control the programming sequence for the electronic control units (ECUs) in their vehicles.
CURRENT
2015-08-21
Standard
ARIS653P2-3
As avionics software continues to evolve, so does ARINC Specification 653. ARINC 653 Part 2 specifies extensions (i.e., optional services) to the required Application Program Interfaces (APIs) described in ARINC 653 Part 1. Supplement 3 adds optional multicore services capabilities.
Viewing 1 to 30 of 97

Filter

  • Standard
    97