IEEE 1633-2016 PDF

IEEE 1633-2016 PDF

IEEE Recommended Practice on Software Reliability

$112.00 $224.00 -50%
isbn 9781504436496
Product Code: IEEE 1633
Stock In Stock
Published: 01/18/2017
Number of Pages: 248
File Size: 1 file, 9.3 MB

Available Options

Product Description

IEEE Recommended Practice on Software Reliability

Introduction: This introduction is not part of IEEE Std 1633-2016, IEEE Recommended Practice on Software Reliability. Software is, from a materials viewpoint, both malleable and ductile. This means there are multiple ways to introduce failures, intentional and un-intentional. Fixing a software defect can introduce a potential defect. In many cases the failures that result from software defects are both predictable and avoidable but they still occur because of the following: a) Lack of available calendar time/resources to find all of the defects that can result in failures b) Exceedingly complex event driven systems that are difficult to conceptualize and therefore implement and test c) Organizational culture that neglects to support sufficient rigor, skills, or methods required to find the defects d) Technical decisions that result in incorrect architecture or design decision that cannot support the stakeholders specifications e) Insufficient project or risk management that leads to schedule delays that lead to less time for reliability testing f) Operations—Contract issues, interoperability due to bad specifications and stakeholder communications Even a small number of software failures can lead to monetary catastrophes such as a cancelled project. Hardware (HW) failures can be random, due to wear-out or the result of a systematic design flaw. Reliability maintainability availability (RMA) is used to prevent and deal with hardware failures. Software failures may result from systematic fla

Contents:

  • 1.1 Scope
  • 1.2 Purpose
  • 3.1 Definitions
  • 3.2 Acronyms and abbreviations
  • 4.1 What is software reliability engineering?
  • 4.2 Strategy
  • 4.3 Project-specific SRE tailoring
  • 4.4 Life-cycle considerations for SRE
  • 5.1 Plan for software reliability
  • 5.2 Develop failure modes model
  • 5.3 Apply software reliability during development
  • 5.4 Apply software reliability during testing
  • 5.5 Support release decision
  • 5.6 Apply software reliability in operation
  • 6.1 Overview
  • 6.2 Models that can be used before testing
  • 6.3 Models that can be used during and after testing

Be the first to write a review for this product.

Write a review

Note: HTML is not translated!
Bad           Good
IEEE 1633-2016 PDF

IEEE 1633-2016 PDF

$112.00 $224.00