NDLI: When to stop testing software? A fuzzy interval approach

Content Provider	IEEE Xplore Digital Library
Author	Gemoets, L. Kreinovich, V. Melendez, H.
Copyright Year	1994
Description	Author affiliation: Dept. of Decision & Inf. Eng., Texas Univ., El Paso, TX, USA (Gemoets, L.)
Abstract	the experience of many programmers shows that it is actually impossible to extract all the faults from system-type software, that is commonly involved in resource contention, or from the programs with a sophisticated user interface. Also, it is necessary to estimate the time interval during which the remaining faults will not influence the program. This problem is vital for estimating the cost of the software project. At present about three dozen statistical models (called software reliability models) are used to get such estimates. However, these statistical models lack convincing theoretical-explanation. They are semi-heuristic, and often look like curve-fitting. In this paper, we consider a fuzzy approach to program testing. We formulate the problem of choosing the best fuzzy software reliability model as a mathematical optimization problem, and solve this problem.<>
Starting Page	182
Ending Page	186
File Size	511613
Page Count	5
File Format	PDF
ISBN	0780321251
DOI	10.1109/IJCF.1994.375102
Language	English
Publisher	Institute of Electrical and Electronics Engineers, Inc. (IEEE)
Publisher Date	1994-12-18
Publisher Place	USA
Access Restriction	Subscribed
Rights Holder	Institute of Electrical and Electronics Engineers, Inc. (IEEE)
Subject Keyword	Software testing Software reliability Computer science Information systems Computer errors Error correction Programming profession Software systems User interfaces Debugging
Content Type	Text
Resource Type	Article

Sl.	Authority	Responsibilities	Communication Details
1	Ministry of Education (GoI), Department of Higher Education	Sanctioning Authority	https://www.education.gov.in/ict-initiatives
2	Indian Institute of Technology Kharagpur	Host Institute of the Project: The host institute of the project is responsible for providing infrastructure support and hosting the project	https://www.iitkgp.ac.in
3	National Digital Library of India Office, Indian Institute of Technology Kharagpur	The administrative and infrastructural headquarters of the project	Dr. B. Sutradhar bsutra@ndl.gov.in
4	Project PI / Joint PI	Principal Investigator and Joint Principal Investigators of the project	Dr. B. Sutradhar bsutra@ndl.gov.in Prof. Saswat Chakrabarti will be added soon
5	Website/Portal (Helpdesk)	Queries regarding NDLI and its services	support@ndl.gov.in
6	Contents and Copyright Issues	Queries related to content curation and copyright issues	content@ndl.gov.in
7	National Digital Library of India Club (NDLI Club)	Queries related to NDLI Club formation, support, user awareness program, seminar/symposium, collaboration, social media, promotion, and outreach	clubsupport@ndl.gov.in
8	Digital Preservation Centre (DPC)	Assistance with digitizing and archiving copyright-free printed books	dpc@ndl.gov.in
9	IDR Setup or Support	Queries related to establishment and support of Institutional Digital Repository (IDR) and IDR workshops	idr@ndl.gov.in

Types, distribution, and test and correction times for programming errors

Effect of fault dependency and debugging time lag on software error models

Debugging On DDP Environment

A Study of Modified Testing-Based Fault Localization Method

Program result-checking: a theory of testing meets a test of theory

Cognitive activities and support in debugging

Hard-to-detect errors due to the assembly-language environment

Assertions in end-user software engineering: a think-aloud study

Hints on Test Data Selection: Help for the Practicing Programmer

When to stop testing software? A fuzzy interval approach

Similar Documents

Types, distribution, and test and correction times for programming errors

Effect of fault dependency and debugging time lag on software error models

Debugging On DDP Environment

A Study of Modified Testing-Based Fault Localization Method

Program result-checking: a theory of testing meets a test of theory

Cognitive activities and support in debugging

Hard-to-detect errors due to the assembly-language environment

Assertions in end-user software engineering: a think-aloud study

Hints on Test Data Selection: Help for the Practicing Programmer

When to stop testing software? A fuzzy interval approach