This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
Representing Software Engineering Models: The TAME Goal Oriented Approach
October 1992 (vol. 18 no. 10)
pp. 886-898

A methodology and a knowledge representation and reasoning framework for top-down goal-oriented characterization, modeling, and execution of software engineering activities is presented. A prototype system (ES-TAME) which demonstrates the underlying knowledge representation and reasoning principles is described. ES-TAME provides an object-oriented metamodel concept that provides support for tailorable and reusable software engineering models (SEMs). It provides the basic mechanisms, functions, and attributes for all the other models. It is based on interobject relationships, dynamic viewpoints, and selective inheritance in addition to traditional object-oriented mechanisms. Descriptive SEMs include representations for basic software engineering activities. They are controlled and made operational by active GQM (goal-question-metric paradigm) models which are built by a systematic mechanism for defining and evaluating project and corporate goals and using measurement to provide feedback in real-time.

[1] J. Banerjeeet al., "Data model issues for object-oriented applications,"ACM Trans. Office Information Systems, Jan. 1987.
[2] V.R. Basili, "Quantitative evaluation of software engineering methodology," Keynote address, First Pan Pacific Computer Conf., Sept. 1985 (also available asTech. Rep., TR-1519, Dept. Computer Science, Univ. Maryland, College Park, July 1985.
[3] V.R. Basili and H.D. Rombach, "TAME: Integrating measurement into software environments,"Computer Science Tech. Rep. Series, (CS-TR- 1764), Univ. Maryland, College Park, June 1987.
[4] V.R. Basili and H.D. Rombach, "The Tame Project: Towards Improvement-Oriented Software Environments,"IEEE Trans. Software Eng., Vol. SE-14, No. 6, June 1988, pp. 758-773.
[5] V.R. Basili, "Software Development: A Paradigm for the Future,"Proc. Compsac 89, IEEE Computer Soc. Press, Los Alamitos, Calif., Order No. 1964, pp. 471-485.
[6] V.R. Basili and H.D. Rombach, "Support for comprehensive reuse,"IEE Software Engineering J., Sept. 1991.
[7] K. Bennet and D. White, "The knowledge-based software assistant, Overview," inProc. Second Annual Knowledge-Based Software Assistant Conf., pp. 13-24, Jan. 1988.
[8] G. Booth,Object-Oriented Design with Applications. Redwood City, CA: Benjamin Cummings, 1991.
[9] C. Chamberset al., "An efficient implementation of SELF, a dynamically-typed object-oriented language based on prototypes," inProc. ACM Conf. on OOPSLA, pp. 49-70, Oct. 1989.
[10] R. Fikes and T. Kehler, "The role of frame-based representation in reasoning,"Commun. ACM, vol. 28, pp. 904-920, Sept. 1985.
[11] A. Goldberg and D. Robson,Smalltalk80: The Language and Its Implementation. Reading, MA: Addison-Wesley, May 1983.
[12] C. Greenet al., "Report on a knowledge-based software assistant," Kestrel Institute Technical Report, 1983.
[13] U. Hahnet al., "Teamwork support in a knowledge-based information systems environment,"IEEE Trans. Software Eng., pp. 467-482, May 1991.
[14] B. Hailpern and H. Ossher, "Extending objects to support multiple interfaces and access control,"IEEE Trans. Software Eng., vol. 16, pp. 1247-1257, Nov. 1990.
[15] W.H. Harrisonet al., "Good news, bad news: Experience building a software development environment using the object-oriented paradigm," inProc. ACM Conf. OOPSLA, pp. 85-94, Oct. 1989.
[16] IntelliCorp, KEE Software Development System User's Manual, 1986.
[17] IntelliCorp, 1986, Kappa System User's Manual.
[18] G.E. Kaiser, "Intelligent assistance for software development and maintenance,"IEEE Software, vol. 5, pp. 40-49, May 1988.
[19] W. Kimet al., "Composite object support in an object-oriented database system," inProc. ACM Conf. OOPSLA, pp. 118-125, Oct. 1987.
[20] M. Lubars and M. Harandi, "The knowledge-based refinement paradigm and IDeA: Concepts, limitations, and future directions," inProc. Workshop on Automating Software Design, AAAI-88, pp. 98-103, 1988.
[21] B. Meyers,Object Oriented Software Construction. Englewood Cliffs, NJ: Prentice-Hall, 1988.
[22] P. Mi and W. Scacchi, "A knowledge-based environment for modeling and simulating software engineering processes,"IEEE Trans. Knowledge and Data Eng., vol. 2, pp. 283-294, Sept. 1990.
[23] M. Oivo, "Knowledge-based support for embedded computer software analysis and design," Tech. Research Centre of Finland, VTT Publications 68, 1990.
[24] P. Puncello, "ASPIS: A knowledge-based CASE environment,"IEEE Software, pp. 58-65, Mar. 1988.
[25] C. Rich and R.C. Waters,The Programmer's Apprentice. Reading, MA: Addison-Wesley, and Baltimore, MD: ACM Press, 1990.
[26] A. Sathiet al., "Representation of activity knowledge for project management,IEEE Trans. Pattern Analysis and Machine Intell., vol. PAMI-7, pp. 531-552, Sept. 1985.
[27] C. Schaffertet al., "An introduction to Trellis/Owl," in [50], pp. 9-16.
[28] A.H. Skarra and S.B. Zdonik, "The management of changing types in an object-oriented database," inProc. ACM Conf. OOPSLA, pp. 483-495, Sept. 1986.
[29] A. Snyder, "Encapsulation and inheritance in object-oriented programming languages," inProc. ACM Conf. OOPSLA, pp. 38-45, Sept. 1986.
[30] M. Stefik and D. G. Babrow, "Object-oriented programming: Themes and variations,"AI Mag., vol. 6, no. 4, pp. 40-62, Dec. 1985.
[31] B. Stroustrup,The C++ Programming Language. Reading, MA: Addison-Wesley, 1986.
[32] D. Ungar and R. Smith, "SELF: The power of simplicity," inProc. ACM Conf. OOPSLA, pp. 227-241, Oct. 1987.
[33] P. T. Ward and S. J. Mellor,Structured Development for Real-Time Systems. New York: Yourdon, 1985.
[34] P. Wegner, "Concepts and paradigms of object-oriented programming," Expansion of Oct. 4 OOPSLA-89 Keynote Address,OOPS Messenger, vol. 1, pp. 7-87, Aug. 1990.
[35] J.C. Wileden. "This is IT: A meta-model of the software process,"ACM SIGSOFT Software Engineering Notes, vol. 11, pp. 11-16, Aug. 1986.

Index Terms:
software engineering models representation; TAME goal oriented approach; knowledge representation; reasoning framework; top-down goal-oriented characterization; modeling; prototype system; ES-TAME; object-oriented metamodel concept; reusable software engineering models; dynamic viewpoints; selective inheritance; goal-question-metric paradigm; artificial intelligence; knowledge representation; object-oriented programming; software engineering; software reusability
Citation:
M. Oivo, V.R. Basili, "Representing Software Engineering Models: The TAME Goal Oriented Approach," IEEE Transactions on Software Engineering, vol. 18, no. 10, pp. 886-898, Oct. 1992, doi:10.1109/32.163605
Usage of this product signifies your acceptance of the Terms of Use.