This Article 
 Bibliographic References 
 Add to: 
Commitment-Based Software Development
October 1992 (vol. 18 no. 10)
pp. 870-885

During the development of a system, software modules can be viewed in terms of their commitments: the constraints imposed by their own structure and behavior, and by their relationships with other modules (in terms of resource consumption, data requirements. etc.). The Comet system uses explicit representation and reasoning with commitments to aid the software design and development process-in particular, to lead software developers to make decisions that result in reuse. Developers can examine the commitments that must be met in order to include an existing module, and can explore how commitments change when modules are modified. Comet has been applied to the domain of sensor-based tracker software.

[1] A. J. Czuchry, Jr. and D. R. Harris, "KBRA: A new paradigm for requirements engineering,"IEEE Expert, vol. 3, pp. 21-35, 1988.
[2] P. Devanbu, R. Brachman, P. Selfridge, and B. Ballard, "LaSSIE: A knowledge-based software information system,"Commun. ACM, vol. 34, pp. 35-49, 1991.
[3] J. Finger and M. Genesereth, "RESIDUE: A deductive approach to design synthesis," Stanford Heuristic Programming Project Memo HPP- 85-1, Stanford, CA, 1985.
[4] H. Graves, "Interactive design in LEAP," inProc. AAAI Workshop on Automated Software Design, pp. 173-182, 1991.
[5] W. L. Johnson, "Overview of the knowledge-based specification assistant," inProc. 2nd Annual Knowledge-Based Software Assistant Conf., 1987.
[6] W. L. Johnson and D. R. Harris, "Requirements analysis using Aries: Themes and examples," inProc. 5th Annual Knowledge-Based Software Assistant Conf., pp. 121-131, 1990.
[7] M. D. Lubars, "A general design representation,"Tech. Rep. STP- 066-89, MCC, Austin, TX, 1989.
[8] M. D. Lubars, "A general design representation--representing design dependencies in the issue-based information style,"Tech. Rep. STP-426-89, MCC, Austin, TX, 1989.
[9] M. D. Lubars and M. T. Harandi, "The knowledge-based refinement paradigm and IDeA: Concepts, limitations and future directions," inProc. 1988 AAAI Workshop on Automating Software Design, 1988.
[10] R. MacGregor, "The evolving technology of classification-based knowledge representation systems," inPrinciples of Semantic Networks: Explorations in the Representation of Knowledge, John Sowa, Ed. San Mateo, CA: Morgan Kaufmann, 1990.
[11] W. Mark, "Software design memory," inProc. AAAI Workshop on Automated Software Design, pp. 115-120, 1991.
[12] P. Patel-Schneider, "Undecidability of subsumption in NIKL,"Artificial Intelligence, vol. 38, 1989.
[13] R. C. Rich, "A formal representation for plans in the programmer's apprentice," inProc. Seventh International Joint Conf. on AI, pp. 1044-1052, 1981.
[14] R. C. Rich and R. C. Waters, "The programmer's apprentice: A research overview,"IEEE Computer, vol. 21, pp. 10-25, 1988.
[15] J. Schmolze and W. Mark, "The NIKL experience,"Computational Intelligence, vol. 7, pp. 134-159, 1991.
[16] P. G. Selfridge, "Integrating code knowledge with a software information system, " inProc. 5th Annual Knowledge-Based Software Assistant Conf., pp. 183-195, 1990.
[17] R. C. Waters, "The programmers' apprentice: A session with KBEmacs,"IEEE Trans Software Eng., vol. SE-11, no. 11, pp. 1296-1320, Nov. 1985.
[18] W. Woods and Schmolze, "The KL-ONE family,"Harvard Univ. Aiken Computation Laboratory TR-20-90, Cambridge, MA, 1990.

Index Terms:
software development; software modules; constraints; resource consumption; data requirements; Comet system; explicit representation; reasoning; commitments; reuse; sensor-based tracker software; artificial intelligence; knowledge representation; software engineering; software reusability
W. Mark, S. Tyler, J. McGuire, J. Schlossberg, "Commitment-Based Software Development," IEEE Transactions on Software Engineering, vol. 18, no. 10, pp. 870-885, Oct. 1992, doi:10.1109/32.163604
Usage of this product signifies your acceptance of the Terms of Use.