This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
A Case History Development of a Foolproofing Interface Documentation System
August 1993 (vol. 19 no. 8)
pp. 765-773

The authors discuss information transmission errors occurring between design engineers involved in software development and describe an interface design documentation system that can prevent them. The equivalence of human errors in software design and hardware manufacturing activities is established. The characteristics that must be included in an interface documentation system to prevent communication errors in software design activities, based on foolproofing principles that were identified for hardware manufacturing, are discussed. Utilizing these characteristics, an example of an interface documentation system for software products which control measuring equipment is presented. Its effects on the resultant number of communication errors between hardware and software engineers is subsequently experimentally evaluated.

[1] ISO 9000-3,Guidelines for the Application of ISO 9001 to the Development, Supply and Maintenance of Software, 1991.
[2] H. D. Mills, "Stepwise refinement and verification in box-structured systems,"IEEE Comput., vol. 21, no. 6, pp. 23-36, June 1988.
[3] W. S. Humphrey,Managing the Software Process. Reading, MA: Addison-Wesley, 1989.
[4] M. Kellner, "Software process modeling: value and experience,"SEI Tech. Rev., pp. 23-54, 1989.
[5] R. C. T. Lai, "On formalization software process description: Consortium's example," inProc. COMPSAC'91, Sept. 1991, pp. 388-389.
[6] N. G. Leveson and P. R. Harvey, "Software fault tree analysis,"J. Syst. Software, vol. 3, no. 2, pp. 173-182, June 1983.
[7] N. G. Leveson and P. R. Harvey, "Analyzing software safety,"IEEE Trans. Software Eng., vol. SE-9, no. 5, pp. 569-579, Sept. 1983.
[8] V. R. Basili and B. T. Perricone, "Software errors and complexity: An empirical investigation,"Commun. ACM, vol. 27, no. 1, p. 42-52, Jan. 1984.
[9] V. R. Basili and R. W. Reiter, Jr., "An investigation on human factors in software development,"IEEE Comput., vol. 12, no. 12, pp. 21-38, Dec. 1979.
[10] T. Nakajo and H. Kume, "A case history analysis of software error cause-effect relationships,"IEEE Trans. Software Eng., vol. SE-17, no. 8, pp. 830-838, Aug. 1991.
[11] T. DeMarco,Structured Analysis and System Specification. New York: Youdon, 1978.
[12] M. A. Jackson,System Development. London: Prentice-Hall International, 1983.
[13] A. Endres, "An analysis of errors and their causes in system programs,"IEEE Trans. Software Eng., vol. SE-2, no. 2, pp. 140-149, June 1975.
[14] R. K. Iyer and P. Velardi, "Hardware-related software errors: Measurement and analysis,"IEEE Trans. Software Eng., vol. SE-11, no. 2, pp. 223-231, Feb. 1985.
[15] T. Nakajo and H. Kume, "The principles of foolproofing and these application in manufacturing,"Rep. Stat. Appl. Rex., JUSE, vol. 32, no. 2, pp. 10-29, June 1985.
[16] C. T. Morganet al., Human Engineering Guide to Equipment Design. New York: McGraw-Hill, 1963.
[17] R.B. Grady and D.L. Caswell,Software Metrics: Establishing a Company-Wide Program. Englewood Cliffs, NJ: Prentice Hall, 1987.
[18] S. Mizuno,Management for Quality Improvement: The 7 New QC Tools. Cambridge, MA: Productivity Press, 1988, pp. 115-142.
[19] W. G. Cochran, "Some methods for strengthening the common Chi-squared tests,"Biometrics, vol. 10, no. 4, pp. 417-451, Dec. 1954.

Index Terms:
measurement equipment control; foolproofing interface documentation system; information transmission errors; design engineers; software development; interface design documentation system; human errors; software design; hardware manufacturing activities; foolproofing principles; measuring equipment; computerised control; fault tolerant computing; human factors; system documentation; user interfaces
Citation:
T. Nakajo, I. Azuma, M. Tada, "A Case History Development of a Foolproofing Interface Documentation System," IEEE Transactions on Software Engineering, vol. 19, no. 8, pp. 765-773, Aug. 1993, doi:10.1109/32.238580
Usage of this product signifies your acceptance of the Terms of Use.