|
Published Articles >> Table of Contents >> Abstract
April 1994 (Vol. 9, No. 2)
pp. 54-59
Representing and Maintaining Process Knowledge for Large-Scale Systems Development
Balasubramaiam Ramaesh
Vasant Dhar
Full Article Text:
 
DOI Bookmark: http://doi.ieeecomputersociety.org/10.1109/64.294137
Send link to a friend
| Abstract |
|
Discusses how the Remap system (representation and maintenance of process knowledge) uses a semiformal representation that supports the design and maintenance of large-scale software systems. The conceptual model relates design rationale knowledge to the resulting system, providing the primitives/ templates with which we can capture (often informal) design rationale information. The model's semantics are well defined, allowing automated reasoning with its components. By providing a complete design history, Remap enhances the understandability of designs and offers a mechanism for propagating changes in design decisions into changes in design solutions.
|
References
|
[1] J. Lee, "Design Rationale Capture and Use,"AI Magazine, Vol. 14, No. 2, Summer 1993, pp. 24-26.
[2] K.B. Yakemovic and J. Conklin, "The Capture of Design Rationale on an Industrial Development Project," Tech. Report STP-279-89, Microelectronics and Computer Technology Corporation, Austin, Tex., 1989.
[3] M. Lease, M. Lively, and J. Leggett, "Using an issue-based hypertext system to capture the software life-cycle process,"Hypermedia, vol. 2, no. 1, 1990.
[4] J. Lee, "SIBYL: A qualitative decision management system," inArtificial Intelligence at MIT: Expanding Frontiers, vol. 1, P. H. Winston and S. A. Shellard, Eds. Cambridge, MA: The MIT Press, 1990, pp. 105-133.
[5] A. Maclean et al., "Questions, Options, and Criteria: Elements of Design Space Analysis,"Human-Computer Interaction, Vol. 6, No. 3/4, 1991, pp. 201-251.
[6] G. Fisher et al., "Making Argumentation Serve Design,"Human-Computer Interaction, Vol. 6, No. 3/4, 1991, pp. 393-420.
[7] S. Toulmin, R. Rieke, and A. Janik,An Introduction to Reasoning, second edition, MacMillan, New York, 1984.
[8] D.G. Lowe, "Cooperative Structuring of Information: The Representation of Reasoning and Debate,"Int'l J. Man-Machine Studies, Vol. 23, Aug. 1985, pp. 97-111.
[9] L. Osterweil, "Software Processes are Software Too,"Proc. Ninth Int'l Conf. SoftwareEng., IEEE Computer Society Press, Los Alamitos, Calif., 1987, pp. 2-13.
[10] D.R. Smith, "Kids: A Semiautomatic Program Development System,"IEEE Trans. Software Eng., Vol. 16, No. 9, Sept. 1990, pp. 1024-1043.
[11] D.A. White, "The knowledge-based software assistant: A program summary," inProc. 6th Annual Knowledge-Based Software Engineering Conf., pp. vi-xiii, Sept. 1991.
[12] W. Market et al., "Commitment-Based Software Development,"IEEE Trans. Software Eng., Vol. 18, No. 10, Oct. 1992, pp. 870-885.
[13] W. Kunz and H. Rittel, "Issues as Elements of Information Systems," Working Paper 131, Institute of Urban and Regional Development, Univ. of California at Berkeley, 1970.
[14] M. Stefik, D. Bobrow, S. Lanning, D. Tatar, and G. Foster, "WYSIWIS revised: early experiences with multi-user interfaces,"ACM Trans. Office Inform. Syst., vol. 5, pp. 147-167, Apr. 1987.
[15] C. Rich and R.C. Waters, "The Programmer's Apprentice: A Research Overview,"Computer, Vol. 21, No. 11, Nov. 1988, pp. 11-25.
[16] M. Jarke, M. Jeusfeld, and T. Rose, "A software process data model for knowledge engineering in information systems,"Inform. Syst., vol. 15, no. 1, pp. 85-116, 1990.
[17] J. Conklin and K. Yakemovic, "A Process-Oriented Approach to Design Rationale," Human-Computer Interaction, Vol. 6, No. 314, 1991, pp. 357-392.
[18] B. Ramesh and Luqi, "Process-Knowledge-Based Rapid Prototyping,"Proc. IEEE Int'l Symp. Requirements Eng., IEEE Computer Society Press, Los Alamitos, Calif., 1993, pp. 248-255.
|
Additional Information
|
Citation:
Balasubramaiam Ramaesh, Vasant Dhar,
"Representing and Maintaining Process Knowledge for Large-Scale Systems Development,"
IEEE Expert: Intelligent Systems and Their Applications,
vol. 09,
no. 2,
pp. 54-59,
Apr.,
1994
|
|