• Complain

Sandeep Kumar - Software Fault Prediction A Road Map

Here you can read online Sandeep Kumar - Software Fault Prediction A Road Map full text of the book (entire story) in english for free. Download pdf and epub, get meaning, cover and reviews about this ebook. year: 2018, publisher: Springer, genre: Computer. Description of the work, (preface) as well as reviews are available. Best literature library LitArk.com created for fans of good reading and offers a wide selection of genres:

Romance novel Science fiction Adventure Detective Science History Home and family Prose Art Politics Computer Non-fiction Religion Business Children Humor

Choose a favorite category and find really read worthwhile books. Enjoy immersion in the world of imagination, feel the emotions of the characters or learn something new for yourself, make an fascinating discovery.

Sandeep Kumar Software Fault Prediction A Road Map

Software Fault Prediction A Road Map: summary, description and annotation

We offer to read an annotation, description, summary or preface (depends on what the author of the book "Software Fault Prediction A Road Map" wrote himself). If you haven't found the necessary information about the book — write in the comments, we will try to find it.

This book focuses on exploring the use of software fault prediction in building reliable and robust software systems. It is divided into the following chapters: Chapter 1 presents an introduction to the study and also introduces basic concepts of software fault prediction. Chapter 2 explains the generalized architecture of the software fault prediction process and discusses its various components. In turn, Chapter 3 provides detailed information on types of fault prediction models and discusses the latest literature on each model. Chapter 4 describes the software fault datasets and diverse issues concerning fault datasets when building fault prediction models. Chapter 5 presents a study evaluating different techniques on the basis of their performance for software fault prediction. Chapter 6 presents another study evaluating techniques for predicting the number of faults in the software modules. In closing, Chapter 7 provides a summary of the topics discussed.The book will be of immense benefit to all readers who are interested in starting research in this area. In addition, it offers experienced researchers a valuable overview of the latest work in this area.

Sandeep Kumar: author's other books


Who wrote Software Fault Prediction A Road Map? Find out the surname, the name of the author of the book and a list of all author's works by series.

Software Fault Prediction A Road Map — read online for free the complete book (whole text) full work

Below is the text of the book, divided by pages. System saving the place of the last page read, allows you to conveniently read the book "Software Fault Prediction A Road Map" online for free, without having to search again every time where you left off. Put a bookmark, and you can go to the page where you finished reading at any time.

Light

Font size:

Reset

Interval:

Bookmark:

Make
The Author(s) 2018
Sandeep Kumar and Santosh Singh Rathore Software Fault Prediction SpringerBriefs in Computer Science
1. Introduction
Sandeep Kumar 1
(1)
Department of Computer Science and Engineering, Indian Institute of Technology Roorkee, Roorkee, India
(2)
Department of Computer Science and Engineering, National Institute of Technology Jalandhar, Jalandhar, India
Sandeep Kumar (Corresponding author)
Email:
Santosh Singh Rathore
Email:
Nowadays, software is the key element of function in many modern engineered systems. It can be found in a variety of applications from the refrigerators to cars to the washing machine, etc. Due to the advancement of technology brought about by the IT industry, the significance of the field of software engineering has been continuously increasing. In this growing number of applications of software, one vital challenge is to ensure that system is matching with the quality specifications and is reliable to use. The quality of the software determines its value and reliability ensures the failure-free operation of software for a specified period of time in the given environmental conditions. Quality and reliability of the software depend on the software faults. The more the faults, the lesser the reliability of the software and more efforts are required to maintain the quality of the software. Software quality assurance (SQA) can be thought as an umbrella activity, which incorporates various activities to organize and monitor the software development process and ensure that the final software product is of higher quality and reliability (Menzies et al. ). However, SQA is a time-consuming process and requires an ample amount of resources.
Software fault prediction ( SFP) can be used to help in allocating limited SQA resources in a cost-effective and optimized manner by predicting the fault-proneness of software modules before the testing. It is a process to predict the fault-prone software modules without executing them by using some underlying characteristics of the given software system. A typical fault prediction model is built by training a learning technique for the dataset having some structural properties together with the fault information for a known project. The trained prediction models are subsequently used to predict fault-proneness of the unknown software project (Arisholm et al. ). The quick and early identification of the faulty modules as a result of using software fault prediction can be utilized by the tester or developer to better strategize the software quality assurance efforts.
The lure of early detection of faults and improving the quality of the system has attracted considerable attention of research community to the software fault prediction . A wide range of statistical and machine learning techniques has been used earlier to build the fault prediction models and to predict the fault-proneness of currently developing software system. Moreover, the availability of open-source and publicly accessible software fault dataset repositories such as NASA Metrics Data Program and PROMISE data repository (PROMISE ) is allowing researchers to undertake more investigations and is opening up new areas of applications.
1.1 Software Faults, Errors, and Failure Terminologies
Software fault can arise in any phase of the software development including requirements gathering and specifications, designs, code, or maintenance. Depending upon the origin of the fault, the nature of the fault differs. The faults that are translated into the code of the software may lead to system failure , if not identified and removed correctly. Errors , defects, faults, and failures are interrelated terms and often created misunderstanding in their definitions (Huizinga and Kolawa ). Here, we follow the IEEE standard 610-1990 to define these terms.
  • Error : A human action that produces an incorrect result.
  • Ex. main()
  • {
  • //some code
  • 1. If (a! = b)
  • 2. {
  • 3. c = (a/b);
  • 4. }
  • //other functionality
  • }
If programmer misses the semicolon at the end of the third line of code and compiles the program, then an error message will occur. This type of mistake called error.
Bug : An unexpected result or deviation in actual functionality found out by an author (who wrote the code) after compilation of program and during any testing phase is called bug.
Ex. In the above program, if the author uses some other variable like d instead of b at third line or uses + operator instead / operator, then no compilation error occurs but it produces some unexpected results. This is called bug.
Exception : An unhandled error occurring at run-time of the program is called exception.
Ex. There is no error generated at the compilation time, but at the run-time it throws an exception for b = 0 (third line).
Fault : An incorrect step, process, or data definition in a computer program that causes the program to perform in an unanticipated manner. It is commonly known as defect also and generally found by moderator (not an author of code).
Ex. In the above program, if the author uses some other variable like d instead of b at third line or uses + operator instead / operator, then no compilation error occurs but it produces some unexpected results and this issue is found by moderator. This is called fault or defect.
Failure : The inability of a software or software component to perform its required functions within specified performance requirements. In other words, the software does not do what the requirements describe.
Ex. Due to the fault occurrence, if any other part of code or module gets affected, this condition is called failure .
Software faults are different from software failures. Software faults are an indication of a quality attribute that explains a condition that the software fails to perform its desired functions. While, software failures are the symptoms, revealed when one or more software faults are executed.
1.2 Benefits of Software Fault Prediction
The potential of software fault prediction to identify the area of code where faults are more likely to occur has drawn a considerable attention of the research community. This early identification of faults can help software testers or developers to narrow down in the risky areas of software design to optimize and prioritize the testing efforts and resources. For example, if there are only limited amount of testing resource left to perform testing, knowing what are the most risky modules in the software system can certainly helpful to the testers to narrow down the testing efforts. Following are some benefits of using software fault prediction in software development process:
  1. (1)
    Advantage in testing cost reduction : In 2013, (Monden et al. ) reported a study where authors shared the experience of applying fault prediction model for ABB Inc. software system. The study showed that modules ranked as fault-prone by the software fault prediction model helped the testers to detect additional faults in the modules that were considered previously to be a low fault-prone. Additionally, modules identified by testers as the most fault-prone are among the top four fault-prone modules identified by the software prediction model.
  2. (2)
    Advantages in early flaw detection in software design : (Jiang et al. ).
  3. (3)
    Advantage in the development of highly dependable system : Use of software fault prediction in software quality assurance activity helps the practitioners to uncover risky areas of the software system that may not be reachable by the regular testing process. In such way, it helps in increasing the robustness of the software system.
Next page
Light

Font size:

Reset

Interval:

Bookmark:

Make

Similar books «Software Fault Prediction A Road Map»

Look at similar books to Software Fault Prediction A Road Map. We have selected literature similar in name and meaning in the hope of providing readers with more options to find new, interesting, not yet read works.


Reviews about «Software Fault Prediction A Road Map»

Discussion, reviews of the book Software Fault Prediction A Road Map and just readers' own opinions. Leave your comments, write what you think about the work, its meaning or the main characters. Specify what exactly you liked and what you didn't like, and why you think so.