SEARCH · Engineering Papers

Results for “interview”

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.

SourceResearch connectionFrom yearThrough year

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 721 records · Page 40

All sources NASA NTRS DOE OSTI

NASA NTRS1983

A methodology for collecting valid software engineering data

An effective data collection method for evaluating software development methodologies and for studying the software development process is described. The method uses goal-directed data collection to evaluate methodologies with respect to the claims made for them. Such claims are used as a basis for defining the goals of the data collection, establishing a list of questions of interest to be answered by data analysis, defining a set of data categorization schemes, and designing a data collection form. The data to be collected are based on the changes made to the software during development, and are obtained when the changes are made. To insure accuracy of the data, validation is performed concurrently with software development and data collection. Validation is based on interviews with those people supplying the data. Results from using the methodology show that data validation is a necessary part of change data collection. Without it, as much as 50% of the data may be erroneous. Feasibility of the data collection methodology was demonstrated by applying it to five different projects in two different environments. The application showed that the methodology was both feasible and useful.

Basili, Victor R.↗

NASA NTRS1986

Apollo - A pioneering generation

This paper describes an ongoing study of the National Aeronautics and Space Administration's (NASA's) first generation of engineers - the generation which accomplished the United States' first major achievements in manned space exploration. Combining statistical analysis with personal interviews, the study explores questions such as the origins, motivations, and career histories of NASA's first generation of engineers; that generation's role in NASA's current leadership; the relationships of science, engineering, and management in NASA's institutional culture; and changes experienced within NASA during and after the Apollo program.

Fries, S. D.↗

NASA NTRS1988

Technology Developed In Two Space Projects

Two projects examined for their influences on commercial products and future space missions. Three-volume report presents study of technological benefits of two spaceflight projects, Galileo, and Hubble space telescope. Study focused on equipment and computer programs developed between initial approval of projects and integration and testing of the systems. Volume 1 presents overview of study, discusses methods of collection and evaluation of data, and offers conclusion and recommendations. Volume 2 describes interview process and summarizes raw data. Volume 3 contains technology-assessment sheets for developments.

Joseph, Carlton H.↗

NASA NTRS1987

Application of expert systems in project management decision aiding

The feasibility of developing an expert systems-based project management decision aid to enhance the performance of NASA project managers was assessed. The research effort included extensive literature reviews in the areas of project management, project management decision aiding, expert systems technology, and human-computer interface engineering. Literature reviews were augmented by focused interviews with NASA managers. Time estimation for project scheduling was identified as the target activity for decision augmentation, and a design was developed for an Integrated NASA System for Intelligent Time Estimation (INSITE). The proposed INSITE design was judged feasible with a low level of risk. A partial proof-of-concept experiment was performed and was successful. Specific conclusions drawn from the research and analyses are included. The INSITE concept is potentially applicable in any management sphere, commercial or government, where time estimation is required for project scheduling. As project scheduling is a nearly universal management activity, the range of possibilities is considerable. The INSITE concept also holds potential for enhancing other management tasks, especially in areas such as cost estimation, where estimation-by-analogy is already a proven method.

Harris, Regina↗

NASA NTRS1988

The need for a comprehensive expert system development methodology

In a traditional software development environment, the introduction of standardized approaches has led to higher quality, maintainable products on the technical side and greater visibility into the status of the effort on the management side. This study examined expert system development to determine whether it differed enough from traditional systems to warrant a reevaluation of current software development methodologies. Its purpose was to identify areas of similarity with traditional software development and areas requiring tailoring to the unique needs of expert systems. A second purpose was to determine whether existing expert system development methodologies meet the needs of expert system development, management, and maintenance personnel. The study consisted of a literature search and personal interviews. It was determined that existing methodologies and approaches to developing expert systems are not comprehensive nor are they easily applied, especially to cradle to grave system development. As a result, requirements were derived for an expert system development methodology and an initial annotated outline derived for such a methodology.

Baumert, John↗

NASA NTRS1987

Intelligent interfaces to aircraft systems

An approach for developing intelligent aiding systems for airline flight crews is proposed. This approach proceeds in four cycles: (1) National Traffic Safety Board data and pilot interviews are used to determine the areas in which pilots require aid; (2) a pilot information processing model is designed; (3) an intelligent pilot-aiding model is developed; and (4) systems for implementing aiding functions are defined. This approach is utilized to design a general situation-response pilot-aiding system. The situation-response model and the structure of a general situation-response pilot-aiding system are described. The computer implementation of the situation-response information processing model is examined.

Schudy, Robert↗

NASA NTRS1988

Using full-mission simulation for human factors research in air transport operations

This study examined state-of-the-art mission oriented simulation and its use in human factors research. Guidelines were developed for doing full-mission human factors research on crew member behavior during simulated air transport operations. The existing literature was reviewed. However, interviews with experienced investigators provided the most useful information. The fundamental scientific and practical issues of behavioral research in a simulation environment are discussed. Guidelines are presented for planning, scenario development, and the execution of behavioral research using full-mission simulation in the context of air transport flight operations . Research is recommended to enhance the validity and productivity of full-mission research by: (1) validating the need for high-fidelity simulation of all major elements in the operational environment, (2) improving methods for conducting full-mission research, and (3) examining part-task research on specific problems through the use of vehicles which contain higher levels of abstraction (and lower fidelity) of the operational environment.

Orlady, Harry W.↗

NASA NTRS1988

MODIS Information, Data, and Control System (MIDACS) system specifications and conceptual design

The MODIS Information, Data, and Control System (MIDACS) Specifications and Conceptual Design Document discusses system level requirements, the overall operating environment in which requirements must be met, and a breakdown of MIDACS into component subsystems, which include the Instrument Support Terminal, the Instrument Control Center, the Team Member Computing Facility, the Central Data Handling Facility, and the Data Archive and Distribution System. The specifications include sizing estimates for the processing and storage capacities of each data system element, as well as traffic analyses of data flows between the elements internally, and also externally across the data system interfaces. The specifications for the data system, as well as for the individual planning and scheduling, control and monitoring, data acquisition and processing, calibration and validation, and data archive and distribution components, do not yet fully specify the data system in the complete manner needed to achieve the scientific objectives of the MODIS instruments and science teams. The teams have not yet been formed; however, it was possible to develop the specifications and conceptual design based on the present concept of EosDIS, the Level-1 and Level-2 Functional Requirements Documents, the Operations Concept, and through interviews and meetings with key members of the scientific community.

Han, D.↗

NASA NTRS1988

An investigation of transitional management problems for the NSTS at NASA, executive summary

A summary is given of the work of the University of Houston research team for the third quarter of effort in a yearly grant for the National Space Transportation System (NSTS). As such it serves as a resting place for the ideas and concepts developed this quarter with the collaboration of the Management Integration Offices of NASA. Another objective is the hope that the report will help to stimulate the healthy problem solving process already present at NASA. The main goal of the contractual work is to help NASA to find ways and means of moving into a truly operational era with the shuttle program. This work is a continuation of early work and the reader is encouraged to read the final reports of earlier years. Chapter One of the report is an introduction. Chapter Two deals with industrial adaptation and is in two parts: theory and application. In the theory section, impressions of the management system immediately after reflight are discussed. A key issue, in the author's opinion is the seeming lack of purpose of the program. The application section has six appendices: 1988 Demographic Survey, Field Notes of Interview with HL/P South Texas Nuclear Project, a comparison of the Agendas of the current manager with that of a previous manager, a note on compartmentalization to assist in manifesting, a study on launch prediction for STS-26, and a discussion of a statistical decision-making course for upper level managers. Chapter Three deals with theoretical results returned on flow shop scheduling which will be of use downstream. Chapter Four deals with a statistical model developed to predict the flight rate in future years and indicates the program will have trouble making its schedule. Chapter Five covers the constructural effort and shows the work to be on schedule.

Hunsucker, John↗

NASA NTRS1988

MODIS information, data and control system (MIDACS) level 2 functional requirements

The MODIS Information, Data and Control System (MIDACS) Level 2 Functional Requirements Document establishes the functional requirements for MIDACS and provides a basis for the mutual understanding between the users and the designers of the EosDIS, including the requirements, operating environment, external interfaces, and development plan. In defining the requirements and scope of the system, this document describes how MIDACS will operate as an element of the EOS within the EosDIS environment. This version of the Level 2 Requirements Document follows an earlier release of a preliminary draft version. The sections on functional and performance requirements do not yet fully represent the requirements of the data system needed to achieve the scientific objectives of the MODIS instruments and science teams. Indeed, the team members have not yet been selected and the team has not yet been formed; however, it has been possible to identify many relevant requirements based on the present concept of EosDIS and through interviews and meetings with key members of the scientific community. These requirements have been grouped by functional component of the data system, and by function within each component. These requirements have been merged with the complete set of Level 1 and Level 2 context diagrams, data flow diagrams, and data dictionary.

Han, D.↗

NASA NTRS1988

MODIS information, data and control system (MIDACS) operations concepts

The MODIS Information, Data, and Control System (MIDACS) Operations Concepts Document provides a basis for the mutual understanding between the users and the designers of the MIDACS, including the requirements, operating environment, external interfaces, and development plan. In defining the concepts and scope of the system, how the MIDACS will operate as an element of the Earth Observing System (EOS) within the EosDIS environment is described. This version follows an earlier release of a preliminary draft version. The individual operations concepts for planning and scheduling, control and monitoring, data acquisition and processing, calibration and validation, data archive and distribution, and user access do not yet fully represent the requirements of the data system needed to achieve the scientific objectives of the MODIS instruments and science teams. The teams are not yet formed; however, it is possible to develop the operations concepts based on the present concept of EosDIS, the level 1 and level 2 Functional Requirements Documents, and through interviews and meetings with key members of the scientific community. The operations concepts were exercised through the application of representative scenarios.

Han, D.↗

NASA NTRS1988

Psychological tools for knowledge acquisition

Knowledge acquisition is said to be the biggest bottleneck in the development of expert systems. The problem is getting the knowledge out of the expert's head and into a computer. In cognitive psychology, characterizing metal structures and why experts are good at what they do is an important research area. Is there some way that the tools that psychologists have developed to uncover mental structure can be used to benefit knowledge engineers? We think that the way to find out is to browse through the psychologist's toolbox to see what there is in it that might be of use to knowledge engineers. Expert system developers have relied on two standard methods for extracting knowledge from the expert: (1) the knowledge engineer engages in an intense bout of interviews with the expert or experts, or (2) the knowledge engineer becomes an expert himself, relying on introspection to uncover the basis of his own expertise. Unfortunately, these techniques have the difficulty that often the expert himself isn't consciously aware of the basis of his expertise. If the expert himself isn't conscious of how he solves problems, introspection is useless. Cognitive psychology has faced similar problems for many years and has developed exploratory methods that can be used to discover cognitive structure from simple data.

Rueter, Henry H.↗

NASA NTRS1989

A two-phase methodology for technology selection and system design

A two-phase methodology that can be used to guide R&D managers in the evaluation and selection of competing technologies is presented. Deterministic multiattribute utility theory is used in the first phase to rank the technological alternatives; the example presented involves the evaluation of electric and hybrid passenger vehicles. In all, 39 individuals from eight automotive firms were interviewed to assess their risk preferences and attitudes toward the vehicle design. In the second phase, the decision-maker must allocate a fixed amount of resources to different projects for the technology selected, some of which may be undertaken in parallel, to maximize a given measure of performance. When parallel funding is pursued the best outcome is chosen. The problem is formulated as a probabilistic network and solved heuristically using Monte Carlo simulation. Results are presented for two decision-makers and three budget options. In each case, the heuristic finds the optimal allocation of funds.

Bard, Jonathan F.↗

NASA NTRS1989

The DAB model of drawing processes

The problem of automatic drawing was investigated in two ways. First, a DAB model of drawing processes was introduced. DAB stands for three types of knowledge hypothesized to support drawing abilities, namely, Drawing Knowledge, Assimilated Knowledge, and Base Knowledge. Speculation concerning the content and character of each of these subsystems of the drawing process is introduced and the overall adequacy of the model is evaluated. Second, eight experts were each asked to understand six engineering drawings and to think aloud while doing so. It is anticipated that a concurrent protocol analysis of these interviews can be carried out in the future. Meanwhile, a general description of the videotape database is provided. In conclusion, the DAB model was praised as a worthwhile first step toward solution of a difficult problem, but was considered by and large inadequate to the challenge of automatic drawing. Suggestions for improvements on the model were made.

Hochhaus, Larry W.↗

NASA NTRS1990

The Advanced Communications Technology Satellite (ACTS) capabilities for serving science

Results of research on potential science applications of the NASA Advanced Communications Technology Satellite (ACTS) are presented. Discussed here are: (1) general research on communications related issues; (2) a survey of science-related activities and programs in the local area; (3) interviews of selected scientists and associated telecommunications support personnel whose projects have communications requirements; (4) analysis of linkages between ACTS functionality and science user communications activities and modes of operation; and (5) an analysis of survey results and the projection of conclusions to a national scale.

Meyer, Thomas R.↗

NASA NTRS1990

Evaluation of a proposed expert system development methodology: Two case studies

Two expert system development projects were studied to evaluate a proposed Expert Systems Development Methodology (ESDM). The ESDM was developed to provide guidance to managers and technical personnel and serve as a standard in the development of expert systems. It was agreed that the proposed ESDM must be evaluated before it could be adopted; therefore a study was planned for its evaluation. This detailed study is now underway. Before the study began, however, two ongoing projects were selected for a retrospective evaluation. They were the Ranging Equipment Diagnostic Expert System (REDEX) and the Backup Control Mode Analysis and Utility System (BCAUS). Both projects were approximately 1 year into development. Interviews of project personnel were conducted, and the resulting data was used to prepare the retrospective evaluation. Decision models of the two projects were constructed and used to evaluate the completeness and accuracy of key provisions of ESDM. A major conclusion reached from these case studies is that suitability and risk analysis should be required for all AI projects, large and small. Further, the objectives of each stage of development during a project should be selected to reduce the next largest area of risk or uncertainty on the project.

Gilstrap, Lewey↗

NASA NTRS1990

Documentation and knowledge acquisition

Traditional approaches to knowledge acquisition have focused on interviews. An alternative focuses on the documentation associated with a domain. Adopting a documentation approach provides some advantages during familiarization. A knowledge management tool was constructed to gain these advantages.

Rochowiak, Daniel↗

NASA NTRS1989

Designers as users - Design supports based on crew system design practices

The behavioral processes in aviation crew system design are theoretically discussed. Interviews with designers concerning actual design experiences were conducted in a structured manner, focusing on the nature of the design problem, the designers's tasks, how decisions governing the human operator's role are made, and how this decision making can be supported. Two taxonomies emerge, one of which summarizes the nature of the design problem and the second of which summarizes the tasks that designers perform toward solving the problem. Combining the taxonomies yields a design problem space that is used to classify existing forms of support. The results of this classification and the implications for needed supports are discussed.

Cody, William J.↗