The Infona portal uses cookies, i.e. strings of text saved by a browser on the user's device. The portal can access those files and use them to remember the user's data, such as their chosen settings (screen view, interface language, etc.), or their login data. By using the Infona portal the user accepts automatic saving and using this information for portal operation purposes. More information on the subject can be found in the Privacy Policy and Terms of Service. By closing this window the user confirms that they have read the information on cookie usage, and they accept the privacy policy and the way cookies are used by the portal. You can change the cookie settings in your browser.
Under the effects of integrated factors, such as IT technology, software engineering, user requirement etc, software reliability engineering has been gradually developed. With the continuous improvement of software engineering technology, the perfection of software reliability tools and the enhancement of user requirement for software reliability, and the research for software reliability are developing...
Based upon the summarization of software reliability engineering, this paper sets forth the process model of software reliability engineering, software reliability demonstration, requirement analysis, design and realization, growth and validation, tracking and management of Command, and Control software. Moreover a primary prospect is presented.
The prediction of software reliability can determine the current reliability of a product, using statistical techniques based on the failures data, obtained during testing or system usability. Software reliability growth models attempt to predict the number of defect using a correlation between exponential function and defect data. The purpose of this paper is to study the evolution of a real-life...
ISA100.11a protocol is one of the three industrial wireless standards. Based on in-depth analyzing the ISA100.11a protocol standards and technology features, referring to international standards ISO/IEC9646, by using the object-oriented method to design ISA100.11a protocol conformance testing software, and develop related software. The testing results show that the software could satisfy the requirements...
Many of the problems found in the uses of exception handling are caused by the lack of testing and a priori design of the exceptional behavior. As a consequence, exceptions flow in unforeseen ways during the execution of a software system, causing a negative impact on reliability. This paper presents a new agile approach to test the exceptional behavior of a system. It supports developers in checking...
Classical requirements validation methods usually work with static behavioral models, and under the assumption that there are no dependencies and interactions between the requirements. Requirements verification is mostly done by statically analyzing the design artifacts and by running tests. This work presents a practical formal approach for requirements validation and verification (V&V) of dependable...
In the past 35 years more than 100 software reliability models are proposed. Most of them are parametric models. In this paper we present a comparative study of different non-parametric models based on the neural networks and regression model learned by the real coded genetic algorithm to predict the cumulative failure in the software. Experimental results show that the training of different models...
Software industry suffer many challenges in developing a high quality reliable software. Many factors affect their development such as the schedule, limited resources, uncertainty in the developing environment and inaccurate requirement specification. Software Reliability Growth Models (SRGM)were significantly used to help in solving these problems by accurately predicting the number of faults in...
By means of analysis of software's usage, it can be known that the software's actual usage is just like a stochastic process, whose series of usage events are extended according to some probability distribution. If the statistical characteristics of software reliability test suite is that of the implementation in practice when customers actually use the software product, that is to say, the test process...
Building large software systems is difficult. Maintaining large systems is equally hard. Making post-release changes requires not only thorough understanding of the architecture of a software component about to be changed but also its dependencies and interactions with other components in the system. Testing such changes in reasonable time and at a reasonable cost is a difficult problem as infinitely...
In order to increase the effectiveness and efficiency of software reliability testing, an accelerated testing method based on test coverage is presented in this paper. The amount of reliability test cases is reduced by a heuristic test-suite reduction algorithm based on static analysis of test coverage. The testing process is accelerated by the strategy of not executing redundant test cases and compensating...
John Musa's first book on Software Reliability Engineering advises the analyst to use the Musa Basic Law or the Musa-Okumoto Logarithmic Law to estimate failure intensity, depending on which provides the best fit to the data. He refered to the papers by Tractenberg and Downs as providing a foundation for these models. I propose using Musa's basic model in combination with an approach Duane and Codier...
This paper proposes a software reliability model with a bathtub-shaped fault detection rate. We discuss how the inherent characteristics of the software testing process support the three phases of the bathtub; the first phase with a decreasing fault detection rate arises from the removal of simple, yet frequent faults like syntax errors and typos; the second phase possesses a constant fault detection...
Software developers typically incorporate error-detection code to find and report faults at all levels. A system's reliability and maintainability can be significantly improved thorough wider use of error detection, better detection methods, and more informative reporting, but the benefits come at a price. This paper explores practical techniques in real-world applications that can greatly improve...
The iterative and incremental development is becoming a major development process model in industry, and allows us for a good deal of parallelism between development and testing. In this paper we develop a quantitative software reliability assessment method in incremental development processes, based on the familiar non-homogeneous Poisson processes. More specifically, we utilize the software metrics...
This article describes the advanced parametric models for assessment and prediction of software reliability, based on statistics of bugs at the initial stage of testing. The parametric model approach, commonly associated with reliability issues, deals with the evaluation of the amount of bugs in the code. Computed parameter values inserted into the model allow to estimate: (a) number of bugs remaining...
It is necessary to assess the reliability of safety-critical software to a high degree of confidence before they are deployed in the field. However, safety-critical software often includes some rarely executed critical operations that are often inadequately tested in statistical testing based reliability estimation. This paper discusses software statistical testing acceleration based on importance...
For software developed under the principles of Cleanroom Software Engineering, the software statistical testing often reveals no failure. Applying Bayesian Inference and taking into account the software structure information, this paper discusses how to estimate the failure probability under this condition. The criterion to stop statistical testing is also discussed under different conditions.
This, paper presents (i) several software reliability, growth models (SRGM) which tries to predict, quantitatively the failure, phenomena, in, an, Open, Source, Software, project over a period of time. Here, it is assumed that the number of failures during testing is dependent upon the number of instructions execution, (ii) in order to cater the, irregular state, of, bug-report, phenomena, on, the,...
Using static analysis tools can detect software vulnerabilities, which is important for improving the security of software. Static analysis technology has developed rapidly, but the comparison and evaluation of static analysis techniques and tools are not much. This paper focuses on software vulnerability static analysis techniques and tools. First we discuss the commonly-used static analysis techniques...
Set the date range to filter the displayed results. You can set a starting date, ending date or both. You can enter the dates manually or choose them from the calendar.