Operational profiles in software-reliability engineering
Abstract
A systematic approach to organizing the process of determining the operational profile for guiding software development is presented. The operational profile is a quantitative characterization of how a system will be used that shows how to increase productivity and reliability and speed development by allocating development resources to function on the basis of use. Using an operational profile to guide testing ensures that if testing is terminated and the software is shipped because of schedule constraints, the most-used operations will have received the most testing and the reliability level will be the maximum that is practically achievable for the given test time. For guiding regression testing, it efficiently allocates test cases in accordance with use, so the faults most likely to be found, of those introduced by changes, are the ones that have the most effect on reliability.>
Integrity signals
Registry
Cites
Statistics
Claims the paper makes
Claims other papers make about this one
Each is checked against this paper’s own text: does it say what the citing paper says it does?
Our prior work on testing software that relies on data management systems has focused on data errors, whereas this work focuses on testing fairness.
“Our prior work on testing software that relies on data management systems has focused on data errors [59, 60], whereas this work focuses on testing fairness.”
From Fairness testing: testing software for discrimination (2017) · cites this paper as [60]
Cites
Software Reliability: Measurement, Prediction, Application
Musa, D., Iannino, A., & Okumoto, K. (1987) · Cited by 1,675 · see citing works
Partition testing does not inspire confidence (program testing)
Hamlet, D., & Taylor, R. (1990) · IEEE Transactions on Software Engineering · doi:10.1109/32.62448 · Cited by 394 · see citing works
Performance analysis rat holes to avoid or how to stall a performance presentation
Musa, J. D. (1991) · ACM SIGSOFT Software Engineering Notes · doi:10.1145/127099.127119 · Cited by 8 · see citing works
Self-citationA software reliability engineering practice
Everett, W. W., & Musa, D. (1993) · Computer · doi:10.1109/2.204697 · Cited by 6 · see citing works
Flagged first, then by citations
Cited by
Sorted by citations
Fairness testing: testing software for discrimination
Galhotra, S., Brun, Y., & Meliou, A. (2017) · Proceedings of the 2017 11th Joint Meeting on Foundations of Software Engineering · doi:10.1145/3106237.3106277 · Cited by 405 · see citing works
Chiang, M.-C., Huang, C.-Y., Wu, C.-Y., & Tsai, C.-Y. (2021) · IEEE Transactions on Reliability · doi:10.1109/tr.2020.2968884 · Cited by 17 · see citing works
Software operational profile based test case allocation using fuzzy logic
Kumar, K. S., & Misra, R. B. (2007) · International Journal of Automation and Computing · doi:10.1007/s11633-007-0388-6 · Cited by 12 · see citing works
- Authors
- Musa, J. D.
- Venue
- IEEE Software
- Published
- 1993-03
- Volume
- 10
- Issue
- 2
- Pages
- 14-32
- ISSN
- 0740-7459 (ISSN-L)
- OpenAlex
- W2113004249
- Cited by
- 765
- References
- 4
- Citations by year
- 2026: 7 · 2025: 3 · 2024: 9 · 2023: 11 · 2022: 8 · 2021: 12 · 2020: 13 · 2019: 17 · 2018: 18 · 2017: 25 · 2016: 16 · 2015: 26 · 2014: 31 · 2013: 25 · 2012: 29
- FWCI
- 77.22
- Type
- journal article
- Language
- en
- Open access
- closed
- Locations
- IEEE Software (publishedVersion)
- Topics
- Physical Sciences › Computer Science › Software › Software Reliability and Analysis Research
- Physical Sciences › Computer Science › Software › Software Testing and Debugging Techniques
- Physical Sciences › Computer Science › Information Systems › Software Engineering Techniques and Practices
- Keywords
- operational profile, software reliability, software testing, regression testing, software productivity, fault detection
About these checks
Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.
Statistics and arithmetic are recomputed, not judged.
Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.
What counts as a claim ›How we measure confidence ›How we check this ›
Are you an author, or do you see a problem with this page? Request a review
