ACM Home Page
Please provide us with feedback. Feedback
Automatic generation of state invariants from requirements specifications
Full text PdfPdf (1.32 MB)
Source Foundations of Software Engineering archive
Proceedings of the 6th ACM SIGSOFT international symposium on Foundations of software engineering table of contents
Lake Buena Vista, Florida, United States
Pages: 56 - 69  
Year of Publication: 1998
ISBN:1-58113-108-9
Also published in ...
Authors
Ralph Jeffords  Naval Research Laboratory, Code 5546, Washington, DC
Constance Heitmeyer  Naval Research Laboratory, Code 5546, Washington, DC
Sponsors
SIGSOFT: ACM Special Interest Group on Software Engineering
SIGPLAN: ACM Special Interest Group on Programming Languages
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 10,   Downloads (12 Months): 58,   Citation Count: 15
Additional Information:

abstract   references   cited by   index terms   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/288195.288218
What is a DOI?

ABSTRACT

Automatic generation of state invariants, properties that hold in every reachable state of a state machine model, can be valuable in software development. Not only can such invariants be presented to system users for validation, in addition, they can be used as auxiliary assertions in proving other invariants. This paper describes an algorithm for the automatic generation of state invariants that, in contrast to most other such algorithms, which operate on programs, derives invariants from requirements specifications. Generating invariants from requirements specifications rather than programs has two advantages: 1) because requirements specifications, unlike programs, are at a high level of abstraction, generation of and analysis using such invariants is easier, and 2) using invariants to detect errors during the requirements phase is considerably more cost-effective than using invariants later in software development. To illustrate the algorithm, we use it to generate state invariants from requirements specifications of an automobile cruise control system and a simple control system for a nuclear plant. The invariants are derived from specifications expressed in the SCR (Software Cost Reduction) tabular notation.


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. Software requirements for the A- 7E aircraft. Tech. Rep. NRL-9194, Naval Research Lab., Wash., DC, 1992.
 
2
ARCHER, M., AND HEITMEYER, C. The use of model checking and abstraction in analyzing requirements specifications: A formal foundation. Tech. rep., Naval Research Lab., Washington, DC, 1998. (Draft).
 
3
 
4
 
5
 
6
 
7
 
8
9
 
10
CROW, J., OWRE, S., RUSHBY, J., SHANKAR, N., AND SRIVAS, M. A tutorial introduction to PVS. Tech. rep., Computer Science Lab, SRI Int'l, Menlo Park, CA, Apr. 1995. (Presented at WIFT '95: Workshop on Industrial-Strength Formal Specification Techniques, Boca Raton, FL).
 
11
 
12
FAULIC, S. R., FINNERAN, L., KIRBY, JR., J., SHAH, S., AND SUTTON, J. Esperience applying the CORE method to the Lockheed C-130J. In Proc. gfh Annual Conf. on Computer Assurance (COdlPASS ' $4) (Gaithersburg, MD, June 1994), pp. 3-8.
 
13
14
 
15
 
16
17
 
18
HEIThIEYER, C. L., KIRBY, JR., J., AND LABAW, B. G. Tools for formal specification, verification, and validation of requirements. In PTOC. 12fh Annual Conf. on Computer Assurance (COM- PASS' 97) (Gaithersburg, MD, June 1997), IEEE.
 
19
HENINGER, K., PARNAS, D. L., SHORE, J. E., AND KALLANDER, J. W. Software requirements for t'he A-7E aircraft. Tech. Rep. 3876, Naval Research Lab., Wash., DC, 1978.
 
20
HENINGER, K. L. Specifying software requiremen& for complex systems: Nelv techniques and their application. IEEE Trans. Soffw. Eng. SE-6, 1 (Jan. 1980), 2-13.
 
21
 
22
JEFFORDS, R. D., AND HEITIEYER, C. L. Efficient automatic generation of state invariants from esecut,able requirements specifications. Tech. rep., Naval Research Lab., Washington DC, 1998. (Draft).
 
23
KIRBY, JR., J. Example NRL/SCR softlvare requirements for an automobile cruise control and monitoring system. Tech. Rep. TR-87-07, Wang Inst. of Graduate Studies, Tyngsboro, MA, July 1987.
24
 
25
 
26
 
27
 
28
 
29
 
30
OWRE, S., SHANKAR, N., AND RUSHBY, J. User guide for the PVS specification and verification system (Draft). Tech. rep., Computer Science Lab, SRI Int'l, Menlo Park, CA, 1993.
 
31
 
32
 
33
SREEMANI, T., AND ATLEE, J. M. Feasibility of model checking software requirements: A case study. In PTOC. 11th Annual Conference on Computer Assurance (COhfPASS ' 96) (Gaithersburg, MD, June 1996), pp. 77-88.
 
34

CITED BY  16

Collaborative Colleagues:
Ralph Jeffords: colleagues
Constance Heitmeyer: colleagues