Fully Employing Software Inspections Data

Software inspections provide a proven approach to quality assurance for software products of all kinds, including requirements, design, code, test plans, among others. Common to all inspections is the aim of finding and fixing defects as early as possible, and thereby providing cost savings by minimizing the amount of rework necessary later in the lifecycle. Measurement data, such as the number and type of found defects and the effort spent by the inspection team, provide not only direct feedback about the software product to the project team but are also valuable for process improvement activities. In this paper, we discuss NASA's use of software inspections and the rich set of data that has resulted. In particular, we present results from analysis of inspection data that illustrate the benefits of fully utilizing that data for process improvement at several levels. Examining such data across multiple inspections or projects allows team members to monitor and trigger cross project improvements. Such improvements may focus on the software development processes of the whole organization as well as improvements to the applied inspection process itself

Evaluating Heuristics for Planning Effective and Efficient Inspections

A significant body of knowledge concerning software inspection practice indicates that the value of inspections varies widely both within and across organizations. Inspection effectiveness and efficiency can be measured in numerous ways, and may be affected by a variety of factors such as Inspection planning, the type of software, the developing organization, and many others. In the early 1990's, NASA formulated heuristics for inspection planning based on best practices and early NASA inspection data. Over the intervening years, the body of data from NASA inspections has grown. This paper describes a multi-faceted exploratory analysis performed on this data to elicit lessons learned in general about conducting inspections and to recommend improvements to the existing heuristics. The contributions of our results include support for modifying some of the original inspection heuristics (e.g. Increasing the recommended page rate), evidence that Inspection planners must choose between efficiency and effectiveness, as a good tradeoff between them may not exist, and Identification of small subsets of inspections for which new inspection heuristics are needed. Most Importantly, this work illustrates the value of collecting rich data on software Inspections, and using it to gain insight into, and Improve, inspection practice

Making Use of a Decade of Widely Varying Historical Data: SARP Project - "Full Life-Cycle Defect Management"

A viewgraph presentation describing the NASA Software Assurance Research Program (SARP) project, with a focus on full life-cycle defect management, is provided. The topics include: defect classification, data set and algorithm mapping, inspection guidelines, and tool support

Risk Factors for Perioperative Brain Lesions in Infants With Congenital Heart Disease: A European Collaboration

Background: Infants with congenital heart disease are at risk of brain injury and impaired neurodevelopment. The aim was to investigate risk factors for perioperative brain lesions in infants with congenital heart disease. Methods: Infants with transposition of the great arteries, single ventricle physiology, and left ventricular outflow tract and/or aortic arch obstruction undergoing cardiac surgery <6 weeks after birth from 3 European cohorts (Utrecht, Zurich, and London) were combined. Brain lesions were scored on preoperative (transposition of the great arteries N=104; single ventricle physiology N=35; and left ventricular outflow tract and/or aortic arch obstruction N=41) and postoperative (transposition of the great arteries N=88; single ventricle physiology N=28; and left ventricular outflow tract and/or aortic arch obstruction N=30) magnetic resonance imaging for risk factor analysis of arterial ischemic stroke, cerebral sinus venous thrombosis, and white matter injury. Results: Preoperatively, induced vaginal delivery (odds ratio [OR], 2.23 [95% CI, 1.06-4.70]) was associated with white matter injury and balloon atrial septostomy increased the risk of white matter injury (OR, 2.51 [95% CI, 1.23-5.20]) and arterial ischemic stroke (OR, 4.49 [95% CI, 1.20-21.49]). Postoperatively, younger postnatal age at surgery (OR, 1.18 [95% CI, 1.05-1.33]) and selective cerebral perfusion, particularly at ≤20 °C (OR, 13.46 [95% CI, 3.58-67.10]), were associated with new arterial ischemic stroke. Single ventricle physiology was associated with new white matter injury (OR, 2.88 [95% CI, 1.20-6.95]) and transposition of the great arteries with new cerebral sinus venous thrombosis (OR, 13.47 [95% CI, 2.28-95.66]). Delayed sternal closure (OR, 3.47 [95% CI, 1.08-13.06]) and lower intraoperative temperatures (OR, 1.22 [95% CI, 1.07-1.36]) also increased the risk of new cerebral sinus venous thrombosis. Conclusions: Delivery planning and surgery timing may be modifiable risk factors that allow personalized treatment to minimize the risk of perioperative brain injury in severe congenital heart disease. Further research is needed to optimize cerebral perfusion techniques for neonatal surgery and to confirm the relationship between cerebral sinus venous thrombosis and perioperative risk factors. Keywords: heart diseases; ischemic stroke; magnetic resonance imaging; pedatrics; risk factors; venous thrombosis; white matter

Guidelines for Evaluation and Improvement of Reuse and Experience Repository Systems through Measurement Programs

Software development organizations are recognizing the increasing importance of investing in the build-up of core competencies for their competitiveness in software system development. This is supported by reuse and experience repository systems that assist in capturing and reusing all kinds of software artifacts (e. g., code, patterns, frameworks) and processes as well as experiences related to these artifacts and processes. To justify such an investment and guide its improvement, it must be evaluated according to the business case, that is, a measurement program has to be developed that is oriented towards the business goals of such a reuse and experience repository system. In this paper, we suggest an approach to iteratively build up measurement programs for gaining feedback and, thereby, controlling and improving such a reuse and experience repository system. The focus is placed on guidelines for the evolution of such measurement programs over time, rather than providing directly applicable metrics or questionnaires. In order to illustrate the feasibility of the approach, examples of running measurement programs at different stages of evolutions are given

An Integrating Approach for Developing Distributed Software Systems -Combining Formal Methods, Software Reuse, and the Experience Base-

The development of complex software systems is driven by many diverse and sometimes contradictory requirements such as correctness and maintainability of resulting products, development costs, and time-to-market. To alleviate these difficulties, we propose a development method for distributed systems that integrates different basic approaches. First, it combines the use of the formal description technique SDL with software reuse concepts. This results in the definition of a use-case driven, incremental development method with SDL-patterns as the main reusable artifacts. Experience with this approach has shown that there are several other factors of influence, such as the quality of reuse artifacts or the experience of the development team. Therefore, we further combined our SDL-pattern approach with an improvement methodology known from the area of experimental software engineering. In order to demonstrate the validity of this integrating approach, we sketch some representative outcomings of a case study

Developing a Tailored Reuse Repository Structure - experience and first results

Learning from experience gained in past projects is seen as a promising way to improve software quality in upcoming projects. Thus, the reuse of patterns or code components to support software development is widely accepted in research and industry. Furthermore, some approaches require the comprehensive reuses of other forms of knowledge that go far beyond mere software artifacts. This includes, for instance, the reuse of techniques, methods, tools, processes, or even metrics that have already been successfully used in projects. However, the different reusable elements must be stored somewhere, to be easily accessible for later reuse. This calls for a repository that organizes the reusable elements and offers them, on demand, to the (re-)user. In accordance with the applied learning and reuse processes, such a repository must be individually adapted and tailored to the special needs of the organization. It can not be expected that a solution that holds for one organization works for another. This paper describes how a comprehensive reuse repository is developed and tailored for a research organization at the University of Kaiserslautern. First, a HTML-based prototype was installed, to define the repository structure. Details of the resulting current structure are discussed. It is sketched how the structure changed over time, before it was stable enough to serve as a basis for a database-supported implementation

Guidelines for Evaluation and Improvement of Reuse and Experience Repository Systems through Measurement Programs

Software development organizations are recognizing the increasing importance of investing in the build-up of core competencies for their competitiveness in software system development. This is supported by reuse and experience repository systems that assist in capturing and reusing all kinds of software artifacts (e. g., code, patterns, frameworks) and processes as well as experiences related to these artifacts and processes. To justify such an investment and guide its improvement, it must be evaluated according to the business case, that is, a measurement program has to be developed that is oriented towards the business goals of such a reuse and experience repository system. In this paper, we suggest an approach to iteratively build up measurement programs for gaining feedback and, thereby, controlling and improving such a reuse and experience repository system. The focus is placed on guidelines for the evolution of such measurement programs over time, rather than providing directly applicable metrics or questionnaires. In order to illustrate the feasibility of the approach, examples of running measurement programs at different stages of evolutions are given