Search Results

In 1994, the SAE G-11 Reliability, Maintainability, Supportability and Logistics (RMSL) Division chartered a software committee, G-11SW, to create several software standards and guidance documents across the RMSL spectrum, including a software reliability program standard. The committee was formed as a cross section of international representatives from commercial industries and governments. The G-11SW committee has attempted to develop a standard that is consistent with a SAE G-11 system level reliability program standard and augmented by necessary software-specific support information. The G-11SW committee believes this document reflects the best current commercial practices, and meets the objectives of the United States Department of Defense Acquisition Reform initiative.

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 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

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

This standard requires the developers and customer/users working as a team to plan and implement a reliability program that provides systems/products that satisfy the user’s requirements and expectations. The user’s requirements and needs are expressed in the form of the following four reliability objectives: The developer shall solicit, investigate, analyze, understand and agree to the user’s requirements and product needs. The developer, working with the customer and user, shall include the activities necessary to ensure that the user’s requirements and product needs are fully understood and defined, so that a comprehensive design specification and Reliability Program Plan can be generated. The developer shall use well-defined reliability- and systems-engineering processes to develop, design, and verify that the system/product meets the user’s documented reliability requirements and needs.