Practical Issues in Measuring Software Quality
Explore the source record for details and available documents.
software mesurement software quality software reli↗
SEARCH · Engineering Papers
Results for “software reliability software”
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.
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↗
Developing Fault Models for Space Mission Software
A viewgraph presentation on the development of fault models for space mission software is shown. The topics include: 1) Goal: Improve Understanding of Technology Fault Generation Process; 2) Required Measurement; 3) Measuring Structural Evolution; 4) Module Attributes; 5) Principal Components of Raw Metrics; 6) The Measurement Process; 7) View of Structural Evolution at the System and Module Level; 8) Identifying and Counting Faults; 9) Fault Enumeration; 10) Modeling Fault Content; 11) Modeling Results; 12) Current and Future Work; and 13) Discussion and Conclusions.
software measurements↗
Safety and Mission Assurance for In-House Design Lessons Learned from Ares I Upper Stage
This viewgraph presentation identifies lessons learned in the course of the Ares I Upper Stage design and in-house development effort. The contents include: 1) Constellation Organization; 2) Upper Stage Organization; 3) Presentation Structure; 4) Lesson-Importance of Systems Engineering/Integration; 5) Lesson-Importance of Early S&MA Involvement; 6) Lesson-Importance of Appropriate Staffing Levels; 7) Lesson-Importance S&MA Team Deployment; 8) Lesson-Understanding of S&MA In-Line Engineering versus Assurance; 9) Lesson-Importance of Close Coordination between Supportability and Reliability/Maintainability; 10) Lesson-Importance of Engineering Data Systems; 11) Lesson-Importance of Early Development of Supporting Databases; 12) Lesson-Importance of Coordination with Safety Assessment/Review Panels; 13) Lesson-Implementation of Software Reliability; 14) Lesson-Implementation of S&MA Technical Authority/Chief S&MA Officer; 15) Lesson-Importance of S&MA Evaluation of Project Risks; 16) Lesson-Implementation of Critical Items List and Government Mandatory Inspections; 17) Lesson-Implementation of Critical Items List Mandatory Inspections; 18) Lesson-Implementation of Test Article Safety Analysis; and 19) Lesson-Importance of Procurement Quality.
Anderson, Joel M.↗
Space Telecommunications Radio System (STRS) Application Repository Design and Analysis
The Space Telecommunications Radio System (STRS) Application Repository Design and Analysis document describes the STRS application repository for software-defined radio (SDR) applications intended to be compliant to the STRS Architecture Standard. The document provides information about the submission of artifacts to the STRS application repository, to provide information to the potential users of that information, and for the systems engineer to understand the requirements, concepts, and approach to the STRS application repository. The STRS application repository is intended to capture knowledge, documents, and other artifacts for each waveform application or other application outside of its project so that when the project ends, the knowledge is retained. The document describes the transmission of technology from mission to mission capturing lessons learned that are used for continuous improvement across projects and supporting NASA Procedural Requirements (NPRs) for performing software engineering projects and NASAs release process.
information retrieval↗
Design, Development, and Testing of a UAV Hardware-in-the-Loop Testbed for Aviation and Airspace Prognostics Research
The airspace is becoming more and more complicated, and will continue to do so in the future with the integration of Unmanned Aerial Vehicles (UAVs), autonomy, spacecraft, other forms of aviation technology into the airspace. The new technology and complexity increases the importance and difficulty of safety assurance. Additionally, testing new technologies on complex aviation systems & systems of systems can be very difficult, expensive, and sometimes unsafe in real life scenarios. Prognostic methodology provides an estimate of the health and risks of a component, vehicle, or airspace and knowledge of how that will change over time. That measure is especially useful in safety determination, mission planning, and maintenance scheduling. The developed testbed will be used to validate prediction algorithms for the real-time safety monitoring of the National Airspace System (NAS) and the prediction of unsafe events. The framework injects flight related anomalies related to ground systems, routing, airport congestion, etc. to test and verify algorithms for NAS safety. In our research work, we develop a live, distributed, hardware-in-the-loop testbed for aviation and airspace prognostics along with exploring further research possibilities to verify and validate future algorithms for NAS safety. The testbed integrates virtual aircraft using the X-Plane simulator and X-PlaneConnect toolbox, UAVs using onboard sensors and cellular communications, and hardware in the loop components. In addition, the testbed includes an additional research framework to support and simplify future research activities. It enables safe, accurate, and inexpensive experimentation and research into airspace and vehicle prognosis that would not have been possible otherwise. This paper describes the design, development, and testing of this system. Software reliability, safety and latency are some of the critical design considerations in development of the testbed. Integration of HITL elements in the development phases and veri cation/ validation are key elements to this report.
HITL↗
A Virtual Laboratory for Aviation and Airspace Prognostics Research
Integration of Unmanned Aerial Vehicles (UAVs), autonomy, spacecraft, and other aviation technologies, in the airspace is becoming more and more complicated, and will continue to do so in the future. Inclusion of new technology and complexity into the airspace increases the importance and difficulty of safety assurance. Additionally, testing new technologies on complex aviation systems and systems of systems can be challenging, expensive, and at times unsafe when implementing real life scenarios. The application of prognostics to aviation and airspace management may produce new tools and insight into these problems. Prognostic methodology provides an estimate of the health and risks of a component, vehicle, or airspace and knowledge of how that will change over time. That measure is especially useful in safety determination, mission planning, and maintenance scheduling. In our research, we develop a live, distributed, hardware- in-the-loop Prognostics Virtual Laboratory testbed for aviation and airspace prognostics. The developed testbed will be used to validate prediction algorithms for the real-time safety monitoring of the National Airspace System (NAS) and the prediction of unsafe events. In our earlier work1 we discussed the initial Prognostics Virtual Laboratory testbed development work and related results for milestones 1 & 2. This paper describes the design, development, and testing of the integrated tested which are part of milestone 3, along with our next steps for validation of this work. Through a framework consisting of software/hardware modules and associated interface clients, the distributed testbed enables safe, accurate, and inexpensive experimentation and research into airspace and vehicle prognosis that would not have been possible otherwise. The testbed modules can be used cohesively to construct complex and relevant airspace scenarios for research. Four modules are key to this research: the virtual aircraft module which uses the X-Plane simulator and X-PlaneConnect toolbox, the live aircraft module which connects fielded aircraft using onboard cellular communications devices, the hardware in the loop (HITL) module which connects laboratory based bench-top hardware testbeds and the research module which contains diagnostics and prognostics tools for analysis of live air traffic situations and vehicle health conditions. The testbed also features other modules for data recording and playback, information visualization, and air traffic generation. Software reliability, safety, and latency are some of the critical design considerations in development of the testbed.
LVC-DE↗
Staffing Strategies for Maintenance of Critical Software Systems at the Jet Propulsion Laboratory
The Mission Design and Navigation Software Group at the Jet Propulsion Laboratory (JPL) maintains mission critical software systems. We have good empirical data and models for maintenance demand—when defects will occur, how many and how severe they will be, and how much effort is needed to address them. However, determining the level of staffing needed to address maintenance issues is an ongoing challenge and is often done ad-hoc. There are two common strategies are (1) reactive – add/remove staff as needed to respond to maintenance issues, and (2) capacitive – retain a given staff size to address issues as they occur, proactively address issues and prevent defects.
software maintenance↗
Status of the Four Bed Carbon Dioxide Scrubber ISS Technology Demonstration
The Four Bed Carbon Dioxide Scrubber flight demonstration is presently operating onboard the International Space Station. After being launched in August and activated in September 2021, the system has been removing metabolic CO2 from the cabin as a supplement and replacement for other CO2 removal systems, specifically the two Carbon Dioxide Removal Assemblies. This paper describes on-orbit operations and changes (including installation of the Calnetix blower) during 2022 and early 2023. Performance of the system especially as affected by changes in the on-orbit configuration will be described. System reliability, software changes, and ongoing efforts will be summarized.
Life Support↗
Status of the Four Bed Carbon Dioxide Scrubber ISS Technology Demonstration 2022-2023
The Four Bed Carbon Dioxide Scrubber flight demonstration is presently operating onboard the International Space Station. After being launched in August and activated in September 2021, the system has been removing metabolic CO2 from the cabin as a supplement and replacement for other CO2 removal systems, specifically the two Carbon Dioxide Removal Assemblies. This paper describes on-orbit operations and changes (including installation of the Calnetix blower) during 2022 and early 2023. Performance of the system especially as affected by changes in the on-orbit configuration will be described. System reliability, software changes, and ongoing efforts will be summarized.
Life Support↗
Status of the Four Bed Carbon Dioxide Scrubber ISS Technology Demonstration 2023-2024
The Four Bed Carbon Dioxide Scrubber (FBCO2) flight demonstration is presently operating as a primary CO 2 removal system onboard the International Space Station (ISS). After activation in October 2021, FBCO2 has been removing metabolic CO 2 from the ISS cabin where it is supplementing or fully replacing the heritage systems. This paper describes the past year’s accomplishments and forward outlook. The performance of the new blower, efforts toward closed-loop operation, and further on-orbit modifications will also be detailed. System reliability, software changes, and ongoing efforts will be summarized.
Life Support↗
IV and V Issues in Achieving High Reliability and Safety in Critical Control System Software
Risk analysis and integrated verification and validation are two important elements in a plan for ensuring the safety of critical software systems. We describe an approach we are currently developing for integrating risk analysis, and metrics analysis, and propose a fault predictor that would integrate the results of these activities. Practical difficulties associated with our approach are also discussed, as are limitations of the proposed predictor. We conclude with a discussion of what as been learned to date, and with suggestions for future work.
validation software reliability software risk asse↗
Infusing Reliability Techniques into Software Safety Analysis
Software safety analysis for a large software intensive system is always a challenge. Software safety practitioners need to ensure that software related hazards are completely identified, controlled, and tracked. This paper discusses in detail how to incorporate the traditional reliability techniques into the entire software safety analysis process. In addition, this paper addresses how information can be effectively shared between the various practitioners involved in the software safety analyses. The author has successfully applied the approach to several aerospace applications. Examples are provided to illustrate the key steps of the proposed approach.
FTA↗
Study of a unified hardware and software fault-tolerant architecture
A unified architectural concept, called the Fault Tolerant Processor Attached Processor (FTP-AP), that can tolerate hardware as well as software faults is proposed for applications requiring ultrareliable computation capability. An emulation of the FTP-AP architecture, consisting of a breadboard Motorola 68010-based quadruply redundant Fault Tolerant Processor, four VAX 750s as attached processors, and four versions of a transport aircraft yaw damper control law, is used as a testbed in the AIRLAB to examine a number of critical issues. Solutions of several basic problems associated with N-Version software are proposed and implemented on the testbed. This includes a confidence voter to resolve coincident errors in N-Version software. A reliability model of N-Version software that is based upon the recent understanding of software failure mechanisms is also developed. The basic FTP-AP architectural concept appears suitable for hosting N-Version application software while at the same time tolerating hardware failures. Architectural enhancements for greater efficiency, software reliability modeling, and N-Version issues that merit further research are identified.
Lala, Jaynarayan↗
Software For Analysis Of Reliability, Redundancy, And Cost
CARRAC is software tool for combined analysis of reliability, redundancy, and cost of alternative choices of subsystem that is part of larger system. Uses various parameters entered from computer keyboard to determine subsystem and redundancy method (if any) that minimizes cost. Also, calculation selected from five different mathematical models that enable application of CARRAC to wide variety of cases. Uses parameters to calculate and compare total expected cost for alternatives of a chosen subsystem. Written in Microsoft Quick-Basic v4.5.
Patterson, R. L.↗
SAPHIRE 8 Basics An Introduction to Probabilistic Risk Assessment via the Systems Analysis Program for Hands-On Integrated Reliability Evaluations (SAPHIRE) Software P-201
The SAPHIRE Basics course material is intended to both (1) provide guidance for learning SAPHIRE during the Basics class and (2) become a stand-alone reference document after finishing the class. Thus, the format for the class material is a combination of the traditional “overhead-type” of presentation information with a structured, reference-type document.
97 MATHEMATICS AND COMPUTING↗
Advanced SAPHIRE 8 Modeling Methods for Probabilistic Risk Assessment via the Systems Analysis Program for Hands-On Integrated Reliability Evaluations (SAPHIRE) Software P-202
1.1. Overview of the Advanced SAPHIRE Material The Advanced SAPHIRE course material is intended to both (1) provide guidance for learning advanced SAPHIRE features during the class and (2) become a stand-alone reference document after finishing the class. Thus, the format for the class material is a combination of the traditional “overhead-type” of presentation information with a structured, reference-type document. Major topics that are covered in the Advanced SAPHIRE class include: Advanced data base concepts such as Model Type (e.g., random, seismic, fire, flood). Definition of house events and how they are used on a sequence-by-sequence basis to manipulate individual fault tree logic using sequence flag sets or fault tree flag sets. ? Basic event templates, compound basic event equation editors, and human error worksheets. A rule-based event tree top event substitution feature (called the Link Event Tree Rule Editor) which allows for top event substitutions. A rule-based cut set post-processing feature (called the Recovery Rules) which allows cut set manipulation. Cut set analysis based upon rule-based end state categories (called End State Analysis). Cut set generation options for both fault trees and event tree sequences. The large event tree methodology and how SAPHIRE can be used to generate sequence cut sets for this method. The transfer of data between SAPHIRE data bases and between other PRA codes (MAR-D).
97 MATHEMATICS AND COMPUTING↗
Reliable Customized Control Software in an R&D Environment
This paper describes the methodology by which we can allow each user or project a high degree of customization. To do this we rely on a mixture of public domain software and locally developed software.
configuration↗