The Community for Technology Leaders
Requirements Engineering, IEEE International Conference on (2000)
Schaumburg, Illinois
June 19, 2000 to June 23, 2000
ISSN: 1097-0592
ISBN: 0-7695-0565-1
pp: 71
Constance L. Heitmeyer , Naval Research Laboratory
ABSTRACT
During the past decade, researchers have proposed numerous formal techniques for describing and analyzing system and software requirements. These include 1) special languages for specifying requirements, such as RSML and SCR, and 2) software tools, such as consistency checkers, simulators, model checkers, and theorem provers, for detecting errors in requirements specifications, for validating that the specifications capture the intended system behavior, and for verifying that the specifications satisfy selected properties. These properties include type correctness, consistency (no unwanted nondeterminism), and completeness (no missing cases) as well as application properties, such as security and safety properties. Although some limited progress has been made in applying these formal techniques in the practical development of requirements documents, use of the techniques by software developers remains rare. This is in sharp contrast to hardware design, where, at companies such as Intel and Motorola, the use of formally based tools such as model checkers is more common. Recently, these and other hardware companies have begun to integrate formally based techniques into their design environments.
INDEX TERMS
CITATION

C. L. Heitmeyer, "Transferring Research Results in Requirements to Practice: Obstacles and Incentives," Requirements Engineering, IEEE International Conference on(ICRE), Schaumburg, Illinois, 2000, pp. 71.
doi:10.1109/ICRE.2000.855590
85 ms
(Ver 3.3 (11022016))