Estimating Residual Faults from Code Coverage

Many reliability prediction techniques require an estimate for the number of residual faults. In this paper, a new theory is developed for using test coverage to estimate the number of residual faults. This theory is applied to a specific example with known faults and the results agree well with the theory. The theory is used to justify the use of linear extrapolation to estimate residual faults. It is also shown that it is important to establish the amount of unreachable code in order to make a realistic residual fault estimate

Worst Case Reliability Prediction Based on a Prior Estimate of Residual Defects

In this paper we extend an earlier worst case bound reliability theory to derive a worst case reliability function R(t), which gives the worst case probability of surviving a further time t given an estimate of residual defects in the software N and a prior test time T. The earlier theory and its extension are presented and the paper also considers the case where there is a low probability of any defect existing in the program. For the "fractional defect" case, there can be a high probability of surviving any subsequent time t. The implications of the theory are discussed and compared with alternative reliability models

B-Nodes: A Proposed New Technique for Database Design and Implementation

There exist a wide range of methods that can be used for the analysis and design of IT systems. However a survey of a wide range of methods and a detailed analysis of one structured method indicated the lack of a simple method for modeling hardware. The ORACLE database provides detailed guidelines regarding the minimum platform to run the database and how to derive table spaces (system, user, applications, rollback etc) size of shared pool buffer, Redo log buffer pool etc.that can be used to define hard disc capacity. The system can then be optimised. However little guidance is given regarding the performance of other devices (microprocessor, RAM, bus structures etc). This paper evaluates the new B-Node modeling technique as a possible standard technique in structured systems analysis and design for evaluating hardware performance

Decision Point Analysis on Learning Process Models in FLOSS mailing Archives

Abstract. Numerous studies continue to explore the potential of social interactions between people in Free/Libre Open Source Software (FLOSS) environments. While the dynamics of interactions in these environments can be understood from different perspectives, we put a particular focus on any interactions resulting in knowledge transfer and acquisition. As learning platforms, FLOSS communities provide immense opportunities for improving software engineering skills. People who engage in FLOSS activities both acquire and improve their software development skills. For this reason, it is very helpful to understand how these learning interactions occur. In this paper, we make use of the decision miner in process mining to conduct our analysis. The purpose of such an endeavour is twofold. Firstly, we provide empirical insights into how people learn while exchanging emails in FLOSS mailing archives. Lastly, we go a step further by providing insights behind the motivation into learning participants' decisions on their learning paths

B-nodes: a new scalable high level abstraction model

This paper proposes a new modeling technique called B-Nodes. B-Nodes represent a new, high-level abstraction that allows technical detail to be controlled using top-down recursive decomposition. This abstraction. is independent of architectural detail and can therefore accommodate rapid changes in technology. The use of recursive decomposition allows B-Nodes to be used not only for entire e-commerce system but also sub-modules within this system. The use of fundamental units allows the performance of heterogeneous technologies to be compared and other units to be derived. Results to date indicate no comparable model exists. Should further work validate this technique the authors recommend its use as a standard technique in information systems analysis and desig

Characterizing Role Models in Software Practitioners' Career: An Interview Study

A role model is a person who serves as an example for others to follow, especially in terms of values, behavior, achievements, and personal characteristics. In this paper, authors study how role models influence software practitioners careers, an aspect not studied in the literature before. By means of this study, authors aim to understand if there are any salient role model archetypes and what characteristics are valued by participants in their role models. To do so, authors use a thematic coding approach to analyze the data collected from interviewing ten Latin American software practitioners. Findings reveal that role models were perceived as sources of knowledge, yet the majority of participants, regardless of their career stage, displayed a stronger interest in the human side and the moral values that their role models embodied. This study also shows that any practitioner can be viewed as a role model.Comment: 6 pages, 2 Tables. To appear in CHASE 2024: Proceedings of the 17th International Conference on Cooperative and Human Aspects of Software Engineering, April 14-15, 2024, Lisbon, Portuga

Model-Based Testing Approaches using UML Diagrams: A Systematic Literature Review

Software Unit Testing (SUT) is the starting point for Model-Based Testing (MBT), a testing method. The Unified Modeling Language (UML) has become the standard for modelling software in professional and academic settings. There are various uses for the modelling language known as UML. The findings of an SLR on UML-based model-based testing methodologies are presented in this paper. Thirty-five primary articles about six research issues were examined using selection and exclusion criteria. Methods, model class, intermediate format use, and testing methodology are the primary points of examination. The review outcomes identify future research needs and avenues of inquiry

Objectives and context of software measurement, analysis and control

Includes bibliographical references (p. 20).Michael A. Cusumano

Objectives and context of software measurement, analysis and control

Includes bibliographical references (p. 19).Michael A. Cusumano