The Operational Profile

Musa, John D.; Fuoco, Gene; Irving, N. S.; Kropfl, D.; Juhlin, B.D.

doi:10.1007/978-3-662-03274-9_18

Cited by 60 publications

(28 citation statements)

References 3 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In other words, rather than using an equal weighting when averaging the failure rates of each MuT in an OS, the average could instead be weighted by relative execution frequency for a ªtypicalº program or set of programs. This approach corresponds to a simple version of operational profiles as used in traditional software testing [27].…”

Section: Failure Rates Weighted By Operational Profilementioning

confidence: 99%

The exception handling effectiveness of POSIX operating systems

Koopman

DeVale

2000

IIEEE Trans. Software Eng.

View full text Add to dashboard Cite

AbstractÐOperating systems form a foundation for robust application software, making it important to understand how effective they are at handling exceptional conditions. The Ballista testing system was used to characterize the handling of exceptional input parameter values for up to 233 POSIX functions and system calls on each of 15 widely used operating system (OS) implementations. This identified ways to crash systems with a single call, ways to cause task hangs within OS code, ways to cause abnormal task termination within OS and library code, failures to implement defined POSIX functionality, and failures to report unsuccessful operations. Overall, only 55 percent to 76 percent of the exceptional tests performed generated error codes, depending on the operating system being tested. Approximately 6 percent to 19 percent of tests failed to generate any indication of error despite exceptional inputs. Approximately 1 percent to 3 percent of tests revealed failures to implement defined POSIX functionality for unusual, but specified, situations. Between 18 percent and 33 percent of exceptional tests caused the abnormal termination of an OS system call or library function, and five systems were completely crashed by individual system calls with exceptional parameter values. The most prevalent sources of these robustness failures were illegal pointer values, numeric overflows, and end-of-file overruns. There is significant opportunity for improving exception handling within OS calls and especially within C library functions. However, the role of signals vs. error return codes is both controversial and the source of divergent implementation philosophies, forming a potential barrier to writing portable, robust applications.

show abstract

Section: Failure Rates Weighted By Operational Profilementioning

confidence: 99%

The exception handling effectiveness of POSIX operating systems

Koopman

DeVale

2000

IIEEE Trans. Software Eng.

View full text Add to dashboard Cite

show abstract

“…Domain experts determine probabilities of occurrence of use cases and the scenarios within each use case. This can be done in a similar fashion as the estimation of the operational profile in the field of software reliability [21]. For the pacemaker example, according to [8], the inhibit modes are more frequently used than the triggered mode.…”

Section: The Use Case Modelmentioning

confidence: 99%

Architectural-level risk analysis using uml

Goševa-Popstojanova

Hassan

Guedem

et al. 2003

IIEEE Trans. Software Eng.

140

131

View full text Add to dashboard Cite

Abstract-Risk assessment is an essential part in managing software development. Performing risk assessment during the early development phases enhances resource allocation decisions. In order to improve the software development process and the quality of software products, we need to be able to build risk analysis models based on data that can be collected early in the development process. These models will help identify the high-risk components and connectors of the product architecture, so that remedial actions may be taken in order to control and optimize the development process and improve the quality of the product. In this paper, we present a risk assessment methodology which can be used in the early phases of the software life cycle. We use the Unified Modeling Language (UML) and commercial modeling environment Rational Rose Real Time (RoseRT) to obtain UML model statistics. First, for each component and connector in software architecture, a dynamic heuristic risk factor is obtained and severity is assessed based on hazard analysis. Then, a Markov model is constructed to obtain scenarios risk factors. The risk factors of use cases and the overall system risk factor are estimated using the scenarios risk factors. Within our methodology, we also identify critical components and connectors that would require careful analysis, design, implementation, and more testing effort. The risk assessment methodology is applied on a pacemaker case study.

show abstract

“…Scenarios are also related to the concepts of operations and run-types used for operational profiles [Musa+96]. A scenario with specified input variables are similar to an operation run-type.…”

Section: Figure 1 An Example Of Component Sequence Diagrammentioning

confidence: 99%

Scenario-based reliability analysis of component-based software

Yacoub

Čukić

Ammar

Proceedings 10th International Symposium on Software Reliability Engineering (Cat. No.PR00443)

136

View full text Add to dashboard Cite

Software designers are motivated to utilize off-the-shelf software components for rapid application development. Such applications are expected to have high reliability as a result of deploying trusted components. The claims of high reliability need further investigation based on reliability estimation models and techniques that are applicable to component-based applications. This paper introduces a probabilistic model and a reliability estimation and analysis technique applicable to high-level designs. The technique is named "Scenario-Based Reliability Estimation" (SBRE). SBRE is specific for component-based software whose analysis is strictly based on execution scenarios. Using

show abstract

The Operational Profile

Cited by 60 publications

References 3 publications

The exception handling effectiveness of POSIX operating systems

The exception handling effectiveness of POSIX operating systems

Architectural-level risk analysis using uml

Scenario-based reliability analysis of component-based software

Contact Info

Product

Resources

About