Operational Profiles in Software-Reliability Engineering
IEEE Software
Combining Testing and Correctness Verification in Software Reliability Assessment
HASE '97 Proceedings of the 2nd High-Assurance Systems Engineering Workshop
Impact of program transformation on software reliability assessment
HASE '96 Proceedings of the 1996 High-Assurance Systems Engineering Workshop
On reducing the sensitivity of software reliability to variations in the operational profile
ISSRE '96 Proceedings of the The Seventh International Symposium on Software Reliability Engineering
Operational profile specification, test case generation, and reliability estimation for modules
Operational profile specification, test case generation, and reliability estimation for modules
Adaptive Random Testing Through Dynamic Partitioning
QSIC '04 Proceedings of the Quality Software, Fourth International Conference
Systematic Operational Profile Development for Software Components
APSEC '04 Proceedings of the 11th Asia-Pacific Software Engineering Conference
An Extended Operational Profile Model
ISSRE '04 Proceedings of the 15th International Symposium on Software Reliability Engineering
Tool Support for Statistical Testing of Software Components
APSEC '05 Proceedings of the 12th Asia-Pacific Software Engineering Conference
| Hi-index | 0.00 |
An operational profile is a quantification of the expected use of a software component that is used for generating test cases in statistical testing. Previous work on operational profiles has concentrated on exploring the occurrence of operations and little has been said about operation parameters. The testing is meaningless if values for input parameters are not consistent according to the expected use. This paper presents a method for defining parameter characteristics by deriving constraints on and relationships between operation parameters. The parameter characteristics are then used to support generation of appropriate values for input parameters of operations. The method applies formal concept analysis using the component API to derive relationships between operations and parameters. Then the method uses these relationships, usage data and intended usage assumptions for defining characteristics of parameters. The method is illustrated on two Java classes but can be applied to any software component that is accessed through an API.