Software Reliability Training

Software Reliability Training by Tonex

Software reliability training covers all the concepts, tools, and methods to predict software reliability before writing the code. Software reliability training provides you with all the knowledge and techniques you need to practically apply software reliability in real world projects.

What is Software Reliability and Why is It Important?

Software reliability is the likelihood of software to operate without failure for a certain time frame under specific environmental conditions. Software reliability is a crucial factor that affects system reliability, both hardware and human factors. There are several methods and techniques to improve the reliability of software with an appropriate balance of time and budget. Also, high software reliability is significantly crucial in the area of cyber security.

Learn About

• Landscape of software reliability
• Software reliability processes
• Verification and validation strategy
• Software reliability standards
• FMEA, DFMEA and Software FMEA
• FMECA
• FTA
• Fault tolerance
• Robustness
• Operational and user profiles
• Integration and testing
• Root cause analysis
• Predicting software reliability
• Reliability growth models

Audience

Software reliability training is a 2-day course designed for:

• Reliability engineers
• Systems engineers
• Software managers
• Engineering managers
• Lead software engineers
• Software quality engineers
• Quality assurance engineers
• Software engineers and testers
• All individuals involved in measuring, analyzing, designing, automating, implementing or ensuring software reliability for either commercial or government programs

Training Objectives

Upon the completion of software reliability training, attendees are able to:

• Apply tools and approaches to develop failure free software
• Develop real world reliable software
• Derive software reliability standards suitable for their software and system
• Identify defects, failure rate, MTTF, MTTCF, availability, reliability and defect density of the software
• Determine the staffing needed for testing and field support
• Ensure that the software releases are spaced to minimize unscheduled maintenance that causes the next project to be late
• How to assess the reliability of vendor supplied software
• Apply solid software reliability techniques to improve their skills in developing software
• Apply FMEA to software
• Estimate costs associated with developing software
• Recommend economically feasible strategies for software reliability
• Collect software testing data
• Analyze the collected data
• Recognize the best practice of software reliability
• Conduct verification and validating
• Identify the failure modes, reliability trends, root failure causes and corrective actions for their software
• Estimate the vulnerability of their software against cyber attacks
• Improve the reliability, safety, and protection of their software

Course Outline

Overview

• History of software reliability
• Software reliability definition
• Software reliability terms
• Sources of software faults

Software Life Cycle

• Life cycle activities
• Life cycle models
• Fault, manpower and cost profiles over life cycle
• Software Development Life Cycles (SDLC)
• Development phases
• Verification and Validation
• Software inspection, demo, testing,  analysis
• What constitutes testing

Software Testing

• Definition of software testing
• Why Test?
• What composes testing?
• What to include in the test sample
• How to select the test sample
• How many inputs should be tested
• Limitations of testing

Software Safety Analysis

• The problem
• What can you learn from “n” successes?
• Extensions
• Applications

Factors Affecting Software Reliability

• Application type
• Methodologies
• Product characteristics
• Testing/verification
• Schedule
• Maintenance
• Operational/user profile

Overview of Software Reliability Models

• Types of software reliability models
• Nomenclature used in modeling
• Assumptions of the models

Data Required for Models

• Types of Data
• Minimum fault data needed
• Setting up data collection system
• Root-cause analyzing bad data

Software Reliability Prediction Models

• Prediction models
• Rome laboratory TR-92-52
• Rome laboratory TR-92-15
• Musa’s execution time model
• Putnam’s model
• Historical data collection

Software Reliability Estimation Models

• Objectives
• Types of Estimation Models
• Fault Count
  • Exponential
  • Shooman Model
  • Lloyd-Lipow Model
  • Musa’s Basic Model
  • Musa’s Logarithmic Model Goel-Okumoto Model
  • Historical Data Collection Model Weibull Models
• Test coverage model
  • IEEE test coverage model
  • Leone’s test coverage model
  • Test success model
• Tagging models
  • Seeding
  • Dual test group model
• Bayesian models
• Thompson and Chelson’s model
• Goodness of fit

Software Reliability Metrics

• Objectives
• Metrics to apply according to your process capability
• Metrics applied in industry
• Wrong-used metrics

Software Fault Trees

• Why Fault Tree is used?
• Applying fault trees to software

Software FMEAs

• Why FMEA is used?
• Applying FMEAs to software
• TONEX Software FMEA process and template

System Reliability Software Redundancy

• Series configuration
• Mission oriented
• Semi-Markov
• Parallel concurrent
• Voting redundancy

Improving Software Reliability

• Evaluating your product and process
• Techniques to improve software reliability

Managing Software Reliability

• Matrix of responsibilities
• Cost benefit of improvement

Numerical Reliability

• Framework reference
• Errors in a single arithmetic operation
• Computing errors for an entire computation

 Software Reliability Training