An overview and case study of a statistical regression testing method for software maintenance

Takagi, Toshihisa; Furukawa, Zengo; Yamasaki, Toshinori

doi:10.1002/ecjb.20414

Cited by 2 publications

(4 citation statements)

References 17 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In Musa (1994Musa ( , 1993 studies, the author assigns an occurrence probability to the execution categories in order to obtain a quantitative characterization of the software corresponding to the operational profile. The data used to get the occurrence probabilities of operation can be obtained from log files generated by previous version of the software or from similar software (Musa, 1993;Takagi et al, 2007). Developer expectations can also determine these probabilities (Takagi et al, 2007).…”

Section: Software Operational Profile (Sop)mentioning

confidence: 99%

“…The data used to get the occurrence probabilities of operation can be obtained from log files generated by previous version of the software or from similar software (Musa, 1993;Takagi et al, 2007). Developer expectations can also determine these probabilities (Takagi et al, 2007).…”

Section: Software Operational Profile (Sop)mentioning

confidence: 99%

“…It is worth noting that the frequency with which a fault becomes apparent during the software operation is more significant for users than the remaining faults (Takagi et al, 2007) and a defect affecting reliability for one user may never be revealed to another who has a different work routine (Sommerville, 2011). The use of SOP does not guarantee the de-tection of all faults, but it ensures that the most used software operations are tested (Ali-Shahid and Sulaiman, 2015).…”

Section: The Sop and The Software Qualitymentioning

confidence: 99%

“…Although the SOP can be obtained from log files recording events that occur in the operating software, in previous versions of the software, in similar software and even from the developers' experience (Musa, 1993;Takagi et al, 2007), there are several problems related to the identification of the SOP reported in the literature.…”

Section: Problems Related To the Use Of Sopmentioning

confidence: 99%

See 3 more Smart Citations

Software Operational Profile vs. Test Profile: Towards a Better Software Testing Strategy

Júnior

Morimoto

Fabbri

et al. 2020

JSERD

View full text Add to dashboard Cite

Software Operational Profile (SOP) is a software specification based on how users use the software. This specification corresponds to a quantitative representation of software that identifies the most used software parts. As software reliability depends on the context in which users operate the software, the SOP is used in software reliability engineering. However, there are evidences of a misalignment between the software tested parts and SOP. Therefore, this paper investigates a possible misalignment between SOP and the tested software parts to obtain, based on experimental data, more evidence of this misalignment. We performed an exploratory study composed of four activities to verify: a) whether there are significant variations in how users operate the software; b) whether there is a misalignment between SOP and the tested software parts; c) if failures occur in untested SOP parts in case of misalignment; d) in case of misalignment between SOP and untested software parts, whether a test strategy based on the amplification of the existent test set with additional test data generated automatically, can contribute to reduce the misalignment. We collected data form four software while users were operating them. We analyzed this collected data in an attempt to reach the goals of this work. To evaluate the originality of this research, we performed a Literature Systematic Review (SLR) and presented its conclusions. The obtained results evidence that there are significant variations in how users operate the software and also that there is a misalignment between SOP and the tested software parts when we evaluated the four software mentioned above. There are also indications of the occurrence of failures in the untested SOP parts. Although the test strategy mentioned above has reduced the possible misalignment, the test strategy is not enough to avoid it, thus denoting the need of specifics test strategies using SOP as a test criterion. These results indicate that SOP becomes relevant not only to software reliability engineering but also to contribute to testing activities, regardless of the adopted strategy.

show abstract