Search NASA⌕ Search

SEARCH · Search NASA

Results for “Configuration Management”

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 199 records · Page 11
All sourcesNASA NTRSDOE OSTI
NASA NTRS1993

Automation and hypermedia technology applications

This paper represents a progress report on HyLite (Hypermedia Library technology): a research and development activity to produce a versatile system as part of NASA's technology thrusts in automation, information sciences, and communications. HyLite can be used as a system or tool to facilitate the creation and maintenance of large distributed electronic libraries. The contents of such a library may be software components, hardware parts or designs, scientific data sets or databases, configuration management information, etc. Proliferation of computer use has made the diversity and quantity of information too large for any single user to sort, process, and utilize effectively. In response to this information deluge, we have created HyLite to enable the user to process relevant information into a more efficient organization for presentation, retrieval, and readability. To accomplish this end, we have incorporated various AI techniques into the HyLite hypermedia engine to facilitate parameters and properties of the system. The proposed techniques include intelligent searching tools for the libraries, intelligent retrievals, and navigational assistance based on user histories. HyLite itself is based on an earlier project, the Encyclopedia of Software Components (ESC) which used hypermedia to facilitate and encourage software reuse.

Jupin, Joseph H.↗
NASA NTRS1990

TMIS-design knowledge capture

The Boeing Advanced Technology Center is conducting research towards the goal of building a corporate memory facility that will provide techniques for capturing and using decision history and rationale throughout the lifecycle of a major NASA program. Currently, much of the information regarding decision alternatives and trade-offs made in the course of a major program development effort is not represented or retained in a way that permits computer-based reasoning over the lifecycle of the program. The loss of this information results in problems in tracing design alternatives to requirements, in assessing the impact of change in requirements, and in configuration management. To address these problems, we are studying the problem of building an intelligent active corporate memory facility which would provide for the capture of the requirements and standards of a program, analyze the design alternatives and trade-offs made over the program's lifetime, and examine relationships between requirements and design trade-offs.

Boose, John H.↗
NASA NTRS1993

Software Engineering Guidebook

The Software Engineering Guidebook describes SEPG (Software Engineering Process Group) supported processes and techniques for engineering quality software in NASA environments. Three process models are supported: structured, object-oriented, and evolutionary rapid-prototyping. The guidebook covers software life-cycles, engineering, assurance, and configuration management. The guidebook is written for managers and engineers who manage, develop, enhance, and/or maintain software under the Computer Software Services Contract.

Connell, John↗
NASA NTRS1993

The Mars mapper science and mission planning tool

The Mars Mapper Program (MOm) is an interactive tool for science and mission design developed for the Mars Observer Mission (MO). MOm is a function of the Planning and Sequencing Element of the MO Ground Data System. The primary users of MOm are members of the science and mission planning teams. Using MOm, the user can display digital maps of Mars in various projections and resolutions ranging from 1 to 256 pixels per degree squared. The user can overlay the maps with ground tracks of the MO spacecraft (S/C) and footprints and swaths of the various instruments on-board the S/C. Orbital and instrument geometric parameters can be computed on demand and displayed on the digital map or plotted in XY-plots. The parameter data can also be saved into files for other uses. MOm is divided into 3 major processes: Generator, Mapper, Plotter. The Generator Process is the main control which spawns all other processes. The processes communicate via sockets. At any one time, only 1 copy of MOm may operate on the system. However, up to 5 copies of each of the major processes may be invoked from the Generator. MOm is developed on the Sun SPARCStation 2GX with menu driven graphical user interface (GUI). The map window and its overlays are mouse-sensitized to permit on-demand calculations of various parameters along an orbit. The program is currently under testing and will be delivered to the MO Mission System Configuration Management for distribution to the MO community in 3/93.

Lo, Martin W.↗
NASA NTRS1995

Microgravity Experiments Safety and Integration Requirements Document Tree

This report is a document tree of the safety and integration documents required to develop a space experiment. Pertinent document information for each of the top level (tier one) safety and integration documents, and their applicable and reference (tier two) documents has been identified. This information includes: document title, revision level, configuration management, electronic availability, listed applicable and reference documents, source for obtaining the document, and document owner. One of the main conclusions of this report is that no single document tree exists for all safety and integration documents, regardless of the Shuttle carrier. This document also identifies the need for a single point of contact for customers wishing to access documents. The data in this report serves as a valuable information source for the NASA Lewis Research Center Project Documentation Center, as well as for all developers of space experiments.

Hogan, Jean M.↗
NASA NTRS1995

Earth Observing System (EOS)/Advanced Microwave Sounding Unit-A (AMSU-A)

This is the thirty-first monthly report for the Earth Observing System (EOS)/Advanced Microwave Sounding Unit- A (AMSU-A), Contract NAS5-32314, and covers the period from 1 July 1995 through 31 July 1995. This period is the nineteenth month of the Implementation Phase which provides for the design, fabrication, assembly, and test of the first EOS/AMSU-A, the Protoflight Model. Included in this report is the Master Program Schedule (Section 2), a report from the Product Team Leaders on the status of all major program elements (Section 3), Drawing status (Section 4), Weight and Power Budgets (CDRL) 503 (Section 5), Performance Assurance (CDRL 204) (Section 6), Configuration Management Status Report (CDRL 203) (Section 7), Documentation/Data Management Status Report (Section 8), and Contract Status (Section 9).

Mullooly, William↗
NASA NTRS1996

User's Manual for the Naval Interactive Data Analysis System-Climatologies (NIDAS-C), Version 2.0

This technical note provides the user's manual for the NIDAS-C system developed for the naval oceanographic office. NIDAS-C operates using numerous oceanographic data categories stored in an installed version of the Naval Environmental Operational Nowcast System (NEONS), a relational database management system (rdbms) which employs the ORACLE proprietary rdbms engine. Data management, configuration, and control functions for the supporting rdbms are performed externally. NIDAS-C stores and retrieves data to/from the rdbms but exercises no direct internal control over the rdbms or its configuration. Data is also ingested into the rdbms, for use by NIDAS-C, by external data acquisition processes. The data categories employed by NIDAS-C are as follows: Bathymetry - ocean depth at

USER M ANUALS↗
NASA NTRS1998

Framework for Small-Scale Experiments in Software Engineering: Guidance and Control Software Project: Software Engineering Case Study

Software is becoming increasingly significant in today's critical avionics systems. To achieve safe, reliable software, government regulatory agencies such as the Federal Aviation Administration (FAA) and the Department of Defense mandate the use of certain software development methods. However, little scientific evidence exists to show a correlation between software development methods and product quality. Given this lack of evidence, a series of experiments has been conducted to understand why and how software fails. The Guidance and Control Software (GCS) project is the latest in this series. The GCS project is a case study of the Requirements and Technical Concepts for Aviation RTCA/DO-178B guidelines, Software Considerations in Airborne Systems and Equipment Certification. All civil transport airframe and equipment vendors are expected to comply with these guidelines in building systems to be certified by the FAA for use in commercial aircraft. For the case study, two implementations of a guidance and control application were developed to comply with the DO-178B guidelines for Level A (critical) software. The development included the requirements, design, coding, verification, configuration management, and quality assurance processes. This paper discusses the details of the GCS project and presents the results of the case study.

Hayhurst, Kelly J.↗
NASA NTRS1998

Telescience Resource Kit Software Lifecycle

The challenge of a global operations capability led to the Telescience Resource Kit (TReK) project, an in-house software development project of the Mission Operations Laboratory (MOL) at NASA's Marshall Space Flight Center (MSFC). The TReK system is being developed as an inexpensive comprehensive personal computer- (PC-) based ground support system that can be used by payload users from their home sites to interact with their payloads on board the International Space Station (ISS). The TReK project is currently using a combination of the spiral lifecycle model and the incremental lifecycle model. As with any software development project, there are four activities that can be very time consuming: Software design and development, project documentation, testing, and umbrella activities, such as quality assurance and configuration management. In order to produce a quality product, it is critical that each of these activities receive the appropriate amount of attention. For TReK, the challenge was to lay out a lifecycle and project plan that provides full support for these activities, is flexible, provides a way to deal with changing risks, can accommodate unknowns, and can respond to changes in the environment quickly. This paper will provide an overview of the TReK lifecycle, a description of the project's environment, and a general overview of project activities.

Griner, Carolyn S.↗
NASA NTRS1999

National Cycle Program (NCP) Common Analysis Tool for Aeropropulsion

Through the NASA/Industry Cooperative Effort (NICE) agreement, NASA Lewis and industry partners are developing a new engine simulation, called the National Cycle Program (NCP), which is the initial framework of NPSS. NCP is the first phase toward achieving the goal of NPSS. This new software supports the aerothermodynamic system simulation process for the full life cycle of an engine. The National Cycle Program (NCP) was written following the Object Oriented Paradigm (C++, CORBA). The software development process used was also based on the Object Oriented paradigm. Software reviews, configuration management, test plans, requirements, design were all apart of the process used in developing NCP. Due to the many contributors to NCP, the stated software process was mandatory for building a common tool intended for use by so many organizations. The U.S. aircraft and airframe companies recognize NCP as the future industry standard for propulsion system modeling.

Follen, G.↗
NASA NTRS1999

Aerospace Engineering Systems and the Advanced Design Technologies Testbed Experience

Continuous improvement of aerospace product development processes is a driving requirement across much of the aerospace community. As up to 90% of the cost of an aerospace product is committed during the first 10% of the development cycle, there is a strong emphasis on capturing, creating, and communicating better information (both requirements and performance) early in the product development process. The community has responded by pursuing the development of computer-based systems designed to enhance the decision-making capabilities of product development individuals and teams. Recently, the historical foci on sharing the geometrical representation and on configuration management are being augmented: 1) Physics-based analysis tools for filling the design space database; 2) Distributed computational resources to reduce response time and cost; 3) Web-based technologies to relieve machine-dependence; and 4) Artificial intelligence technologies to accelerate processes and reduce process variability. The Advanced Design Technologies Testbed (ADTT) activity at NASA Ames Research Center was initiated to study the strengths and weaknesses of the technologies supporting each of these trends, as well as the overall impact of the combination of these trends on a product development event. Lessons learned and recommendations for future activities are reported.

VanDalsem, William R.↗
NASA NTRS1999

Performing Verification and Validation in Reuse-Based Software Engineering

The implementation of reuse-based software engineering not only introduces new activities to the software development process, such as domain analysis and domain modeling, it also impacts other aspects of software engineering. Other areas of software engineering that are affected include Configuration Management, Testing, Quality Control, and Verification and Validation (V&V). Activities in each of these areas must be adapted to address the entire domain or product line rather than a specific application system. This paper discusses changes and enhancements to the V&V process, in order to adapt V&V to reuse-based software engineering.

Addy, Edward A.↗
NASA NTRS1999

Product Structure, the Heart of Product Definition

This paper describes the LMMSS Product Definition System (PDS) philosophy and approach were the use of each item parts document or software can be traced to a specific end item (EI) serial/tail number of the product. It explains why a part-oriented approach to data organization and configuration management is required. The definition of part-oriented is that all appropriate product definition data products will be collected. Referenced and managed by their linkage/relationship to parts/items, The paper will touch upon how LMMSS store/controls product definition information under each project's top product designator in a two tiered approach. One tier for each product end item and another tier which contain/controls listings of drawings, documents. Specifications and standards that are required for hardware item definition.

DeHoog, C., Jr.↗
NASA NTRS1999

The Hitchhiker's Guide to I&T

With over two dozen missions since the first in 1986, the Hitchhiker project has a reputation for providing quick-reaction, low-cost flight services for Shuttle Small Payloads Project (SSPP) customers. Despite the successes, several potential improvements in customer payload integration and test (I&T) deserve consideration. This paper presents suggestions to Hitchhiker customers on how to help make the I&T process run smoother. Included are: customer requirements and interface definition, pre-integration test and evaluation, configuration management, I&T overview and planning, problem mitigation, and organizational communication. In this era of limited flight opportunities and new ISO-based requirements, issues such as these have become more important than ever.

Wright, Michael R.↗
NASA NTRS1998

Integrated Advanced Microwave Sounding Unit-A (AMSU-A)

This is the 69th Monthly Report for the Advanced Microwave Sounding Unit-A (EOS/AMSU-A), Contract NAS5-32314, and covers the period from 01 September through 30 September 1998. Included in this report are Combined Program Delivery Schedules and Reports (Section 2); a report from the Product Team Leaders on the status of all major program elements (Section 3); Contract Data Requirements List (CDRL) 503, the Weight and Power Budgets (Section 5); CDRL 204, reporting on the activities of Performance Assurance (Section 6); CDRL 203, the Configuration Management Status Report (Section 7); and the Document/Data Management Status Report (Section 8).

Hauerwaas, R.↗
NASA NTRS2000

The Road to a TERRA Operational System

EOS-Terra (formerly known as AM-1) is the first in a series of NASA Earth Observing System (EOS) spacecraft. This paper describes what it took to get ready for Terra, the problems encountered along the way, and the challenge of making an integrated system and integrated team out of many diverse systems and groups, including the international partners and agencies. This paper describes how the coordination role for system resources scheduling, system configuration management, and status reporting was implemented, and the vital role this coordination effort played for enhanced productivity and improved communication across the teams. Lessons which can be learned from this major effort are presented.

Kelly, Angelita C.↗
NASA NTRS2000

Integrated Advanced Microwave Sounding Unit-A (AMSU-A): Monthly Report for August

Included in this report are Combined Program Delivery Schedules and Reports; a report from the Product Team Leaders on the status of all major program elements; Contract Data Requirements List (CDRL) 503, the Weight and Power Budgets; CDRL 204, reporting on the activities of Performance Assurance; CDRL 203, the Configuration Management Status Report; and the Documentation/Data Management Status Report.

Nieto, A.↗
NASA NTRS2000

CM and DM in an ISO R and D Environment

ISO 9000 - a common buzz word in industry is making inroads to government agencies. The National Aeronautics and Space Agency (NASA) achieved ISO 9001 certification at each of its nine (9) Centers and Headquarters in 1998-1999. NASA Glenn Research Center (GRC) was recommended for certification in September 1999. Since then, each of the Centers has been going through the semi-annual surveillance audits. Growing out of the manufacturing industry, successful application of the international quality standard to a research and development (R&D) environment has had its challenges. This paper will address how GRC applied Configuration Management (CM) and Data (or Document) Management (DM) to meet challenges to achieve ISO certification. One of the first challenges was to fit the ISO 9001-1994 elements to the GRC environment. Some of the elements fit well-Management Responsibility (4.1), Internal Audits (4.17), Document and Data Control (4.5). Other elements were not suited or applied easily to the R&D environment-Servicing (4.19), Statistical Techniques (4.20). Since GRC "builds" only one or two items at a time, these elements were considered not applicable to the environment.

Crowley, Sandra L.↗