Search NASA⌕ Search

SEARCH · Search NASA

Results for “project documentation”

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 91 records · Page 5

Abrstract - OnePlace Redesign Spring 2020 Internship

The project I worked on was the OnePlace Redesign. In that, I converted the OnePlace home page to the Service Portal to match NASA OnePlace’s current application design standards, I was able to allow users to easily find applications in OnePlace and I was able to allow users to easily find and request OnePlace services (new app development, new knowledge base, etc.). It was a major accomplishment to be able to remodel a website that soon the entire Langley center that uses OnePlace will use. The website was made through ServiceNow’s Service Portal, and I organized the applications like never before, allowed a clear styling to applications a user does not have access to and/or are new applications, browsing of applications with clear button divisions, and allowing for different options depending if app is accessible or not, with proper error checking in place and very-well documented code. It was amazing to incorporate all this logic into one widget so that whoever wants to utilize this feature has no trouble at all to do so. The 3 most important things I learned were being able to do this work within ServiceNow, as it is such an important enterprise platform for CRM and boosting the connected workforce of NASA, incorporate built-in APIs from ServiceNow Glide Records to connect Server Scripts to Client Scripts and HTML, and be able to use agile to get another experience of managing work capacity with stories, and having proper communication with the team if every feature is done correctly and steps for continuing forward. The part that I enjoyed the most was the training I did for ServiceNow and I freedom I had to experiment to see how to structure the Service Portal. I was not tied down, and I believe this allowed for a better outcome of the product. As part of the internship, I created a very in-depth design document with the help of my team to document the project goals before it was started and technical documentation (including the design document) summarizing the final result of the product in terms of the new features added and the explanation of the logic thoroughly so that anyone can understand the project easily. The technical documentation will be published as a Knowledge Article within OnePlace Knowledge Base documentation.

Ariel Wald↗

Development of iterative techniques for the solution of unsteady compressible viscous flows

The work done under this project was documented in detail as the Ph. D. dissertation of Dr. Duane Hixon. The objectives of the research project were evaluation of the generalized minimum residual method (GMRES) as a tool for accelerating 2-D and 3-D unsteady flows and evaluation of the suitability of the GMRES algorithm for unsteady flows, computed on parallel computer architectures.

Sankar, Lakshmi↗

Extravehicular Activity and Human Surface Mobility Program (EHP): Integrated Concept of Operations (ConOps), Revision B

The EHP Integrated ConOps detailed in this document are intended to provide the operational context to inform the development of the xEVA System, LTV, and PR projects. This document describes a bounding set of Design Reference Missions (DRM) to provide scope for interpretation and implementation guidance of the controlled requirements in EHP-10012, Extravehicular Activity and Human Surface Mobility Program (EHP) System Requirements Document.

Extravehicular Activity↗

Software Management Environment (SME): Components and algorithms

This document presents the components and algorithms of the Software Management Environment (SME), a management tool developed for the Software Engineering Branch (Code 552) of the Flight Dynamics Division (FDD) of the Goddard Space Flight Center (GSFC). The SME provides an integrated set of visually oriented experienced-based tools that can assist software development managers in managing and planning software development projects. This document describes and illustrates the analysis functions that underlie the SME's project monitoring, estimation, and planning tools. 'SME Components and Algorithms' is a companion reference to 'SME Concepts and Architecture' and 'Software Engineering Laboratory (SEL) Relationships, Models, and Management Rules.'

Hendrick, Robert↗

High-Rate Delay Tolerant Networking (HDTN) Software Requirements Analysis

This document serves as a detailed analysis of the main networking protocols implemented by HDTN. Sources of the protocol specifications include Internet Engineering Task Force (IETF) Request for Comments (RFC) and Consultative Committee for Space Data Systems (CCSDS) standards. The focus of this report is to derive software requirements suitable for NASA Procedural Requirements 7150.2D Class B compliance, including requirements traceability and software verification and validation, from the source specifications. This analysis will be incorporated into the finalized HDTN Software Requirements Specification (SRS) but does not encompass the full scope of the HDTN SRS. Requirements in this document are considered draft. The complete requirements will include bundle application requirements, interface requirements, computer resource requirements, software quality factors, and additional requirements as determined by the project. This document is publicly released to the greater community to receive feedback and foster collaboration opportunities.

Rachel Dudukovich↗

United States Space Station technical and programmatic interfaces

This paper describes the design of the U.S. Space Station and explains the control factors used for internal and external interfaces among the various government and contractor participants. It discusses the documentation of the U.S. Space Station Program including the Program Approval Document (PAD), the Program Plans (PPs), the Program Requirements Document (PRD), the Program Definition and Requirements Document (PDRD), the Level III project plans, and the Level III project design requirements documents. It discusses the relationship of Space Station documentation to the international Memoranda of Understanding (MOUs) and the Joint PP, PRD, and PDRD, the interrelationship of the Architectural Control Documents (ACDs), the Baseline Control Document (BCD), and the Interface Requirement Documents (IRDs) and Interface Control Documents (ICDs). Also included are the controlling functions of the various NASA and contractor participants and the international partners.

Carlisle, Richard F.↗

Hyperspectral Technology Transfer to the US Department of Interior: Summary of Results of the NASA/DOI Hyperspectral Technology Transfer Project

In 1997 the Office of Biological Informatics and Outreach (OBIO), Biological Resources Division, US Geological Survey and NASA, Office of Earth Science (OES), initiated a coordinated effort for applying Airborne Visible and Infrared Imaging Spectrometer (AVIRIS) data and analysis, as a technology transfer project, to critical DOI environmental issues in four study sites throughout the United States. This work was accomplished by four US Department of the Interior (DOI) study teams with support from NASA/OES principal investigators and the Office of Earth Science programs. The studies, including personnel, objectives, background, project plans, and milestones were documented in a project website at . This report summarizes the final outcomes of the project, detailing accomplishments, lessons learned, and benefits realized to NASA, the US Geological Survey, and the participating DOI bureaus.

Root, Ralph↗

Automatic Extraction of JPF Options and Documentation

Documenting existing Java PathFinder (JPF) projects or developing new extensions is a challenging task. JPF provides a platform for creating new extensions and relies on key-value properties for their configuration. Keeping track of all possible options and extension mechanisms in JPF can be difficult. This paper presents jpf-autodoc-options, a tool that automatically extracts JPF projects options and other documentation-related information, which can greatly help both JPF users and developers of JPF extensions.

Static Analysis↗

Technology Evaluation for Environmental Risk Mitigation Compendium

The Technology Evaluation for Environmental Risk Mitigation (TEERM) Principal Center and its predecessor organization the Acquisition Pollution Prevention Program (AP2) supported the National Aeronautics and Space Administration (NASA) in identifying technology solutions to risks and costs to NASA programs driven by environmental regulations and requirements. TEERM researched the commercial and government marketplace to locate viable and available technologies that met NASAs needs. TEERM focused on addressing environmentally-driven risks of direct concern to NASA programs and facilities, including hazardous materials in NASA operations and materials that became obsolescent because of environmental regulations. TEERM projects aimed to reduce cost; ensure the health and safety of people, assets, and the environment; promote efficiency; and minimize duplication. Major TEERM and AP2 projects focused on waste minimization and hazardous waste treatment, recycling, corrosion prevention and control, solvent and ozone depleting substances substitution, and aqueous based cleaners. In 2017, NASA made the decision to terminate the TEERM Principal Center. This Compendium Report documents TEERM and AP2 project successes. The Compendium Report traces the evolution of TEERM based on evolving risks and requirements for NASA and its relationship to the Space Shuttle Program, the United States Department of Defense, the European Space Agency, and other public and private stakeholders. This Compendium Report also documents project details from Project Summaries and Joint Test Plans and describes project stakeholders and collaborative effort results.

material obsolescent↗

LCS Content Document Application

My project at KSC during my spring 2011 internship was to develop a Ruby on Rails application to manage Content Documents..A Content Document is a collection of documents and information that describes what software is installed on a Launch Control System Computer. It's important for us to make sure the tools we use everyday are secure, up-to-date, and properly licensed. Previously, keeping track of the information was done by Excel and Word files between different personnel. The goal of the new application is to be able to manage and access the Content Documents through a single database backed web application. Our LCS team will benefit greatly with this app. Admin's will be able to login securely to keep track and update the software installed on each computer in a timely manner. We also included exportability such as attaching additional documents that can be downloaded from the web application. The finished application will ease the process of managing Content Documents while streamlining the procedure. Ruby on Rails is a very powerful programming language and I am grateful to have the opportunity to build this application.

Hochstadt, Jake↗

NASA newsletters for the Weber Student Shuttle Involvement Project

Biweekly reports generated for the Weber Student Shuttle Involvement Project (SSIP) are discussed. The reports document the evolution of science, hardware, and logistics for this Shuttle project aboard the eleventh flight of the Space Transportation System (STS-41B), launched from Kennedy Space Center on February 3, 1984, and returned to KSC 8 days later. The reports were intended to keep all members of the team aware of progress in the project and to avoid redundancy and misunderstanding. Since the Weber SSIP was NASA's first orbital rat project, documentation of all actions was essential to assure the success of this complex project. Eleven reports were generated: October 3, 17 and 31; November 14 and 28; and December 12 and 17, 1983; and January 3, 16, and 23; and May 1, 1984. A subject index of the reports is included. The final report of the project is included as an appendix.

Morey-Holton, E. R.↗

Software Management Environment (SME) concepts and architecture, revision 1

This document presents the concepts and architecture of the Software Management Environment (SME), developed for the Software Engineering Branch of the Flight Dynamic Division (FDD) of GSFC. The SME provides an integrated set of experience-based management tools that can assist software development managers in managing and planning flight dynamics software development projects. This document provides a high-level description of the types of information required to implement such an automated management tool.

Hendrick, Robert↗

Automated ISS Flight Utilities

During my internship at NASA Johnson Space Center, I worked in the Space Radiation Analysis Group (SRAG), where I was tasked with a number of projects focused on the automation of tasks and activities related to the operation of the International Space Station (ISS). As I worked on a number of projects, I have written short sections below to give a description for each, followed by more general remarks on the internship experience. My first project is titled "General Exposure Representation EVADOSE", also known as "GEnEVADOSE". This project involved the design and development of a C++/ ROOT framework focused on radiation exposure for extravehicular activity (EVA) planning for the ISS. The utility helps mission managers plan EVAs by displaying information on the cumulative radiation doses that crew will receive during an EVA as a function of the egress time and duration of the activity. SRAG uses a utility called EVADOSE, employing a model of the space radiation environment in low Earth orbit to predict these doses, as while outside the ISS the astronauts will have less shielding from charged particles such as electrons and protons. However, EVADOSE output is cumbersome to work with, and prior to GEnEVADOSE, querying data and producing graphs of ISS trajectories and cumulative doses versus egress time required manual work in Microsoft Excel. GEnEVADOSE automates all this work, reading in EVADOSE output file(s) along with a plaintext file input by the user providing input parameters. GEnEVADOSE will output a text file containing all the necessary dosimetry for each proposed EVA egress time, for each specified EVADOSE file. It also plots cumulative dose versus egress time and the ISS trajectory, and displays all of this information in an auto-generated presentation made in LaTeX. New features have also been added, such as best-case scenarios (egress times corresponding to the least dose), interpolated curves for trajectories, and the ability to query any time in the EVADES output. As mentioned above, GEnEVADOSE makes extensive use of ROOT version 6, the data analysis framework developed at the European Organization for Nuclear Research (CERN), and the code is written to the C++11 standard (as are the other projects). My second project is the Automated Mission Reference Exposure Utility (AMREU).Unlike GEnEVADOSE, AMREU is a combination of three frameworks written in both Python and C++, also making use of ROOT (and PyROOT). Run as a combination of daily and weekly cron jobs, these macros query the SRAG database system to determine the active ISS missions, and query minute-by-minute radiation dose information from ISS-TEPC (Tissue Equivalent Proportional Counter), one of the radiation detectors onboard the ISS. Using this information, AMREU creates a corrected data set of daily radiation doses, addressing situations where TEPC may be offline or locked up by correcting doses for days with less than 95% live time (the total amount time the instrument acquires data) by averaging the past 7 days. As not all errors may be automatically detectable, AMREU also allows for manual corrections, checking an updated plaintext file each time it runs. With the corrected data, AMREU generates cumulative dose plots for each mission, and uses a Python script to generate a flight note file (.docx format) containing these plots, as well as information sections to be filled in and modified by the space weather environment officers with information specific to the week. AMREU is set up to run without requiring any user input, and it automatically archives old flight notes and information files for missions that are no longer active. My other projects involve cleaning up a large data set from the Charged Particle Directional Spectrometer (CPDS), joining together many different data sets in order to clean up information in SRAG SQL databases, and developing other automated utilities for displaying information on active solar regions, that may be used by the space weather environment officers to monitor solar activity. I consulted my mentor Dr. Ryan Rios and Dr. Kerry Lee for project requirements and added features, and ROOT developer Edmond Offermann for advice on using the ROOT library. I also received advice and feedback from Dr. Janet Barzilla of SRAG, who tested my code. Besides these inputs, I worked independently, writing all of the code by myself. The code for all these projects is documented throughout, and I have attempted to write it in a modular format. Assuming that ROOT is updated accordingly, these codes are also Y2038-compliant (and Y10K-compliant). This allows the code to be easily referenced, modified and possibly repurposed for non-ISS missions in the future, should the necessary inputs exist. These projects have taught me a lot about coding and software design - I have become a much more skilled C++ programmer and ROOT user, and I also learned to code in Python and PyROOT (and its advantages and disadvantages compared to C++/ ROOT). Furthermore, I have learned about space radiation and radiation modeling, topics that greatly interest me as I pursue a degree in physics. Working alongside experimental physicists like Dr. Rios, I have developed a greater understanding and appreciation for experimental science, something I have always leaned towards but to which I lacked significant exposure. My work in SRAG has also given me the invaluable opportunity to witness the work environment for physicists at NASA, and what a career in academia may look like at a government laboratory such as NASA Johnson Space Center. As I continue my studies and look forward to graduate school and a future career, this experience at NASA has given me a meaningful and enjoyable opportunity to put my skills to use and see what my future career path might hold.

Offermann, Jan Tuzlic↗

Parametric Fin-Body and Fin-Plate Database for a Series of 12 Missile Fins

A cooperative experimental investigation has been performed to obtain a systematic fin-body and fin-plate database for a series of 12 missile fins. These data are intended to complement and extend the information contained in the Triservice missile project and to provide a systematic set of experimental data from which fin-body interference factors can be derived. Data were obtained with the fins mounted on both an axisymmetric body and on a flat plate that was used to simulate fin-alone measurements. The experiments were conducted at Mach numbers from 0.60 to 3.95; fin deflection angles of 0 deg, 10 deg, and -10 deg; and angles of attack up to 30 deg on the body and up to 95 deg on the flat plate. The data were obtained from three-component balances attached to the fins and a six-component balance located in the axisymmetric body. The data obtained in this project are documented in tabular form in this report. In addition, selected data are presented in graphical form to illustrate the effects of the test variables. These variables are configuration angle of attack; Mach number; and fin parameters of deflection angle, planform size, taper ratio, and aspect ratio. A very limited comparison with the Triservice missile data is made to illustrate the consistency between the data from these two projects.

Allen, Jerry M.↗

The Decision to Send Humans Back to the Moon and on to Mars: Space Exploration Initiative History Project

This folder contains working papers collected to date on a NASA-sponsored history project to document the events leading up to the July 20, 1989 speech setting forth the objectives of the Space Exploration Initiative. Included are a chronology of events, briefing papers produced by the NASA Working Group laying out proposal, briefing charts used to present the proposal, a copy of the President's speech, and an essay summarizing the events that led up to the announcement. Additionally, two fo the interviews conducted as part of the project are enclosed.

McCurdy, Howard E.↗

Development Efforts Expanded in Ion Propulsion: Ion Thrusters Developed With Higher Power Levels

The NASA Glenn Research Center was the major contributor of 2-kW-class ion thruster technology to the Deep Space 1 mission, which was successfully completed in early 2002. Recently, NASA s Office of Space Science awarded approximately $21 million to Glenn to develop higher power xenon ion propulsion systems for large flagship missions such as outer planet explorers and sample return missions. The project, referred to as NASA's Evolutionary Xenon Thruster (NEXT), is a logical follow-on to the ion propulsion system demonstrated on Deep Space 1. The propulsion system power level for NEXT is expected to be as high as 25 kW, incorporating multiple ion thrusters, each capable of being throttled over a 1- to 6-kW power range. To date, engineering model thrusters have been developed, and performance and plume diagnostics are now being documented. The project team-Glenn, the Jet Propulsion Laboratory, General Dynamics, Boeing Electron Dynamic Devices, the Applied Physics Laboratory, the University of Michigan, and Colorado State University-is in the process of developing hardware for a ground demonstration of the NEXT propulsion system, which comprises a xenon feed system, controllers, multiple thrusters, and power processors. The development program also will include life assessments by tests and analyses, single-string tests of ion thrusters and power systems, and finally, multistring thruster system tests in calendar year 2005. In addition, NASA's Office of Space Science selected Glenn to lead the development of a 25-kW xenon thruster to enable NASA to conduct future missions to the outer planets of Jupiter and beyond, under the High Power Electric Propulsion (HiPEP) program. The development of a 100-kW-class ion propulsion system and power conversion systems are critical components to enable future nuclear-electric propulsion systems. In fiscal year 2003, a team composed of Glenn, the Boeing Company, General Dynamics, the Applied Physics Laboratory, the Naval Research Laboratory, the University of Wisconsin, the University of Michigan, and Colorado State University will perform a 6-month study that will result in the design of a 25-kW ion thruster, a propellant feed system, and a power processing architecture. The following 2 years will involve hardware development, wear tests, single-string tests of the thruster-power circuits and the xenon feed system, and subsystem service life analyses. The 2-kW-class ion propulsion technology developed for the Deep Space 1 mission will be used for NASA's discovery mission Dawn, which involves maneuvering a spacecraft to survey the asteroids Ceres and Vesta. The 6-kW-class ion thruster subsystem technology under NEXT is scheduled to be flight ready by calendar year 2006. The less mature 25- kW ion thruster system under HiPEP is expected to be ready for a flight advanced development program in calendar year 2006.

Patterson, Michael J.↗

Space Mission Concept Development Using Concept Maturity Levels

Over the past five years, pre-project formulation experts at the Jet Propulsion Laboratory (JPL) has developed and implemented a method for measuring and communicating the maturity of space mission concepts. Mission concept development teams use this method, and associated tools, prior to concepts entering their Formulation Phases (Phase A/B). The organizing structure is Concept Maturity Level (CML), which is a classification system for characterizing the various levels of a concept's maturity. The key strength of CMLs is the ability to evolve mission concepts guided by an incremental set of assessment needs. The CML definitions have been expanded into a matrix form to identify the breadth and depth of analysis needed for a concept to reach a specific level of maturity. This matrix enables improved assessment and communication by addressing the fundamental dimensions (e.g., science objectives, mission design, technical risk, project organization, cost, export compliance, etc.) associated with mission concept evolution. JPL's collaborative engineering, dedicated concept development, and proposal teams all use these and other CML-appropriate design tools to advance their mission concept designs. This paper focuses on mission concept's early Pre-Phase A represented by CMLs 1- 4. The scope was limited due to the fact that CMLs 5 and 6 are already well defined based on the requirements documented in specific Announcement of Opportunities (AO) and Concept Study Report (CSR) guidelines, respectively, for competitive missions; and by NASA's Procedural Requirements NPR 7120.5E document for Projects in their Formulation Phase.

Concept Maturity Levels (CMLs)↗

Standardized development of computer software. Part 1: Methods

This work is a two-volume set on standards for modern software engineering methodology. This volume presents a tutorial and practical guide to the efficient development of reliable computer software, a unified and coordinated discipline for design, coding, testing, documentation, and project organization and management. The aim of the monograph is to provide formal disciplines for increasing the probability of securing software that is characterized by high degrees of initial correctness, readability, and maintainability, and to promote practices which aid in the consistent and orderly development of a total software system within schedule and budgetary constraints. These disciplines are set forth as a set of rules to be applied during software development to drastically reduce the time traditionally spent in debugging, to increase documentation quality, to foster understandability among those who must come in contact with it, and to facilitate operations and alterations of the program as requirements on the program environment change.

Tausworthe, R. C.↗