On Fault Representativeness of Software Fault Injection
#1

The injection of software faults in software components to assess the impact of these faults on other components or on the system as a whole, allowing the evaluation of fault tolerance, is relatively new compared to decades of research on hardware fault injection. This paper presents an extensive experimental study (more than 3.8 millions of individual experiments in three real systems) to evaluate the representativeness of faults injected by a state-of-the-art approach (G-SWFIT). Results show that a significant share (up to 72%) of injected faults cannot be considered representative of residual software faults, as they are consistently detected by regression tests, and that representativeness of injected faults is affected by the fault location within the system, resulting in different distributions of representative/non-representative faults across files and functions. Therefore, we propose a new approach to refine the faultload by removing faults that are not representative of residual software faults. This filtering is essential to assure meaningful results and to reduce the cost (in terms of number of faults) of software fault injection campaigns in complex software. The proposed approach is based on classification algorithms, is fully automatic, and can be used for improving fault representativeness of existing software fault injection approaches.
Reply

Important Note..!

If you are not satisfied with above reply ,..Please

ASK HERE

So that we will collect data for you and will made reply to the request....OR try below "QUICK REPLY" box to add a reply to this page
Popular Searches: first fault identification and announcing system pdf, auto fault codes, wireless mcb fault detector, distributed systems fault tolerance, project on exact locations of fault ppt, software fault tolerance, huntsman fault indicators,

[-]
Quick Reply
Message
Type your reply to this message here.

Image Verification
Please enter the text contained within the image into the text box below it. This process is used to prevent automated spam bots.
Image Verification
(case insensitive)

Possibly Related Threads...
Thread Author Replies Views Last Post
  A Conceptual Overview of Service-Oriented Software Systems Development 1 841 14-02-2017, 03:38 PM
Last Post: jaseela123d
  Fault Secure Encoder and Decoder For NanoMemory Applications computer girl 2 2,929 25-02-2015, 07:17 AM
Last Post: Guest
Tongue Bug Tracking for Improving Software Quality and Reliability projectsofme 5 3,660 28-01-2013, 06:45 PM
Last Post: Guest
  Intra-Communication Software mechanical engineering crazy 3 4,422 28-11-2012, 11:11 AM
Last Post: seminar details
  PREVENTION OF SQL INJECTION AND DATA THEFTS USING DIVIDE AND CONQUER APPROACH seminar presentation 3 4,193 24-10-2012, 01:09 PM
Last Post: seminar details
  college management software mechanical engineering crazy 2 3,299 10-10-2012, 12:14 PM
Last Post: seminar details
  morpheus software project topics 1 1,952 26-07-2012, 05:42 PM
Last Post: [email protected]
  Hr2Payroll,Easy To Use Payroll Software for Businesses project report helper 1 1,516 06-06-2012, 02:25 PM
Last Post: Guest
  COMBINATORIAL APPROACH FOR PREVENTING SQL INJECTION ATTACKS electronics seminars 7 7,369 23-02-2012, 05:05 PM
Last Post: seminar paper
  An Adaptive Programming Model for Fault-Tolerant Distributed Computing electronics seminars 3 2,592 20-02-2012, 01:13 PM
Last Post: seminar paper

Forum Jump: