Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “software development”

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 577 records · Page 32
All sourcesNASA NTRSDOE OSTI
NASA NTRS1994

Lessons learned in transitioning to an open systems environment

Software development organizations, both commercial and governmental, are undergoing rapid change spurred by developments in the computing industry. To stay competitive, these organizations must adopt new technologies, skills, and practices quickly. Yet even for an organization with a well-developed set of software engineering models and processes, transitioning to a new technology can be expensive and risky. Current industry trends are leading away from traditional mainframe environments and toward the workstation-based, open systems world. This paper presents the experiences of software engineers on three recent projects that pioneered open systems development for NASA's Flight Dynamics Division of the Goddard Space Flight Center (GSFC).

Boland, Dillard E.↗
DOE OSTI2019

Port Hope Area Initiative: Information Management for A Very Large Radiation Survey - 19567

The Port Hope Area Initiative (PHAI) represents the Government of Canada's commitment to the cleanup and safe, local, long-term management of historic low-level radioactive waste (LLRW) in two Southern Ontario municipalities - Port Hope. The PHAI is based on community-recommended solutions for the cleanup and safe long-term management of approximately 1.7 million cubic meters of LLRW. It is currently one of Canada's largest environmental remediation projects at a cost of over one billion dollars. The PHAI is being implemented by Canadian Nuclear Laboratories (CNL) on behalf of Atomic Energy of Canada Limited, a federal Crown corporation. The waste is the result of radium and uranium processing in Port Hope by the former federal crown corporation Eldorado Nuclear Limited between 1933 and 1988. The waste has been distributed in the Municipality of Port Hope through placement of contaminated materials (e.g. fill), reuse of contaminated objects (e.g. tailings use in concrete, steel posts, structural wood) and air-borne deposition. Signature contaminants of potential concern (COPCs) are Ra-226, Th-230, uranium and arsenic; however, there are an additional 17 COPCs that also need to be considered. A very large amount of information has been collected during the survey and effectively managing and analyzing this information is critical to the success for the property owners, CNL's implementation of the PHAI, and Arcadis. Data collected during the survey includes information pertaining to long-term interior radon gas measurements, interior gamma radiation surveys, contaminated objects and surfaces, exterior gamma radiation and subsurface investigations. exterior gamma radiation surveys. The information management (IM) is structured with SharePoint as a focal point supported by an EQuIS database, mobile data collection and GIS support. The IM process for this project is being advanced using recent software developments to assist with internal activities (e.g. QA) and interactions with CNL including notifications and scheduling and status of property completion. Different applications have been developed to help automate, visualize, actively track, and QA different processes using recent software developments by Microsoft. We have used SharePoint to organize and track our data. Power BI has been used to actively track and visualize our data from Interior gamma surveying to exterior drilling. The creation of dynamic/advanced visualizations in Power BI gathers data daily from our multiple sources and analyzes it for anomalous data and trends. Microsoft Flow syncs with Power BI and has been implemented to automate many processes including the QA of surveys and soil results for identification of LLRW. To tie everything together, our GIS and EQuIS systems are our primary data compilation source that makes our advanced analytics/visualization and automation/tracking our data possible. Specific examples will be discussed, as will challenges encountered during the continuing development of the IM system. The incorporation of software advancements to the existing IM system for Port Hope characterization has improved the quality of the surveys, the tracking of completion, meeting schedule requirements and providing the required data for tracking, report preparation and supporting remediation of contamination on the properties. (authors)

12 MANAGEMENT OF RADIOACTIVE AND NON-RADIOACTIVE W↗
NASA NTRS1999

Development of GENOA Progressive Failure Parallel Processing Software Systems

A capability consisting of software development and experimental techniques has been developed and is described. The capability is integrated into GENOA-PFA to model polymer matrix composite (PMC) structures. The capability considers the physics and mechanics of composite materials and structure by integration of a hierarchical multilevel macro-scale (lamina, laminate, and structure) and micro scale (fiber, matrix, and interface) simulation analyses. The modeling involves (1) ply layering methodology utilizing FEM elements with through-the-thickness representation, (2) simulation of effects of material defects and conditions (e.g., voids, fiber waviness, and residual stress) on global static and cyclic fatigue strengths, (3) including material nonlinearities (by updating properties periodically) and geometrical nonlinearities (by Lagrangian updating), (4) simulating crack initiation. and growth to failure under static, cyclic, creep, and impact loads. (5) progressive fracture analysis to determine durability and damage tolerance. (6) identifying the percent contribution of various possible composite failure modes involved in critical damage events. and (7) determining sensitivities of failure modes to design parameters (e.g., fiber volume fraction, ply thickness, fiber orientation. and adhesive-bond thickness). GENOA-PFA progressive failure analysis is now ready for use to investigate the effects on structural responses to PMC material degradation from damage induced by static, cyclic (fatigue). creep, and impact loading in 2D/3D PMC structures subjected to hygrothermal environments. Its use will significantly facilitate targeting design parameter changes that will be most effective in reducing the probability of a given failure mode occurring.

Abdi, Frank↗
NASA NTRS1988

Machine Tool Software

A NASA-developed software package has played a part in technical education of students who major in Mechanical Engineering Technology at William Rainey Harper College. Professor Hack has been using (APT) Automatically Programmed Tool Software since 1969 in his CAD/CAM Computer Aided Design and Manufacturing curriculum. Professor Hack teaches the use of APT programming languages for control of metal cutting machines. Machine tool instructions are geometry definitions written in APT Language to constitute a "part program." The part program is processed by the machine tool. CAD/CAM students go from writing a program to cutting steel in the course of a semester.

Source record↗
NASA NTRS1990

New direction in CAD tools

Chip and software development communities are concerned with the runaway pace of chip development and the monumental problems which can quickly accumulate and overwhelm those charged with the task of IC development. This 'weight' must be transferred from the shoulders of the human developers to the software tools which assimilate and control the defining data of the development process. This paper details many of the problems which are being resolved by reviewing the obstacles and resultant advancements which the industry has made. Specifically, it will describe many of the things which are being done in one company to provide this much-needed relief.

Peterson, S.↗
DOE OSTI2014

RELAP-7 Beta Release: Summary of Capabilities

RELAP-7 is a nuclear systems safety analysis code being developed at the Idaho National Laboratory (INL). Building upon the decades of software development at the INL, we began the development of RELAP-7 in 2011 to support the Risk Informed Safety Margins Characterization (RISMC) Pathway. As part of this development, the first lines of RELAP-7 code were committed to the software revision control repository on November 7th, 2011. The overall design goal of RELAP-7 is to take advantage of the previous thirty years of advancements in computer architecture, software design, numerical methods, and physical models in order to provide capabilities needed for the RISMC methodology and to support nuclear power safety analysis. RELAP-7 is built using the INL’s modern scientific software development framework, MOOSE (Multi-physics Object Oriented Simulation Environment). MOOSE provides improved numerical calculations (including higher-order integration in both space and time, yielding converged second-order accuracy). The RELAP-7 code structure is based on multiple physical component models such as pipes, junctions, pumps, etc. Each component can have options for different fluid models such as single- and two-phase flow. This component-based and physics-based software architecture allows RELAP-7 to adopt different physical models for different applications. A relatively new two-phase hydrodynamic model, termed the ''7-Equation model'' for two phasic pressures, velocities, energies, and volumetric fraction, is incorporated into RELAP-7 for liquid-gas (water-steam) flows. This new model allows second-order integration because it is well-posed, which will reduce the numerical error associated with traditional systems analysis codes. In this paper, we provide a RELAP-7 capability list describing analysis features, range of applicability, and reactor components that will be available for the December 15th, 2014 beta release of the software.

22 GENERAL STUDIES OF NUCLEAR REACTORS↗
DOE OSTI2015

D and D knowledge management information tool feasibility study for cross-platform mobile applications - 15704

The D and D Knowledge Management Information tool (D and D KM- IT) is a web-based knowledge management information tool built for the D and D user community. A feasibility study is being conducted on cross-platform application frameworks for their viability to the D and D KM-IT mobile needs. Currently, three main Operating Systems comprise the majority of the mobile market IOS, Android, and Windows, requiring a separate application for each device. Cross-development software allows the development of one application using one language, that can be ported or deployed on multiple devices with little effort. Using Xamarin, a native cross-platform framework, create a shared mobile application using Visual Studio. Build a D and D KMIT mobile application designed for the three major mobile platforms. Use Xamarin to compile the application into native applications for the three target platforms. Build and deploy the application on all three mobile platforms. Perform benchmark tests of the developed applications to analyze the performance on the three platforms. A large portion of the business logic of the application has been shared, eliminating development redundancy and minimizing planning, design, and validation time. The user interface development could not fully be shared cross-platform and some platform specific code must be individually implemented for each device. Maintenance, testing and design phases of the software engineering process were reduced from one for each device to having just one shared cycle processes. A less diverse skill-set for developers is required with cross-platform development. Some processes within the development cycle still require redundant activities.

22 GENERAL STUDIES OF NUCLEAR REACTORS↗
NASA NTRS2008

Cassini Attitude Control Flight Software: from Development to In-Flight Operation

The Cassini Attitude and Articulation Control Subsystem (AACS) Flight Software (FSW) has achieved its intended design goals by successfully guiding and controlling the Cassini-Huygens planetary mission to Saturn and its moons. This paper describes an overview of AACS FSW details from early design, development, implementation, and test to its fruition of operating and maintaining spacecraft control over an eleven year prime mission. Starting from phases of FSW development, topics expand to FSW development methodology, achievements utilizing in-flight autonomy, and summarize lessons learned during flight operations which can be useful to FSW in current and future spacecraft missions.

Architecture↗
NASA NTRS1992

Ground Systems Development Environment (GSDE) software configuration management

This report presents a review of the software configuration management (CM) plans developed for the Space Station Training Facility (SSTF) and the Space Station Control Center. The scope of the CM assessed in this report is the Systems Integration and Testing Phase of the Ground Systems development life cycle. This is the period following coding and unit test and preceding delivery to operational use. This report is one of a series from a study of the interfaces among the Ground Systems Development Environment (GSDE), the development systems for the SSTF and the SSCC, and the target systems for SSCC and SSTF. This is the last report in the series. The focus of this report is on the CM plans developed by the contractors for the Mission Systems Contract (MSC) and the Training Systems Contract (TSC). CM requirements are summarized and described in terms of operational software development. The software workflows proposed in the TSC and MSC plans are reviewed in this context, and evaluated against the CM requirements defined in earlier study reports. Recommendations are made to improve the effectiveness of CM while minimizing its impact on the developers.

Church, Victor E.↗
NASA NTRS1980

The software engineering laboratory: An approach to measuring software technology

The investigations of the software evaluation laboratory into the software development process at NASA/Goddard are described. A data collection process for acquiring detailed histories of software development projects is outlined. The application of different sets of software methodologies to specific applications projects is summarized. The effect of the development methodology on productivity is discussed.

Mcgarry, F.↗
DOE OSTI2016

In Situ Data Infrastructure for Scientific Unit Testing Platform

Testing is a significant software development process for the management of software systems and scientific code. However, as the complexity of scientific codes increases, extra checks are needed to monitor impacts to dependent models and to verify system constraints. The software complexity also impedes the efforts of module developers and software engineers to rapidly develop and extend their code. Recently, we have developed an automatic methodology and prototype platform to facilitate scientific verification of individual functions within complex scientific codes. With this system, the scientific module builders are able to track variables conveniently in one module or track variables’ changes among different modules. In this paper, we present a procedure for automatic unit testing generation. For the interest of a general audience of this conference, we are emphasizing the technical details of integrating the In Situ data infrastructure into our platform. At the end of this paper, we have included an implementation of unit testing for the ACME Land Model (ALM) to demonstrate the usefulness and correctness of the platform. We have also used single- and multipoint checks to demonstrate the efficient variable tracking capability of this platform.

97 MATHEMATICS AND COMPUTING↗
NASA NTRS1992

Description of research interests and current work related to automating software design

Enclosed is a list of selected and recent publications. Most of these publications concern applied research in the areas of software engineering and human-computer interaction. It is felt that domain-specific knowledge plays a major role in software development. Additionally, it is believed that improvements in the general software development process (e.g., object-oriented approaches) will have to be combined with the use of large domain-specific knowledge bases.

Kaindl, Hermann↗
NASA NTRS2002

A Quantitative Software Risk Assessment Model

This slide presentation reviews a risk assessment model as applied to software development. the presentation uses graphs to demonstrate basic concepts of software reliability. It also discusses the application to the risk model to the software development life cycle.

Lee, Alice↗
DOE OSTI2024

WETO Software Stack Best Practices

Wind energy researchers typically share one key characteristic: a passion for increasing wind energy in the global energy mix. The U.S. Department of Energy (DOE) supports this mission in a number of ways including allocating funding directly to various aspects of wind energy research through the Office of Energy Efficiency and Renewable Energy (EERE) via the Wind Energy Technologies Office (WETO). While the traditional output of research is academic publication, software development efforts are increasingly a major focus. Software tools in the research environment allow researchers to describe an idea and quickly increase the scope and scale as they study it further. As a product of research, these tools represent a direct pipeline from researcher to industry practitioners since they are the implementation of ideas described in academic publications. Given this vital role in wind energy research and commercial development, the broad research software portfolio supported by WETO must maintain a minimum level of quality to support the wind energy field in the growing transition to renewable energy. This report outlines a series o f best practices to be adopted by all WETO-supported software projects, as well as expectations that the communities interacting with these projects should have of the developers and tools themselves. Wind energy research software has a unique standing in the field of scientific software. The stakeholders are varied with a subset being: (1) DOE EERE leadership, (2) DOE WETO leadership and program managers, (3) National lab leadership, (4) Associated project principle investigators, (5) Research software engineers, (6) Wind energy researchers in academia (including graduate students, post docs, and national lab staff), (7) Industry researchers and practitioners, (8) Commercial software developers, and (9) The general public interested in wind energy. These software are typically the end-user of other generic software libraries, so the funding cycles are often tied to applied research rather than the development of the software itself. Since the developers are also wind energy researchers, these tools are typically designed in a way that closely resembles the application in which they're used. Additionally, the expertise and incentives for the developers have a high variability, and often neither are aligned with software engineering or computer science. Given the unique environment in which wind energy research software is produced and consumed, it is critical for model owners to understand the context of their software. A framework for developing this understanding is to answer the following questions of a given software project: What is it's purpose? What is its role in the field of wind energy? What is the profile of the expected users? For how long will it be relevant? What is the expected impact? These questions allow model owners to identify the appropriate methods for the design, development, and long term maintenance of their software. Additionally, the answer provide context for future planners to understand why particular decisions were made and discern the consequences of changing course. The information is aggregated from experience within WETO-supported software development groups as well as external organizations and efforts to define the craft of research software engineering. These best practices aim to make the collaborative development process efficient and effective while improving the model understanding across stakeholders. Additionally, the general adoption of a common framework for software quality ensures that the end users of WETO software can trust these tools and accurately understand the risks to workflow integration.

17 WIND ENERGY↗
NASA NTRS1995

Object-Oriented Software Metrics for Predicting Reusability and Estimating Size

As object-oriented software development methods come into more widespread use, basic questions of software quality assurance must be reconsidered. We will highlight efforts now underway at NASA's Jet Propulsion Laboratory to both assess the quality of software systems developed using object oriented technology and develop guidelines for future development of such systems. The current focus is on design and code reusability., and system size estimation. A number of metrics are proposed and two software systems measured and analyzed. The preliminary results reported here should be useful to software development and quality assurance personnel working in C++ implementation environment.

Sanderson, D. Peter↗
DOE OSTI2018

System Advisor Model (SAM) General Description (Version 2017.9.5)

This document describes the capabilities of the System Advisor Model (SAM) developed and distributed by the U.S. Department of Energy's National Renewable Energy Laboratory. The document is for potential users and others wanting to learn about the model's capabilities. SAM is a techno-economic computer model that calculates performance and financial metrics of renewable energy projects. Project developers, policy makers, equipment manufacturers, and researchers use graphs and tables of SAM results in the process of evaluating financial, technology, and incentive options for renewable energy projects. SAM simulates the performance of photovoltaic, concentrating solar power, solar water heating, wind, geothermal, biomass, and conventional power systems. The financial models are for projects that either buy and sell electricity at retail rates (residential and commercial) or sell electricity at a price determined in a power purchase agreement (PPA). SAM's simulation tools facilitate parametric and sensitivity analyses, Monte Carlo simulation and weather variability (P50/P90) studies. SAM can also read input variables from Microsoft Excel worksheets. For software developers, the SAM software development kit (SDK) makes it possible to use SAM simulation modules in their applications written in C/C plus plus, C sharp, Java, Python, MATLAB, and other languages. NREL provides both SAM and the SDK as free downloads at https://sam.nrel.gov. SAM is an open source project, so its source code is available to the public. Researchers can study the code to understand the model algorithms, and software programmers can contribute their own models and enhancements to the project. Technical support and more information about the software are available on the website.

47 OTHER INSTRUMENTATION↗
NASA NTRS1990

The cleanroom case study in the Software Engineering Laboratory: Project description and early analysis

This case study analyzes the application of the cleanroom software development methodology to the development of production software at the NASA/Goddard Space Flight Center. The cleanroom methodology emphasizes human discipline in program verification to produce reliable software products that are right the first time. Preliminary analysis of the cleanroom case study shows that the method can be applied successfully in the FDD environment and may increase staff productivity and product quality. Compared to typical Software Engineering Laboratory (SEL) activities, there is evidence of lower failure rates, a more complete and consistent set of inline code documentation, a different distribution of phase effort activity, and a different growth profile in terms of lines of code developed. The major goals of the study were to: (1) assess the process used in the SEL cleanroom model with respect to team structure, team activities, and effort distribution; (2) analyze the products of the SEL cleanroom model and determine the impact on measures of interest, including reliability, productivity, overall life-cycle cost, and software quality; and (3) analyze the residual products in the application of the SEL cleanroom model, such as fault distribution, error characteristics, system growth, and computer usage.

Green, Scott↗