Software reliability and dependability

Littlewood, Bev; Strigini, Lorenzo

doi:10.1145/336512.336551

Cited by 104 publications

(44 citation statements)

References 29 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…When speaking about business-critical systems, the critical quality attribute is often experienced as the dependability of the system. According to Littlewood et al [2], dependability is a software quality attribute that encompasses several other attributes, the most important are reliability, availability, safety and security.…”

Section: Previous Studies On Software Faults and Fault Implicationsmentioning

confidence: 99%

Results and Experiences from an Empirical Study of Fault Reports in Industrial Projects

Børretzen

Conradi

2006

Product-Focused Software Process Improvement

View full text Add to dashboard Cite

Abstract. Faults introduced into systems during development are costly to fix, and especially so for business-critical systems. These systems are developed using common development practices, but have high requirements for dependability. This paper reports on an ongoing investigation of fault reports from Norwegian IT companies, where the aim is to seek a better understanding on faults that have been found during development and how this may affect the quality of the system. Our objective in this paper is to investigate the fault profiles of four business-critical commercial projects to explore if there are differences in the way faults appear in different systems. We have conducted an empirical study by collecting fault reports from several industrial projects, comparing findings from projects where components and reuse have been core strategies with more traditional development projects. Findings show that some specific fault types are generally dominant across reports from all projects, and that some fault types are rated as more severe than others.

show abstract

Section: Previous Studies On Software Faults and Fault Implicationsmentioning

confidence: 99%

Results and Experiences from an Empirical Study of Fault Reports in Industrial Projects

Børretzen

Conradi

2006

Product-Focused Software Process Improvement

View full text Add to dashboard Cite

show abstract

“…This problem follows the 'Dijkstra's dictum': "Program testing can be used to show the presence of bugs, but never to show their absence" (Dijkstra 1970, p.7). Model-based hypotheses concerning future computations of a represented software system are tested up to a certain time fixed by testers; they are assigned a probabilistic evaluation according to statistical estimations of future incorrect executions based on past observed failures (Littlewood and Strigini 2000). Accordingly, they assume the epistemological status of probabilistic statements that are corroborated by failed attempts of falsification (Angius 2014) .…”

Section: Discovering Empirical Theories Of Software Systemsmentioning

confidence: 99%

Discovering Empirical Theories of Modular Software Systems. An Algebraic Approach

Angius

Stefaneas

2016

Synthese Library

View full text Add to dashboard Cite

This paper is concerned with the construction of theories of software systems yielding adequate predictions of their target systems' computations. It is first argued that mathematical theories of programs are not able to provide predictions that are consistent with observed executions. Empirical theories of software systems are here introduced semantically, in terms of a hierarchy of computational models that are supplied by formal methods and testing techniques in computer science. Both deductive top-down and inductive bottom-up approaches in the discovery of semantic software theories are refused to argue in favour of the abductive process of hypothesising and refining models at each level in the hierarchy, until they become satisfactorily predictive. Empirical theories of computational systems are required to be modular, as modular are most software verification and testing activities. We argue that logic relations must be thereby defined among models representing different modules in a semantic theory of a modular software system. We exclude that scientific structuralism is able to define module relations needed in software modular theories. The algebraic Theory of Institutions is finally introduced to specify the logic structure of modular semantic theories of computational systems.

show abstract

“…Component-based software engineering supported by middleware technologies (e.g., CORBA Component Model (CCM)) have emerged as a preferred way of developing distributed real-time and embedded (DRE) systems, such as shipboard computing systems, enterprise security and hazard sensing systems, and intrusion-tolerance systems. These systems consist of applications whose quality of service (QoS) requirements -notably predictability, availability, and security, must be satisfied simultaneously to ensure dependable operation [2], [14].…”

Section: Introductionmentioning

confidence: 99%

MoPED: A Model-Based Provisioning Engine for Dependability in Component-Based Distributed Real-Time Embedded Systems

Tambe

Dabholkar

Gokhale

2011

2011 18th IEEE International Conference and Workshops on Engineering of Computer-Based Systems

View full text Add to dashboard Cite

Abstract-Developing dependable distributed real-time and embedded (DRE) systems incurs significant complexities in the tradeoffs resulting from the different conflicting attributes of dependability, such as predictability, availability, and security. In component-based systems, these challenges are exacerbated since the tradeoffs must faithfully be reflected within the complex metadata descriptors used to compose, deploy and configure the system. The benefits of design-time approaches to address these problems are well-understood. Existing model-driven designtime tools for developing dependable systems, however, focus largely on only one dependability attribute at a time and lack of extensibility results in rigid and hard to maintain tool support. This paper describes MoPED (Model-based Provisioning Engine for Dependability), which is a model-driven framework that unifies reasoning about predictability, availability, and security requirements for developing dependable component-based DRE systems. We evaluate the capabilities of MoPED using a representative case study and show how it alleviates complexities in the design of dependable systems and reduces manual efforts in the deployment phase by an order of magnitude.

show abstract

Software reliability and dependability

Cited by 104 publications

References 29 publications

Results and Experiences from an Empirical Study of Fault Reports in Industrial Projects

Results and Experiences from an Empirical Study of Fault Reports in Industrial Projects

Discovering Empirical Theories of Modular Software Systems. An Algebraic Approach

MoPED: A Model-Based Provisioning Engine for Dependability in Component-Based Distributed Real-Time Embedded Systems

Contact Info

Product

Resources

About