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 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.↗
NASA NTRS2000

Ubiquitous CM and DM

Ubiquitous is a real word. I thank a former Total Quality Coach for my first exposure some years ago to its existence. My version of Webster's dictionary defines ubiquitous as "present, or seeming to be present, everywhere at the same time; omnipresent." While I believe that God is omnipresent, I have come to discover that CM and DM are present everywhere. Oh, yes; I define CM as Configuration Management and DM as either Data or Document Management. Ten years ago, I had my first introduction to the CM world. I had an opportunity to do CM for the Space Station effort at the NASA Lewis Research Center. I learned that CM was a discipline that had four areas of focus: identification, control, status accounting, and verification. I was certified as a CMIl graduate and was indoctrinated about clear, concise, and valid. Off I went into a world of entirely new experiences. I was exposed to change requests and change boards first hand. I also learned about implementation of changes, and then of technical and CM requirements.

Crowley, Sandra L.↗
NASA NTRS1996

A Model-based Approach to Reactive Self-Configuring Systems

This paper describes Livingstone, an implemented kernel for a self-reconfiguring autonomous system, that is reactive and uses component-based declarative models. The paper presents a formal characterization of the representation formalism used in Livingstone, and reports on our experience with the implementation in a variety of domains. Livingstone's representation formalism achieves broad coverage of hybrid software/hardware systems by coupling the concurrent transition system models underlying concurrent reactive languages with the discrete qualitative representations developed in model-based reasoning. We achieve a reactive system that performs significant deductions in the sense/response loop by drawing on our past experience at building fast prepositional conflict-based algorithms for model-based diagnosis, and by framing a model-based configuration manager as a prepositional, conflict-based feedback controller that generates focused, optimal responses. Livingstone automates all these tasks using a single model and a single core deductive engine, thus making significant progress towards achieving a central goal of model-based reasoning. Livingstone, together with the HSTS planning and scheduling engine and the RAPS executive, has been selected as the core autonomy architecture for Deep Space One, the first spacecraft for NASA's New Millennium program.

Williams, Brian C.↗
NASA NTRS1998

A Hybrid Procedural/Deductive Executive for Autonomous Spacecraft

The New Millennium Remote Agent (NMRA) will be the first AI system to control an actual spacecraft. The spacecraft domain places a strong premium on autonomy and requires dynamic recoveries and robust concurrent execution, all in the presence of tight real-time deadlines, changing goals, scarce resource constraints, and a wide variety of possible failures. To achieve this level of execution robustness, we have integrated a procedural executive based on generic procedures with a deductive model-based executive. A procedural executive provides sophisticated control constructs such as loops, parallel activity, locks, and synchronization which are used for robust schedule execution, hierarchical task decomposition, and routine configuration management. A deductive executive provides algorithms for sophisticated state inference and optimal failure recover), planning. The integrated executive enables designers to code knowledge via a combination of procedures and declarative models, yielding a rich modeling capability suitable to the challenges of real spacecraft control. The interface between the two executives ensures both that recovery sequences are smoothly merged into high-level schedule execution and that a high degree of reactivity is retained to effectively handle additional failures during recovery.

Pell, Barney↗
NASA NTRS1999

Aerospace Engineering Systems

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: Physics-based analysis tools for filling the design space database; Distributed computational resources to reduce response time and cost; Web-based technologies to relieve machine-dependence; and Artificial intelligence technologies to accelerate processes and reduce process variability. Activities such as the Advanced Design Technologies Testbed (ADTT) project at NASA Ames Research Center 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 will be reported.

VanDalsem, William R.↗
NASA NTRS2002

Software Development and Test Methodology for a Distributed Ground System

The Marshall Space Flight Center's (MSFC) Payload Operations Center (POC) ground system has evolved over a period of about 10 years. During this time the software processes have migrated from more traditional to more contemporary development processes in an effort to minimize unnecessary overhead while maximizing process benefits. The Software processes that have evolved still emphasize requirements capture, software configuration management, design documenting, and making sure the products that have been developed are accountable to initial requirements. This paper will give an overview of how the Software Processes have evolved, highlighting the positives as well as the negatives. In addition, we will mention the COTS tools that have been integrated into the processes and how the COTS have provided value to the project.

Ritter, George↗
NASA NTRS2002

Software Design Methodology Migration for a Distributed Ground System

The Marshall Space Flight Center's (MSFC) Payload Operations Center (POC) ground system has been developed and has evolved over a period of about 10 years. During this time the software processes have migrated from more traditional to more contemporary development processes. The new Software processes still emphasize requirements capture, software configuration management, design documenting, and making sure the products that have been developed are accountable to initial requirements. This paper will give an overview of how the Software Process have evolved highlighting the positives as well as the negatives. In addition, we will mention the COTS tools that have been integrated into the processes and how the COTS have provided value to the project .

Ritter, George↗
NASA NTRS2001

External Data and Attribute Hyperlink Programs for Promis*e(Registered Trademark)

External Data and Attribute Hyperlink are computer programs that can be added to Promis*e(trademark) which is a commercial software system that automates routine tasks in the design (including drawing schematic diagrams) of electrical control systems. The programs were developed under the Stennis Space Center's (SSC) Dual Use Technology Development Program to provide capabilities for SSC's BMCS configuration management system which uses Promis*e(trademark). The External Data program enables the storage and management of information in an external database linked to a drawing. Changes can be made either in the database or on the drawing. Information that originates outside Promis*e(trademark) can be stored in custom fields that can be added to the database. Although this information is not available in Promis*e(trademark) printed drawings, it can be associated with symbols in the drawings, and can be retrieved through the drawings when the software is running. The Attribute Hyperlink program enables the addition of hyperlink information as attributes of symbols. This program enables the formation of a direct hyperlink between a schematic diagram and an Internet site or a file on a compact disk, on the user's hard drive, or on another computer on a network to which the user's computer is connected. The user can then obtain information directly related to the part (e.g., maintenance, or troubleshooting information) associated with the hyperlink.

Derengowski, Rich↗
NASA NTRS2005

NASA Remote Sensing Data in Earth Sciences: Processing, Archiving, Distribution, Applications at the GES DISC

The NASA Goddard Earth Sciences Data and Information Services Center (GES DISC) is one of the major Distributed Active Archive Centers (DAACs) archiving and distributing remote sensing data from the NASA's Earth Observing System. In addition to providing just data, the GES DISC/DAAC has developed various value-adding processing services. A particularly useful service is data processing a t the DISC (i.e., close to the input data) with the users' algorithms. This can take a number of different forms: as a configuration-managed algorithm within the main processing stream; as a stand-alone program next to the on-line data storage; as build-it-yourself code within the Near-Archive Data Mining (NADM) system; or as an on-the-fly analysis with simple algorithms embedded into the web-based tools (to avoid downloading unnecessary all the data). The existing data management infrastructure at the GES DISC supports a wide spectrum of options: from data subsetting data spatially and/or by parameter to sophisticated on-line analysis tools, producing economies of scale and rapid time-to-deploy. Shifting processing and data management burden from users to the GES DISC, allows scientists to concentrate on science, while the GES DISC handles the data management and data processing at a lower cost. Several examples of successful partnerships with scientists in the area of data processing and mining are presented.

Leptoukh, Gregory G.↗
NASA NTRS2005

Lessons Learned Implementing DOORS in a Citrix Environment

NASA's James Web Space Telescope (JWST) Project is a large multi-national project with geographically dispersed contractors that all need access to the Projects requirement database. Initially, the project utilized multiple DOORS databases with the built-in partitions feature to exchange modules amongst the various contractor sites. As the requirements databases matured the use of partitions became extremely difficult. There have been many issues such as incompatible versions of DOORS, inefficient mechanism for sharing modules, security concerns, performance issues, and inconsistent document import and export formats. Deployment of the client software with limited IT resources available was also an issue. The solution chosen by JWST was to integrate the use of a Citrix environment with the DOORS database to address most of the project concerns. The use of the Citrix solution allowed a single Requirements database in a secure environment via a web interface. The Citrix environment allows JWST to upgrade to the most current version of DOORS without having to coordinate multiple sites and user upgrades. The single requirements database eliminates a multitude of Configuration Management concerns and facilitated the standardization of documentation formats. This paper discusses the obstacles and the lessons learned throughout the installation, implementation, usage and deployment process of a centralized DOORS database solution.

Bussman, Marie↗