Search NASA⌕ Search

SEARCH · Search NASA

Results for “code compliance”

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 19 records

Recertification analysis and inspection planning for environmental test facilities

Program development and implementation for recertification of pressure vessels used at NASA facilities are outlined, together with inspection procedures. The recertification is carried out in three phases: analysis, inspection planning, and long term inspection plans and management. A data base was developed for each piece of equipment and the associated performance parameters. Either documentation was obtained or NDT was performed on the vessels to confirm design and Code compliance. A Failure Modes and Effects Analysis technique was used to target recurring inspection items and guidelines were drawn up for inspections of parts and systems and intervals between inspections. The steps taken in establishing the program are considered applicable in both research and industrial situations.

Rebeck, K. J.↗

LTF/Fluid and Cryogenic Systems Branch

Functions of the Branch: Cross-Cutting Fluids Engineering; Research and Technology Development of Cryogenic Fluid Management (CFM) Systems; Component and System level; Design, Development Test and Evaluation (DDT&E) for Fluid, CFM, Propellant and Gaseous Systems; Fluid Component Specification and Selection; Code Compliance of Pressurized Systems; Fluid/Cryogenic System Performance Analysis and Trade Studies; Hazards Analysis and Risk Assessment of Fluidic Systems; Fluids Modeling and Simulation Capabilities

Fluid↗

Verification of effective thicknesses for side-grooved compact specimens

The definition of effective thicknesses of the ASTM standard 25 percent side-grooved compact specimens to calculate the elastic compliance, elastic SIF, and elastic-plastic J integral is reevaluated. 3D elastic-plastic analyses of polane-strain, smooth, and 25 percent side-grooved compact specimen models are conducted using the ZIP3D code. Calculated compliance, SIFs, and J-integrals are compared with E-813 solutions.

Shivakumar, Kunigal N.↗

Certifying Domain-Specific Policies

Proof-checking code for compliance to safety policies potentially enables a product-oriented approach to certain aspects of software certification. To date, previous research has focused on generic, low-level programming-language properties such as memory type safety. In this paper we consider proof-checking higher-level domain -specific properties for compliance to safety policies. The paper first describes a framework related to abstract interpretation in which compliance to a class of certification policies can be efficiently calculated Membership equational logic is shown to provide a rich logic for carrying out such calculations, including partiality, for certification. The architecture for a domain-specific certifier is described, followed by an implemented case study. The case study considers consistency of abstract variable attributes in code that performs geometric calculations in Aerospace systems.

Lowry, Michael↗

Synthesizing Safety Conditions for Code Certification Using Meta-Level Programming

In code certification the code consumer publishes a safety policy and the code producer generates a proof that the produced code is in compliance with the published safety policy. In this paper, a novel viewpoint approach towards an implementational re-use oriented framework for code certification is taken. It adopts ingredients from Necula's approach for proof-carrying code, but in this work safety properties can be analyzed on a higher code level than assembly language instructions. It consists of three parts: (1) The specification language is extended to include generic pre-conditions that shall ensure safety at all states that can be reached during program execution. Actual safety requirements can be expressed by providing domain-specific definitions for the generic predicates which act as interface to the environment. (2) The Floyd-Hoare inductive assertion method is refined to obtain proof rules that allow the derivation of the proof obligations in terms of the generic safety predicates. (3) A meta-interpreter is designed and experimentally implemented that enables automatic synthesis of proof obligations for submitted programs by applying the modified Floyd-Hoare rules. The proof obligations have two separate conjuncts, one for functional correctness and another for the generic safety obligations. Proof of the generic obligations, having provided the actual safety definitions as context, ensures domain-specific safety of program execution in a particular environment and is simpler than full program verification.

Eusterbrock, Jutta↗

Credible Computations: Standard and Uncertainty

The discipline of computational fluid dynamics (CFD) is at a crossroad. Most of the significant advances related to computational methods have taken place. The emphasis is now shifting from methods to results. Significant efforts are made in applying CFD to solve design problems. The value of CFD results in design depends on the credibility of computed results for the intended use. The process of establishing credibility requires a standard so that there is a consistency and uniformity in this process and in the interpretation of its outcome. The key element for establishing the credibility is the quantification of uncertainty. This paper presents salient features of a proposed standard and a procedure for determining the uncertainty. A customer of CFD products - computer codes and computed results - expects the following: A computer code in terms of its logic, numerics, and fluid dynamics and the results generated by this code are in compliance with specified requirements. This expectation is fulfilling by verification and validation of these requirements. The verification process assesses whether the problem is solved correctly and the validation process determines whether the right problem is solved. Standards for these processes are recommended. There is always some uncertainty, even if one uses validated models and verified computed results. The value of this uncertainty is important in the design process. This value is obtained by conducting a sensitivity-uncertainty analysis. Sensitivity analysis is generally defined as the procedure for determining the sensitivities of output parameters to input parameters. This analysis is a necessary step in the uncertainty analysis, and the results of this analysis highlight which computed quantities and integrated quantities in computations need to be determined accurately and which quantities do not require such attention. Uncertainty analysis is generally defined as the analysis of the effect of the uncertainties involved in all stages of a process on the final responses. There are two approaches for conducting the uncertainty analysis: experimental and computational. These analyses and approaches are briefly described.

Mehta, Unmeel B.↗

The HiVY Tool Set

Our aim is to validate mission-specific components of spacecraft flight software designs that are specified using state-charts and translated automatically to the final flight code for the mission. We established an automatic translation tool set from state-charts to SPIN for the validation of such mission-specific components. To guarantee compliance with autogenerated flight code, our translation tool set preserves the StateFlow@ semantics. We are now able to specify and validate portions of mission-critical software design and implementation using the exhaustive exploration techniques of model checking.

stateflow↗

Two- and Three-Dimensional Numerical Experiments Representing Two Limiting Cases of an In-Line Pair of Finger Seal Components

The work presented here concerns the numerical development and simulation of the flow, pressure patterns and motion of a pair of fingers arranged behind each other and axially aligned in-line. The fingers represent the basic elemental component of a Finger Seal (FS) and form a tight seal around the rotor. Yet their flexibility allows compliance with rotor motion and in a passive-adaptive mode complies also with the hydrodynamic forces induced by the flowing fluid. While the paper does not treat the actual staggered configuration of a finger seal, the inline arrangement represents a first step towards that final goal. The numerical 2-D (axial-radial) and 3-D results presented herein were obtained using a commercial package (CFD-ACE+). Both models use an integrated numerical approach, which couples the hydrodynamic fluid model (Navier-Stokes based) to the solid mechanics code that models the compliance of the fingers.

Braun, M. J.↗

Protective Coatings

General Magnaplate Corporation's pharmaceutical machine is used in the industry for high speed pressing of pills and capsules. Machine is automatic system for molding glycerine suppositories. These machines are typical of many types of drug production and packaging equipment whose metal parts are treated with space spinoff coatings that promote general machine efficiency and contribute to compliance with stringent federal sanitation codes for pharmaceutical manufacture. Collectively known as "synergistic" coatings, these dry lubricants are bonded to a variety of metals to form an extremely hard slippery surface with long lasting self lubrication. The coatings offer multiple advantages; they cannot chip, peel or be rubbed off. They protect machine parts from corrosion and wear longer, lowering maintenance cost and reduce undesired heat caused by power-robbing friction.

Source record↗

Significance of Strain in Formulation in Theory of Solid Mechanics

The basic theory of solid mechanics was deemed complete circa 1860 when St. Venant provided the strain formulation or the field compatibility condition. The strain formulation was incomplete. The missing portion has been formulated and identified as the boundary compatibility condition (BCC). The BCC, derived through a variational formulation, has been verified through integral theorem and solution of problems. The BCC, unlike the field counterpart, do not trivialize when expressed in displacements. Navier s method and the stiffness formulation have to account for the extra conditions especially at the inter-element boundaries in a finite element model. Completion of the strain formulation has led to the revival of the direct force calculation methods: the Integrated Force Method (IFM) and its dual (IFMD) for finite element analysis, and the completed Beltrami-Michell formulation (CBMF) in elasticity. The benefits from the new methods in elasticity, in finite element analysis, and in design optimization are discussed. Existing solutions and computer codes may have to be adjusted for the compliance of the new conditions. Complacency because the discipline is over a century old and computer codes have been developed for half a century can lead to stagnation of the discipline.

Patnaik, Surya N.↗

X-57 Maxwell Airworthiness Validation Plan

This report is a Final Airworthiness Validation Plan (AVP) and describes how an aircraft like X-57 does (and does not) meet current airworthiness standards. The objective of this report is to create an example certification basis, associated means of compliance (MoC), and method of compliance for a distributed electric propulsion airplane under 14 Code of Federal Regulations (CFR) Part 21, “Certification Procedures for Products and Articles,” and its associated relevant sections of 14 CFR for “Airworthiness Standards” of Part 23, “Normal Category Airplanes,” Part 33 “Aircraft Engines,” and Part 35 “Propellers.” The approach to meet the objective is to use NASA’s X-57 Modification (Mod) IV flight demonstrator as an example and categorize its applicability to the regulations and standards according to the following three conditions: 1. Identify, where applicable, that the MoC and methods of compliance can be associated with existing Standard Specifications and Standard Practices of (ASTM) Committee F39 on Aircraft Systems and ASTM Committee F44 on General Aviation Aircraft; 2. If relevant ASTM standards do not exist, identify means and-or methods of compliance from appropriate Federal Aviation Administration (FAA) Advisory Circulars and other sources to use for the X-57 Mod IV vehicle; or 3. If no relevant certification rule, MoC, or method of compliance exists, highlight this omission and provide recommendations.

Herbert W Schlickenmaier↗

Update on SLD Engineering Tools Development

The airworthiness authorities (FAA, JAA, Transport Canada) will be releasing a draft rule in the 2006 timeframe concerning the operation of aircraft in a Supercooled Large Droplet (SLD) environment aloft. The draft rule will require aircraft manufacturers to demonstrate that their aircraft can operate safely in an SLD environment for a period of time to facilitate a safe exit from the condition. It is anticipated that aircraft manufacturers will require a capability to demonstrate compliance with this rule via experimental means (icing tunnels or tankers) and by analytical means (ice prediction codes). Since existing icing research facilities and analytical codes were not developed to account for SLD conditions, current engineering tools are not adequate to support compliance activities in SLD conditions. Therefore, existing capabilities need to be augmented to include SLD conditions. In response to this need, NASA and its partners conceived a strategy or Roadmap for developing experimental and analytical SLD simulation tools. Following review and refinement by the airworthiness authorities and other international research partners, this technical strategy has been crystallized into a project plan to guide the SLD Engineering Tool Development effort. This paper will provide a brief overview of the latest version of the project plan and technical rationale, and provide a status of selected SLD Engineering Tool Development research tasks which are currently underway.

Miller, Dean R.↗

A new environment to simulate the dynamics in the close proximity of rubble-pile asteroids

This paper presents a new environment to simulate close-proximity dynamics around rubble-pile asteroids. The code provides methods for modeling the asteroid’s gravity field and surface through granular dynamics. It implements stateof-the-art techniques to model both gravity and contact interaction between particles: 1) mutual gravity as either direct N2 or Barnes-Hut GPU-parallel octree and 2) contact dynamics with a soft-body (force-based, smooth dynamics), hard-body (constraint-based, non-smooth dynamics), or hybrid (constraint-based with compliance and damping) approach. A very relevant feature of the code is its ability to handle complex-shaped rigid bodies and their full 6D motion. Examples of spacecraft close-proximity scenarios and their numerical simulations are shown.

Ferrari, Fabio↗

Hardware independence checkout software

ACSI has developed a program utilizing CLIPS to assess compliance with various programming standards. Essentially the program parses C code to extract the names of all function calls. These are asserted as CLIPS facts which also include information about line numbers, source file names, and called functions. Rules have been devised to establish functions called that have not been defined in any of the source parsed. These are compared against lists of standards (represented as facts) using rules that check intersections and/or unions of these. By piping the output into other processes the source is appropriately commented by generating and executing parsed scripts.

Cameron, Barry W.↗

Towards Streamlining Auditing for Compliance With Requirements in Open-Source Software at NASA

Context: NASA requires all software to meet several requirements (NPR 7150.2) depending on software criticality. The instantiation of these requirements may vary per project; however, once decided upon, projects must undergo audits to evaluate compliance with these requirements. Aim: We propose that audit effort can be reduced when requirements are realized by leveraging commonly used open-source infrastructure for version control, issue tracking and continuous integration, and the generated records are analyzed using a repository mining software tool to quantify process compliance. Method: We perform a case study in the NASA-funded Copilot project, utilizing Kaiaulu, a repository mining software tool. We define four software compliance metrics based on the Copilot’s requirements, and analyze their impact on source code quality. Results: Our work demonstrates how it is possible to leverage existing open source tools and platforms to facilitate software certification and qualification, and to streamline the auditing process required even when stringent requirements must be enforced. Conclusion: Together, both project and tool can be utilized to visualize project compliance, and metrics can be defined to more easily identify process irregularities to minimize auditing efforts. Project Repository: github.com/Copilot-Language/copilot Tool Repository: github.com/sailuh/kaiaulu

code-quality↗

Fidelity of the Integrated Force Method Solution

The theory of strain compatibility of the solid mechanics discipline was incomplete since St. Venant's 'strain formulation' in 1876. We have addressed the compatibility condition both in the continuum and the discrete system. This has lead to the formulation of the Integrated Force Method. A dual Integrated Force Method with displacement as the primal variable has also been formulated. A modest finite element code (IFM/Analyzers) based on the IFM theory has been developed. For a set of standard test problems the IFM results were compared with the stiffness method solutions and the MSC/Nastran code. For the problems IFM outperformed the existing methods. Superior IFM performance is attributed to simultaneous compliance of equilibrium equation and compatibility condition. MSC/Nastran organization expressed reluctance to accept the high fidelity IFM solutions. This report discusses the solutions to the examples. No inaccuracy was detected in the IFM solutions. A stiffness method code with a small programming effort can be improved to reap the many IFM benefits when implemented with the IFMD elements. Dr. Halford conducted a peer-review on the Integrated Force Method. Reviewers' response is included.

Hopkins, Dale↗

TPSAS-NF1676L-13678-DND

An area that shows promise in enhancing structural integrity of aircraft and aerospace structures is integral stitched composite technology. The most recent generation of this technology is the Pultruded Rod Stitched Efficient Unitized Structure (PRSEUS) concept. The goal of the PRSEUS concept is to provide damage-containment capability for composite structures while reducing overall structural weight. The National Aeronautics and Space Administration, the Boeing Company, and the Federal Aviation Administration (FAA) have partnered in an effort to assess the damage-containment features of a full-scale curved PRSEUS panel using the FAA Full-Scale Aircraft Structural Test Evaluation and Research facility. The background, test plan, fixture modifications, pre-test analysis, and planned experimental procedure were presented at the 2011 Aircraft Airworthiness and Sustainment Conference. This follow-on paper and presentation will provide details of the experimental procedure, test results, nondestructive inspection results, and preliminary test analysis comparison. The test program included three phases of loading and inspections: Phase I, as-built; Phase II, with barely visible impact damage (BVID); and Phase III, with a two-bay notch severing the central stiffener. Axial tension, internal pressure, and combined axial tension and internal pressure load conditions were applied during each phase using load levels that demonstrate compliance with the strength, deformation, and damage-tolerance requirements of Title 14 Code of Federal Regulations Part 25. Pressure loads were based on an operating pressure of 9.2 psi, designated as 1P, and the axial loads were based on a design limit load (DLL) of 227 kip. The Phase I test results provided a baseline. First, 50 percent limit-load levels were applied for each of the three load cases to verify proper load introduction and repeatability by examining strain and displacement results. Next, three limit-load cases were applied: limit pressure of 12.2 psi (1.33 P), axial DLL of 227 kip, and combined 1P pressure and axial DLL. Linear strain and displacement results were observed in all load cases. For Phase-II testing, the panel was impacted to introduce BVID with an energy of 40 ft-lb, with the impact located between the central stringer stitch line and flange edge. The impact created non-penetrating visual damage with fiber breaks and delamination between the skin and stringer flange. Limit-load conditions were applied followed by pressure overload of 18.4 psi (2P) and ultimate load conditions, defined as 1.5 times DLL. Inspections were performed after each load case; no damage growth was observed. For Phase-III testing, a two-bay notch was machined severing the central stiffener. The panel was then subjected to limit-load conditions, followed by combined 1P pressure while increasing axial tension load to catastrophic failure. As limit combined loads were approached, damage initiation was observed in the form of 45? splitting at 1P + 79% DLL. Axial loading was increased to 1P + 150 percent DLL causing damage to propagate to the adjacent stringer flanges. Damage was contained within the two-bay region by the stitching rows up to 1P + 176% DLL. Axial load was further increased until catastrophic failure, when a stringer rod failed at 1P + 192% DLL. These test results further verify the damage containment features of the PRSEUS concept and suggest its appropriateness for future flight vehicles.

Andrew Bergan↗

Space Telecommunications Radio System (STRS) Compliance Testing

The Space Telecommunications Radio System (STRS) defines an open architecture for software defined radios. This document describes the testing methodology to aid in determining the degree of compliance to the STRS architecture. Non-compliances are reported to the software and hardware developers as well as the NASA project manager so that any non-compliances may be fixed or waivers issued. Since the software developers may be divided into those that provide the operating environment including the operating system and STRS infrastructure (OE) and those that supply the waveform applications, the tests are divided accordingly. The static tests are also divided by the availability of an automated tool that determines whether the source code and configuration files contain the appropriate items. Thus, there are six separate step-by-step test procedures described as well as the corresponding requirements that they test. The six types of STRS compliance tests are: STRS application automated testing, STRS infrastructure automated testing, STRS infrastructure testing by compiling WFCCN with the infrastructure, STRS configuration file testing, STRS application manual code testing, and STRS infrastructure manual code testing. Examples of the input and output of the scripts are shown in the appendices as well as more specific information about what to configure and test in WFCCN for non-compliance. In addition, each STRS requirement is listed and the type of testing briefly described. Attached is also a set of guidelines on what to look for in addition to the requirements to aid in the document review process.

Handler, Louis M.↗