Methodology for Software Reliability Prediction. Volume 1.

McCall, James A.; Randall, W; Bowen, Clayton R.; McKelvey, Nigel; Senn, R

doi:10.21236/ada190018

Cited by 5 publications

(9 citation statements)

References 0 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…The effort in software reliability growth based models is concentrated on statistical testing, and therefore the models are applicable in the late development phase. There are also some other measurement based approaches, such as [23] and [24], which suggest measures for software artifacts. These types of methods are called black-box approaches, since they ignore the internal structure of software systems.…”

Section: Overview Of Reliability and Availability Prediction Approachesmentioning

confidence: 99%

Survey of reliability and availability prediction methods from the viewpoint of software architecture

2007

View full text Add to dashboard Cite

Many future software systems will be distributed across a network, extensively providing different kinds of services for their users. These systems must be highly reliable and provide services when required. Reliability and availability must be engineered into software from the onset of its development, and potential problems must be detected in the early stages, when it is easier and less expensive to implement modifications. The software architecture design phase is the first stage of software development in which it is possible to evaluate how well the quality requirements are being met. For this reason, a method is needed for analyzing software architecture with respect to reliability and availability. In this paper, we define a framework for comparing reliability and availability analysis methods from the viewpoint of software architecture. Our contribution is the comparison of the existing analysis methods and techniques that can be used for reliability and availability prediction at the architectural level. The objective is to discover which methods are suitable for the reliability and availability prediction of today's complex systems, what are the shortcomings of the methods, and which research activities need to be conducted in order to overcome these identified shortcomings. The comparison reveals that none of the existing methods entirely fulfill the requirements that are defined in the Communicated by Oystein Haugen.A. Immonen (B) · E. Niemelä

show abstract

Section: Overview Of Reliability and Availability Prediction Approachesmentioning

confidence: 99%

Survey of reliability and availability prediction methods from the viewpoint of software architecture

2007

View full text Add to dashboard Cite

show abstract

“…This distinction between hardware reliability assessment and software reliability assessment is recognized by McCall, et al Their articulation of the problem, repeated here for emphasis, is as follows [McCa87a]:…”

Section: Unclassifiedmentioning

confidence: 99%

“…Some work has been done on predicting reliability from properties of the software and the process by which it was developed [Musa87,McCa87a]. This work is not addressed here, because it is so closely associated with software metrics, the topic of the previous section of this report.…”

Section: General Approach To Software Reliability Assessmentmentioning

confidence: 99%

SDS (Strategic Defense System) Software Testing and Evaluation: a Review of the State-of-the-Art in Software Testing and Evaluation with Recommended R&D Tasks

Youngblut¹,

Brykczynski²,

Salasin³

et al. 1989

View full text Add to dashboard Cite

896 19 037 IDA Memorandum M-496 is a related document which provides a comprehensive, annotated bibliography of the reference material acquired in the course of this work. IDA Memorandum M-513, another related document, is a collection of the papers provided by leading experts in testing and evaluation tech-* nology preparatory to an IDA workshop held in support of this work.The authors gratefully acknoledge the support given by all those who participated in the workshop and reviewed this paper. The insights and experience these people so willingly shared has been invaluable. In particular, special thanks go to the following people: IntroductionTesting and uvaluation are recognized as pivotal problems in the development of the Strategic Defense System (SDS). Consequently, a development approach combining design, prototyping, and simulation is being used to allow early evaluation of system requirements and designs. Loosely-coupled, decentralized system architectures are being examined for their facility to reduce the testing problem to a manageable level. But what testing and evaluation technology shall be used to ensure the reliability of, and provide the necessary level of confidence in, SDS software? The purpose of this report is to address this question. *For the past decade, software testing and evaluation have been relatively unpopular subjects. Why this happened is less important than its consequences. It has been a contributing factor to the lag between the state-of-the-art and state-of-the-practice, which is the largest of any in the diverse areas of software engineering, and has resulted in a shortage of research and development (R&D) resources and a small, weak research community. Since SDS prototype software is already being developed, software testing and evaluation are now critical concerns. The Strategic Defense Initiative Organization (SDIO) cannot * wait for testing and evaluation issues to pop up later in the development process (a traditional approach which has proven costly in the past), but must meet the challenge up front.Once the importance of this challenge is recognized, appropriate actions can be taken. There is a substantial body of testing and evaluation technology whose use in an industrial environment is ready to be investigated, preparatory to transitioning the technology into practice. The main body of this report * describes the current status of different areas of this technology. It also outlines a number of tasks for bringing promising elements of the technology into practice. While the use of advanced technology will certainly help, it is by no means sufficient to resolve all testing and evaluation problems. In particular, technology for the testing and evaluation of large, distributed and real-time software systems is still in its infancy. The final part of this report, therefore, recommends a number of tasks to extend the boundaries of technology to meet SDS needs.Testing and evaluation technology is not, by itself, enough to ensure improved practices. Policy must evolve ...

show abstract

“…This model expects that fault densities will be expressed in terms of the number of faults per thousand lines of source code (KSLOC), which means that faults found during the requirements analysis and software design will have to be normalized by the code size estimates. Another well known work in this field initiated by RADC [10]. To prediction of software reliability in the early phases of software lifecycle, the researchers applied some software development metrics which they felt affect to the reliability to obtain the initial fault density, which could then be transformed into other reliability measures.…”

Section: Related Workmentioning

confidence: 99%

Software reliability assessment based on a formal requirements specification

Alipour

Isazadeh

2008

2008 Conference on Human System Interactions

View full text Add to dashboard Cite

Assessment of reliability using characteristics of software development process phases is one of the discussions which has been attracting more and more attentions during the recent three decades. Most of the techniques and models use the result of design, implementation and test phases; there are only a few models that are employed at the early phase of software development. Assessment of software reliability in the early phases of software development process, however, is very important for better prognosis and management of risks. In this paper we propose an approach for early software reliability assessment, based on software behavioral requirements. The major difference between our approach and those of others is the fact that we use a formal method, called Viewcharts, to specify the behavior of software systems.

show abstract

Methodology for Software Reliability Prediction. Volume 1.

Cited by 5 publications

References 0 publications

Survey of reliability and availability prediction methods from the viewpoint of software architecture

Survey of reliability and availability prediction methods from the viewpoint of software architecture

SDS (Strategic Defense System) Software Testing and Evaluation: a Review of the State-of-the-Art in Software Testing and Evaluation with Recommended R&D Tasks

Software reliability assessment based on a formal requirements specification

Contact Info

Product

Resources

About