
Action taken by an aircraft engineering organization to improve the quality and reliability of its technical software is described. Before and after comparisons are given to illustrate that the quality and reliability were improved to where engineers no longer considered them to be a major factor in task planning and the expenditure of programing time for "fire drills" during production use was reduced to a negligible amount. The action taken was administrative rather than technical. It was, however based upon general procedures for control and communication that can be adapted by other engineering organizations for the same purpose.
| selected citations These citations are derived from selected sources. This is an alternative to the "Influence" indicator, which also reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically). | 0 | |
| popularity This indicator reflects the "current" impact/attention (the "hype") of an article in the research community at large, based on the underlying citation network. | Average | |
| influence This indicator reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically). | Average | |
| impulse This indicator reflects the initial momentum of an article directly after its publication, based on the underlying citation network. | Average |
