ACM Home Page
Please provide us with feedback. Feedback
Automated consistency checking of requirements specifications
Full text PdfPdf (404 KB)
Source ACM Transactions on Software Engineering and Methodology (TOSEM) archive
Volume 5 ,  Issue 3  (July 1996) table of contents
Pages: 231 - 261  
Year of Publication: 1996
ISSN:1049-331X
Authors
Constance L. Heitmeyer  Naval Research Laboratory, Code 5546, Washington, D.C
Ralph D. Jeffords  Naval Research Laboratory, Code 5546, Washington, D.C
Bruce G. Labaw  Naval Research Laboratory, Code 5546, Washington, D.C
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 38,   Downloads (12 Months): 207,   Citation Count: 78
Additional Information:

abstract   references   cited by   index terms   review   collaborative colleagues  

Tools and Actions: Request Permissions Request Permissions    Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/234426.234431
What is a DOI?

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.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

 
1
ALSPAUGH, T.A., FAULK, S.R., BRITTON, K.H., PARKER, R.A., PARNAS, D.L., AND SHORE, J.E. 1992. Software requirements for the A-7E aircraft. Tech. Rep. NRL-9194, Naval Research Laboratory, Washington, D.C.
 
2
 
3
 
4
BHARADWAJ, R. 1996. A generalized validity checker. Tech. Rep., Naval Research Laboratory, Washington, D.C. In preparation.
 
5
 
6
7
 
8
 
9
CROW, J., OWRE, S., RUSHBY, J., SHANKAR, N., AND SRIVAS, M. 1995. A tutorial introduction to PVS. Tech. Rep., Computer Science Laboratory, SRI International, Menlo Park, Calif. Apr. Presented at WIFT '95: Workshop on Industrial-Strength Formal Specification Techniques (Boca Raton, Fla.).
 
10
 
11
 
12
 
13
FAULK, S.R. 1995. Software requirements: A tutorial. Tech. Rep. NRL-7775, Naval Research Laboratory, Washington, D.C.
 
14
 
15
FAULK, S.R., FINNERAN, L., KIRBY, J., JR., SHAH, S., AND SUTTON, J. 1994. Experience applying the CoRE method to the Lockheed C-130J. In Proceedings of the 9th Annual Conference on Computer Assurance (COMPASS '94) (Gaithersburg, Md., June). IEEE, New York, 3-8.
 
16
GAO. 1992. Mission critical systems: Defense attempting to address major software challenges. Tech. Rep. GAO/IMTEC-93-13, U.S. General Accounting Office, Washington, D.C. Dec.
 
17
 
18
GRINDLEY, C. B.B. 1968. The use of decision tables within Systematics. Comput. J. 11, 2 (Aug.), 128-133.
 
19
20
 
21
HEITMEYER, C.L. 1996. Requirements specification for hybrid systems. In Proceedings of Hybrid Systems Workshop III. Lecture Notes in Computer Science, R. Alur, T. Henzinger, and E. Sontag, Eds. Springer-Verlag, Norwell, Mass. To be published.
 
22
 
23
HEITMEYER, C. L. AND MCLEAN, J. 1983. Abstract requirements specifications: A new approach and its application. IEEE Trans. Softw. Eng. SE-9, 5 (Sept.), 580-589.
 
24
HEITMEYER, C. L., BULL, A., GASARCH, C., AND LABAW, B. 1995a. SCR*: A toolset for specifying and analyzing requirements. In Proceedings of the l Oth Annual Conference on Computer Assurance (COMPASS '95) (Gaithersburg, Md., June). IEEE, New York, 109-122.
 
25
HEITMEYER, C. L., JEFFORDS, R. D., AND LABAW, B.G. 1996. Tools for analyzing SCR-style requirements specifications: A formal foundation. Tech. Rep., Naval Research Laboratory, Washington, D.C. In preparation.
 
26
 
27
HENINGER, K.L. 1980. Specifying software requirements for complex systems: New techniques and their application. IEEE Trans. Softw. Eng. SE-6, 1 (Jan.), 2-13.
 
28
HENINGER, K., PARNAS, D. L., SHORE, J. E., AND KALLANDER, J.W. 1978. Software requirements for the A-7E aircraft. Tech. Rep. 3876, Naval Research Laboratory, Washington, D.C.
 
29
HESTER, S. D., PARNAS, D. L., AND UTTER, D.F. 1981. Using documentation as a software design medium. Bell Syst. Tech. J. 60, 8 (Oct.), 1941-1977.
 
30
HOOVER, D. N. AND CHEN, Z. 1995. Tablewise, a decision table tool. In Proceedings of the 1Oth Annual Conference on Computer Assurance (COMPASS '95) (Gaithersburg, Md., June). IEEE, New York, 97-108.
 
31
HUGHES, M.L., SHANK, R. M., AND STEIN, E.S. 1968. Decision Tables. MDI Publications, Wayne, Pa.
 
32
 
33
34
35
 
36
 
37
38
 
39
 
40
MEYER, S. AND WHITE, S. 1983. Software requirements methodology and tool study for A6-E technology transfer. Tech. Rep., Grumman Aerospace Corp., Bethpage, N.Y. July.
 
41
PARNAS, D.L. 1992. Tabular representation of relations. Tech. Rep. CRL-260, Telecommunications Research Institute of Ontario (TRIO), McMaster Univ., Hamilton, Ontario, Canada. Oct.
 
42
 
43
PARNAS, D.L. 1994. Inspection of safety-critical software using program-function tables. Tech. Rep. CRL-288, Communications Research Laboratory, McMaster Univ., Hamilton, Ontario, Canada.
 
44
 
45
 
46
PARNAS, D.L., ASMIS, G., AND MADLY, g. 1991. Assessment of safety-critical software in nuclear power plants. Nucl. Safety 32, 2 (Apr.-June), 189-198.
 
47
 
48
 
49
SMULLYAN, R.M. 1968. First-Order Logic. Springer-Verlag, New York.
 
50
VAN SCHOUWEN, A.J. 1990. The A-7 requirements model: Re-examination for real-time systems and an application for monitoring systems. Tech. Rep. TR 90-276, Queen's Univ., Kingston, Ontario, Canada.
 
51
VAN SCHOUWEN, A. g., PARNAS, D. L., AND MADEY, g. 1993. Documentation of requirements for computer systems. In Proceedings of RE'93: IEEE International Symposium on Requirements Engineering (San Diego, Calif., Jan.). IEEE Computer Society Press, Los Alamitos, Calif., 198-207.

CITED BY  78


REVIEW

"James C. Pleasant : Reviewer"

A technique is described for automatic detection of domain-independent errors in requirements specifications expressed in the software cost reduction (SCR) tabular notation. Types of errors considered include type errors, nondeterminism, missi  more...

Collaborative Colleagues:
Constance L. Heitmeyer: colleagues
Ralph D. Jeffords: colleagues
Bruce G. Labaw: colleagues