-
[show abstract]
[hide abstract]
ABSTRACT: There are many technical challenges in ensuring high life-time quality of NASA’s systems. Some of NASA’s software-related
challenges could potentially be addressed by the many powerful technologies that are being developed in software research
laboratories. However, most such research technologies do not make the transition from the research lab to the software lab
because research infusion and technology transfer is difficult. For example, there must be evidence that the technology works
in the practitioner’s particular domain, and there must be a potential for great improvements and enhanced competitive edge
for the practitioner, for such infusion to take place. NASA IV&V’s Research Infusion initiative strives to facilitate such
infusion. In 2006, a research infusion project involving Johns Hopkins University Applied Physics Laboratory (JHU/APL) and
the Fraunhofer Center for Experimental Software Engineering Maryland, was successfully completed infusing Fraunhofer’s software
architecture visualization and evaluation (SAVE) tool. The infusion project helped improve JHU/APL’s software architecture
and produced evidence that SAVE is applicable to software architecture problems in the aerospace domain, spawning a series
of related research infusion projects. The project also led to the discovery of other needs that could not be addressed by
current technologies and, therefore, spawned the research and development of a new technology that will be ready for infusion
in the future. This paper describes the SAVE technology followed by a description of the infusion of SAVE at JHU/APL and the
other projects that followed, as well as the newly started Dynamic SAVE research and development project. Lessons learned
related to various aspects of research infusion conclude the paper.
KeywordsSoftware architecture-Research infusion
Innovations in Systems and Software Engineering 05/2012;
-
[show abstract]
[hide abstract]
ABSTRACT: 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 life cycle. 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.
KeywordsFormal software inspections-Measurement and analysis-Process monitoring and improvement-Experience-based approach-Management by data-NPR 7150.2
Innovations in Systems and Software Engineering 05/2012;
-
19th International Symposium on Software Reliability Engineering (ISSRE 2008), 11-14 November 2008, Seattle/Redmond, WA, USA; 01/2008
-
Proceedings of the Second International Symposium on Empirical Software Engineering and Measurement, ESEM 2008, October 9-10, 2008, Kaiserslautern, Germany; 01/2008
