N-Fold inspection: a requirements analysis technique

ABSTRACT

N-fold inspection uses traditional inspections of the user requirements document (URD) but replicates the inspection activities using N independent teams. A pilot study was conducted to explore the usefulness of N-fold inspection during requirements analysis. A comparison of N-fold inspection with other development techniques reveals that N-fold inspection is a cost-effective method for finding faults in the URD and may be a valid technique in the development of mission-critical software systems.

REFERENCES

• 1: A!ford, M. SREM at the age of eight: The distributed computing design system. IEEE Comput. 18, 4 (Apr. 1985}, 36-46.
• 2: Av~zienis. A. The n-version approach to fault-tolerant software. IEEE Trans. on Sofiw. Eng. 11, 12 (Dec. 1985). 1491-1501.
• 3: Avizienis, A.. Lyu. M. R.. and Schutz. W. In Search of efiective divers~ty: A six-language slucly of fault-tolerant flight~:ontrol software. In Proc~edings of th~ IEEE 18th International Syrnposium on Fault Tolerant Computing (Tokyo, Japan, }une 27-30.) IEEE/CS, New York, 1988, pp. 15-22.
• 4: Valdis Berzins , Michael Gray, Analysis and design in MSG.84: formalizing functional specifications, IEEE Transactions on Software Engineering, v.11 n.8, p.657-670, Aug. 1985 [doi>10.1109/TSE.1985.232516]
• 5: N. D. Birrell , M. A. Ould, A practical handbook for software development, Cambridge University Press, New York, NY, 1985
• 6: Boehm, B. lndustrial software metrJcs top-'10 list. IEEE Sofiw. 3, 9 (Sept. '1987J, 84-85.
• 7: Boehm, B. Verifving and validating software requirements and ~lesign specifications. IEEE Sofiw. 1, I (Jan. 1984), 75-88.
• 8: Grady Booch, Software engineering with Ada, Benjamin-Cummings Publishing Co., Inc., Redwood City, CA, 1983
• 9: Tom DeMarco, Structured Analysis and System Specification, Prentice Hall PTR, Upper Saddle River, NJ, 1979
• 10: I3. S. Departement of Defense. Reference Manual for the Ada Programming Language. ANSI-MIL-STD-1815A-1983, 1983.
• 11: M E Eagan, Advances in software inspections, IEEE Transactions on Software Engineering, v.12 n.7, p.744-751, July 1986
• 12: Fagan, M. E. Design and code inspections to reduce errors in program development. IBM Syst. }. 15, 3 (1976). 182-211.
• 13: C B Jones, Systematic software development using VDM, Prentice Hall International (UK) Ltd., Hertfordshire, UK, 1986
• 14: Kjell W. Nielsen , Ken Shumate, Designing large real-time systems with Ada, Communications of the ACM, v.30 n.8, p.695-715, Aug. 1987 [doi>10.1145/27651.27655]
• 15: Martyn A. Ould , Charles Unwin, Testing in software development, Cambridge University Press, New York, NY, 1987
• 16: Ramamoorthy, C. V.. et al. Application of a methodology for the development and validation of reliable process control software. IEEE Trans. on Softw. Eng. 7, 6 (Nov. '1981), 537-555.
• 17: Sheil. B. Power tools for programmers. Datamation, (Feb. 1983). 131-143.

INDEX TERMS

Primary Classification:
  K. Computing Milieux
  K.6 MANAGEMENT OF COMPUTING AND INFORMATION SYSTEMS
      K.6.1 Project and People Management
          Subjects: Systems development

Additional Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING
      D.2.9 Management
          Subjects: Programming teams

  K. Computing Milieux
  K.6 MANAGEMENT OF COMPUTING AND INFORMATION SYSTEMS
      K.6.3 Software Management
          Subjects: Software development

General Terms:
Management