IEEE 1633 Software Reliability Engineering (SRE) Training

IEEE 1633 Software Reliability Engineering (SRE) Training

The IEEE 1633 software reliability engineering (SRE) standard is rather involved, however, one very important part focuses on how each software reliability program should precisely define the conditions under which the software will operate as well as what constitutes an “unreliable” event (software failure).

These definitions are necessary for ensuring process consistency and fostering a common understanding among the vendors, contracting officers, and acquisition program personnel.

Consequently, products and deliverables should be using these terms in a manner consistent with the formal program definitions. For example, guidance in both DoD and DHS calls for Test and Evaluation Master Plans (TEMPs) to include failure definitions and scoring criteria.

Today IEEE 1633 is a recommended practice that basically defines the software reliability engineering (SRE) processes, prediction models, growth models, tools, and practices of an organization. Organizations that acquire software subsystems or products developed with consideration to standard IEEE 1633 will benefit by knowing the reliability of the software before acquisition.

IEEE 1633 provides information necessary for the application of software reliability (SR) measurement to a project, lays a foundation for building consistent methods, and establishes the basic principle for collecting the data needed to assess and predict the reliability of software.

IEEE 1633 also prescribes how any user can participate in SR assessments and predictions.

The need for a software reliability engineering standard like IEEE 1633 is well documented. Software failure rates are a function of the development process used. The more comprehensive and better the process is, the lower the fault density of the resulting code.

Experts in this area say there is an intuitive correlation between the development process used and the quality and reliability of the resulting. The software development process is largely an assurance and bug removal process, and 80% of the development effort is spent removing bugs.

According to IEEE, the largest technical professional organization in the world for the advancement of technology, IEEE 1633’s models and tools are useful to any development organization to identify the methods, equations, and criteria for quantitatively assessing the reliability of a software or firmware subsystem or product.

IEEE 1633 Software Reliability Engineering (SRE) Training Course by Tonex

IEEE 1633 Software Reliability Engineering (SRE) Training  is a 3-day practical training program focusing on advantages of IEEE 1633-2016, IEEE Recommend Practices for Software Reliability.

IEEE 1633 Software Reliability Engineering (SRE) Training Course will cover the key features of Recommended Practices for software reliability.

Who Should Attend?

• Software engineers and managers to enhance their knowledge and skills in methods to predict software reliability
• Reliability engineers new to software development
  Project managers involved in software releases and maintenance
• Acquisition professionals to assess and validate reliability of software packages and vendor supplied software
• Technical, operation and support staffing needed for testing and field support
• Anyone else who requires guidance and tools to apply software reliability models

Learning Objectives

Participants will learn about:

• Tonex  Recommended Practices for Software Reliability
• Best practices applied to IEEE 1633
• Recommended Practice for Software Reliability
• Best practices and checklist
• Compare and contrast Software FMEA (SFMEA) and Software Fault Tree Analysis (SFTA)
• Applied to software lifecycle model
• Tools for predicting software reliability

Course Content and Agenda

Executive Software Reliability Overview

• Fundamental Software Quality/Reliability Definitions
• Software Reliability (SR), Software Reliability Engineering (SRE) And Software Quality (SQ)
• Software Defects, Faults
• Failures Vs. Problems
• Examples and Case Study 1

Introduction to Software Reliability Engineering (SRE)

• Software Requirements, Design, Production, Verification and Validation
• Software Development Plan (SDP)
• Software Verification Plan (SVP)
• Software Quality Assurance Plan (SQAP)
• Software Configuration Management Plan (SCMP)
• Software Reliability and System Reliability
• Software Reliability Modeling Principles
• Techniques for Prediction Analysis
• Software Failure Modes and Root Causes
• Functional Failure Modes
• Interface Failure Modes
• Detailed Design Failure Modes
• Maintenance Failure Modes
• Usability Failure Modes
• Serviceability Failure Modes
• Vulnerability Failure Modes
• Process Failure Modes
• Software Operational Profile
• Principles of Software Reliability Engineering (SRE)
• Software Development Life Cycle, Including Software Specifications, Software Design, Software Coding, And Software Testing
• Cost Analysis Of SRE
• Example of SRE Tools
• Purpose of The Software FMEA and FTA
• Software Failure Modes and Effects Analysis (SFMEA)
• Software Fault Tree Analysis (SFTA)
• Examples and Case Study 2

Safety-Critical Software

• Software Reliability & Safety
• Software Failures
• Software Reliability
• Reliability Allocation
• Defining and Analyzing Operational Profiles

Software Reliability Program and Project Management

• Software Reliability Projects and Tasks
• Planning for Software Reliability
• SRE During Software Development Phases
• Working With SFMEA, FMEAs and SFTA
• SRE During Testing (Verification and Validation)
• Developing Software Failure Modes
• Role of Software Reliability in Operation and Maintenance
• Reliability Data Collection & Analysis
• Reliability Modeling & Prediction Management
• Parts Control Programs
• Parts Qualification
• Failure Reporting and Corrective Action Systems (Fracas)
• Failure Mode, Effects and Criticality Analysis (FMECA)
• Fault Tree Analysis (FTA)
• Reliability Centered Maintenance (RCM)
• Reliability/maintainability Test Planning & Control

Software Failure Mode and Effect Analysis (SFMEA)

• FMEA Applied to Software Development
• Software Failure Mode Analysis
• Process Variation Elimination
• Applications
• Control Plan
• Mitigation Techniques
• Documentation

Build Software Fault Tree (FTA)

• Software Fault and Failures
• Role of Software in a System Fault Tree Analysis or Quantitative Hazard Analysis
• Fault Tree with OR, AND, K-out-of-N (voting) gates and different types of basic events, including Evident, Latent, External, Repairable and Unrepairable
• Calculate Fault Tree probability/unavailability (including events and intermediary gate probabilities) for Mission time (with defined mission duration) or for Steady-state mode

Workshop 1: Developing Software FMEA and FTA

• Faulty Functionality, Sequencing, Timing, Output and Undesired Outputs
• Tools to Analyze Embedded Software Reliability
• Mapping Software to Hardware Reliability
• Using Tools to Perform Software Failures Modes Effects Analysis (FMEA)
• Using Software in a System Fault Tree Analysis (FTA)

IEEE 1633 Software Reliability Engineering (SRE) Training