Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Development assurance”

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.

At least 703 records · Page 39

Measurement of thermoelectric inhomogeneity of thermocouples

In a thermocouple probe that has significantly inhomogeneous legs, the relationship between emf and temperature is indefinite and depends on temperature distribution along the circuit. An inhomogeneous thermocouple cannot be calibrated to arbitrarily small uncertainty. Therefore, testing for inhomogeneities is a necessary preliminary to meaningful calibration. As most significant inhomogeneity that does occur is introduced during use (and sometimes during calibration) a post-test inhomogeneity measurement should also be employed to detect degradation that might have substantially affected the data. This paper presents a practical test method that is being developed for the observation, interpretation, and application of thermoelectric inhomogeneity as a routine quality assurance measurement that is an essential complement to traditional sheathed thermocouple calibration.

Reed, R. P.↗

Software Engineering Guidebook

The Software Engineering Guidebook describes SEPG (Software Engineering Process Group) supported processes and techniques for engineering quality software in NASA environments. Three process models are supported: structured, object-oriented, and evolutionary rapid-prototyping. The guidebook covers software life-cycles, engineering, assurance, and configuration management. The guidebook is written for managers and engineers who manage, develop, enhance, and/or maintain software under the Computer Software Services Contract.

Connell, John↗

Continuous Risk Management at NASA

NPG 7120.5A, "NASA Program and Project Management Processes and Requirements" enacted in April, 1998, requires that "The program or project manager shall apply risk management principles..." The Software Assurance Technology Center (SATC) at NASA GSFC has been tasked with the responsibility for developing and teaching a systems level course for risk management that provides information on how to comply with this edict. The course was developed in conjunction with the Software Engineering Institute at Carnegie Mellon University, then tailored to the NASA systems community. This presentation will briefly discuss the six functions for risk management: (1) Identify the risks in a specific format; (2) Analyze the risk probability, impact/severity, and timeframe; (3) Plan the approach; (4) Track the risk through data compilation and analysis; (5) Control and monitor the risk; (6) Communicate and document the process and decisions. This risk management structure of functions has been taught to projects at all NASA Centers and is being successfully implemented on many projects. This presentation will give project managers the information they need to understand if risk management is to be effectively implemented on their projects at a cost they can afford.

Hammer, Theodore F.↗

Continuous Risk Management: A NASA Program Initiative

NPG 7120.5A, "NASA Program and Project Management Processes and Requirements" enacted in April, 1998, requires that "The program or project manager shall apply risk management principles..." The Software Assurance Technology Center (SATC) at NASA GSFC has been tasked with the responsibility for developing and teaching a systems level course for risk management that provides information on how to comply with this edict. The course was developed in conjunction with the Software Engineering Institute at Carnegie Mellon University, then tailored to the NASA systems community. This presentation will briefly discuss the six functions for risk management: (1) Identify the risks in a specific format; (2) Analyze the risk probability, impact/severity, and timeframe; (3) Plan the approach; (4) Track the risk through data compilation and analysis; (5) Control and monitor the risk; (6) Communicate and document the process and decisions.

Hammer, Theodore F.↗

Transformational Systems Concepts and Technologies for Our Future in Space

NASA is constantly searching for new ideas and approaches yielding opportunities for assuring maximum returns on space infrastructure investments. Perhaps the idea of transformational innovation in developing space systems is long overdue. However, the concept of utilizing modular space system designs combined with stepping-stone development processes has merit and promises to return several times the original investment since each new space system or component is not treated as a unique and/or discrete design and development challenge. New space systems can be planned and designed so that each builds on the technology of previous systems and provides capabilities to support future advanced systems. Subsystems can be designed to use common modular components and achieve economies of scale, production, and operation. Standards, interoperability, and "plug and play" capabilities, when implemented vigorously and consistently, will result in systems that can be upgraded effectively with new technologies. This workshop explored many building-block approaches via way of example across a broad spectrum of technology discipline areas for potentially transforming space systems and inspiring future innovation. Details describing the workshop structure, process, and results are contained in this Conference Publication.

Howell, J. T.↗

Integrating International Engineering Organizations For Successful ISS Operations

The International Space Station (ISS) is a multinational orbiting space laboratory that is built in cooperation with 16 nations. The design and sustaining engineering expertise is spread worldwide. As the number of Partners with orbiting elements on the ISS grows, the challenge NASA is facing as the ISS integrator is to ensure that engineering expertise and data are accessible in a timely fashion to ensure ongoing operations and mission success. Integrating international engineering teams requires definition and agreement on common processes and responsibilities, joint training and the emergence of a unique engineering team culture. ISS engineers face daunting logistical and political challenges regarding data sharing requirements. To assure systematic information sharing and anomaly resolution of integrated anomalies, the ISS Partners are developing multi-lateral engineering interface procedures. Data sharing and individual responsibility are key aspects of this plan. This paper describes several examples of successful multilateral anomaly resolution. These successes were used to form the framework of the Partner to Partner engineering interface procedures, and this paper describes those currently documented multilateral engineering processes. Furthermore, it addresses the challenges experienced to date, and the forward work expected in establishing a successful working relationship with Partners as their hardware is launched.

Blome, Elizabeth↗

Kennedy Space Center (KSC) Mishap Response Plan

KSC Medical Operations, in exercising the KSC Psychological Triage Plan, provided crewmember family support following notification of the Columbia accident. KSC Medical Operations also provided field support in working with FEMA and EPA to assure adequate occupational medicine and environmental health care of KSC workers. In addition, the development of policy and procedures for handling and clearing biohazardous debris material in the KSC reconstruction hangar was prepared and implemented.

Scarpa, Philip↗

Autonomous Space Shuttle

The continued assembly and operation of the International Space Station (ISS) is the cornerstone within NASA's overall Strategic P an. As indicated in NASA's Integrated Space Transportation Plan (ISTP), the International Space Station requires Shuttle to fly through at least the middle of the next decade to complete assembly of the Station, provide crew transport, and to provide heavy lift up and down mass capability. The ISTP reflects a tight coupling among the Station, Shuttle, and OSP programs to support our Nation's space goal . While the Shuttle is a critical component of this ISTP, there is a new emphasis for the need to achieve greater efficiency and safety in transporting crews to and from the Space Station. This need is being addressed through the Orbital Space Plane (OSP) Program. However, the OSP is being designed to "complement" the Shuttle as the primary means for crew transfer, and will not replace all the Shuttle's capabilities. The unique heavy lift capabilities of the Space Shuttle is essential for both ISS, as well as other potential missions extending beyond low Earth orbit. One concept under discussion to better fulfill this role of a heavy lift carrier, is the transformation of the Shuttle to an "un-piloted" autonomous system. This concept would eliminate the loss of crew risk, while providing a substantial increase in payload to orbit capability. Using the guidelines reflected in the NASA ISTP, the autonomous Shuttle a simplified concept of operations can be described as; "a re-supply of cargo to the ISS through the use of an un-piloted Shuttle vehicle from launch through landing". Although this is the primary mission profile, the other major consideration in developing an autonomous Shuttle is maintaining a crew transportation capability to ISS as an assured human access to space capability.

Siders, Jeffrey A.↗

An MBSE Approach for Developing an Autonomous Rover Platform

The proliferation of increasingly autonomous systems calls for new ways to address how safety is assured. As these systems become more advanced and complex, it becomes more important to model and prototype autonomous functions at the systems level and the functions that assure they are operating safely and as expected. To that effect, researchers at the National Aeronautics and Space Administration (NASA) 's Robust Software Engineering (RSE) group are working on prototyping a Research Autonomous Vehicle, commonly referred to as R-RAV. The R-RAV is an autonomous rover platform designed to act as a case study for assured autonomy research. Moreover, an overarching goal is for the R-RAV to serve as a training ground for other mission projects. In this paper, we will detail how we have used a Model-Based Systems Engineering (MBSE) approach to model a prototype of the R-RAV and test and verify its different functionalities.

MBSE↗

Guide de base pour l'energie solaire hors reseau en Haiti: 2. Produits cles et assurance qualite pour le solaire hors reseau

Cette formation donne un apercu des informations et des concepts cles de l'energie solaire hors reseau en Haiti, renforcant ainsi les connaissances fondamentales et la capacite de catalyser l'interet pour l'energie solaire hors reseau pour l'electrification rurale en Haiti. Ce cours a rythme libre est offert en anglais et en francais et couvre une variete de sujets lies a l'acces a l'energie en Haiti, notamment les produits solaires hors reseau, le potentiel du marche en Haiti, les considerations liees a l'offre et a la demande, la conception, l'installation et la maintenance du systeme, -modeles commerciaux solaires en reseau, modelisation financiere, genre et acces a l'energie, utilisation productive de l'energie et adaptation au climat. La formation est destinee aux etudiants universitaires, aux partenaires gouvernementaux, aux ONG, aux bailleurs de fonds, aux partenaires de developpement, aux professionnels, etc. Aucune connaissance prealable du solaire hors reseau ou d'Haiti n'est requise pour beneficier de cette formation. See NREL/PR-7A40-89245 for the English translation of this document.

ENERGY PLANNING, POLICY, AND ECONOMY,SOLAR ENERGY↗

Validation and Verification (V&V) of Safety-Critical Systems Operating Under Off-Nominal Conditions

Loss of control (LOC) remains one of the largest contributors to aircraft fatal accidents worldwide. Aircraft LOC accidents are highly complex in that they can result from numerous causal and contributing factors acting alone or more often in combination. Hence, there is no single intervention strategy to prevent these accidents. Research is underway at the National Aeronautics and Space Administration (NASA) in the development of advanced onboard system technologies for preventing or recovering from loss of vehicle control and for assuring safe operation under off-nominal conditions associated with aircraft LOC accidents. The transition of these technologies into the commercial fleet will require their extensive validation and verification (V&V) and ultimate certification. The V&V of complex integrated systems poses highly significant technical challenges and is the subject of a parallel research effort at NASA. This chapter summarizes the V&V problem and presents a proposed process that could be applied to complex integrated safety-critical systems developed for preventing aircraft LOC accidents. A summary of recent research accomplishments in this effort is referenced.

Belcastro, Christine M.↗

Assurance of Fault Management: Risk-Significant Adverse Condition Awareness

Fault Management (FM) systems are ranked high in risk-based assessment of criticality within flight software, emphasizing the importance of establishing highly competent domain expertise to provide assurance for NASA projects, especially as spaceflight systems continue to increase in complexity. Insight into specific characteristics of FM architectures seen embedded within safety- and mission-critical software systems analyzed by the NASA Independent Verification Validation (IVV) Program has been enhanced with an FM Technical Reference (TR) suite. Benefits are aimed beyond the IVV community to those that seek ways to efficiently and effectively provide software assurance to reduce the FM risk posture of NASA and other space missions. The identification of particular FM architectures, visibility, and associated IVV techniques provides a TR suite that enables greater assurance that critical software systems will adequately protect against faults and respond to adverse conditions. The role FM has with regard to overall asset protection of flight software systems is being addressed with the development of an adverse condition (AC) database encompassing flight software vulnerabilities.Identification of potential off-nominal conditions and analysis to determine how a system responds to these conditions are important aspects of hazard analysis and fault management. Understanding what ACs the mission may face, and ensuring they are prevented or addressed is the responsibility of the assurance team, which necessarily should have insight into ACs beyond those defined by the project itself. Research efforts sponsored by NASAs Office of Safety and Mission Assurance defined terminology, categorized data fields, and designed a baseline repository that centralizes and compiles a comprehensive listing of ACs and correlated data relevant across many NASA missions. This prototype tool helps projects improve analysis by tracking ACs, and allowing queries based on project, mission type, domain component, causal fault, and other key characteristics. The repository has a firm structure, initial collection of data, and an interface established for informational queries, with plans for integration within the Enterprise Architecture at NASA IVV, enabling support and accessibility across the Agency. The development of an improved workflow process for adaptive, risk-informed FM assurance is currently underway.

Software Verification & Validation↗

Physics-Based Design Tools for Lightweight Ceramic Composite Turbine Components with Durable Microstructures

Under the Supersonics Project of the NASA Fundamental Aeronautics Program, modeling and experimental efforts are underway to develop generic physics-based tools to better implement lightweight ceramic matrix composites into supersonic engine components and to assure sufficient durability for these components in the engine environment. These activities, which have a crosscutting aspect for other areas of the Fundamental Aero program, are focusing primarily on improving the multi-directional design strength and rupture strength of high-performance SiC/SiC composites by advanced fiber architecture design. This presentation discusses progress in tool development with particular focus on the use of 2.5D-woven architectures and state-of-the-art constituents for a generic un-cooled SiC/SiC low-pressure turbine blade.

DiCarlo, James A.↗

Formal Foundations for Hierarchical Safety Cases

Safety cases are increasingly being required in many safety-critical domains to assure, using structured argumentation and evidence, that a system is acceptably safe. However, comprehensive system-wide safety arguments present appreciable challenges to develop, understand, evaluate, and manage, partly due to the volume of information that they aggregate, such as the results of hazard analysis, requirements analysis, testing, formal verification, and other engineering activities. Previously, we have proposed hierarchical safety cases, hicases, to aid the comprehension of safety case argument structures. In this paper, we build on a formal notion of safety case to formalise the use of hierarchy as a structuring technique, and show that hicases satisfy several desirable properties. Our aim is to provide a formal, theoretical foundation for safety cases. In particular, we believe that tools for high assurance systems should be granted similar assurance to the systems to which they are applied. To this end, we formally specify and prove the correctness of key operations for constructing and managing hicases, which gives the specification for implementing hicases in AdvoCATE, our toolset for safety case automation. We motivate and explain the theory with the help of a simple running example, extracted from a real safety case and developed using AdvoCATE.

Hierarchy↗

Systems Integration Processes for NASA's Crew Launch Vehicle

NASA's Exploration Initiative will require development of many new elements to constitute a robust system of systems. New launch vehicles are needed to place cargo and crew in stable low earth orbit. This paper examines the systems integration processes NASA is utilizing to ensure integration and control of propulsion and non-propulsion elements within NASA's Crew Launch Vehicle (CLV). The objective of the CLV is to provide the transportation capabilities to meet the Constellation Program requirements for delivering a Crew Exploration Vehicle (CEV) or other payload to Low Earth Orbit (LEO) in support of the lunar and Mars missions. The CLV must successfully provide the capability within cost and schedule with an acceptable risk approach. This paper will describe in detail the systems engineering management processes that will be applied to assure CLV Project success through complete and efficient technical integration. Discussion of specific processes for requirements development and verification, integrated design and analysis, integrated simulation and testing and the integration of reliability, maintainability and supportability (RMS) into the design will also be included. The CLV Project is broken logically into elements by the major hardware groupings, and associated management, system engineering, and integration functions. The processes to be described herein are designed to integrate within these CLV elements and among the other Constellation projects. Launch vehicle stack integration (CLV to CEV, and Ground and Flight Operations integration) throughout the life cycle, including integrated vehicle performance through orbital insertion, recovery of the first stage, and reentry of the upper stage will also be discussed. The processes for decomposing requirements to the Elements and ensuring that requirements have been correctly validated, decomposed, allocated, and that the verification requirements are properly defined to ensure that the system design meets requirements will be discussed.

Reuter, James L.↗

A CubeSat-Payload Radiation-Reliability Assurance Case using Goal Structuring Notation

CubeSats have become an attractive platform for universities, industry, and government space missions because they are cheaper and quicker to develop than full-scale satellites. One way CubeSats keep costs low is by using commercial off-the-shelf parts (COTS) instead of space-qualified parts. Space-qualified parts are often costlier, larger, and consume more power than their commercial counterparts precluding their use within the CubeSat form-factor. Given typical power budgets, monetary budgets, and timelines for CubeSat missions, conventional radiation hardness assurance, like the use of space-qualified parts and radiation testing campaigns of COTS parts, is not practical. Instead, a system-level approach to radiation effects mitigation is needed. In this paper an assurance case for a system-level approach to mitigate radiation effects of a CubeSat science experiment is expressed using Goal Structuring Notation (GSN), a graphical argument standard. The case specifically looks at three main mitigation strategies for the radiation environment: total ionizing dose (TID) screening of parts, detection and recovery from single-event latch-ups (SEL) and single-event functional interrupts (SEFI). The graphical assurance case presented makes a qualitative argument for the radiation reliability of the CubeSat experiment using part and system-level mitigation strategies.

COTS↗

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.↗

Total Quality Management: Analysis, Evaluation and Implementation Within ACRV Project Teams

Total quality management (TQM) is a cooperative form of doing business that relies on the talents of everyone in an organization to continually improve quality and productivity, using teams and an assortment of statistical and measurement tools. The Assured Crew Return Vehicle (ACRV) Project Office was identified as an excellent project in which to demonstrate the applications and benefits of TQM processes. As the ACRV Program moves through its various stages of development, it is vital that effectiveness and efficiency be maintained in order to provide the Space Station Freedom (SSF) crew an affordable, on-time assured return to Earth. A critical factor for the success of the ACRV is attaining the maximum benefit from the resources applied to the program. Through a series of four tutorials on various quality improvement techniques, and numerous one-on-one sessions during the SSF's 10-week term in the project office, results were obtained which are aiding the ACRV Office in implementing a disciplined, ongoing process for generating fundamental decisions and actions that shape and guide the organization. Significant advances were made in improving the processes for two particular groups - the correspondence distribution team and the WATER Test team. Numerous people from across JSC were a part of the various team activities including engineering, man systems, and safety. The work also included significant interaction with the support contractor to the ACRV Project. The results of the improvement activities can be used as models for other organizations desiring to operate under a system of continuous improvement. In particular, they have advanced the ACRV Project Teams further down the path of continuous improvement, in support of a working philosophy of TQM.

Raiman, Laura B.↗