[NASA Logo]

NASA Procedures and Guidelines

This Document is Obsolete and Is No Longer Used.
Check the NODIS Library to access the current version:
http://nodis3.gsfc.nasa.gov


NPR 8621.1
Eff. Date: June 02, 2000
Cancellation Date: February 11, 2004

NASA Procedures and Guidelines for Mishap Reporting, Investigating, and Recordkeeping

| TOC | ChangeHistory | Preface | Chp1 | Chp2 | Chp3 | Chp4 | Chp5 | Chp6 | All-Appendices | AppdxA | AppdxB-All | AppdxB1 | AppdxB2 | AppdxB3 | AppdxB4 | AppdxC | AppdxD | AppdxE-All | AppdxE1 | AppdxE2 | AppdxF-All | AppdxF1 | AppdxF2 | AppdxF3 | AppdxG | AppdxH-All | AppdxH1 | AppdxH2 | AppdxH21 | AppdxH3 | AppdxH4 | AppdxH5 | AppdxH6 | AppdxH7 | AppdxI-All | AppdxI1 | AppdxI2 | AppdxI3-All | AppdxI31 | AppdxI32 | AppdxI33 | AppdxI34 | AppdxI35 | AppdxJ-All | AppdxJ1 | AppdxJ2 | AppdxJ3 | AppdxJ4 | AppdxJ5 | AppdxJ6 | AppdxJ7 | AppdxJ8 | AppdxJ9 | AppdxJ10 | AppdxJ11 | AppdxK | AppdxL | AppdxM | Cover | ALL |


Appendix I-3.4. Change Analysis
A change analysis examines the potential effects of modifications from a starting point or baseline. The change analysis systematically hypothesizes worst-case effects from each modification from that baseline.

1.1 Method

1.1.1 Using the existing known system as a baseline, the investigator should examine the nature of all contemplated or real changes, and analyze the probable effect of each change (singly) and all changes (collectively) upon system risks. The process often requires the use of a walk-down, the method of physically examining the system or facility to identify the current configuration.

1.1.2 Alternatively, a change analysis could be initiated on an existing facility by comparing "as designed" with the "as built" configurations. In order to accomplish this, there would first be the need to physically identify the differences from the "as designed" configuration.

1.1.3 In either case, an exhaustive evaluation of the modifications or changes would be made and tabulated. Then the likely worst-case effects of each of those changes from the baseline are postulated. Finally, the combined effects are developed, the change in risk developed, and the overall results are reported. The process is graphically shown in Figure I-3.4-1 below.
 
                                                                            1. Identify the system baseline
                                                                            2. Identify changes - Walk-down
                                                                            3. Examine each baseline change by postulating effects
                                                                            4. Postulate collective/interactive effects
                                                                            5. Conclude system risk or deviation from baseline risk
                                                                            6. Report findings

Figure I-3.4-1. Actions for Change Analysis

1.1.4 Although originally conceived for management system applications, change analysis has come to be applied to systems of all kinds. It can only be applied, of course, if system design change or actual alteration has occurred or is contemplated. It is well applied as a means of optimizing the selection of a preferred change from among several candidate changes, or in aiding the design of a needed change. The technique can be applied meaningfully only to a system for which baseline risk has been established (e.g., as a result of prior analysis).

1.2 Thoroughness

Thoroughness is constrained only by the depth/detail in performing the analysis. Thoroughness required to analyze a given change is governed by the extent of the change itself. Effectiveness cannot exceed that of prior analyses used in establishing the baseline risk. Understanding of the physical principles governing the behavior of the system being changed is essential, in order that the effects of the change can be determined with confidence adequate to the purposes of the analysis. Assuming that the complexity of the changes does not appreciably exceed that of the system prior to alteration, mastery of the baseline analytical technique becomes sufficient.

1.3 Comments
Difficulty is determined largely by the extent to which the system had undergone (or will undergo) change, in combination with system baseline complexity. Identification of any existing configuration management documentation may reduce the time and effort involved with the change analysis process. The chief advantage of the technique lies in its "shortcut" approach, i.e., only the effects of changes need be analyzed, rather than the system as a whole. In this advantage also lies the technique's chief shortcoming, i.e., the presumption that the baseline analyses have been carried out adequately.




| TOC | ChangeHistory | Preface | Chp1 | Chp2 | Chp3 | Chp4 | Chp5 | Chp6 | All-Appendices | AppdxA | AppdxB-All | AppdxB1 | AppdxB2 | AppdxB3 | AppdxB4 | AppdxC | AppdxD | AppdxE-All | AppdxE1 | AppdxE2 | AppdxF-All | AppdxF1 | AppdxF2 | AppdxF3 | AppdxG | AppdxH-All | AppdxH1 | AppdxH2 | AppdxH21 | AppdxH3 | AppdxH4 | AppdxH5 | AppdxH6 | AppdxH7 | AppdxI-All | AppdxI1 | AppdxI2 | AppdxI3-All | AppdxI31 | AppdxI32 | AppdxI33 | AppdxI34 | AppdxI35 | AppdxJ-All | AppdxJ1 | AppdxJ2 | AppdxJ3 | AppdxJ4 | AppdxJ5 | AppdxJ6 | AppdxJ7 | AppdxJ8 | AppdxJ9 | AppdxJ10 | AppdxJ11 | AppdxK | AppdxL | AppdxM | Cover | ALL |
 
| NODIS Library | Program Management(8000s) | Search |

DISTRIBUTION:
NODIS


This Document is Obsolete and Is No Longer Used.
Check the NODIS Library to access the current version:
http://nodis3.gsfc.nasa.gov