Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “corrective action 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 127 records · Page 7
All sourcesNASA NTRSDOE OSTI
NASA NTRS1988

Requirements for significant problem reporting and trend analysis

This handbook supplements policies, requirements, and procedures of NMI 8070.3 to ensure that NASA management at each organizational level is: fully aware of trends affecting both the level of safety and the potential for mission success established for both NASA manned space programs and its supporting institutions; fully and independently informed of problems that represent significant risk to the safety of all personnel (including the general populace) and to the success of a mission or operation through a program mechanism herein defined as Significant Problem Reporting; and in full agreement with the level of elimination of these problems through the closed-loop accounting of corrective actions. The requirements of this handbook are supportive of the agency's safety, reliability, maintainability, and quality assurance (SRM&QA) program objectives and are applicable to all organizational elements of NASA connected with or supporting developmental or operational manned space program/projects (including associated payloads) and the related institutional facilities.

George A Rodney↗
NASA NTRS1993

Management of government quality assurance functions for NASA contracts

This handbook sets forth requirements for NASA direction and management of government quality assurance functions performed for NASA contracts and is applicable to all NASA installations. These requirements will standardize management to provide the minimum oversight and effective use of resources. This handbook implements Federal Acquisition Regulation (FAR) Part 46, NASA FAR Supplement 18-46, Quality Assurance, and NMI 7410.1. Achievement of established quality and reliability goals at all levels is essential to the success of NASA programs. Active participation by NASA and other agency quality assurance personnel in all phases of contract operations, including precontract activity, will assist in the economic and timely achievement of program results. This involves broad participation in design, development, procurement, inspection, testing, and preventive and corrective actions. Consequently, government, as well as industry, must place strong emphasis on the accomplishment of all functions having a significant bearing on quality and reliability from program initiation through end-use of supplies and services produced. For purposes of implementing NASA and other agency agreements, and to provide for uniformity and consistency, the terminology and definitions prescribed herein and in a future handbook shall be utilized for all NASA quality assurance delegations and subsequent redelegations.

Source record↗
NASA NTRS2003

A Predictive Safety Management System Software Package Based on the Continuous Hazard Tracking and Failure Prediction Methodology

The goal of this research was to integrate a previously validated and reliable safety model, called Continuous Hazard Tracking and Failure Prediction Methodology (CHTFPM), into a software application. This led to the development of a safety management information system (PSMIS). This means that the theory or principles of the CHTFPM were incorporated in a software package; hence, the PSMIS is referred to as CHTFPM management information system (CHTFPM MIS). The purpose of the PSMIS is to reduce the time and manpower required to perform predictive studies as well as to facilitate the handling of enormous quantities of information in this type of studies. The CHTFPM theory encompasses the philosophy of looking at the concept of safety engineering from a new perspective: from a proactive, than a reactive, viewpoint. That is, corrective measures are taken before a problem instead of after it happened. That is why the CHTFPM is a predictive safety because it foresees or anticipates accidents, system failures and unacceptable risks; therefore, corrective action can be taken in order to prevent all these unwanted issues. Consequently, safety and reliability of systems or processes can be further improved by taking proactive and timely corrective actions.

Quintana, Rolando↗
NASA NTRS1987

A 1987 overview of free-piston Stirling technology for space power application

An overview is presented of the NASA Lewis Research Center free-piston Stirling engine activities directed toward space-power application. NASA Lewis serves as the project office to manage the newly initiated NASA SP-100 Advanced Technology Program. One of the major elements of this five-year program is the development of advanced power conversion concepts of which the Stirling cycle is a viable growth candidate. Under this program the status of the 25 kWe opposed-piston Space Power Demonstrator Engine (SPDE) is presented. Included in the SPDE discussion are comparisons between predicted and experimental engine performance, enhanced performance resulting from regenerator modification, increased operating stroke brought about by isolating the gas bearing flow between the displacer and power piston, identifying excessive energy losses and recommending corrective action, and a better understanding of linear alternator design and operation. Technology work is also conducted on heat exchanger concepts, both design and fabrication. Design parameters and conceptual design features are also presented for a 25 kWe, single-cylinder free-piston Stirling space-power converter.

Slaby, Jack G.↗
NASA NTRS2011

The Necessity of Functional Analysis for Space Exploration Programs

As NASA moves toward expanded commercial spaceflight within its human exploration capability, there is increased emphasis on how to allocate responsibilities between government and commercial organizations to achieve coordinated program objectives. The practice of program-level functional analysis offers an opportunity for improved understanding of collaborative functions among heterogeneous partners. Functional analysis is contrasted with the physical analysis more commonly done at the program level, and is shown to provide theoretical performance, risk, and safety advantages beneficial to a government-commercial partnership. Performance advantages include faster convergence to acceptable system solutions; discovery of superior solutions with higher commonality, greater simplicity and greater parallelism by substituting functional for physical redundancy to achieve robustness and safety goals; and greater organizational cohesion around program objectives. Risk advantages include avoidance of rework by revelation of some kinds of architectural and contractual mismatches before systems are specified, designed, constructed, or integrated; avoidance of cost and schedule growth by more complete and precise specifications of cost and schedule estimates; and higher likelihood of successful integration on the first try. Safety advantages include effective delineation of must-work and must-not-work functions for integrated hazard analysis, the ability to formally demonstrate completeness of safety analyses, and provably correct logic for certification of flight readiness. The key mechanism for realizing these benefits is the development of an inter-functional architecture at the program level, which reveals relationships between top-level system requirements that would otherwise be invisible using only a physical architecture. This paper describes the advantages and pitfalls of functional analysis as a means of coordinating the actions of large heterogeneous organizations for space exploration programs.

program management↗
NASA NTRS2015

Methodology to Define Delivery Accuracy Under Current Day ATC Operations

In order to enable arrival management concepts and solutions in a NextGen environment, ground- based sequencing and scheduling functions have been developed to support metering operations in the National Airspace System. These sequencing and scheduling algorithms as well as tools are designed to aid air traffic controllers in developing an overall arrival strategy. The ground systems being developed will support the management of aircraft to their Scheduled Times of Arrival (STAs) at flow-constrained meter points. This paper presents a methodology for determining the undelayed delivery accuracy for current day air traffic control operations. This new method analyzes the undelayed delivery accuracy at meter points in order to understand changes of desired flow rates as well as enabling definition of metrics that will allow near-future ground automation tools to successfully achieve desired separation at the meter points. This enables aircraft to meet their STAs while performing high precision arrivals. The research presents a possible implementation that would allow delivery performance of current tools to be estimated and delivery accuracy requirements for future tools to be defined, which allows analysis of Estimated Time of Arrival (ETA) accuracy for Time-Based Flow Management (TBFM) and the FAA's Traffic Management Advisor (TMA). TMA is a deployed system that generates scheduled time-of-arrival constraints for en- route air traffic controllers in the US. This new method of automated analysis provides a repeatable evaluation of the delay metrics for current day traffic, new releases of TMA, implementation of different tools, and across different airspace environments. This method utilizes a wide set of data from the Operational TMA-TBFM Repository (OTTR) system, which processes raw data collected by the FAA from operational TMA systems at all ARTCCs in the nation. The OTTR system generates daily reports concerning ATC status, intent and actions. Due to its availability, ease of use, and vast collection of data across several airspaces it was determined that the OTTR data set would be the best method to utilize moving forward with this analysis. The particular variables needed for further analysis were determined along with the necessary OTTR reports, by working closely with the repository team additional analysis reports were developed that provided key ETA and STA information at the freeze horizon. One major benefit of the OTTR data is that using the correct reports the data across several airports could be analyzed over large periods of time. The OTTR data processes the TBFM data daily and is stored in various formats across several airspaces. This allowed us to develop our own parsing methods and raw data processing that would not rely on other computationally expensive tools that perform more in depth analysis of similar sets of data. The majority of this work consisted of the development of the ability to filter flights to create a subset of flights that could be considered undelayed, which is defined as a flight at the freeze horizon with an ETA and STA difference that was minimal or close to zero. This was a broad method that allowed the consideration of a large data set which consisted of all the traffic across a two month period in 2013, the hottest and coldest months, arriving into four airports: George Bush Intercontinental, Denver International, Los Angeles International, and Phoenix Sky Harbor.

delivery accuracy↗
NASA NTRS2007

Engineering and Safety Partnership Enhances Safety of the Space Shuttle Program (SSP)

Project Management must use the risk assessment documents (RADs) as tools to support their decision making process. Therefore, these documents have to be initiated, developed, and evolved parallel to the life of the project. Technical preparation and safety compliance of these documents require a great deal of resources. Updating these documents after-the-fact not only requires substantial increase in resources - Project Cost -, but this task is also not useful and perhaps an unnecessary expense. Hazard Reports (HRs), Failure Modes and Effects Analysis (FMEAs), Critical Item Lists (CILs), Risk Management process are, among others, within this category. A positive action resulting from a strong partnership between interested parties is one way to get these documents and related processes and requirements, released and updated in useful time. The Space Shuttle Program (SSP) at the Marshall Space Flight Center has implemented a process which is having positive results and gaining acceptance within the Agency. A hybrid Panel, with equal interest and responsibilities for the two larger organizations, Safety and Engineering, is the focal point of this process. Called the Marshall Safety and Engineering Review Panel (MSERP), its charter (Space Shuttle Program Directive 110 F, April 15, 2005), and its Operating Control Plan emphasizes the technical and safety responsibilities over the program risk documents: HRs; FMEA/CILs; Engineering Changes; anomalies/problem resolutions and corrective action implementations, and trend analysis. The MSERP has undertaken its responsibilities with objectivity, assertiveness, dedication, has operated with focus, and has shown significant results and promising perspectives. The MSERP has been deeply involved in propulsion systems and integration, real time technical issues and other relevant reviews, since its conception. These activities have transformed the propulsion MSERP in a truly participative and value added panel, making a difference for the safety of the Space Shuttle Vehicle, its crew, and personnel. Because of the MSERP's valuable contribution to the assessment of safety risk for the SSP, this paper also proposes an enhanced Panel concept that takes this successful partnership concept to a higher level of 'true partnership'. The proposed panel is aimed to be responsible for the review and assessment of all risk relative to Safety for new and future aerospace and related programs.

Duarte, Alberto↗
NASA NTRS2015

The SMART-NAS Testbed

The SMART-NAS Testbed for Safe Trajectory Based Operations Project will deliver an evaluation capability, critical to the ATM community, allowing full NextGen and beyond-NextGen concepts to be assessed and developed. To meet this objective a strong focus will be placed on concept integration and validation to enable a gate-to-gate trajectory-based system capability that satisfies a full vision for NextGen. The SMART-NAS for Safe TBO Project consists of six sub-projects. Three of the sub-projects are focused on exploring and developing technologies, concepts and models for evolving and transforming air traffic management operations in the ATM+2 time horizon, while the remaining three sub-projects are focused on developing the tools and capabilities needed for testing these advanced concepts. Function Allocation, Networked Air Traffic Management and Trajectory Based Operations are developing concepts and models. SMART-NAS Test-bed, System Assurance Technologies and Real-time Safety Modeling are developing the tools and capabilities to test these concepts. Simulation and modeling capabilities will include the ability to assess multiple operational scenarios of the national airspace system, accept data feeds, allowing shadowing of actual operations in either real-time, fast-time and/or hybrid modes of operations in distributed environments, and enable integrated examinations of concepts, algorithms, technologies, and NAS architectures. An important focus within this project is to enable the development of a real-time, system-wide safety assurance system. The basis of such a system is a continuum of information acquisition, analysis, and assessment that enables awareness and corrective action to detect and mitigate potential threats to continuous system-wide safety at all levels. This process, which currently can only be done post operations, will be driven towards "real-time" assessments in the 2035 time frame.

Trajectory Based Operations↗
NASA NTRS1986

Report of the Presidential Commission on the Space Shuttle Challenger Accident, Volume 1

The findings of the Commission regarding the circumstances surrounding the Challenger accident are reported and recommendations for corrective action are outlined. All available mission data, subsequent tests, and wreckage analyses were reviewed and specific failure scenarios were developed. The Commission concluded that the cause of the Mission 51-L accident was the failure of the pressure seal in the aft field joint of the right solid rocket motor. The failure was due to a faulty design unacceptably sensitive to a number of factors. These factors were the effects of temperature, physical dimensions, the character of materials, the effects of reuse, processing, and the reaction of the joint to dynamic loading. In addition to analyzing the material causes of the accident, the Commission examined the chain of decisions that culminated in approval of the launch. It concluded that the decision making process was flawed in several ways including (1) failure in communication resulting in a launch decision based on incomplete and misleading information, (2) a conflict between engineering data and management judgements, and (3) a NASA management structure that permitted flight safety problems to bypass key Shuttle managers.

Rogers, W. P.↗
NASA NTRS2013

Earth Observation from Space - The Issue of Environmental Sustainability

Remote sensing scientists work under assumptions that should not be taken for granted and should, therefore, be challenged. These assumptions include the following: 1. Space, especially Low Earth Orbit (LEO), will always be available to governmental and commercial space entities that launch Earth remote sensing missions. 2. Space launches are benign with respect to environmental impacts. 3. Minimization of Type 1 error, which provides increased confidence in the experimental outcome, is the best way to assess the significance of environmental change. 4. Large-area remote sensing investigations, i.e. national, continental, global studies, are best done from space. 5. National space missions should trump international, cooperative space missions to ensure national control and distribution of the data products. At best, all of these points are arguable, and in some cases, they're wrong. Development of observational space systems that are compatible with sustainability principles should be a primary concern when Earth remote sensing space systems are envisioned, designed, and launched. The discussion is based on the hypothesis that reducing the environmental impacts of thedata acquisition step,which is at the very beginning of the information streamleading to decision and action, will enhance coherence in the information streamand strengthen the capacity of measurement processes to meet their stated functional goal, i.e. sustainable management of Earth resources. We suggest that unconventional points of view should be adopted and when appropriate, remedial measures considered that could help to reduce the environmental footprint of space remote sensing and of Earth observation and monitoring systems in general. This article discusses these five assumptions inthe contextof sustainablemanagementof Earth's resources. Takingeachassumptioninturn,we find the following: (1) Space debris may limit access to Low Earth Orbit over the next decades. (2) Relatively speaking, given that they're rare event, space launches may be benign, but study is merited on upper stratospheric and exospheric layers given the chemical activity associated with rocket combustion by-products. (3) Minimization of Type II error should be considered in situations where minimization of Type I error greatly hampers or precludes our ability to correct the environmental condition being studied. (4) In certain situations, airborne collects may be less expensive and more environmentally benign, and comparative studies should be done to determine which path is wisest. (5) International cooperation and data sharing will reduce instrument and launch costs and mission redundancy. Given fiscal concerns of most of the major space agencies e e.g. NASA, ESA, CNES e it seems prudent to combine resources.

Earth observation systems↗
NASA NTRS1994

Citrate and renal calculi: an update

Citrate is an inhibitor of the crystallization of stone-forming calcium salts. Hypocitraturia, frequently encountered in patients with nephrolithiasis, is therefore an important risk factor for stone formation. Potassium citrate provides physiological and physicochemical correction and inhibits new stone formation, not only in hypocitraturic calcium nephrolithiasis but also in uric acid nephrolithiasis. Inhibition of stone recurrence has now been validated by a randomized trial. Ongoing research has disclosed additional causes of hypocitraturia (sodium excess, low intestinal alkali absorption, but not primary citrate malabsorption). Moreover, new insights on potassium citrate action have been shown, notably that some of absorbed citrate escapes oxidation and contributes to the citraturic response, that ingestion with a meal does not sacrifice physiological or physicochemical action, that orange juice mimics but does not completely duplicate its actions, that potassium citrate may have a beneficial bone-sparing effect, that it may reduce stone fragments following ESWL, and that danger of aluminum toxicity is not great in subjects with functioning kidneys. Finally, the research on potassium citrate has led to two promising products, calcium citrate as an optimum calcium supplement and potassium-magnesium citrate which may be superior to potassium citrate in the management of stone disease.

NASA Discipline Regulatory Physiology↗
NASA NTRS1997

Analysis, Repair, and Management of the Total Ozone Mapping Spectrometer Database

In the ensuing period we were able to demonstrate that the origin of these filamentous patterns resulted from the action of synoptic-scale vortical velocity field on the global-scale background gradient of ozone concentration in the meridional direction. Hyperbolic flow patterns between long-lived atmospheric vortices bring together air parcels from different latitudes, thus creating large gradients along the separatrices leaving the hyperbolic (stagnation) point. This result is further confirmed by the KL analysis of the ozone field in the equatorial region, where the background concentration gradient vanishes. The spectral slope in this region has been found to lie close to -1, in agreement with Batchelor's prediction. Another outcome of this result is that it at least provides indirect evidence about the kinetic energy spectrum of the atmospheric turbulence in the range of scales approximately 200 to 2000 km. Namely, Batchelor's analysis is based on the assumption that the velocity field is large-scale, that is the kinetic energy spectrum decays as O(k(sup -3)) or steeper. Since the scalar spectrum is confirmed, this also supports this form of the kinetic energy spectrum. The study of equatorial regions of TOMS data revealed the efficiency of the KL method is in detecting and separating a wave-like measurement artifact inherently present in the dataset due to the non-perfect correction for cross-track bias. Just two to three eigenfunctions represent the error, which makes it possible to enhance the data by reconstituting it from the data by eliminating the subspace of artifactual eigenfunctions. This represents a highly efficient means for achieving an improved rendering of the data. This has been implemented on the database. A wide range of techniques and algorithms have been developed for the repair and extension of the TOMS database.

Sirovich, Lawrence↗
NASA NTRS2016

Topic Modeling of NASA Space System Problem Reports: Research in Practice

Problem reports at NASA are similar to bug reports: they capture defects found during test, post-launch operational anomalies, and document the investigation and corrective action of the issue. These artifacts are a rich source of lessons learned for NASA, but are expensive to analyze since problem reports are comprised primarily of natural language text. We apply topic modeling to a corpus of NASA problem reports to extract trends in testing and operational failures. We collected 16,669 problem reports from six NASA space flight missions and applied Latent Dirichlet Allocation topic modeling to the document corpus. We analyze the most popular topics within and across missions, and how popular topics changed over the lifetime of a mission. We find that hardware material and flight software issues are common during the integration and testing phase, while ground station software and equipment issues are more common during the operations phase. We identify a number of challenges in topic modeling for trend analysis: 1) that the process of selecting the topic modeling parameters lacks definitive guidance, 2) defining semantically-meaningful topic labels requires nontrivial effort and domain expertise, 3) topic models derived from the combined corpus of the six missions were biased toward the larger missions, and 4) topics must be semantically distinct as well as cohesive to be useful. Nonetheless,topic modeling can identify problem themes within missions and across mission lifetimes, providing useful feedback to engineers and project managers.

Data Mining↗
NASA NTRS1994

General purpose architecture for intelligent computer-aided training

An intelligent computer-aided training system having a general modular architecture is provided for use in a wide variety of training tasks and environments. It is comprised of a user interface which permits the trainee to access the same information available in the task environment and serves as a means for the trainee to assert actions to the system; a domain expert which is sufficiently intelligent to use the same information available to the trainee and carry out the task assigned to the trainee; a training session manager for examining the assertions made by the domain expert and by the trainee for evaluating such trainee assertions and providing guidance to the trainee which are appropriate to his acquired skill level; a trainee model which contains a history of the trainee interactions with the system together with summary evaluative data; an intelligent training scenario generator for designing increasingly complex training exercises based on the current skill level contained in the trainee model and on any weaknesses or deficiencies that the trainee has exhibited in previous interactions; and a blackboard that provides a common fact base for communication between the other components of the system. Preferably, the domain expert contains a list of 'mal-rules' which typifies errors that are usually made by novice trainees. Also preferably, the training session manager comprises an intelligent error detection means and an intelligent error handling means. The present invention utilizes a rule-based language having a control structure whereby a specific message passing protocol is utilized with respect to tasks which are procedural or step-by-step in structure. The rules can be activated by the trainee in any order to reach the solution by any valid or correct path.

Loftin, R. Bowen↗
NASA NTRS2023

Paint and Oil Locker, SWMU 067 Southern Treatment Area Air Sparge System Construction Completion and Performance Monitoring and Paint and Oil Locker, Northern Area (SWMU 067) and Supply Warehouse #3, SWMU 088 Long-Term Monitoring Report Kennedy Space Center, Florida

This Air Sparge (AS) System Construction Completion, Performance Monitoring, and Long-Term Monitoring (LTM) Report presents activities conducted at the Paint and Oil Locker (POL) (Solid Waste Management Unit [SWMU] 067) and Supply Warehouse #3 (SW3) (SWMU 088) sites located at the Kennedy Space Center (KSC), Florida. Activities include implementation and Year 1 (Quarters [Q] 1 through 4) and Q5 operation, maintenance, and monitoring (OM&M) activities and performance monitoring results for the AS Interim Measure (IM) in the POL Southern Treatment Area, LTM results for the POL Northern Area and SW3, and supplemental direct push technology (DPT) sampling at both sites to support the LTM and performance monitoring programs. The timeframe for activities included in this report extends from August 2019 to August 2022. The scope for these sites currently includes two main components, which are documented within this report: (1) LTM at SW3 and POL Northern Area where an AS system began operation at these sites in May 2009 and June 2013, respectively, and subsequently turned off for both sites in March 2018 (during the previous reporting period); and (2) Active AS operations and performance monitoring in the POL Southern Treatment Area where an AS system was installed and began operation in 2021. The AS IM in the POL Southern Treatment Area was implemented between 2019 and 2021 to treat a chlorinated solvent groundwater plume that resulted from historic operations supporting the National Aeronautics and Space Administration’s (NASA) Space Program. The objective of the AS IM is to remediate groundwater within the treatment zone to support transition to monitored natural attenuation (MNA). The overall Corrective Action objective is to reduce concentrations of trichloroethene (TCE), cis-1,2-dichloroethene (cDCE), trans-1,2- dichloroethene (tDCE), and vinyl chloride (VC) present in groundwater to levels below their respective State of Florida Groundwater Cleanup Target Levels (GCTLs). The AS IM was installed in the POL Southern Treatment Area to target the high concentration plume (HCP), which includes a source zone (SZ) area where TCE was found to exceed 11,000 micrograms per liter (µg/L), and extend to a depth of 30 feet below land surface (bls).

TCE↗
NASA NTRS2006

Fault Management Techniques in Human Spaceflight Operations

This paper discusses human spaceflight fault management operations. Fault detection and response capabilities available in current US human spaceflight programs Space Shuttle and International Space Station are described while emphasizing system design impacts on operational techniques and constraints. Preflight and inflight processes along with products used to anticipate, mitigate and respond to failures are introduced. Examples of operational products used to support failure responses are presented. Possible improvements in the state of the art, as well as prioritization and success criteria for their implementation are proposed. This paper describes how the architecture of a command and control system impacts operations in areas such as the required fault response times, automated vs. manual fault responses, use of workarounds, etc. The architecture includes the use of redundancy at the system and software function level, software capabilities, use of intelligent or autonomous systems, number and severity of software defects, etc. This in turn drives which Caution and Warning (C&W) events should be annunciated, C&W event classification, operator display designs, crew training, flight control team training, and procedure development. Other factors impacting operations are the complexity of a system, skills needed to understand and operate a system, and the use of commonality vs. optimized solutions for software and responses. Fault detection, annunciation, safing responses, and recovery capabilities are explored using real examples to uncover underlying philosophies and constraints. These factors directly impact operations in that the crew and flight control team need to understand what happened, why it happened, what the system is doing, and what, if any, corrective actions they need to perform. If a fault results in multiple C&W events, or if several faults occur simultaneously, the root cause(s) of the fault(s), as well as their vehicle-wide impacts, must be determined in order to maintain situational awareness. This allows both automated and manual recovery operations to focus on the real cause of the fault(s). An appropriate balance must be struck between correcting the root cause failure and addressing the impacts of that fault on other vehicle components. Lastly, this paper presents a strategy for using lessons learned to improve the software, displays, and procedures in addition to determining what is a candidate for automation. Enabling technologies and techniques are identified to promote system evolution from one that requires manual fault responses to one that uses automation and autonomy where they are most effective. These considerations include the value in correcting software defects in a timely manner, automation of repetitive tasks, making time critical responses autonomous, etc. The paper recommends the appropriate use of intelligent systems to determine the root causes of faults and correctly identify separate unrelated faults.

O'Hagan, Brian↗
NASA NTRS2008

Problem Reporting System

The Problem Reporting System (PRS) is a Web application, running on two Web servers (load-balanced) and two database servers (RAID-5), which establishes a system for submission, editing, and sharing of reports to manage risk assessment of anomalies identified in NASA's flight projects. PRS consolidates diverse anomaly-reporting systems, maintains a rich database set, and incorporates a robust engine, which allows tracking of any hardware, software, or paper process by configuring an appropriate life cycle. Global and specific project administration and setup tools allow lifecycle tailoring, along with customizable controls for user, e-mail, notifications, and more. PRS is accessible via the World Wide Web for authorized user at most any location. Upon successful log-in, the user receives a customizable window, which displays time-critical 'To Do' items (anomalies requiring the user s input before the system moves the anomaly to the next phase of the lifecycle), anomalies originated by the user, anomalies the user has addressed, and custom queries that can be saved for future use. Access controls exist depending on a user's role as system administrator, project administrator, user, or developer, and then, further by association with user, project, subsystem, company, or item with provisions for business-to-business exclusions, limitations on access according to the covert or overt nature of a given project, all with multiple layers of filtration, as needed. Reporting of metrics is built in. There is a provision for proxy access (in which the user may choose to grant one or more other users to view screens and perform actions as though they were the user, during any part of a tracking life cycle - especially useful during tight build schedules and vacations to keep things moving). The system also provides users the ability to have an anomaly link to or notify other systems, including QA Inspection Reports, Safety, GIDEP (Government-Industry Data Exchange Program) Alert, Corrective Actions, and Lessons Learned. The PRS tracking engine was designed as a very extensible and scalable system, able to support additional applications, with future development possibilities already discussed, including Incident Surprise Anomalies (for anomalies occurring during Operations phases of NASA Flight projects), GIDEP and NASA Alerts, and others.

Potter, Don↗
NASA NTRS2010

Model for Simulating a Spiral Software-Development Process

A discrete-event simulation model, and a computer program that implements the model, have been developed as means of analyzing a spiral software-development process. This model can be tailored to specific development environments for use by software project managers in making quantitative cases for deciding among different software-development processes, courses of action, and cost estimates. A spiral process can be contrasted with a waterfall process, which is a traditional process that consists of a sequence of activities that include analysis of requirements, design, coding, testing, and support. A spiral process is an iterative process that can be regarded as a repeating modified waterfall process. Each iteration includes assessment of risk, analysis of requirements, design, coding, testing, delivery, and evaluation. A key difference between a spiral and a waterfall process is that a spiral process can accommodate changes in requirements at each iteration, whereas in a waterfall process, requirements are considered to be fixed from the beginning and, therefore, a waterfall process is not flexible enough for some projects, especially those in which requirements are not known at the beginning or may change during development. For a given project, a spiral process may cost more and take more time than does a waterfall process, but may better satisfy a customer's expectations and needs. Models for simulating various waterfall processes have been developed previously, but until now, there have been no models for simulating spiral processes. The present spiral-process-simulating model and the software that implements it were developed by extending a discrete-event simulation process model of the IEEE 12207 Software Development Process, which was built using commercially available software known as the Process Analysis Tradeoff Tool (PATT). Typical inputs to PATT models include industry-average values of product size (expressed as number of lines of code), productivity (number of lines of code per hour), and number of defects per source line of code. The user provides the number of resources, the overall percent of effort that should be allocated to each process step, and the number of desired staff members for each step. The output of PATT includes the size of the product, a measure of effort, a measure of rework effort, the duration of the entire process, and the numbers of injected, detected, and corrected defects as well as a number of other interesting features. In the development of the present model, steps were added to the IEEE 12207 waterfall process, and this model and its implementing software were made to run repeatedly through the sequence of steps, each repetition representing an iteration in a spiral process. Because the IEEE 12207 model is founded on a waterfall paradigm, it enables direct comparison of spiral and waterfall processes. The model can be used throughout a software-development project to analyze the project as more information becomes available. For instance, data from early iterations can be used as inputs to the model, and the model can be used to estimate the time and cost of carrying the project to completion.

Mizell, Carolyn↗