Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “process 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 NTRS1995

An approach to verification and validation of a reliable multicasting protocol: Extended Abstract

This paper describes the process of implementing a complex communications protocol that provides reliable delivery of data in multicast-capable, packet-switching telecommunication networks. The protocol, called the Reliable Multicasting Protocol (RMP), was developed incrementally using a combination of formal and informal techniques in an attempt to ensure the correctness of its implementation. Our development process involved three concurrent activities: (1) the initial construction and incremental enhancement of a formal state model of the protocol machine; (2) the initial coding and incremental enhancement of the implementation; and (3) model-based testing of iterative implementations of the protocol. These activities were carried out by two separate teams: a design team and a V&V team. The design team built the first version of RMP with limited functionality to handle only nominal requirements of data delivery. This initial version did not handle off-nominal cases such as network partitions or site failures. Meanwhile, the V&V team concurrently developed a formal model of the requirements using a variant of SCR-based state tables. Based on these requirements tables, the V&V team developed test cases to exercise the implementation. In a series of iterative steps, the design team added new functionality to the implementation while the V&V team kept the state model in fidelity with the implementation. This was done by generating test cases based on suspected errant or off-nominal behaviors predicted by the current model. If the execution of a test in the model and implementation agreed, then the test either found a potential problem or verified a required behavior. However, if the execution of a test was different in the model and implementation, then the differences helped identify inconsistencies between the model and implementation. In either case, the dialogue between both teams drove the co-evolution of the model and implementation. We have found that this interactive, iterative approach to development allows software designers to focus on delivery of nominal functionality while the V&V team can focus on analysis of off nominal cases. Testing serves as the vehicle for keeping the model and implementation in fidelity with each other. This paper describes (1) our experiences in developing our process model; and (2) three example problems found during the development of RMP. Although RMP has provided our research effort with a rich set of test cases, it also has practical applications within NASA. For example, RMP is being considered for use in the NASA EOSDIS project due to its significant performance benefits in applications that need to replicate large amounts of data to many network sites.

Callahan, John R.↗
NASA NTRS1994

An Approach to Verification and Validation of a Reliable Multicasting Protocol

This paper describes the process of implementing a complex communications protocol that provides reliable delivery of data in multicast-capable, packet-switching telecommunication networks. The protocol, called the Reliable Multicasting Protocol (RMP), was developed incrementally using a combination of formal and informal techniques in an attempt to ensure the correctness of its implementation. Our development process involved three concurrent activities: (1) the initial construction and incremental enhancement of a formal state model of the protocol machine; (2) the initial coding and incremental enhancement of the implementation; and (3) model-based testing of iterative implementations of the protocol. These activities were carried out by two separate teams: a design team and a V&V team. The design team built the first version of RMP with limited functionality to handle only nominal requirements of data delivery. In a series of iterative steps, the design team added new functionality to the implementation while the V&V team kept the state model in fidelity with the implementation. This was done by generating test cases based on suspected errant or offnominal behaviors predicted by the current model. If the execution of a test was different between the model and implementation, then the differences helped identify inconsistencies between the model and implementation. The dialogue between both teams drove the co-evolution of the model and implementation. Testing served as the vehicle for keeping the model and implementation in fidelity with each other. This paper describes (1) our experiences in developing our process model; and (2) three example problems found during the development of RMP.

Callahan, John R.↗
NASA NTRS1995

An approach to verification and validation of a reliable multicasting protocol

This paper describes the process of implementing a complex communications protocol that provides reliable delivery of data in multicast-capable, packet-switching telecommunication networks. The protocol, called the Reliable Multicasting Protocol (RMP), was developed incrementally using a combination of formal and informal techniques in an attempt to ensure the correctness of its implementation. Our development process involved three concurrent activities: (1) the initial construction and incremental enhancement of a formal state model of the protocol machine; (2) the initial coding and incremental enhancement of the implementation; and (3) model-based testing of iterative implementations of the protocol. These activities were carried out by two separate teams: a design team and a V&V team. The design team built the first version of RMP with limited functionality to handle only nominal requirements of data delivery. In a series of iterative steps, the design team added new functionality to the implementation while the V&V team kept the state model in fidelity with the implementation. This was done by generating test cases based on suspected errant or off-nominal behaviors predicted by the current model. If the execution of a test was different between the model and implementation, then the differences helped identify inconsistencies between the model and implementation. The dialogue between both teams drove the co-evolution of the model and implementation. Testing served as the vehicle for keeping the model and implementation in fidelity with each other. This paper describes (1) our experiences in developing our process model; and (2) three example problems found during the development of RMP.

Callahan, John R.↗
NASA NTRS1988

A communication channel model of the software process

Beginning research into a noisy communication channel analogy of software development process productivity, in order to establish quantifiable behavior and theoretical bounds is discussed. The analogy leads to a fundamental mathematical relationship between human productivity and the amount of information supplied by the developers, the capacity of the human channel for processing and transmitting information, the software product yield (object size) the work effort, requirements efficiency, tool and process efficiency, and programming environment advantage. An upper bound to productivity is derived that shows that software reuse is the only means that can lead to unbounded productivity growth; practical considerations of size and cost of reusable components may reduce this to a finite bound.

Tausworthe, Robert C.↗
DOE OSTI2025

Light, High Performance and Scalable Coal-Derived Composites for Construction: Precast and Cast-in-Place Applications

The overall objective of this project was to produce a coal-based construction material that has up to ~95 weight percent (wt. %) coal with physical, chemical, and thermal properties exceeding those of ordinary Portland cement (OPC)-based construction materials. Additionally, the project aimed to minimize external binders by implementing novel mixing techniques, while exceeding the performance/cost ratio of OPC. Finally, the project was to demonstrate production of precast products via the design and fabrication of products via a bench scale process. Consistent with some of these objectives, the project successfully fabricated samples of coal-based composite materials with >80 wt% coal with physical, chemical and thermal properties on par with cement-based concrete. Select samples demonstrated compressive strengths with >7,000 psi and flexural strength of >420 psi. The composite materials minimized external binders and also demonstrated durability, as evidenced by resistance to acidic and basic solutions. Finally, larger slab and beam type samples were produced using a process developed by the Recipient, although, the process was not semicontinuous in nature. Taken together, the results of this project suggest that domestic coal has potential to serve as a replacement for cementitious materials utilized in incumbent construction technologies, which could significantly reduce the energy and emissions of the construction industry

01 COAL, LIGNITE, AND PEAT↗
NASA NTRS1979

Development of pulsed processes for the manufacture of solar cells

Low-energy ion implantation processes for the automated production of silicon solar cells were investigated. Phosphorus ions at an energy of 10 keV and dose of 2 x 10 to the 15th power/sq cm were implanted in silicon solar cells to produce junctions, while boron ions at 25 keV and 5 x 10 to the 15th power were implanted in the cells to produce effective back surface fields. An ion implantation facility with a beam current up to 4 mA and a production throughput of 300 wafers per hour was designed and installed. A design was prepared for a 100 mA, automated implanter with a production capacity of 100 MW sub e/sq cm per year. Two process sequences were developed which employ ion implantation and furnace or pulse annealing. A computer program was used to determine costs for junction formation by ion implantation and various furnace annealing cycles to demonstrate cost effectiveness of these methods.

Minnucci, J. A.↗
NASA NTRS1991

Fabrication Of Lightweight Mirrors Via CVD

New chemical-vapor deposition (CVD) process developed for fabricating lightweight Si/SiC mirrors. Process involves three CVD steps: to produce faceplate of mirror; to form lightweight back structure deposited integrally with faceplate; and to deposit layer of optical-grade material onto front surface of faceplate. Figure and finish of mirror fabricated into this latter material. Produces dense, highly pure polycrystalline materials polished to surface figures of high precision and finish.

Goela, Jitendra S.↗
NASA NTRS1999

High Reynolds Number Predictions for the Baseline Arrow Wing at Mach 2.48

The NASA High Speed Research (HSR) Program is intended to establish a technology base enabling industry development of an economically viable and environmentally acceptable second generation high speed civil transport (HSCT). The objective of the Configuration Aerodynamics task of the program is the development of aerodynamic drag reduction, stability and control, and propulsion airframe integration technologies required to support the HSCT development process. Aerodynamic design tools are being developed, evaluated, and validated through ground based experimental testing. In addition, methods for ground to flight scaling are being developed and refined.

Rivers, Melissa↗
NASA NTRS2005

Human Centered Computing for Mars Exploration

The science objectives are to determine the aqueous, climatic, and geologic history of a site on Mars where conditions may have been favorable to the preservation of evidence of prebiotic or biotic processes. Human Centered Computing is a development process that starts with users and their needs, rather than with technology. The goal is a system design that serves the user, where the technology fits the task and the complexity is that of the task not of the tool.

Trimble, Jay↗
NASA NTRS2012

Test Driven Development of Scientific Models

Test-Driven Development (TDD) is a software development process that promises many advantages for developer productivity and has become widely accepted among professional software engineers. As the name suggests, TDD practitioners alternate between writing short automated tests and producing code that passes those tests. Although this overly simplified description will undoubtedly sound prohibitively burdensome to many uninitiated developers, the advent of powerful unit-testing frameworks greatly reduces the effort required to produce and routinely execute suites of tests. By testimony, many developers find TDD to be addicting after only a few days of exposure, and find it unthinkable to return to previous practices. Of course, scientific/technical software differs from other software categories in a number of important respects, but I nonetheless believe that TDD is quite applicable to the development of such software and has the potential to significantly improve programmer productivity and code quality within the scientific community. After a detailed introduction to TDD, I will present the experience within the Software Systems Support Office (SSSO) in applying the technique to various scientific applications. This discussion will emphasize the various direct and indirect benefits as well as some of the difficulties and limitations of the methodology. I will conclude with a brief description of pFUnit, a unit testing framework I co-developed to support test-driven development of parallel Fortran applications.

Clune, Thomas L.↗
NASA NTRS2014

Assessment of MSFCs Process for the Development and Activation of Space Act Agreement

Space Act Agreements (SAAs) are contractual agreements that NASA utilizes to form partnerships with researchers, industry, and academia to stimulate cutting-edge innovation within the science and technology communities. center dot This study assessed the current SAA development and activation process at Marshall Space Flight Center (MSFC) to determine if improvements could be implemented to increase productivity, decrease time to activation, and improve the quality of deliverables.

Daugherty, Rachel↗
NASA NTRS1985

Measuring the software process and product: Lessons learned in the SEL

The software development process and product can and should be measured. The software measurement process at the Software Engineering Laboratory (SEL) has taught a major lesson: develop a goal-driven paradigm (also characterized as a goal/question/metric paradigm) for data collection. Project analysis under this paradigm leads to a design for evaluating and improving the methodology of software development and maintenance.

Basili, V. R.↗
NASA NTRS1979

LaRC-160 fabrication development

The scope and status of the fabrication development program on the third candidate graphite/polyimide material, utilizing the LARC-160 polyimide system is reported. The results of initial chemical characterization studies on resin monomer constituents and intermediate esters are discussed, in particular, the problem of identifying the nadic ester endcapper material and establishing specifications to ensure material reproducibility. Progress on the process development task, including prestaging, cure, and postcure studies on flat laminates is reported. In addition, the design and processing of hat and "I" section stiffeners is reviewed. Initial efforts on the development of standards for nondestructive C-scan inspection for the various types of structures are discussed. The approach to qualifying the developed processes is outlined along with other ancillary studies in progress.

Leahy, J. D.↗
NASA NTRS1992

A process for prototyping onboard payload displays for Space Station Freedom

Significant advances have been made in the area of Human-Computer Interface design. However, there is no well-defined process for going from user interface requirements to user interface design. Developing and designing a clear and consistent user interface for medium to large scale systems is a very challenging and complex task. The task becomes increasingly difficult when there is very little guidance and procedures on how the development process should flow from one stage to the next. Without a specific sequence of development steps each design becomes difficult to repeat, to evaluate, to improve, and to articulate to others. This research contributes a process which identifies the phases of development and products produced as a result of each phase for a rapid prototyping process to be used to develop requirements for the onboard payload displays for Space Station Freedom. The functional components of a dynamic prototyping environment in which this process can be carried out is also discussed. Some of the central questions which are answered here include: How does one go from specifications to an actual prototype? How is a prototype evaluated? How is usability defined and thus measured? How do we use the information from evaluation in redesign of an interface? and Are there techniques which allow for convergence on a design?

Moore, Loretta A.↗
NASA NTRS2011

The MSFC Collaborative Engineering Process for Preliminary Design and Concept Definition Studies

This paper describes a collaborative engineering process developed by the Marshall Space Flight Center's Advanced Concepts Office for performing rapid preliminary design and mission concept definition studies for potential future NASA missions. The process has been developed and demonstrated for a broad range of mission studies including human space exploration missions, space transportation system studies and in-space science missions. The paper will describe the design team structure and specialized analytical tools that have been developed to enable a unique rapid design process. The collaborative engineering process consists of integrated analysis approach for mission definition, vehicle definition and system engineering. The relevance of the collaborative process elements to the standard NASA NPR 7120.1 system engineering process will be demonstrated. The study definition process flow for each study discipline will be will be outlined beginning with the study planning process, followed by definition of ground rules and assumptions, definition of study trades, mission analysis and subsystem analyses leading to a standardized set of mission concept study products. The flexibility of the collaborative engineering design process to accommodate a wide range of study objectives from technology definition and requirements definition to preliminary design studies will be addressed. The paper will also describe the applicability of the collaborative engineering process to include an integrated systems analysis approach for evaluating the functional requirements of evolving system technologies and capabilities needed to meet the needs of future NASA programs.

Mulqueen, Jack↗
NASA NTRS2010

Human Engineering of Space Vehicle Displays and Controls

Proper attention to the integration of the human needs in the vehicle displays and controls design process creates a safe and productive environment for crew. Although this integration is critical for all phases of flight, for crew interfaces that are used during dynamic phases (e.g., ascent and entry), the integration is particularly important because of demanding environmental conditions. This panel addresses the process of how human engineering involvement ensures that human-system integration occurs early in the design and development process and continues throughout the lifecycle of a vehicle. This process includes the development of requirements and quantitative metrics to measure design success, research on fundamental design questions, human-in-the-loop evaluations, and iterative design. Processes and results from research on displays and controls; the creation and validation of usability, workload, and consistency metrics; and the design and evaluation of crew interfaces for NASA's Crew Exploration Vehicle are used as case studies.

Whitmore, Mihriban↗