Predicting fault content for evolving software systems
Explore the source record for details and available documents.
software evolution software measurement software m↗
SEARCH · Engineering Papers
Results for “software measurement”
Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.
Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.
Software metrics in use at JPL applications and research
Explore the source record for details and available documents.
software metrics software measurement software ass↗
Practical Methods for Estimating Software Systems Fault Content and Location
Over the past several years, we have developed techniques to discriminate between fault-prone software modules and those that are not, to estimate a software system's residual fault content, to identify those portions of a software system having the highest estimated number of faults, and to estimate the effects of requirements changes on software quality.
fault-prone discriminant function↗
The Effects of Fault Counting Methods on Fault Model Quality
In this paper, we describe three other fault-counting techniques and compare the models resulting from the application of two of those methods to the models obtained from the application of our proposed definition.
software reliability↗
NASA Tech Briefs, December 2000
Topics include: special coverage sections on Imaging/Video/Display Technology, and sections on electronic components and systems, test and measurement, software, information sciences, and special sections of Electronics Tech Briefs and Motion Control Tech Briefs.
Source record↗
Pragmatic quality metrics for evolutionary software development models
Due to the large number of product, project, and people parameters which impact large custom software development efforts, measurement of software product quality is a complex undertaking. Furthermore, the absolute perspective from which quality is measured (customer satisfaction) is intangible. While we probably can't say what the absolute quality of a software product is, we can determine the relative quality, the adequacy of this quality with respect to pragmatic considerations, and identify good and bad trends during development. While no two software engineers will ever agree on an optimum definition of software quality, they will agree that the most important perspective of software quality is its ease of change. We can call this flexibility, adaptability, or some other vague term, but the critical characteristic of software is that it is soft. The easier the product is to modify, the easier it is to achieve any other software quality perspective. This paper presents objective quality metrics derived from consistent lifecycle perspectives of rework which, when used in concert with an evolutionary development approach, can provide useful insight to produce better quality per unit cost/schedule or to achieve adequate quality more efficiently. The usefulness of these metrics is evaluated by applying them to a large, real world, Ada project.
Royce, Walker↗
Theory and operation of the Gould 32/27 programs ABLE-2A and EBLE for the tropospheric air motion measurement system
Software development for the Trospheric Air Motion Measurement Systems (TAMMS) is documented. In July/August the TAMMS was flown on the NASA/Goddard Flight Center Electra aircraft for 19 mission for the ABLE-2A (Amazon Boundary Layer Experiment) in Brazil. In December 1985, several flights were performed to assess the contamination and boundary layer of the Electra. Position data, flow angles, pressure transducer measurements were recorded. The programs written for the ABLE-2A were modified due to timing considerations for this particular program. The 3-step programs written for EBLE (Electra Boundary Layer Experiment) are described. Power up and log-on procedures are discussed. A few editing techniques are described for modification of the programs.
Butler, C.↗
Hardware in-the-Loop Demonstration of Real-Time Orbit Determination in High Earth Orbits
This paper presents results from a study conducted at Goddard Space Flight Center (GSFC) to assess the real-time orbit determination accuracy of GPS-based navigation in a number of different high Earth orbital regimes. Measurements collected from a GPS receiver (connected to a GPS radio frequency (RF) signal simulator) were processed in a navigation filter in real-time, and resulting errors in the estimated states were assessed. For the most challenging orbit simulated, a 12 hour Molniya orbit with an apogee of approximately 39,000 km, mean total position and velocity errors were approximately 7 meters and 3 mm/s respectively. The study also makes direct comparisons between the results from the above hardware in-the-loop tests and results obtained by processing GPS measurements generated from software simulations. Care was taken to use the same models and assumptions in the generation of both the real-time and software simulated measurements, in order that the real-time data could be used to help validate the assumptions and models used in the software simulations. The study makes use of the unique capabilities of the Formation Flying Test Bed at GSFC, which provides a capability to interface with different GPS receivers and to produce real-time, filtered orbit solutions even when less than four satellites are visible. The result is a powerful tool for assessing onboard navigation performance in a wide range of orbital regimes, and a test-bed for developing software and procedures for use in real spacecraft applications.
Moreau, Michael↗
Software Programs Derive Measurements from Photographs
Even under the most unfortunate circumstances, NASA continues on a path of innovation. After the Space Shuttle Columbia reentered the atmosphere on February 1, 2003, it experienced a catastrophic failure, and the entire crew and vehicle were lost. For the two weeks prior to the accident, Columbia STS-107 was on a mission to perform physical, life, and space sciences research in the unique environment of microgravity. Following the accident, the remaining shuttles - Endeavor, Atlantis, and Discovery - were grounded, and an intense investigation ensued. The Columbia Accident Investigation Board spent nearly 7 months examining the cause of the accident and determining what would ensure a safe return to flight. To this end, investigators performed an extensive review down five analytic paths: aerodynamic, thermodynamic, sensor data timeline, debris reconstruction, and imaging. As part of the evaluation of all the available imagery from Columbia's ascent, orbit, and entry, investigators needed a new method for analyzing still video images to determine the size of the material that fell from Columbia, as well as the distance that the material traveled. John Lane, a scientist at Kennedy Space Center, devised a software program to calculate the unknown dimension of the material in the images, and soon after the investigation was complete, continued to enhance the technology. Eventually, the program that assisted in the Columbia investigation became available for licensing.
Source record↗
The role of metrics and measurements in a software intensive total quality management environment
Paramax Space Systems began its mission as a member of the Rockwell Space Operations Company (RSOC) team which was the successful bidder on a massive operations consolidation contract for the Mission Operations Directorate (MOD) at JSC. The contract awarded to the team was the Space Transportation System Operations Contract (STSOC). Our initial challenge was to accept responsibility for a very large, highly complex and fragmented collection of software from eleven different contractors and transform it into a coherent, operational baseline. Concurrently, we had to integrate a diverse group of people from eleven different companies into a single, cohesive team. Paramax executives recognized the absolute necessity to develop a business culture based on the concept of employee involvement to execute and improve the complex process of our new environment. Our executives clearly understood that management needed to set the example and lead the way to quality improvement. The total quality management policy and the metrics used in this endeavor are presented.
Daniels, Charles B.↗
A measurement system for large, complex software programs
This paper describes measurement systems required to forecast, measure, and control activities for large, complex software development and support programs. Initial software cost and quality analysis provides the foundation for meaningful management decisions as a project evolves. In modeling the cost and quality of software systems, the relationship between the functionality, quality, cost, and schedule of the product must be considered. This explicit relationship is dictated by the criticality of the software being developed. This balance between cost and quality is a viable software engineering trade-off throughout the life cycle. Therefore, the ability to accurately estimate the cost and quality of software systems is essential to providing reliable software on time and within budget. Software cost models relate the product error rate to the percent of the project labor that is required for independent verification and validation. The criticality of the software determines which cost model is used to estimate the labor required to develop the software. Software quality models yield an expected error discovery rate based on the software size, criticality, software development environment, and the level of competence of the project and developers with respect to the processes being employed.
Rone, Kyle Y.↗
Software Project Management and Measurement on the World-Wide-Web (WWW)
We briefly describe a system for forms-based, work-flow management that helps members of a software development team overcome geographical barriers to collaboration. Our system, called the Web Integrated Software Environment (WISE), is implemented as a World-Wide-Web service that allows for management and measurement of software development projects based on dynamic analysis of change activity in the workflow. WISE tracks issues in a software development process, provides informal communication between the users with different roles, supports to-do lists, and helps in software process improvement. WISE minimizes the time devoted to metrics collection and analysis by providing implicit delivery of messages between users based on the content of project documents. The use of a database in WISE is hidden from the users who view WISE as maintaining a personal 'to-do list' of tasks related to the many projects on which they may play different roles.
Callahan, John↗
Quality measures and assurance for AI (Artificial Intelligence) software
This report is concerned with the application of software quality and evaluation measures to AI software and, more broadly, with the question of quality assurance for AI software. Considered are not only the metrics that attempt to measure some aspect of software quality, but also the methodologies and techniques (such as systematic testing) that attempt to improve some dimension of quality, without necessarily quantifying the extent of the improvement. The report is divided into three parts Part 1 reviews existing software quality measures, i.e., those that have been developed for, and applied to, conventional software. Part 2 considers the characteristics of AI software, the applicability and potential utility of measures and techniques identified in the first part, and reviews those few methods developed specifically for AI software. Part 3 presents an assessment and recommendations for the further exploration of this important area.
Rushby, John↗
Measuring Ada as a software development technology in the Software Engineering Laboratory (SEL)
An experiment is in progress to measure the effectiveness of Ada in the National Aeronautics and Space Administration/Goddard Space Flight Center flight dynamics software development environment. The experiment features the parallel development of software in FORTRAN and Ada. The experiment organization, objectives, and status are discussed. Experiences with an Ada training program and data from the development of a 5700-line Ada training exercise are reported.
Agresti, W. W.↗
A Taxonomy of Object-Oriented Measures Modeling the Object Oriented Space
In order to control the quality of software and the software development process, it is important to understand the measurement of software. A first step toward a better comprehension of software measurement is the categorization of software measures by some meaningful taxonomy. The most worthwhile taxonomy would capture the fundamental nature of the object-oriented (O-O) space. The principal characteristics of object-oriented software offer a starting point for such a categorization of measures. This paper introduces a taxonomy of measures based upon fourteen characteristics of object-oriented software gathered from the literature. This taxonomy allows us to easily see gaps or redundancies in the existing O-O measures. The taxonomy also clearly differentiates among taxa so that there is no ambiguity as to the taxon to which a measure belongs. The taxonomy has been populated with measures taken from the literature.
Neal, Ralph D.↗
A Taxonomy of Object-Oriented Measures Modeling the Object-Oriented Space
In order to control the quality of software and the software development process, it is important to understand the measurement of software. A first step toward a better comprehension of software measurement is the categorization of software measures by some meaningful taxonomy. The most worthwhile taxonomy would capture the fundamental nature of the object-oriented (O-O) space. The principal characteristics of object-oriented software offer a starting point for such a categorization of measures. This paper introduces a taxonomy of measures based upon fourteen characteristics of object-oriented software gathered from the literature. This taxonomy allows us to easily see gaps or redundancies in the existing O-O measures. The taxonomy also clearly differentiates among taxa so that there is no ambiguity as to the taxon to which a measure belongs. The taxonomy has been populated with measures taken from the literature.
Neal, Ralph D.↗
24.1.3.4 Upgraded Fixed Energy Response Function Analysis with Multiple Efficiencies (FRAM) Software for U/Pu/MOX Mass Measurements
Fixed-energy Response-function Analysis with Multiple efficiency (FRAM) is a software code designed primarily for plutonium and uranium isotopic analysis. It is widely used in both the domestic and international safeguards community. FRAM can quickly and accurately determine the isotopic compositions of plutonium, uranium, and mixed oxides (MOX) when measuring with a high-purity germanium (HPGe), cadmium zinc telluride (CZT), or lanthanum bromide (LaBr 3 ) detector. The capabilities of FRAM have been enhanced to analyze the data of the pixelated CZT detector (made by H3D) and to measure the mass of plutonium, uranium, and MOX. Both the isotopic composition and mass of the item can be quickly determined with one measurement using a gamma detector with FRAM v.7.1.
46 INSTRUMENTATION RELATED TO NUCLEAR SCIENCE AND ↗
A JPL Software Reliability Study and a Windows-Based Software Reliability Tool
This paper describes the development of a software reliability measurement tool.
software reliability measurement tools CASRE↗