The Requirements Apprentice: Automated Assistance for Requirements Acquisition

IEEE Transactions on Software Engineering

Volumn 17, Issue 3, 1991, Pages 226-240

  Reubenstein, Howard B ^a   Waters, Richard C ^b  

^a MITRE CORPORATION   (United States)

^b MASSACHUSETTS INSTITUTE OF TECHNOLOGY   (United States)

Author keywords

[No Author keywords available]

Indexed keywords

COMPUTER METATHEORY--PROGRAMMING THEORY;

KNOWLEDGE ACQUISITION; SOFTWARE DEVELOPMENT;

COMPUTER SOFTWARE;

EID: 0026121505     PISSN: 00985589     EISSN: None     Source Type: Journal    
DOI: 10.1109/32.75413     Document Type: Article

References (49)

1. G. Arango, P. Freeman, “Modeling knowledge for software development,” in Proc. 3rd Int. Workshop Software Specification, Design. Washington, DC: IEEE Computer Society Press, Aug. 1985, pp. 63-66.
2. R. Babb et al, “Workshop on models, languages for software specification, design,” Computer, Vol. 18, No. 3, pp. 103-108, Mar. 1985.
3. B. W. Boehm, “Verifying, validating software requirements, design specifications,” IEEE Software, Vol. 1, No. 1, pp. 75-88, Jan. 1984.
4. R. Balzer, N. Goldman, D. Wile, “Informality in program specifications,” IEEE Trans. Software Eng., Vol. 4, No. 2, pp. 94-103, Mar. 1978.
5. D. R. Barstow, “Domain-specific automatic programming,” IEEE Trans. Software Eng., Vol. 11, No. 11, pp. 1321-1336, Nov. 1985.
6. J. S. Bennett, “A knowledge-based system for acquiring the conceptual structure of a diagnostic expert system,” J. Automated Reasoning, vol. 1, no. 1, pp. 49-74, 1985.
7. A. Borgida, S. Greenspan, J. Mylopoulos, “Knowledge representation as the basis for requirements specifications,” Computer, Vol. 18, No. 4, pp. 82-90, Apr. 1985.
8. A. Crawford, “Joint application design: A new way to design systems,” in Guide Int. Proc., Guide Int. Corp., 1982.
9. A. Czuchry, D. Harris, “KBRA: A new paradigm for requirements engineering,” IEEE Expert, Vol. 3, No. 4, pp. 21-35, Winter 1988.
10. R. Davis, “Interactive transfer of expertise: Acquisition of new inference rules,” Artificial Intell., vol. 12, pp. 121–157, 1979.
11. J. Diederich, I. Ruhmann, M. Maym, “KRTTON: A knowledge acquisition tool for expert systems,” Int. J. Man-Machine Studies, Vol. 26, No. 1, pp. 29-40, Jan. 1987.
12. J. Doyle, “A truth maintenance system,” Artificial Intell., vol. 12, pp. 231–272, 1979.
13. Y. A. Feldman, C. Rich, “Principles of knowledge representation, reasoning in the FRAPPE system,” in Proc. Sixth Israeli Symp. Artificial Intelligence, Dec. 1989.
14. S. Fickas, “Automating analysis: An example,” in Proc. 4th Int. Workshop Software Specification, Design. Washington, DC: IEEE Computer Society Press, Apr. 1987, pp. 58-67.
15. S. Fickas, P. Nagarajan, “Critiquing software specifications,” IEEE Software, Vol. 5, No. 6, pp. 37-47, Nov. 1988.
16. N. Haas, G. G. Hendrix, “Learning by being told: Acquiring knowledge for information management,” in Machine Learning an Artificial Intelligence Approach, R. Michalski et al, Eds., 1983, pp. 405-421.
17. M. T. Harandi, F. H. Young, “Template based specification, design,” in Proc. 3rd Int. Workshop Software Specification, Design. Washington, DC: IEEE Computer Society Press, Aug. 1985, pp. 94-97.
18. W. Johnson, M. Feather, “Representing evolution transformations,” in Proc. 11th Int. Joint Conf. Artificial Intelligence, Workshop Automating Software Design, Aug. 1989, pp. 125-131.
19. T. S. Kaczmarek, R. Bates, G. Robins, “Recent developments in NIKL,” in Proc. 6th Nat. Conf. Artificial Intelligence, Aug. 1986, pp. 978-985.
20. R. A. Kemmerer, “Testing formal specifications to detect design errors,” IEEE Trans. Software Eng., Vol. 11, No. 1, pp. 32-43, Jan. 1985.
21. J. Z. Lavi, “Improving the embedded computer systems software process using a generic model,” in Proc. 3rd Int. Workshop Software Specification, Design. Washington, DC: IEEE Computer Society Press, Aug. 1985, pp. 127-129.
22. S. Lee, S. Sluizer, “SXL: An executable specification language,” in Proc. 4th Int. Workshop Software Specification, Design. Washington, DC: IEEE Computer Society Press, Apr. 1987, pp. 231-235.
23. P. M. Lefelhocz, “An experiment in knowledge acquisition for software requirements,” MIT Artificial Intelligence Lab., Rep. MIT/AI/WP-330, May 1990.
24. J. C. Leite, “Viewpoint analysis: A case study,” in Proc. 5th Int. Workshop Software Specification, Design. Washington, DC: IEEE Computer Society Press, May 1989, pp. 111-119.
25. M. L. Minsky, “A framework for representing knowledge,” in The Psychology of Computer Vision, P. H. Winston, Ed. New York: McGraw-Hill, 1975.
26. M. L. Minsky, Society of Mind. New York: Simon, Schuster, 1987.
27. M. Musem, L. Fagan, D. Combs, E. Shortliffe, “Use of a domain model to drive an interactive knowledge-editing tool,” Int. J. Man-Machine Studies, Vol. 26, No. 1, pp. 105-125, Jan. 1987.
28. J. M. Neighbors, “The Draco approach to constructing software from reusable components,” IEEE Trans. Software Eng., Vol. SE-10, No. 5, pp. 564-574, Sept. 1984.
29. P. Politakis, S. Weiss, “Using empirical analysis to refine expert system knowledge bases,” Artificial Intell, vol. 22, no. 1, pp. 23-48, 1984.
30. C. Potts, “Requirements analysis, domain knowledge,, design,” MCC, Tech. Rep. STP-313-88, Feb. 1989.
31. C. Rich, “A formal representation for plans in the programmer's apprentice,” in Proc. 7th Int. Joint Conf. Artificial Intelligence, Aug. 1981, pp. 1044-1052.
32. C. Rich, “The layered architecture of a system for reasoning about programs,” in Proc. 9th Int. Joint Conf. Artificial Intelligence, Aug. 1985, pp. 540-546.
33. C. Rich, R. C. Waters, “The programmer's apprentice: A program design scenario,” MIT Artificial Intelligence Lab., Rep. MIT/AIM-933A, Nov. 1987.
34. C. Rich, R. C. Waters, “The programmer's apprentice: A research overview,”, vol. 21, no. 11, pp. 10–25, Nov. 1988.
35. C. Rich, R. C. Waters, The Programmer's Apprentice. Reading, MA: Addison- Wesley,, Baltimore, MD: ACM Press, 1990.
36. C. Rich, R. C. Waters, H. B. Reubenstein, “Toward a requirements apprentice,” in Proc. 4th Int. Workshop Software Specification, Design. Washington, DC: IEEE Computer Society Press, Apr. 1987, pp. 79-86.
37. H. B. Reubenstein, “Automated acquisition of evolving informal descriptions,” Ph.D. dissertation, MIT Artificial Intelligence Lab., Rep. MIT/AI/rR-1205, June 1990.
38. H. B. Reubenstein, R. C. Waters, “The requirements apprentice: An initial scenario,” in Proc. 5th Int. Workshop Software Specification, Design. Washington, DC: IEEE Computer Society Press, May 1989, pp. 211-218.
39. W. Robinson, “Integrating multiple specifications using domain goals,” in Proc. 5th Int. Workshop Software Specification, Design. Washington, DC: IEEE Computer Society Press, May 1989, pp. 219-226.
40. R. Schank, “A conceptual dependency representation for a computer-oriented semantics,” Stanford Univ., Tech. Rep. AIM-83, 1969.
41. J. G. Schmolze, T. A. Lipkis, “Classification in the KL-ONE knowledge representation system,” in Proc. 8th Int. Joint Conf. Artificial Intelligence, Aug. 1983, pp. 330-332.
42. G. J. Susman, “The virtuous nature of bugs,” in Proc. Conf. Artificial Intelligence, the Simulation of Behavior, Univ. Sussex, England, July 1974.
43. W. Swartout, “The GIST behavior explainer,” in Proc. 3rd Nat. Conf. Artificial Intelligence, Aug. 1983, pp. 402-407.
44. D. Teichroew, E. Hershey, “PSL/PSA: A computer-aided technique for structured documentation, analysis of information processing systems,” IEEE Trans. Software Eng., Vol. 3, No. 1, pp. 41-48, Jan. 1977.
45. R. B. Terwilliger, M.J. Maybee, L. J. Osterweil, “An example of formal specification as an aid to design, development,” in Proc. 5th Int. Workshop Software Specification, Design. Washington, DC: IEEE Computer Society Press, May 1989, pp. 266-272.
46. R. C. Waters, “The programmers' apprentice: A session with KBEmacs,” IEEE Trans Software Eng., Vol. SE-11, No. 11, pp. 1296-1320, Nov. 1985.
47. J. M. Wing, “A Larch specification of the library problem,” in Proc. 4th Int. Workshop Software Specification, Design. Washington, DC: IEEE Computer Society Press, Apr. 1987, pp. 34-41.
48. S. Wrobel, “Design goals for sloppy modeling systems,” Int. J. Man-Machine Studies, Vol. 29, No. 4, pp. 461-482, Oct. 1988.
49. “Using the WISDM team method to define system requirements,” Western Institute Software Engineering, 1986.