Object oriented CASE: The TPS life cycle evolution

Author

Ellis, Monty

Author_Institution

NCR, Peachtree City, GA, USA

fYear

1993

fDate

20-23 Sep 1993

Firstpage

49

Lastpage

53

Abstract

The emergence of object-oriented (O-O) test program set (TPS) development is the result of increased demands for productivity, quality, and portability. While rewards of O-O software development are substantial they are not accomplished by simply switching to an O-O language. O-O software development necessitates an evolution of the traditional Test Program Set (TPS) life cycle. Developers must learn and adjust to O-O methodologies. They must have tools to have manage the process, promote O-O thinking, and automate the object-oriented TPS life cycle. TPS developers with an eye on the future are currently using or evaluating O-O computer aided software engineering (CASE) tools. This paper addresses the TPS life cycle evolution that results from implementing O-O technology and what to look for in the evaluation of O-O CASE tools

Keywords

automatic test software; computer aided software engineering; object-oriented methods; CASE; TPS life cycle evolution; Test Program Set; computer aided software engineering; life cycle; object oriented test porgram; polymorphism; portability; productivity; quality; software development; Cities and towns; Computer aided software engineering; Encapsulation; Life testing; Microprocessors; Productivity; Programming; Road transportation; System testing; User interfaces;

fLanguage

English

Publisher

ieee

Conference_Titel

AUTOTESTCON '93. IEEE Systems Readiness Technology Conference. Proceedings

Conference_Location

San Antonio, TX

Print_ISBN

0-7803-0646-5

Type

conf

DOI

10.1109/AUTEST.1993.396369

Filename

396369