Software Reliability Program Implementation Guide

Standard [CURRENT]

SAE JA 1003:2012-05-07

Software Reliability Program Implementation Guide

Publication date
2012-05-07
Original language
English
Pages
176

209.70 EUR VAT included

195.98 EUR VAT excluded

Format and language options

PDF download
  • 209.70 EUR

Shipment (3-5 working days)
  • 209.70 EUR

Monitor with the Standards Ticker

This option is only available after login.
Easily subscribe: Save time and money now!

You can also subscribe to this document - together with other important standards in your industry. This makes your work easier and pays for itself after a short time.

Sparschwein_data
Subscription advantages
Sparschwein Vorteil 1_data

Important standards for your industry, regularly updated

Sparschwein Vorteil 2_data

Much cheaper than buying individually

Sparschwein Vorteil 3_data

Useful functions: Filters, version comparison and more

Publication date
2012-05-07
Original language
English
Pages
176
Loading recommended items...

Quick delivery via download or delivery service

Buy securely with a credit card or pay upon receipt of invoice

All transactions are encrypted

Short description

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. Applicability of specific practices will depend on the reliability-significance of the software, application domain, and life cycle stage of the software. Following guidelines in this document does not guarantee required reliability will be achieved, or that any certification authority will accept the results as sufficient evidence that requisite reliability has been achieved. Following guidelines in this document will provide insight into what level of reliability has been achieved. With proper customer, certification authority, and supplier negotiation and interaction in accordance with these guidelines, it is more likely that the achieved reliability will be acceptable.
Loading recommended items...