Object oriented CASE: The TPS life cycle evolution

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.<
>