Automated consistency checking of requirements specifications

  • Authors:

  • Constance L. Heitmeyer;Ralph D. Jeffords;Bruce G. Labaw

  • Affiliations:

  • Naval Research Laboratory, Code 5546, Washington, D.C;Naval Research Laboratory, Code 5546, Washington, D.C;Naval Research Laboratory, Code 5546, Washington, D.C

  • Venue:
  • ACM Transactions on Software Engineering and Methodology (TOSEM)
  • Year:
  • 1996

Quantified Score

Hi-index 0.01

Visualization

Abstract

This article describes a formal analysis technique, called consistency checking, for automatic detection of errors, such as type errors, nondeterminism, missing cases, and circular definitions, in requirements specifications. The technique is designed to analyze requirements specifications expressed in the SCR (Software Cost Reduction) tabular notation. As background, the SCR approach to specifying requirements is reviewed. To provide a formal semantics for the SCR notation and a foundation for consistency checking, a formal requirements model is introduced; the model represents a software system as a finite-state automation which produces externally visible outputs in response to changes in monitored environmental quantities. Results of two experiments are presented which evaluated the utility and scalability of our technique for consistency checking in real-world avionics application. The role of consistency checking during the requirements phase of software development is discussed.