Search NASASearch

SEARCH · Search NASA

Results for “software training plan”

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 19 records

JPL software training plan

The purpose of this document is to define the software training approach and plans for the Jet Propulsion Laboratory.

software training plan

A report on NASA software engineering and Ada training requirements

NASA's software engineering and Ada skill base are assessed and information that may result in new models for software engineering, Ada training plans, and curricula are provided. A quantitative assessment which reflects the requirements for software engineering and Ada training across NASA is provided. A recommended implementation plan including a suggested curriculum with associated duration per course and suggested means of delivery is also provided. The distinction between education and training is made. Although it was directed to focus on NASA's need for the latter, the key relationships to software engineering education are also identified. A rationale and strategy for implementing a life cycle education and training program are detailed in support of improved software engineering practices and the transition to Ada.

Legrand, Sue

A suggested classification system for standard on-orbit shuttle flight phases

The definition of standard flight segments of phases, representing flight profile components which can be combined in various sequences to satisfy particular objectives, is a necessity for simplifying operational procedures and for minimizing the cost of flight planning, software development, and training. The critical elements are (1) a greater variety of generic segment types that may be incorporated into a given flight profile, (2) a greater variability of the order in which segments may be combined to construct a particular flight profile, and (3) a greater variation of detail within a given generic segment type. All of these variations arise basically from shuttle payload characteristics. They are manifested in a number of ways, including changes in the shuttle configuration from one flight to another.

Wilson, S. W.

Ground Systems Development Environment (GSDE) software configuration management

This report presents a review of the software configuration management (CM) plans developed for the Space Station Training Facility (SSTF) and the Space Station Control Center. The scope of the CM assessed in this report is the Systems Integration and Testing Phase of the Ground Systems development life cycle. This is the period following coding and unit test and preceding delivery to operational use. This report is one of a series from a study of the interfaces among the Ground Systems Development Environment (GSDE), the development systems for the SSTF and the SSCC, and the target systems for SSCC and SSTF. This is the last report in the series. The focus of this report is on the CM plans developed by the contractors for the Mission Systems Contract (MSC) and the Training Systems Contract (TSC). CM requirements are summarized and described in terms of operational software development. The software workflows proposed in the TSC and MSC plans are reviewed in this context, and evaluated against the CM requirements defined in earlier study reports. Recommendations are made to improve the effectiveness of CM while minimizing its impact on the developers.

Church, Victor E.

NASA Tech Briefs, October 2003

Topics covered include: Cryogenic Temperature-Gradient Foam/Substrate Tensile Tester; Flight Test of an Intelligent Flight-Control System; Slat Heater Boxes for Thermal Vacuum Testing; System for Testing Thermal Insulation of Pipes; Electrical-Impedance-Based Ice-Thickness Gauges; Simulation System for Training in Laparoscopic Surgery; Flasher Powered by Photovoltaic Cells and Ultracapacitors; Improved Autoassociative Neural Networks; Toroidal-Core Microinductors Biased by Permanent Magnets; Using Correlated Photons to Suppress Background Noise; Atmospheric-Fade-Tolerant Tracking and Pointing in Wireless Optical Communication; Curved Focal-Plane Arrays Using Back-Illuminated High-Purity Photodetectors; Software for Displaying Data from Planetary Rovers; Software for Refining or Coarsening Computational Grids; Software for Diagnosis of Multiple Coordinated Spacecraft; Software Helps Retrieve Information Relevant to the User; Software for Simulating a Complex Robot; Software for Planning Scientific Activities on Mars; Software for Training in Pre-College Mathematics; Switching and Rectification in Carbon-Nanotube Junctions; Scandia-and-Yttria-Stabilized Zirconia for Thermal Barriers; Environmentally Safer, Less Toxic Fire-Extinguishing Agents; Multiaxial Temperature- and Time-Dependent Failure Model; Cloverleaf Vibratory Microgyroscope with Integrated Post; Single-Vector Calibration of Wind-Tunnel Force Balances; Microgyroscope with Vibrating Post as Rotation Transducer; Continuous Tuning and Calibration of Vibratory Gyroscopes; Compact, Pneumatically Actuated Filter Shuttle; Improved Bearingless Switched-Reluctance Motor; Fluorescent Quantum Dots for Biological Labeling; Growing Three-Dimensional Corneal Tissue in a Bioreactor; Scanning Tunneling Optical Resonance Microscopy; The Micro-Arcsecond Metrology Testbed; Detecting Moving Targets by Use of Soliton Resonances; and Finite-Element Methods for Real-Time Simulation of Surgery.

Source record

Flight Planning Branch NASA Co-op Tour

This semester I worked with the Flight Planning Branch at the NASA Johnson Space Center. I learned about the different aspects of flight planning for the International Space Station as well as the software that is used internally and ISSLive! which is used to help educate the public on the space program. I had the opportunity to do on the job training in the Mission Control Center with the planning team. I transferred old timeline records from the planning team's old software to the new software in order to preserve the data for the future when the software is retired. I learned about the operations of the International Space Station, the importance of good communication between the different parts of the planning team, and enrolled in professional development classes as well as technical classes to learn about the space station.

Marr, Aja M.

Structural considerations for a software life cycle dynamic simulation model

This paper presents the results of a preliminary study into the prospects for simulating the software implementation and maintenance life cycle process, with the aim of producing a computerized tool for use by management and software engineering personnel in project planning, tradeoff studies involving product, environmental, situational, and technological factors, and training. The approach taken is the modular application of a 'flow of resource' concept to the systems dynamics simulation modeling technique. The software life cycle process is represented as a number of stochastic, time-varying, interacting work tasks that each achieves one of the project milestones. Each task is characterized by the item produced, the personnel applied, and the budgetary profile.

Tausworthe, R. C.

New approaches to virtual environment surgery

This research focused on two main problems: 1) low cost, high fidelity stereoscopic imaging of complex tissues and organs; and 2) virtual cutting of tissue. A further objective was to develop these images and virtual tissue cutting methods for use in a telemedicine project that would connect remote sites using the Next Generation Internet. For goal one we used a CT scan of a human heart, a desktop PC with an OpenGL graphics accelerator card, and LCD stereoscopic glasses. Use of multiresolution meshes ranging from approximately 1,000,000 to 20,000 polygons speeded interactive rendering rates enormously while retaining general topography of the dataset. For goal two, we used a CT scan of an infant skull with premature closure of the right coronal suture, a Silicon Graphics Onyx workstation, a Fakespace Immersive WorkBench and CrystalEyes LCD glasses. The high fidelity mesh of the skull was reduced from one million to 50,000 polygons. The cut path was automatically calculated as the shortest distance along the mesh between a small number of hand selected vertices. The region outlined by the cut path was then separated from the skull and translated/rotated to assume a new position. The results indicate that widespread high fidelity imaging in virtual environment is possible using ordinary PC capabilities if appropriate mesh reduction methods are employed. The software cutting tool is applicable to heart and other organs for surgery planning, for training surgeons in a virtual environment, and for telemedicine purposes.

NASA Discipline Neuroscience

Guidance and Control Software Project Data - Volume 1: Planning Documents

The Guidance and Control Software (GCS) project was the last in a series of software reliability studies conducted at Langley Research Center between 1977 and 1994. The technical results of the GCS project were recorded after the experiment was completed. Some of the support documentation produced as part of the experiment, however, is serving an unexpected role far beyond its original project context. Some of the software used as part of the GCS project was developed to conform to the RTCA/DO-178B software standard, "Software Considerations in Airborne Systems and Equipment Certification," used in the civil aviation industry. That standard requires extensive documentation throughout the software development life cycle, including plans, software requirements, design and source code, verification cases and results, and configuration management and quality control data. The project documentation that includes this information is open for public scrutiny without the legal or safety implications associated with comparable data from an avionics manufacturer. This public availability has afforded an opportunity to use the GCS project documents for DO-178B training. This report provides a brief overview of the GCS project, describes the 4-volume set of documents and the role they are playing in training, and includes the planning documents from the GCS project. Volume 1 contains five appendices: A. Plan for Software Aspects of Certification for the Guidance and Control Software Project; B. Software Development Standards for the Guidance and Control Software Project; C. Software Verification Plan for the Guidance and Control Software Project; D. Software Configuration Management Plan for the Guidance and Control Software Project; and E. Software Quality Assurance Activities.

Hayhurst, Kelly J.

Supporting Exploration Missions by Enabling Exploration Mission System Software

Future exploration missions will consist of a multitude of data sources, systems, and operators collaborating to complete mission objectives. Presently, NASA is instantiating the contractual mechanisms, such as the xEVAS and HLS contracts, to produce these mission assets. Architectural planning is also underway to establish the networking protocols and infrastructure to digitally create and connect mission elements, such as LunaNET. However, without new horizontally integrated data systems, these advancements will be limited in their ability to get mission data appropriately integrated into the plan, train, fly, explore workflow of the operations workforce. Here we describe several mission system software development efforts underway that are designed to support human spaceflight missions. We describe the current iterations of a suite of tools to support EVA procedure authoring and execution, for both ISS and Artemis missions, as well as a software solution to establish and interact with mission context and data products. These tools have been developed iteratively and continue to be tested in several NASA facilities such as the Neutral Buoyancy Lab (NBL), Artemis field testing, and in present-day International Space Station (ISS) operations on orbit. Our solutions demonstrate how software development can be aligned with ongoing operations development activities to discover the features that best support future human spaceflight missions.

EVA Mission System Software

Supporting Exploration Missions by Enabling Exploration Mission System Software

Future exploration missions will consist of a multitude of data sources, systems, and operators collaborating to complete mission objectives. Presently, NASA is instantiating the contractual mechanisms, such as the Exploration Extravehicular Activity Services (xEVAS) and Human Landing System (HLS) contracts, to produce these mission assets. Architectural planning is also underway to establish the networking protocols and infrastructure to digitally create and connect mission elements, such as LunaNET. However, without new horizontally integrated data systems, these advancements will be limited in their ability to get mission data appropriately integrated into the plan, train, fly, explore workflow of the flight operations workforce. Here we describe several mission system software development efforts underway that are designed to support human spaceflight missions. This paper describes the current iterations of a suite of tools to support EVA procedure authoring and execution, and mission context creation for both International Space Station (ISS) and Artemis missions. These tools have been developed iteratively and continue to be used in present-day ISS operations on orbit and in several NASA facilities such as the Neutral Buoyancy Lab (NBL) and Artemis field testing. These solutions demonstrate how software development can be aligned with ongoing operations development activities to discover the features that best support both current and future human spaceflight missions.

Matthew J. Miller

Supporting Exploration Missions by Enabling Exploration Mission System Software

Future exploration missions will consist of a multitude of data sources, systems, and operators collaborating to complete mission objectives. Presently, NASA is instantiating the contractual mechanisms, such as the Exploration Extravehicular Activity Services (xEVAS) and Human Landing System (HLS) contracts, to produce these mission assets. Architectural planning is also underway to establish the networking protocols and infrastructure to digitally create and connect mission elements, such as LunaNET. However, without new horizontally integrated data systems, these advancements will be limited in their ability to get mission data appropriately integrated into the plan, train, fly, explore workflow of the flight operations workforce. Here we describe several mission system software development efforts underway that are designed to support human spaceflight missions. This paper describes the current iterations of a suite of tools to support EVA procedure authoring and execution, and mission context creation for both International Space Station (ISS) and Artemis missions. These tools have been developed iteratively and continue to be used in present-day ISS operations on orbit and in several NASA facilities such as the Neutral Buoyancy Lab (NBL) and Artemis field testing. These solutions demonstrate how software development can be aligned with ongoing operations development activities to discover the features that best support both current and future human spaceflight missions.

Matthew Miller

Constellation Training Facility Support

The National Aeronautics and Space Administration is developing the next set of vehicles that will take men back to the moon under the Constellation Program. The Constellation Training Facility (CxTF) is a project in development that will be used to train astronauts, instructors, and flight controllers on the operation of Constellation Program vehicles. It will also be used for procedure verification and validation of flight software and console tools. The CxTF will have simulations for the Crew Exploration Vehicle (CEV), Crew Module (CM), CEV Service Module (SM), Launch Abort System (LAS), Spacecraft Adapter (SA), Crew Launch Vehicle (CLV), Pressurized Cargo Variant CM, Pressurized Cargo Variant SM, Cargo Launch Vehicle, Earth Departure Stage (EDS), and the Lunar Surface Access Module (LSAM). The Facility will consist of part-task and full-task trainers, each with a specific set of mission training capabilities. Part task trainers will be used for focused training on a single vehicle system or set of related systems. Full task trainers will be used for training on complete vehicles and all of its subsystems. Support was provided in both software development and project planning areas of the CxTF project. Simulation software was developed for the hydraulic system of the Thrust Vector Control (TVC) of the ARES I launch vehicle. The TVC system is in charge of the actuation of the nozzle gimbals for navigation control of the upper stage of the ARES I rocket. Also, software was developed using C standards to send and receive data to and from hand controllers to be used in CxTF cockpit simulations. The hand controllers provided movement in all six rotational and translational axes. Under Project Planning & Control, support was provided to the development and maintenance of integrated schedules for both the Constellation Training Facility and Missions Operations Facilities Division. These schedules maintain communication between projects in different levels. The CxTF support provided is one that requires continuous maintenance since the project is still on initial development phases.

Flores, Jose M.

A systems approach to computer-based training

This paper describes the hardware and software systems approach used in the Automated Recertification Training System (ARTS), a Phase 2 Small Business Innovation Research (SBIR) project for NASA Kennedy Space Center (KSC). The goal of this project is to optimize recertification training of technicians who process the Space Shuttle before launch by providing computer-based training courseware. The objectives of ARTS are to implement more effective CBT applications identified through a need assessment process and to provide an ehanced courseware production system. The system's capabilities are demonstrated by using five different pilot applications to convert existing classroom courses into interactive courseware. When the system is fully implemented at NASA/KSC, trainee job performance will improve and the cost of courseware development will be lower. Commercialization of the technology developed as part of this SBIR project is planned for Phase 3. Anticipated spin-off products include custom courseware for technical skills training and courseware production software for use by corporate training organizations of aerospace and other industrial companies.

Drape, Gaylen W.

Advanced life support study. Modification 10: ECLSS logistical support analysis for Space Station Freedom

This addendum to the final report provides a description of the work performed under the subject contract. This report describes the work that was performed by SRS Technologies from Jan. 1992 - Jan. 1993. The work that was performed included the following: (1) a study of the Space Station Freedom (SSF) Preliminary Design Review (PDR) data package and an identification of the maintenance concept, structure, implementation plans, training plan, and the LSAR approach; development of a working ability with the ALSTAR and DATA Express software; (3) a review of the SSF maintenance concept; and (4) an update of the ALSTAR data base.

Source record

Conducting Feasibility Studies in a Virtual World: Lessons Learned and Emerging Best Practices from the NASA DEVELOP Program

In response to new workplace realities, the NASA DEVELOP National Program pivoted from co-locating students, emerging professionals, and science advisors to bringing together virtual teams from across the United States. In its spring 2020 term, rapidly evolving circumstances required an ad-hoc roll-out of a virtual approach to complete the spring projects. Based on the experience from the spring term and a few weeks of planning, DEVELOP then conducted a fully virtual summer term with features such as 1) online collaboration tools, 2) virtual machines for analysis, and 3) streamed training offerings, including DEVELOP’s first ever program-wide Software Carpentry workshop. This full term of bringing together remote actors to select, build, and manage teams brought many challenges. Summer feedback has influenced planning for the fall 2020 term and process improvement is ongoing. This presentation will highlight lessons learned throughout this period of rapid change. Feedback from spring and summer terms and the Software Carpentry workshop will be summarized. Beyond participant impacts, there will also be discussion of effects on project results and partner experience. Final takeaways will focus on best practices that have been distilled for virtually-conducted feasibility studies.

NASA DEVELOP

Online Learning Flight Control for Intelligent Flight Control Systems (IFCS)

The research accomplishments for the cooperative agreement 'Online Learning Flight Control for Intelligent Flight Control Systems (IFCS)' include the following: (1) previous IFC program data collection and analysis; (2) IFC program support site (configured IFC systems support network, configured Tornado/VxWorks OS development system, made Configuration and Documentation Management Systems Internet accessible); (3) Airborne Research Test Systems (ARTS) II Hardware (developed hardware requirements specification, developing environmental testing requirements, hardware design, and hardware design development); (4) ARTS II software development laboratory unit (procurement of lab style hardware, configured lab style hardware, and designed interface module equivalent to ARTS II faceplate); (5) program support documentation (developed software development plan, configuration management plan, and software verification and validation plan); (6) LWR algorithm analysis (performed timing and profiling on algorithm); (7) pre-trained neural network analysis; (8) Dynamic Cell Structures (DCS) Neural Network Analysis (performing timing and profiling on algorithm); and (9) conducted technical interchange and quarterly meetings to define IFC research goals.

Niewoehner, Kevin R.