Search NASA⌕ Search

SEARCH · Search NASA

Results for “engineering process”

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

Leveraging object-oriented development at Ames

This paper presents lessons learned by the Software Engineering Process Group (SEPG) from results of supporting two projects at NASA Ames using an Object Oriented Rapid Prototyping (OORP) approach supported by a full featured visual development environment. Supplemental lessons learned from a large project in progress and a requirements definition are also incorporated. The paper demonstrates how productivity gains can be made by leveraging the developer with a rich development environment, correct and early requirements definition using rapid prototyping, and earlier and better effort estimation and software sizing through object-oriented methods and metrics. Although the individual elements of OO methods, RP approach and OO metrics had been used on other separate projects, the reported projects were the first integrated usage supported by a rich development environment. Overall the approach used was twice as productive (measured by hours per OO Unit) as a C++ development.

Wenneson, Greg↗
NASA NTRS1995

Aerosol and cloud observations from the Lidar In-space Technology Experiment

The Lidar In-Space Technology Experiment (LITE) is a backscatter lidar built by NASA Langley Research Center to fly on the Space Shuttle. The purpose of the program was to develop the engineering processes required for space lidar and to demonstrate applications of space lidar to remote sensing of the atmosphere. The instrument was flown on Discovery in September 1994. Global observations of clouds and aerosols were made between the latitudes of 57 deg N and 57 deg S during 10 days of the mission.

Winker, D. M.↗
NASA NTRS1994

Aerosol and cloud sensing with the Lidar In-space Technology Experiment (LITE)

The Lidar In-space Technology Experiment (LITE) is a multi-wavelength backscatter lidar developed by NASA Langley Research Center to fly on the Space Shuttle. The LITE instrument is built around a three-wavelength ND:YAG laser and a 1-meter diameter telescope. The laser operates at 10 Hz and produces about 500 mJ per pulse at 1064 nm and 532 nm, and 150 mJ per pulse at 355 nm. The objective of the LITE program is to develop the engineering processes required for space lidar and to demonstrate applications of space-based lidar to remote sensing of the atmosphere. The LITE instrument was designed to study a wide range of cloud and aerosol phenomena. To this end, a comprehensive program of scientific investigations has been planned for the upcoming mission. Simulations of on-orbit performance show the instrument has sufficient sensitivity to detect even thin cirrus on a single-shot basis. Signal averaging provides the capability of measuring the height and structure of the planetary boundary layer, aerosols in the free troposphere, the stratospheric aerosol layer, and density profiles to an altitude of 40 km. The instrument has successfully completed a ground-test phase and is scheduled to fly on the Space Shuttle Discovery for a 9-day mission in September 1994.

Winker, D. M.↗
NASA NTRS1996

Experiences Using Formal Methods for Requirements Modeling

This paper describes three cases studies in the lightweight application of formal methods to requirements modeling for spacecraft fault protection systems. The case studies differ from previously reported applications of formal methods in that formal methods were applied very early in the requirements engineering process, to validate the evolving requirements. The results were fed back into the projects, to improve the informal specifications. For each case study, we describe what methods were applied, how they were applied, how much effort was involved, and what the findings were. In all three cases, the formal modeling provided a cost effective enhancement of the existing verification and validation processes. We conclude that the benefits gained from early modeling of unstable requirements more than outweigh the effort needed to maintain multiple representations.

Easterbrook, Steve↗
NASA NTRS1996

V&V Within Reuse-Based Software Engineering

Verification and Validation (V&V) is used to increase the level of assurance of critical software, particularly that of safety-critical and mission-critical software. V&V is a systems engineering discipline that evaluates the software in a systems context, and is currently applied during the development of a specific application system. In order to bring the effectiveness of V&V to bear within reuse-based software engineering, V&V must be incorporated within the domain engineering process.

Addy, Edward A.↗
NASA NTRS1996

Renaissance: A revolutionary approach for providing low-cost ground data systems

The NASA is changing its attention from large missions to a greater number of smaller missions with reduced development schedules and budgets. In relation to this, the Renaissance Mission Operations and Data Systems Directorate systems engineering process is presented. The aim of the Renaissance approach is to improve system performance, reduce cost and schedules and meet specific customer needs. The approach includes: the early involvement of the users to define the mission requirements and system architectures; the streamlining of management processes; the development of a flexible cost estimation capability, and the ability to insert technology. Renaissance-based systems demonstrate significant reuse of commercial off-the-shelf building blocks in an integrated system architecture.

Butler, Madeline J.↗
NASA NTRS1997

The 1997 JANNAF Propellant Development and Characterization Subcommittee and Safety and Environmental Protection Subcommittee Joint Meeting

In the Propellant Development and Characterization Subcommittee (PDCS) meeting, topics included: the analysis, characterization, and processing of propellants and propellant ingredients; chemical reactivity; liquid propellants; test methods; rheology; surveillance and aging; and process engineering. In the Safety and Environmental Protection Subcommittee (S&EPS) meeting, topics covered included: hydrazine propellant vapor detection methods; toxicity of propellants and propellants; explosives safety; atmospheric modeling and risk assessment of toxic releases; reclamation, disposal, and demilitarization methods; and remediation of explosives or propellant contaminated sites.

Cocchiaro, James E.↗
NASA NTRS1997

Experiences Using Lightweight Formal Methods for Requirements Modeling

This paper describes three case studies in the lightweight application of formal methods to requirements modeling for spacecraft fault protection systems. The case studies differ from previously reported applications of formal methods in that formal methods were applied very early in the requirements engineering process, to validate the evolving requirements. The results were fed back into the projects, to improve the informal specifications. For each case study, we describe what methods were applied, how they were applied, how much effort was involved, and what the findings were. In all three cases, formal methods enhanced the existing verification and validation processes, by testing key properties of the evolving requirements, and helping to identify weaknesses. We conclude that the benefits gained from early modeling of unstable requirements more than outweigh the effort needed to maintain multiple representations.

Easterbrook, Steve↗
NASA NTRS1997

Providing the Persistent Data Storage in a Software Engineering Environment Using Java/COBRA and a DBMS

An investigation was undertaken to build the software foundation for the WHERE (Web-based Hyper-text Environment for Requirements Engineering) project. The TCM (Toolkit for Conceptual Modeling) was chosen as the foundation software for the WHERE project which aims to provide an environment for facilitating collaboration among geographically distributed people involved in the Requirements Engineering process. The TCM is a collection of diagram and table editors and has been implemented in the C++ programming language. The C++ implementation of the TCM was translated into Java in order to allow the editors to be used for building various functionality of the WHERE project; the WHERE project intends to use the Web as its communication back- bone. One of the limitations of the translated software (TcmJava), which militated against its use in the WHERE project, was persistent data management mechanisms which it inherited from the original TCM; it was designed to be used in standalone applications. Before TcmJava editors could be used as a part of the multi-user, geographically distributed applications of the WHERE project, a persistent storage mechanism must be built which would allow data communication over the Internet, using the capabilities of the Web. An approach involving features of Java, CORBA (Common Object Request Broker), the Web, a middle-ware (Java Relational Binding (JRB)), and a database server was used to build the persistent data management infrastructure for the WHERE project. The developed infrastructure allows a TcmJava editor to be downloaded and run from a network host by using a JDK 1.1 (Java Developer's Kit) compatible Web-browser. The aforementioned editor establishes connection with a server by using the ORB (Object Request Broker) software and stores/retrieves data in/from the server. The server consists of a CORBA object or objects depending upon whether the data is to be made persistent on a single server or multiple servers. The CORBA object providing the persistent data server is implemented using the Java progranu-ning language. It uses the JRB to store/retrieve data in/from a relational database server. The persistent data management system provides transaction and user management facilities which allow multi-user, distributed access to the stored data in a secure manner.

Dhaliwal, Swarn S.↗
NASA NTRS1998

Intelligent Systems and Advanced User Interfaces for Design, Operation, and Maintenance of Command Management Systems

Historically Command Management Systems (CMS) have been large, expensive, spacecraft-specific software systems that were costly to build, operate, and maintain. Current and emerging hardware, software, and user interface technologies may offer an opportunity to facilitate the initial formulation and design of a spacecraft-specific CMS as well as a to develop a more generic or a set of core components for CMS systems. Current MOC (mission operations center) hardware and software include Unix workstations, the C/C++ and Java programming languages, and X and Java window interfaces representations. This configuration provides the power and flexibility to support sophisticated systems and intelligent user interfaces that exploit state-of-the-art technologies in human-machine systems engineering, decision making, artificial intelligence, and software engineering. One of the goals of this research is to explore the extent to which technologies developed in the research laboratory can be productively applied in a complex system such as spacecraft command management. Initial examination of some of the issues in CMS design and operation suggests that application of technologies such as intelligent planning, case-based reasoning, design and analysis tools from a human-machine systems engineering point of view (e.g., operator and designer models) and human-computer interaction tools, (e.g., graphics, visualization, and animation), may provide significant savings in the design, operation, and maintenance of a spacecraft-specific CMS as well as continuity for CMS design and development across spacecraft with varying needs. The savings in this case is in software reuse at all stages of the software engineering process.

Mitchell, Christine M.↗
NASA NTRS1999

Human Factors Engineering at Marshall Space Flight Center

The mission of NASA Marshall Space Flight Center (MSFC) is to develop, implement, and maintain systems for space transportation and microgravity research. Factors impacting the MSFC position as a leader in advancing science and technology include: (1) heightened emphasis on safety; (2) increased interest in effective resource utilization; and (3) growing importance of employing systems and procedures that pragmatically support mission science. In light of these factors, MSFC is integrating human factors engineering (HFE) into the systems engineering process. This paper describes the HFE program, applications of HFE in MSFC projects, and the future of HFE at MSFC.

Dunn, M. C.↗
NASA NTRS1999

Third Aerospace Environmental Technology Conference

The elimination of CFC's, Halons, TCA, other ozone depleting chemicals, and specific hazardous materials is well underway. The phaseout of these chemicals has mandated changes and new developments in aerospace materials and processes. We are beyond discovery and initiation of these new developments and are now in the implementation phase. This conference provided a forum for materials and processes engineers, scientists, and managers to describe, review, and critically assess the evolving replacement and clean propulsion technologies from the standpoint of their significance, application, impact on aerospace systems, and utilization by the research and development community. The use of these new technologies, their selection and qualification, their implementation, and the needs and plans for further developments are presented.

Whitaker, A. F.↗
NASA NTRS1999

JANNAF 28th Propellant Development and Characterization Subcommittee and 17th Safety and Environmental Protection Subcommittee Joint Meeting

This volume contains 37 unclassified/unlimited-distribution technical papers that were presented at the JANNAF 28th Propellant Development & Characterization Subcommittee (PDCS) and 17th Safety & Environmental Protection Subcommittee (S&EPS) Joint Meeting, held 26-30 April 1999 at the Town & Country Hotel and the Naval Submarine Base, San Diego, California. Volume II contains 29 unclassified/limited-distribution papers that were presented at the 28th PDCS and 17th S&EPS Joint Meeting. Volume III contains a classified paper that was presented at the 28th PDCS Meeting on 27 April 1999. Topics covered in PDCS sessions include: solid propellant rheology; solid propellant surveillance and aging; propellant process engineering; new solid propellant ingredients and formulation development; reduced toxicity liquid propellants; characterization of hypergolic propellants; and solid propellant chemical analysis methods. Topics covered in S&EPS sessions include: space launch range safety; liquid propellant hazards; vapor detection methods for toxic propellant vapors and other hazardous gases; toxicity of propellants, ingredients, and propellant combustion products; personal protective equipment for toxic liquid propellants; and demilitarization/treatment of energetic material wastes.

Cocchiaro, James E.↗
NASA NTRS1999

A Discussion of Zero Spring Rate Mechanisms Used for the Active Isolation Mount Experiment

In the summer of 1995 the Structural Dynamics Branch at NASA Langley Research Center set out to conceive a small, lightweight, low frequency isolation mount that could be used for spaceflight experiments. The Engineering Design Branch undertook the task of developing the isolation mount. This report describes the engineering process that led to three phases of a study entitled "Active Isolation Mounts" (AIM). A zero spring rate mechanism was used to achieve low fundamental frequencies for a payloads in the 1 to 10 pound range. It worked by balancing both a positive and a negative stiffness so that the net result was a small positive stiffness. The study demonstrated devices that could reduce the initial corner frequency by a factor of six for brief periods and a factor of two for extended periods. The designs were relatively simple and minimized weight, volume, and power. They could be scaled down and they were made of spaceflight compatible materials. All designs offered the ability to continuously vary the fundamental frequency. Yet, the goal of reducing the frequency by an order of magnitude was not achieved because the systems were too unstable at low frequencies. There was a trade between performance and stability.

Teter, John E., Jr.↗
NASA NTRS2000

Summary of Results from the Risk Management Program for the Mars Microrover Flight Experiment

On 4 July 1997, the Mars Pathfinder landed on the surface of Mars carrying the first planetary rover, known as the Sojourner. Formally known as the Microrover Flight Experiment (MFEX), the Sojourner was a low cost, high-risk technology demonstration, in which new risk management techniques were tried. This paper summarizes the activities and results of the effort to conduct a low-cost, yet meaningful risk management program for the MFEX. The specific activities focused on cost, performance, schedule, and operations risks. Just as the systems engineering process was iterative and produced successive refinements of requirements, designs, etc., so was the risk management process. Qualitative risk assessments were performed first to gain some insights for refining the microrover design and operations concept. These then evolved into more quantitative analyses. Risk management lessons from the manager's perspective is presented for other low-cost, high-risk space missions.

Shishko, Robert↗
NASA NTRS2000

2nd Generation RLV Risk Definition Program

The 2nd Generation RLV Risk Reduction Mid-Term Report summarizes the status of Kelly Space & Technology's activities during the first two and one half months of the program. This report was presented to the cognoscente Contracting Officer's Technical Representative (COTR) and selected Marshall Space Flight Center staff members on 26 September 2000. The report has been approved and is distributed on CD-ROM (as a PowerPoint file) in accordance with the terms of the subject contract, and contains information and data addressing the following: (1) Launch services demand and requirements; (2) Architecture, alternatives, and requirements; (3) Costs, pricing, and business cases analysis; (4) Commercial financing requirements, plans, and strategy; (5) System engineering processes and derived requirements; and (6) RLV system trade studies and design analysis.

Davis, Robert M.↗
NASA NTRS2001

Proceedings of the 4th Conference on Aerospace Materials, Processes, and Environmental Technology

The next millennium challenges us to produce innovative materials, processes, manufacturing, and environmental technologies that meet low-cost aerospace transportation needs while maintaining US leadership. The pursuit of advanced aerospace materials, manufacturing processes, and environmental technologies supports the development of safer, operational, next-generation, reusable, and expendable aeronautical and space vehicle systems. The Aerospace Materials, Processes, and Environmental Technology Conference (AMPET) provided a forum for manufacturing, environmental, materials, and processes engineers, scientists, and managers to describe, review, and critically assess advances in these key technology areas.

Griffin, D. E.↗