By Topic

Using extended general statecharts to generate test cases for overloaded/polymorphic object-oriented programs: a case study

Sign In

Cookies must be enabled to login.After enabling cookies , please use refresh or reload or ctrl+f5 on the browser for the login options.

Formats Non-Member Member
$31 $13
Learn how you can qualify for the best price for this item!
Become an IEEE Member or Subscribe to
IEEE Xplore for exclusive pricing!
close button

puzzle piece

IEEE membership options for an individual and IEEE Xplore subscriptions for an organization offer the most affordable access to essential journal articles, conference papers, standards, eBooks, and eLearning courses.

Learn more about:

IEEE membership

IEEE Xplore subscriptions

3 Author(s)
Bor-Yuan Tsai ; Sch. of Comput. & Inf. Syst., Sunderland Univ., UK ; Stobart, S. ; Parrington, N.

There are two particular theories in object oriented programming languages: overloading and polymorphism. When a program has either of these two specialities and is depicted with a statechart, problems arise because different transition arcs are labelled with the same name but represent different duties on that statechart. What we call “general statecharts” (GS) can be used as a pattern to model the overloading and polymorphism aspect of C++ programs. Furthermore, method functions can be mapped to general statecharts to form extended general statechart (EGS). From these, state/transition trees can be generated easily

Published in:

Technology of Object-Oriented Languages, 1997. TOOLS 24. Proceedings

Date of Conference:

Sep 1997