T
Thomas J. Ostrand
Researcher at Mälardalen University College
Publications - 55
Citations - 4983
Thomas J. Ostrand is an academic researcher from Mälardalen University College. The author has contributed to research in topics: Software system & Test case. The author has an hindex of 25, co-authored 55 publications receiving 4745 citations. Previous affiliations of Thomas J. Ostrand include AT&T Labs & AT&T.
Papers
More filters
Proceedings ArticleDOI
Experiments on the effectiveness of dataflow- and control-flow-based test adequacy criteria
TL;DR: An experimental study investigating the effectiveness of two code-based test adequacy criteria for identifying sets of test cases that detect faults found that tests based respectively on control-flow and dataflow criteria are frequency complementary in their effectiveness.
Journal ArticleDOI
The category-partition method for specifying and generating fuctional tests
Thomas J. Ostrand,M. J. Balcer +1 more
TL;DR: A method for creating functional test suites has been developed in which a test engineer analyzes the system specification, writes a series of formal test specifications, and then uses a generator tool to produce test descriptions from which test scripts are written.
Journal ArticleDOI
Predicting the location and number of faults in large software systems
TL;DR: A negative binomial regression model has been developed and used to predict the expected number of faults in each file of the next release of a system, based on the code of the file in the current release, and fault and modification history of thefile from previous releases.
Proceedings ArticleDOI
Where the bugs are
TL;DR: A negative binomial regression model using information from previous releases has been developed and used to predict the numbers of faults for a large industrial inventory system, and was extremely accurate.
Journal ArticleDOI
The distribution of faults in a large industrial software system
TL;DR: The ultimate goal of this study is to help identify characteristics of files that can be used as predictors of fault-proneness, thereby helping organizations determine how best to use their testing resources.