Identifying Error-Prone Software An Empirical Study
IEEE Transactions on Software Engineering
Handbook of software reliability engineering
Handbook of software reliability engineering
Handbook of software reliability engineering
Software maintenance—an industrial experience
Journal of Software Maintenance: Research and Practice
Journal of Software Maintenance: Research and Practice
Regression testing in an industrial environment
Communications of the ACM
Programmers use slices when debugging
Communications of the ACM
Art of Software Testing
Data-Centered Program Understanding
ICSM '94 Proceedings of the International Conference on Software Maintenance
Application of data-centered approach to Year 2000 problem
COMPSAC '97 Proceedings of the 21st International Computer Software and Applications Conference
Business Rule Extraction from Legacy Code
COMPSAC '96 Proceedings of the 20th Conference on Computer Software and Applications
Distributed End-to-End Testing Management
EDOC '01 Proceedings of the 5th IEEE International Conference on Enterprise Distributed Object Computing
Hi-index | 0.00 |
Reliability growth models, formal specifications, testing, safety analysis have been proposed to address system and software reliability. This paper presents a technique, called ripple effect analysis, which is well known in software maintenance, for system and software reliability. This technique is useful to ensure that all the changes that need to be done are indeed changed after a software modification. It is different from regression test of which the purpose is to show that those parts that should not be changed remain unchanged after a software modification. We have used this technique at Guidant-CPI and found ripple effect analysis is an effective technique for ensuring system and software reliability in developing safety-critical systems.