This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
Representation and Presentation of Requirements Knowledge
October 1992 (vol. 18 no. 10)
pp. 853-869

The approach to representation and presentation of knowledge used in ARIES, an environment to experiment with support for analysts in modeling target domains and in entering and formalizing system requirements, is described. To effectively do this, ARIES must manage a variety of notations so that analysts can enter information in a natural manner, and ARIES can present it back in different notations and from different viewpoints. To provide this functionality, a single, highly expressive internal representation is used for all information in the system. The system architecture separates representation and presentation, in order to localize consistency and propagation issues. The presentation architecture is tailored to be flexible enough so that new notations can be easily introduced on top of the underlying representation. Presentation knowledge is coupled to specification evolution knowledge thereby leveraging common representations for both in order to provide automated focusing support to users who need informative guidance in creating and modifying specifications.

[1] M. Alford, "SREM at the age of eight: The distributed computing design system,"IEEE Computer, vol. 18, Feb. 1985.
[2] ASA,Airman's Information Manual, Aviation Supplies and Academics, 1989.
[3] R. Balzeret al., "Operational specification as the basis for specification validation," inTheory and Practice of Software Technology, pp. 21-49. Amsterdam: North-Holland, 1983.
[4] J. Bateman, "Upper modeling: Organizing knowledge for natural language processing," inProc. 4th Int. Nat. Lang. Generation Workshop, June 1990.
[5] K. Benner, "Using simulation techniques to analyze specifications," inProc. 5th KBSA Conf., pp. 305-316, 1990.
[6] K. Benner,"The ARIES Simulation Component," submitted to the 7th Annual RADC Knowledge-Based Software Engineering (KBSE) Conference.
[7] A. Borgidaet al., "CLASSIC: A structural data model for objects," inProc. ACM SIGMOD '89 Conf., June 1989.
[8] A. Borgida, S. Greenspan, and J. Mylopoulos, "Knowledge representation as the basis for requirements specifications,"IEEE Computer, vol. 18, pp. 82-91, 1985.
[9] R. Brachman and H. Levesque, "The tractability of subsumption in frame-based description languages," inProc. Third National Conf. Artificial Intelligence, pp. 34-37, 1984.
[10] D. Cohen, "Symbolic execution of the Gist specification language," inProc. 8th Int. Joint Conf. Artificial Intelligence, pp. 17-20, Aug. 1983.
[11] D. Cohen,AP5 Manual. USC-Information Sciences Institute, June 1989. (draft).
[12] J. Dick and J. Loubersac, "Integrating structured and formal methods: A visual approach to VDM," inProc. 3rd European Software Engineering Conf., pp. 37-59, 1991.
[13] J. C. S. do P. Leite and P. A. Freeman, "Requirements validation through viewpoint resolution,"IEEE Trans. Software Eng., vol. 17, pp. 1253-1268, Dec. 1991.
[14] A. Finkelstein. J. Kramer, B. Nuseibeh, and L. Finkelstein, "Viewpoints: A framework for integrating multiple perspectives in system development,"Int. J. Software Engineering and Knowledge Engineering, 1992 (to appear).
[15] M. D. Fraser, K. Kumar, and V. K. Vaishnavi, "Informal and formal requirements specification languages: Bridging the gap,"IEEE Trans. Software Eng., vol. 17, pp. 454-466, May 1991.
[16] M. Geneserethet al., "Knowledge Interchange Format,"Tech. Rep. Logic-90-04, Stanford University, 1990.
[17] C. Greenet al., "Report on a knowledge-based software assistant," inReadings in Artificial Intelligence and Software Engineering, C. Richard and R. Waters, Eds. Los Altos, CA: Morgan Kaufmann, 1986.
[18] R. V. Guha and D. B. Lenat, "Cyc: A midterm report,"AI Magazine, vol. 11, pp. 32-59, 1991.
[19] J. Hagelstein, "Declarative approach to information system requirements.J. Knowledge-Based Systems, vol. 1, pp. 211-220, Sept. 1988.
[20] U. Hahn, M. Jarke, and T. Rose, "Teamwork support in a knowledge-based information systems environment,"IEEE Trans. Software Eng., vol. 17, pp. 467-482, May 1991.
[21] D. Harris and A. Czuchry, "KBRA: A New Paradigm for Requirements Engineering,"IEEE Expert, vol. 3, 1988.
[22] V. Hunt and A. Zellweger, "The FAA's Advanced Automation Svstem: Strategies for future air traffic control systems,"IEEE Computer, vol. 20, pp. 19-32, Feb. 1987.
[23] W. L. Johnson, "Deriving specifications from requirements," inProc. 10th Int. Conf. on Software Eng. (Singapore), 1988, pp. 428-438.
[24] W. L. Johnson, "Specification as formalizing and transforming domain knowledge," inProc. AAAI Workshop on Automating Software Design, pp. 48-55, 1988.
[25] W. L. Johnson and M. S. Feather, "Reusable Gist language description," available from USC/ISI, 1991.
[26] W. L. Johnson and M. S. Feather, "Using evolution transformations to construct specifications," inAutomating Software Design, pp. 65-92, AAAI Press, 1991.
[27] W. L. Johnson, M. S. Feather, and D. R. Harris, "Integrating domain knowledge, requirements, and specifications,"J. Syst. Integration, vol. 1, pp. 283-320, Nov. 1991.
[28] H. A. Kautz and J. F. Allen, "Generalized plan recognition," inProc. AAAI-86, pp. 32-37, 1986.
[29] R. Mac Gregor,Loom Users Manual, 1989.
[30] W. Mark,IEEE Trans. Software Eng., this issue.
[31] J. J. Myers and W. L. Johnson, "Toward specification explanation: Issues and lessons," inProc. 3rd Annual RADC Knowledge-Based Software Assistant (KBSA) Conference 1988, pp. 251-269, 1988.
[32] K. Narayanaswamy and N. M. Goldman, "A flexible framework for cooperative software development,"J. Syst. Software, Oct. 1991.
[33] R. Necheset al., "Enabling technology for knowledge sharing,"AI Magazine, pp. 36-56, Fall 1991.
[34] C. Niskier, T. Maibaum, and D. A. Schwabe, "Look through PRISMA: toward pluralistic knowledge-based environments," inProc. 5th Int. Workshop on Software Specification and Design(Pittsburgh, PA). Los Alamitos, CA: IEEE Computer Soc. Press, 1989, pp. 128-136.
[35] "The KBSA Project. Knowledge-Based Specification Assistant," Final report (available from USC/Information Sciences Institute), 1988.
[36] Refine User's Guide, Reasoning Systems, Palo Alto, CA. 1986.
[37] S. P. Reiss, "Pecan: Program development systems that support multiple views,"IEEE Trans. Software Eng., vol. SE-11, pp. 276-285, Mar. 1985.
[38] W. Swartout, "Gist English generator," inProc. Nat. Conf. Artificial Intelligence, pp. 404-409, 1982.
[39] W. Swartout and S. Smoliar, "Report from the frontiers of knowledge representation,"USC/ISI Tech. Rep., 1988.
[40] L. Terveen, "Person-computer cooperation through collaborative manipulation,"Tech. Rep. ACT-AI-048-91, MCC, 1991.
[41] D. S. Wile, "Integrating syntaxes and their associated semantics," available from the author at USC/Information Sciences Institute, 4676 Admiralty Way, Marina del Rey, CA 90292, USA--wile@isi.edu.
[42] D. S. Wile, "Organizing programming knowledge into syntax-directed experts," inProc. Int. Workshop on Advanced Programming Environments, pp. 551-565, 1986.
[43] G. B. Williams and J. J. Myers, "Exploiting metamodel correspondences to provide paraphrasing capabilities for the KBSA Concept Demonstration project," inProc. 5th Annual RADC Knowledge-Based Software Assistant (KBSA) Conf., pp. 331-345, 1990.

Index Terms:
requirements knowledge; representation; presentation; ARIES; target domains; formalizing system requirements; system architecture; consistency; propagation; evolution knowledge; automated focusing support; specifications; formal specification; knowledge based systems; knowledge representation; software reusability
Citation:
W.L. Johnson, M.S. Feather, D.R. Harris, "Representation and Presentation of Requirements Knowledge," IEEE Transactions on Software Engineering, vol. 18, no. 10, pp. 853-869, Oct. 1992, doi:10.1109/32.163603
Usage of this product signifies your acceptance of the Terms of Use.