scholarly journals Improving software reliability in data-centered software systems by enforcing composition time constraints

2004 ◽  
Author(s):  
L. Desmet
Keyword(s):  
Software Reliability ◽  
Time Constraints ◽  
Software Systems

scholarly journals Methods of formalized quality assessment of intelligent transport systems

2021 ◽  
Vol 2061 (1) ◽  
pp. 012125
Author(s):  
K Goloskokov ◽  
V Korotkov ◽  
V Gaskarov ◽  
T Knysh
Keyword(s):  
Software Design ◽  
Software Reliability ◽  
Development Process ◽  
Control Process ◽  
Transport Systems ◽  
Software Systems ◽  
Intelligent Transport Systems ◽  
Intelligent Transport ◽  
Intelligent Information Systems ◽  
Intelligent Information

Abstract The purpose of the paper is to identify the main problems of creating software systems with a given level of reliability for intelligent transport systems. Considering the importance of this approach and the gained experience, the paper discusses design solutions to ensure software reliability in the development process. The paper is based on domestic and foreign experience of software design for intelligent information systems, which include transport systems. The issues of achieving a given level of software reliability during the control process are considered taking into account the continuation of the development process. It also reflects efforts to model and evaluate the reliability of software systems by considering the most common types of software reliability assessment models during development, as well as to predict the reliability during maintenance. The emphasis is upon detecting and correcting software errors.

scholarly journals Software Reliability for Agile Testing

Mathematics ◽  
2020 ◽  
Vol 8 (5) ◽  
pp. 791
Author(s):  
Willem Dirk van Driel ◽  
Jan Willem Bikker ◽  
Matthijs Tijink ◽  
Alessandro Di Bucchianico
Keyword(s):  
Software Reliability ◽  
Product Development Process ◽  
Software Systems ◽  
Extended Model ◽  
Testing Time ◽  
Total System ◽  
Reliability Models ◽  
Software Reliability Models ◽  
Research Activities ◽  
Testing Environments

It is known that quantitative measures for the reliability of software systems can be derived from software reliability models, and, as such, support the product development process. Over the past four decades, research activities in this area have been performed. As a result, many software reliability models have been proposed. It was shown that, once these models reach a certain level of convergence, it can enable the developer to release the software and stop software testing accordingly. Criteria to determine the optimal testing time include the number of remaining errors, failure rate, reliability requirements, or total system cost. In this paper, we present our results in predicting the reliability of software for agile testing environments. We seek to model this way of working by extending the Jelinski–Moranda model to a “stack” of feature-specific models, assuming that the bugs are labeled with the features they belong to. In order to demonstrate the extended model, two use cases are presented. The questions to be answered in these two cases are: how many software bugs remain in the software and should one decide to stop testing the software?

SOFTWARE RELIABILITY ESTIMATIONS THROUGH USAGE ANALYSIS OF SPECIFICATIONS AND DESIGNS

1996 ◽  
Vol 03 (02) ◽  
pp. 101-117
Author(s):  
CLAES WOHLIN ◽  
ANDERS WESSLÉN ◽  
PER RUNESON
Keyword(s):  
Software Design ◽  
Software Reliability ◽  
Formal Specification ◽  
Development Process ◽  
Early Stage ◽  
Software Systems ◽  
Implementation Phase ◽  
Failure Data ◽  
Full Analysis ◽  
Usage Analysis

This paper presents a method proposal for estimation of software reliability before the implementation phase. The method is based upon that a formal specification technique is used and that it is possible to develop a tool performing dynamic analysis, i.e., locating semantic faults in the design. The analysis is performed with both applying a usage profile as input as well as doing a full analysis, i.e., locate all faults that the tool can find. The tool must provide failure data in terms of time since the last failure was detected. The mapping of the dynamic failures to the failures encountered during statistical usage testing and operation is discussed. The method can be applied either on the software specification or as a step in the development process by applying it on the software design. The proposed method allows for software reliability estimations that can be used both as a quality indicator, and for planning and controlling resources, development times, etc. at an early stage in the development of software systems.

Bayesian Software Reliability Prediction Based on Yamada Delayed S-Shaped Model

2014 ◽  
Vol 490-491 ◽  
pp. 1267-1278 ◽  
Author(s):  
Tean Quay Lee ◽  
Chun Wu Yeh ◽  
Chih Chiang Fang
Keyword(s):  
Bayesian Analysis ◽  
Software Reliability ◽  
Growth Models ◽  
Failure Process ◽  
Analytical Models ◽  
Release Time ◽  
Software Systems ◽  
Failure Behavior ◽  
Software Project ◽  
Numerical Example

Software Reliability Growth Models (SRGMs) provide techniques to predict future failure behavior from known characteristics of the software testing work. However, in some cases, software developers did not have sufficient historical data to estimate the corresponding reliability and the expected testing cost, especially for a newly developed software project, and thus the results obtained from analytical models may not be reliable. In such situations, Bayesian analysis is a reasonable approach to additionally take expert's opinions into account for better decision making. In this paper, we utilized Yamada Delayed S-shaped Model with Bayesian analysis in predicting software reliability and expected testing costs to determine an optimal release time for software systems. Besides, the failure process of software are assumed to be drawn from a non-homogeneous Poisson process (NHPP), and the parameters of the proposed model are assumed to be mutually independent and Gamma distributed. Finally, a numerical example is given to verify the effectiveness of the proposed approach, and the sensitive and risk analyses are performed in light of the numerical example.

Test based safety-critical software reliability estimation using Bayesian method and flow network structure

2019 ◽  
Vol 233 (5) ◽  
pp. 847-856
Author(s):  
Yaguang Yang
Keyword(s):  
Software Reliability ◽  
Probabilistic Method ◽  
Reliability Estimation ◽  
Software Test ◽  
Consensus Method ◽  
Software Systems ◽  
Engineering Systems ◽  
Critical Systems ◽  
Safety Requirements ◽  
Safety Critical

System safety is closely related to system reliability. Safety requirements many times are translated to reliability requirements. Nowadays, software systems exist in many engineering systems. However, there is no consensus method for software reliability estimation. On the contrary, there is an increasing interest in estimating the software reliability due to concerns for safety-critical systems. In this article, we try to close the gap by proposing a systematic and probabilistic method to estimate the software reliability based on software test data.

Software Reliability Using SPRT: Burr Type III Process Model

2016 ◽  
Vol 6 (6) ◽  
pp. 3060
Author(s):  
CH. Smitha ◽  
R. Satya Prasad ◽  
R. Kiran Kumar
Keyword(s):  
Software Reliability ◽  
Process Model ◽  
Sequential Analysis ◽  
Likelihood Estimation ◽  
Software Systems ◽  
Ratio Test ◽  
Software Projects ◽  
Type Iii ◽  
Time Domain Data ◽  
Adopted Model

<p>Increased dependence on software systems elicited the assessment of their reliability, a crucial task in software development. Effective tools and mechanisms are required to facilitate the assessment of software reliability. Classical approaches like hypothesis testing are significantly time consuming as the conclusion can only be drawn after collecting huge amounts of data. Statistical method such as Sequential Analysis can be applied to arrive at a decision quickly. This paper implemented Sequential Probability Ratio Test (SPRT) for Burr Type III model based on time domain data. For this, parameters were estimated using Maximum Likelihood Estimation to apply SPRT on five real time software failure datasets borrowed from different software projects. The results exemplify that the adopted model has given a rejection decision for the used datasets.</p>

Reliability and Performance Analysis of Architecture-Based Software Implementing Restarts and Retries Subject to Correlated Component Failures

2015 ◽  
Vol 25 (08) ◽  
pp. 1307-1334 ◽  
Author(s):  
Xiao-Dan Li ◽  
Yong-Feng Yin ◽  
Lance Fiondella
Keyword(s):  
Software Reliability ◽  
High Reliability ◽  
Experimental Studies ◽  
Software Systems ◽  
Fault Recovery ◽  
Recovery Mechanism ◽  
Software Models ◽  
And Performance ◽  
Component Failures ◽  
The Impact

High reliability and performance are essential attributes of software systems designed for critical real-time applications. To improve the reliability and performance of software, many systems incorporate some form of fault recovery mechanism. However, contemporary models of software reliability and performance rarely consider these fault recovery mechanisms. Another notable shortcoming of many software models is that they make the simplifying assumption that component failures are statistically independent, which disagrees with several experimental studies that have shown that the failures of software components can exhibit correlation. This paper presents an architecture-based model of software reliability and performance that explicitly considers a two-stage fault recovery mechanism implementing component restarts and application-level retries. The application architecture is characterized by a Discrete Time Markov Chain (DTMC) to represent the dynamic branching behavior of control between the components of the application. Correlations between the component failures are computed with an efficient numerical algorithm for a multivariate Bernoulli (MVB) distribution. We illustrate the utility of the model through a case study of an embedded software application. The results suggest that the model can be used to quantify the impact of software fault recovery and correlated component failures on application reliability and performance.

REFACTORIZATION'S IMPACT ON SOFTWARE RELIABILITY

2006 ◽  
Vol 13 (01) ◽  
pp. 47-60
Author(s):  
IRENEUSZ JÓŹWIAK ◽  
MAKSYMILIAN KOWALCZYK ◽  
ANDRZEJ PIOTROWICZ
Keyword(s):  
Software Reliability ◽  
Source Code ◽  
Software Systems ◽  
Fundamental Study ◽  
Reliability Improvement ◽  
Code Structure

Software refactorization is a process of changing program's source code structure without changing its functionality. The purpose of the refactorization is to make program's source code easier to understand and maintain, which in turn influence the fact that in a long term such code should have fewer errors (be more reliable). In recent years many works described refactorization, but till now there are no researches, which would assess long term influence of refactoring on reliability. In this work we try to depict our fundamental study on software systems reliability improvement in context of refactoring. We tried to find the answer to the question: What are benefits of using refactorization as far as reliability is concerned?

C0 COVERAGE-MEASURE AND TESTING-DOMAIN METRICS BASED ON A SOFTWARE RELIABILITY GROWTH MODEL

2002 ◽  
Vol 09 (04) ◽  
pp. 329-340 ◽  
Author(s):  
TAKAJI FUJIWARA ◽  
SHIGERU YAMADA
Keyword(s):  
Growth Model ◽  
Software Reliability ◽  
Software Systems ◽  
Reliability Growth ◽  
Software Reliability Growth Model ◽  
Progress Management ◽  
Case Tools ◽  
Path Coverage ◽  
Software Reliability Growth ◽  
Testing Coverage

Generally, a software development manager is performing the testing-progress management by using various CASE tools. These CASE tools support testing activities of Windows applications or embedded software systems. Then, by using various testing coverage-measures, the testing-progress management can be recognized visually. However, in the system-testing phase, it is impossible to measure them of software systems which have been becoming large-scale and complicated recently. Therefore, the manager has to determine the testing termination time in consideration of the convergence situation of the cumulative number of detected faults and the prespecified delivery time to the users. These determination method have ambiguity based on the manager's experience or intuition. In this paper, we investigate the relationship between the testing-domain rate derived from a testing-domain dependent software reliability growth model and the testing-path coverage. Then, we show that the testing-domain rate, which is defined as the increasing ratio of the testing-paths in the modules and functions in the software system to be influenced by executed test-cases, is useful as an alternative measure of testing-coverage metrics. Further, this model is applied to the fault data observed in an actual software project, and the comparisons of goodness-of-fit with the conventional software reliability growth models are performed. Finally, in numerical illustrations, we discuss the software reliability analysis and the usefulness of the testing-domain rate, and propose a new testing-path coverage rate.

Sign in / Sign up

Export Citation Format

Share Document