Search Results

This SAE standard establishes the requirement for suppliers to plan a reliability program that satisfies the following three requirements: a The supplier shall ascertain customer requirements b The supplier shall meet customer requirements c The supplier shall assure that customer requirements have been met

The importance of reliability in design engineering has significantly grown since the early 1960’s. Competition has been a primary driver in this growth. The three realities of competition today are: world class quality and reliability, cost-effectiveness, and fast time-to-market. Formerly, companies could effectively compete if they could achieve at least two of these features in their products and product development processes, often at the expense of the third. However, customers today, whether military, aerospace, or commercial, have been sensitized to a higher level of expectation and demand products that are highly reliable, yet affordable. Product development practices are shifting in response to this higher level of expectation. Today, there is seldom time, or necessary resources to extensively test, analyze, and fix to achieve high quality and reliability.

This document provides methods and techniques for implementing a reliability program throughout the full life cycle of a software product, whether the product is considered as standalone or part of a system. This document is the companion to the Software Reliability Program Standard [JA1002]. The Standard describes the requirements of a software reliability program to define, meet, and demonstrate assurance of software product reliability using a Plan-Case framework and implemented within the context of a system application. This document has general applicability to all sectors of industry and commerce and to all types of equipment whose functionality is to some degree implemented by software components. It is intended to be guidance for business purposes and should be applied when it provides a value-added basis for the business aspects of development, use, and sustainment of software whose reliability is an important performance parameter.

This SAE Standard provides a framework for the management of software reliability within system reliability requirements. It is based around the Software Reliability Plan and Software Reliability Case and emphasizes the importance of evaluating progress towards meeting software reliability requirements throughout the project life-cycle.

This SAE Standard provides a framework for the management of software reliability within system reliability requirements. It is based around the Software Reliability Plan and Software Reliability Case and emphasizes the importance of evaluating progress towards meeting software reliability requirements throughout the project life-cycle.

This SAE Recommended Practice provides a framework for the establishment of a software support concept related to the support and supportability of both custom-developed and Off-the-Shelf (OTS) software. This document complements SAE AIR 5121, JA1004, and JA1005 by providing information needed to understand the support aspects that should be covered by a software supportability program. It should be noted that particular information indicated here should not be considered a complete list of all aspects of the support concept. In particular, the information should not be confused with a list of data elements. This document has general applicability to all sectors of industry and commerce and to all types of equipment that contain software. The target audience for this document includes software acquisition organizations, software logisticians, developers, supporters, and customers.

This SAE Recommended Practice provides a framework for the establishment of a software support concept related to the support and supportability of both custom-developed and Off-the-Shelf (OTS) software. This document complements SAE AIR 5121, JA1004, and JA1005 by providing information needed to understand the support aspects that should be covered by a software supportability program. It should be noted that particular information indicated here should not be considered a complete list of all aspects of the support concept. In particular, the information should not be confused with a list of data elements. This document has general applicability to all sectors of industry and commerce and to all types of equipment that contain software. The target audience for this document includes software acquisition organizations, software logisticians, developers, supporters, and customers.

This SAE Recommended Practice provides recommended guidelines and best practices for implementing a supportability program to ensure that software is supportable throughout its life cycle. This Implementation Guide is the companion to the Software Supportability Program Standard, SAE JA1004, that describes, within a Plan-Case framework, what software supportability performance requirements are necessary. This document has general applicability to all sectors of industry and commerce and to all types of equipment whose functionality is to some degree implemented via software. It is intended to be guidance for business purposes and should be applied when it provides a value-added basis for the business aspects of development, use, and sustainment of support-critical software. Applicability of specific recommended practices will depend on the support-significance of the software, application domain, and life cycle stage of the software.

This SAE Recommended Practice provides recommended guidelines and best practices for implementing a supportability program to ensure that software is supportable throughout its life cycle. This Implementation Guide is the companion to the Software Supportability Program Standard, SAE JA1004, that describes, within a Plan-Case framework, what software supportability performance requirements are necessary. This document has general applicability to all sectors of industry and commerce and to all types of equipment whose functionality is to some degree implemented via software. It is intended to be guidance for business purposes and should be applied when it provides a value-added basis for the business aspects of development, use, and sustainment of support-critical software. Applicability of specific recommended practices will depend on the support-significance of the software, application domain, and life cycle stage of the software.

This SAE Standard defines the basic structural elements, and guidance on compilation and management, for a software supportability program. Software supportability considerations include initial design influence and through-life support embracing the operational use, post-delivery modification, and logistics management of software. This document requires that the processes of design, development, selection, and production of software include software supportability considerations, as relevant to particular project needs.

This SAE Standard defines the basic structural elements, and guidance on compilation and management, for a software supportability program. Software supportability considerations include initial design influence and through-life support embracing the operational use, post-delivery modification, and logistics management of software. This document requires that the processes of design, development, selection, and production of software include software supportability considerations, as relevant to particular project needs.