1SAS 03/ GSFC/SATC- NSWC-DD System and Software Reliability Dolores R. Wallace SRS Technologies Software Assurance Technology Center

Slides:



Advertisements
Similar presentations
Lecture 8: Testing, Verification and Validation
Advertisements

LaQuSo is an activity of Technische Universiteit Eindhoven Confidence intervals in software reliability testing Confidence intervals in software reliability.
Software Quality Assurance Plan
Chapter 4 Quality Assurance in Context
1 Exponential Distribution and Reliability Growth Models Kan Ch 8 Steve Chenoweth, RHIT Right: Wait – I always thought “exponential growth” was like this!
Software Reliability Engineering
1 The Role of the Revised IEEE Standard Dictionary of Measures of the Software Aspects of Dependability in Software Acquisition Dr. Norman F. Schneidewind.
Ask Pete Acquired Software Knowledge Project - Estimation- Tool - Effort Presented to the NASA OSMA SAS ‘01 NASA IV&V Facility September 5-7, 2001 Tim.
1 Software Reliability Growth Models Incorporating Fault Dependency with Various Debugging Time Lags Chin-Yu Huang, Chu-Ti Lin, Sy-Yen Kuo, Michael R.
1 Building with Assurance CSSE 490 Computer Security Mark Ardis, Rose-Hulman Institute May 10, 2004.
1 Software Testing and Quality Assurance Lecture 15 - Planning for Testing (Chapter 3, A Practical Guide to Testing Object- Oriented Software)
1 Validation and Verification of Simulation Models.
4-1 Statistical Inference The field of statistical inference consists of those methods used to make decisions or draw conclusions about a population.
Testing Metrics Software Reliability
SQA Architecture Software Quality.
West Virginia University A Bayesian Approach to Reliability Predication of Component Based Systems H. Singh, V. Cortellessa, B. Cukic, E. Gunel, V. Bharadwaj.
Software Verification and Validation (V&V) By Roger U. Fujii Presented by Donovan Faustino.
Elec471 Embedded Computer Systems Chapter 4, Probability and Statistics By Prof. Tim Johnson, PE Wentworth Institute of Technology Boston, MA Theory and.
Aaron Hoff. Overview Compare and hardware and software reliability Discuss why software should be reliable? Describe MLE (Maximum Likelihood Estimation)
Overview Software Quality Assurance Reliability and Availability
1 Prediction of Software Reliability Using Neural Network and Fuzzy Logic Professor David Rine Seminar Notes.
Software Project Management
Models for Software Reliability N. El Kadri SEG3202.
1 NASA OSMA SAS02 Software Reliability Modeling: Traditional and Non-Parametric Dolores R. Wallace Victor Laing SRS Information Services Software Assurance.
Software faults & reliability Presented by: Presented by: Pooja Jain Pooja Jain.
SENG521 (Fall SENG 521 Software Reliability & Testing Software Reliability Tools (Part 8a) Department of Electrical & Computer.
SQA Architecture Software Quality By: MSMZ.
1 Building and Maintaining Information Systems. 2 Opening Case: Yahoo! Store Allows small businesses to create their own online store – No programming.
SAS 03/ GSFC/SATC-ERAU-DoC Fault Tree Analysis Application for Safety and Reliability Massood Towhidnejad Embry-Riddle University Dolores Wallace & Al.
Slide 6.1 CHAPTER 6 TESTING. Slide 6.2 Overview l Quality issues l Nonexecution-based testing l Execution-based testing l What should be tested? l Testing.
Chapter 2 The process Process, Methods, and Tools
1 Using Excel to Implement Software Reliability Models Norman F. Schneidewind Naval Postgraduate School 2822 Racoon Trail, Pebble Beach, California, 93953,
Software Inspection A basic tool for defect removal A basic tool for defect removal Urgent need for QA and removal can be supported by inspection Urgent.
Software Reliability SEG3202 N. El Kadri.
Appraisal and Data Mining of Large Size Complex Documents Rob Kooper, William McFadden and Peter Bajcsy National Center for Supercomputing Applications.
What is a Business Analyst? A Business Analyst is someone who works as a liaison among stakeholders in order to elicit, analyze, communicate and validate.
Product Metrics An overview. What are metrics? “ A quantitative measure of the degree to which a system, component, or process possesses a given attribute.”
1 Software Reliability Assurance for Real-time Systems Joel Henry, Ph.D. University of Montana NASA Software Assurance Symposium September 4, 2002.
Current and Future Applications of the Generic Statistical Business Process Model at Statistics Canada Laurie Reedman and Claude Julien May 5, 2010.
Ch. 1.  High-profile failures ◦ Therac 25 ◦ Denver Intl Airport ◦ Also, Patriot Missle.
1 Reliability-Sept2001 Software Reliability Through Hardware Reliability Dolores R. Wallace SRS Information Services Software Assurance Technology Center.
Historical Aspects Origin of software engineering –NATO study group coined the term in 1967 Software crisis –Low quality, schedule delay, and cost overrun.
Development of Methodologies for Independent Verification and Validation of Neural Networks NAG OSMA-F001-UNCLASS Methods and Procedures.
Enabling Reuse-Based Software Development of Large-Scale Systems IEEE Transactions on Software Engineering, Volume 31, Issue 6, June 2005 Richard W. Selby,
Software Testing and Quality Assurance Practical Considerations (4) 1.
Fault Tolerance Benchmarking. 2 Owerview What is Benchmarking? What is Dependability? What is Dependability Benchmarking? What is the relation between.
Estimating “Size” of Software There are many ways to estimate the volume or size of software. ( understanding requirements is key to this activity ) –We.
Effort Estimation In WBS,one can estimate effort (micro-level) but needed to know: –Size of the deliverable –Productivity of resource in producing that.
Software Engineering1  Verification: The software should conform to its specification  Validation: The software should do what the user really requires.
1 NASA OSMA SAS02 Software Fault Tree Analysis Dolores R. Wallace SRS Information Services Software Assurance Technology Center
Software Quality Assurance SOFTWARE DEFECT. Defect Repair Defect Repair is a process of repairing the defective part or replacing it, as needed. For example,
1 Experience from Studies of Software Maintenance and Evolution Parastoo Mohagheghi Post doc, NTNU-IDI SEVO Seminar, 16 March 2006.
1 Overview of Maintenance CPRE 416-Software Evolution and Maintenance-Lecture 3.
Smart Home Technologies
1 SAS 04/ GSFC/SATC-NSWCDD System and Software Reliability Technical Presentation Naval Surface Warfare Center Dahlgren Division Software Assurance Technology.
1 Object-Oriented Analysis and Design with the Unified Process Figure 13-1 Implementation discipline activities.
Software Reliability Estimates/ Projections, Cumulative & Instantaneous Presented by Dave Dwyer With help from: Ann Marie Neufelder, John D. Musa, Martin.
SAS_08_Legacy_Safety_Hill Assurance and Recertification of Safety Critical Software In Legacy Systems Janie Hill NASA Kennedy Space Center, Florida
Main Title Slide Software Reliability Estimates/ Projections, Cumulative & Instantaneous - Dave Dwyer With help from: Ann Marie Neufelder, John D. Musa,
Testing Overview Software Reliability Techniques Testing Concepts CEN 4010 Class 24 – 11/17.
SwCDR (Peer) Review 1 UCB MAVEN Particles and Fields Flight Software Critical Design Review Peter R. Harvey.
6/6/ SOFTWARE LIFE CYCLE OVERVIEW Professor Ron Kenett Tel Aviv University School of Engineering.
What is a software? Computer Software, or just Software, is the collection of computer programs and related data that provide the instructions telling.
Week#3 Software Quality Engineering.
IEEE Std 1074: Standard for Software Lifecycle
Software Reliability Models.
Gerald Dyer, Jr., MPH October 20, 2016
COCOMO Models.
Estimating the number of components with defects post-release that showed no defects in testing C. Stringfellow A. Andrews C. Wohlin H. Peterson Jeremy.
Confidence intervals in software reliability testing
Presentation transcript:

1SAS 03/ GSFC/SATC- NSWC-DD System and Software Reliability Dolores R. Wallace SRS Technologies Software Assurance Technology Center / Dr. William H. Farr, Dr. John R. Crigler Naval Surface Warfare Center Dahlgren Division / NASA OSMA SAS '03

2SAS 03/ GSFC/SATC- NSWC-DD Overview of the Problem Reliability Measurement is a critical objective for NASA systems Systems are assessed from the software/hardware/systems perspective Methodologies for hardware reliability assessment have been developed and utilized over the past several decades Methodologies for software reliability assessment have been developed since the 70’s and have been utilized over the last twenty years Methodologies for system reliability assessment have only been addressed over the last 10 years with little application experience Need for a tool that integrates all aspects of reliability data (software, hardware, and systems perspectives)

3SAS 03/ GSFC/SATC- NSWC-DD Project Objectives Enhance the capability for NASA to assess software reliability by identifying and incorporating recent models into the tool Statistical Modeling and Estimation of Reliability Functions for Systems (SMERFS^3) –First Year Initiative –Perform a detailed literature search (1990 and beyond) Enhance the capability for NASA to assess system reliability by updating SMERFS^3 –Second Year Initiative –Identify system models for incorporation Apply the identified methodologies to project data sets within the NASA/DoD environments

4SAS 03/ GSFC/SATC- NSWC-DD FY03 Research Plan Literature search Selection of new models Build new models into SMERFS^3 Test new models with Goddard project data Make latest version of SMERFS^3 available

5SAS 03/ GSFC/SATC- NSWC-DD Literature Search Articles from 1990 forward Journals - sample – IEEE TSE – IEEE Reliability – Software Testing, Verification, and Reliability – IEEE Software – IEEE Computer Conferences – ISSRE – ICSE – Reliability & Maintainability – High-Assurance Systems Eng. – Various others Model selection criteria – Model assumptions – Fit within current SMERFS^3 – Type of system – Data availability Domain Experts

6SAS 03/ GSFC/SATC- NSWC-DD Characteristics of the Software Based Systems Software – Real-time – Large-scale – Time-critical – Embedded – Maybe heavy COTS – Distributed System – Safety-critical components – Heterogeneous – Fault tolerant – Costly to develop – Long lifetime, evolutionary

7SAS 03/ GSFC/SATC- NSWC-DD SMERFS^3 Current Version features: –6 software reliability models –2D, 3D plots of input data, fit into each model –Various reliability estimates –User queries for predictions Updates constraints: –Employ data from integration, system test, or operational phase –Use existing graphics of SMERFS^3 –Integrate with existing user interfaces, goodness-of-fit tests, and prediction capabilities

8SAS 03/ GSFC/SATC- NSWC-DD Available Data Large GSFC project, but confidentiality required GSFC person invaluable in explaining the system and the data Several subsystems Data flat files – much effort into spreadsheet/database Operational failures only Remove specific faults and sort others Apply IntervalCounter Bottom line: organizing data required substantial effort – minimized if project person prepared the data

9SAS 03/ GSFC/SATC- NSWC-DD Identified Models Hypergeometric Schneidewind (enhancements) Log-logistic Extended Execution Time (EET) The first two models require error count failure data; the last two require time-between-failure data Only error count data has been captured in the GSFC project database available for analysis Hence, software reliability additions to SMERFS^3 in this task will be limited to the hypergeometric model and the metrics enhancements to the Schneidewind model

10SAS 03/ GSFC/SATC- NSWC-DD Hypergeometric Model Assumptions Test instance, t(i): A collection of input test data. N: Total number of initial faults in the software. Faults detected by a test instance are removed before the next test instance is exercised No new fault is inserted into the software in the removal of the detected fault. A test instance t(i) senses w(i) initial faults. w(i) may vary with the condition of test instances over i. It is sometimes referred to in the authors' papers as a "sensitivity" factor. The initial faults actually sensed by t(i) depend upon t(i) itself. The w(i) initial faults are taken randomly from the N initial faults.

11SAS 03/ GSFC/SATC- NSWC-DD Meets many of our selection criteria: –Data type –Fits within the framework of the SMERFS^3 software –Research shows that it appears to perform well against other models Allows for testing intensity factor (for example: number of test cases, number of testing personnel, debug time ) Scheduled for implementation in the last quarter of FY03 Hypergeometric Model

12SAS 03/ GSFC/SATC- NSWC-DD Schneidewind Model There are three versions: –Model 1: All of the fault counts for each testing period are treated the same. –Model 2: Ignore the first s-1 testing periods and their associated fault counts. Only use the data from s to n. –Model 3: Combine the fault counts of the intervals 1 to s-1 into the first data point. Thus there are s+1 data points.

13SAS 03/ GSFC/SATC- NSWC-DD Schneidewind Assumptions The number of faults detected in each of the respective intervals are independent. The fault correction rate is proportional to the number of faults to be corrected. The intervals over which the software is tested are all taken to be of the same length. The cumulative number of faults by time t, M(t), follows a Poisson process with mean value function μ(t). The mean value function is such that the expected number of fault occurrences for any time period is proportional to the expected number of undetected faults at that time. The failure intensity function, λ(t), is assumed to be an exponentially decreasing function of time; that is, λ(t)=αexp(-βt) for some α, β > 0.

14SAS 03/ GSFC/SATC- NSWC-DD Meets many of our selection criteria: –Data type –Basic model already in the SMERFS^3 software –It has been shown to perform well against other models Allows learning curve effect Updates are being implemented this quarter –Risk measures Operational quality at time t Risk criterion metric for the remaining faults at time t Risk criterion metric for the time to next failure at time t –Confidence intervals Schneidewind Model Enhancements

Data Analysis of NASA Three Month Fault Counts

17SAS 03/ GSFC/SATC- NSWC-DD Proposed Next Steps FY03 – Focused on software –Complete implementation and testing –Prepare paper describing the research and model selection, implementation, conclusions Apply the enhancements on the Goddard data set –Prepare SMERFS^3 for distribution FY04 –Conduct similar research effort for System Reliability University of Connecticut will participate –Enhance and validate system models