The Community for Technology Leaders
RSS Icon
Issue No.06 - November/December (1988 vol.5)
pp: 37-47
<p>The authors describe how the knowledge of expert-systems analysts is being input to use in an automated critic for specification debugging. They are working on a system, named Kate, that tries to acquire a problem specification that includes a description of the objects, transitions (actions), and constraints of the intended system. They have built a computer-based critic as part of the Kate environment that has its roots in a set of protocols they collected over several analysis sessions. The critic has three major components: a model of the domain, a matcher to connect parts of the model to the specification being analyzed, and a critique to supply the analysis. The model represents a set of policy issues for building systems in a particular domain and a set of relevant problem specification cases to consider for systems in the domain. The critic has been run on a library database problem. The results are presented and compared with a critique by an experienced library analyst.</p>
expert-systems; specification debugging; Kate; problem specification; library database; expert systems; formal specification; program debugging; programming environments
Stephen Fickas, P. Nagarajan, "Critiquing Software Specifications", IEEE Software, vol.5, no. 6, pp. 37-47, November/December 1988, doi:10.1109/52.10002
7 ms
(Ver 2.0)

Marketing Automation Platform Marketing Automation Tool