This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
Supporting Systems Development by Capturing Deliberations During Requirements Engineering
June 1992 (vol. 18 no. 6)
pp. 498-510

Support for various stakeholders involved in software projects (designers, maintenance personnel, project managers and executives, end users) can be provided by capturing the history about design decisions in the early stages of the system's development life cycle in a structured manner. Much of this knowledge, which is called the process knowledge, involving the deliberation on alternative requirements and design decisions, is lost in the course of designing and changing such systems. Using an empirical study of problem-solving behavior of individual and groups of information systems professionals, a conceptual model called REMAP (representation and maintenance of process knowledge) that relates process knowledge to the objects that are created during the requirements engineering process has been developed. A prototype environment that provides assistance to the various stakeholders involved in the design and management of large systems has been implemented.

[1] C. Potts and G. Bruns, "Recording the reasons for design decisions," inProc. 10th Int. Conf. Software Engineering, Singapore, 1988, pp. 418-427.
[2] V. Dhar and M. Jarke, "Dependency directed reasoning and learning in systems maintenance support,"IEEE Trans. Software Eng., vol. 14, pp. 211-227, Feb. 1988.
[3] B. Curtis, H. Krasner, and N. Iscoe, "A Field Study of the Software Design Process for Large Systems,"Comm. ACM, Vol. 31, No. 11, pp. 1,268-1,287.
[4] H. Thimbleby, "Delaying commitment,"IEEE Software, pp. 78-86, May 1988.
[5] R. Guindon and B. Curtis, "Control of cognitive processes during software design: what tools would support software designers?" inProc. CHI'88(Washington, DC), 1988, pp. 263-268.
[6] C. Wild and K. Maly, "Toward a software maintenance support environment," inProc. Conf. on Software Maintenance(Washington, DC), 1988, pp. 297-306.
[7] R. Balzer, T. Cheatham, and C. Green, "Software technology in the 1990's: using a new paradigm,"IEEE Computer, vol. 16, pp. 39-45, Nov. 1983.
[8] R. Balzer, "A 15 year perspective on automatic programming,"IEEE Trans. Software Eng., vol. SE-11, no. 11, pp. 1257-1268, Nov. 1985.
[9] T. Biggerstaff and C. Richter, "Reusability framework, assessment, and directions,"IEEE Software, pp. 41-49, July 1987.
[10] R. V. Scoy and C. Plinta, "An informal experiment in reuse," inProc. Reuse in Practice Workshop(Pittsburgh, PA), July 1989.
[11] M. D. Lubars and B. Ramesh, "Domain analysis for multiple target systems," inProc. Workshop on Domain Modeling for Software Eng., OOPSLA'89(New Orleans), Oct. 1989, pp. 92-96.
[12] M. Shaw,Group Dynamics: The Psychology of Small Group Behavior. New York: McGraw-Hill, 1981.
[13] B. Fisher, "Leadership: when does the difference make a difference?" inCommunication and Group Decision Making, R. Hirokawa and M. Poole, Eds. Beverly Hills, CA: Sage, 1986.
[14] D. Walz, J. Elam, H. Krasner, and B. Curtis, "A methodology for studying software design teams: An investigation of conflict behavior in the requirements definition phase," inProc. 2nd Workshop on Empirical Studies of Programmers. Norwood, NJ: Ablex, 1987.
[15] J. Conklin and M.L. Begeman, "A hypertext tool for exploratory policy discussion,"ACM Trans. Office Inform. Syst., vol. 6, no. 4, pp. 303-331, 1988.
[16] K. B. Yakemovic and E. J. Conklin, "Report on a development project use of an issue-based information system," inProc. Conf. on Computer-Supported Cooperative Work, Oct. 1990, pp. 105-118.
[17] H. Rittel, "Dilemmas in a general theory of planning,"Policy Sci., vol. 4, pp. 155-169, 1973.
[18] T. Winograd, "A language/action perspective on the design of cooperative work,"Human Computer Interaction, vol. 3, no. 1, pp. 3-30, 1988.
[19] 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.
[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] R. Thayer and M. Thayer, "Glossary," inSystem and Software Requirements Engineering, R. Thayer and M. Dorfman, Eds. Los Almitos, CA: IEEE Computer Soc. Press, 1990, pp. 605-676.
[22] L. Hubert, "Kappa revisited,"Psychological Bull., vol. 84, pp. 288-297, 1977.
[23] S. Biggs, "An Investigation of the decision processes underlying the assessment of corporate earning power," Ph.D. thesis, Univ. Minnesota, 1978.
[24] I. Vessey, "An investigation of the psychological processes underlying the debugging of computer programs," Ph.D. thesis, Dept. Commerce, Univ. Queensland (Australia), Apr. 1984.
[25] P. Johnson, F. Hasserbrock, A. Duran, and J. Moller, "Multimethod study of clinical judgment,"Organization. Behavior and Human Perform., vol. 30, pp. 201-230, 1982.
[26] J. Mylopoulos, A. Borgida, M. Jarke, and M. Koubarakis, "Telos: Representing knowledge about information systems,"ACM Trans. Inform. Syst., vol. 8, no. 4, 1990.
[27] 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.
[28] S. Greenspan, "Requirements modeling: a knowledge representation approach to software requirements definition Ph.D. thesis," Computer Res. Group, Univ. Toronto, Mar. 1984.
[29] J. Allen and P. Hayes, "Moments and points in an interval-based temporal logic,"Comput. Intell., vol. 5, pp. 225-238, Nov. 1989.
[30] R. Prieto-Diaz and P. Freeman, "Classifying software for reusability,"IEEE Software, pp. 6-16, Jan. 1987.
[31] M. Lubars, "The idea design environment," inProc. 11th Int. Conf. on Software Eng.(Pittsburgh, PA), 1989, pp. 23-32.
[32] M. Jarke, "Conceptbase v 3.0 user manual," Univ. Passau, Passau, Germany, Tech. Rep. MIP-9106, Mar. 1991.
[33] M. Lubars, "Code reusability in the large versus code reusability in the small," inSoftware Reuse: Emerging Technology, W. Tracz, Ed. Washington, DC: IEEE Computer Soc. Press, 1988, pp. 68-76.
[34] C. Rich and R. C. Waters, "Automatic programming: myths and prospects,"IEEE Computer, pp. 40-51, Aug. 1988.
[35] H. Reubenstein and R. Waters, "The requirements apprentice: automated assistance for requirements acquisition,"IEEE Trans. Software Eng., vol. 17, pp. 226-240, Mar. 1991.
[36] D. R. Barstow, "Domain-specific automatic programming,"IEEE Trans. Software Eng., vol. 11, no. 11, pp. 1321-1336, Nov. 1985.
[37] A. J. Czuchry and D. R. Harris, "KBRA: a new paradigm for requirements engineering,"IEEE Expert, pp. 21-35, Winter 1988.
[38] D. R. Smith, "KIDS: a semiautomatic program development system,"IEEE Trans. Software Eng., vol. 16, pp. 1024-1043, Sept. 1990.
[39] 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.
[40] J. Lee, "SIBYL: a tool for managing group decision rationale," inProc. Conf. Computer-Supported Cooperative Work(Los Angeles, CA), Oct. 1990, pp. 79-92.
[41] 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.
[42] S. Toulmin, R. Rieke, and A. Janik,An introduction to Reasoning, 2nd ed. New York: Macmillan, 1984.
[43] D. G. Lowe, "Co-operative structuring of information: the representation of reasoning and debate,"Int. J. Man-Machine Studies, vol. 23, pp. 97-111, Aug. 1985.
[44] T. Rose, M. Jarke, M. Gocek, M. Maltzahn, and H. Nissen, "A decision based configuration process environment,"Software Eng. J., vol. 6, no. 5, pp. 332-346, 1991.
[45] L. Osterweil, "Software processes are software too," inProc. 9th Int. Conf. Software Engineering, Monterey, CA, Mar. 1987, pp. 2-13.

Index Terms:
issue based information systems method; knowledge capture; systems development; deliberations; requirements engineering; software projects; history; design decisions; development life cycle; process knowledge; problem-solving behavior; information systems professionals; conceptual model; REMAP; formal specification; knowledge acquisition
Citation:
B. Ramesh, V. Dhar, "Supporting Systems Development by Capturing Deliberations During Requirements Engineering," IEEE Transactions on Software Engineering, vol. 18, no. 6, pp. 498-510, June 1992, doi:10.1109/32.142872
Usage of this product signifies your acceptance of the Terms of Use.