Debug and trace Rational Software Architect patterns and transformations
Techniques for effective problem determination
From the developerWorks archives
Date archived: May 15, 2019 | First published: April 25, 2006
Although highly effective, the IBM Rational® Software Architect pattern and transformation engines can be a bit overwhelming. As in all software development, patterns and transformations require testing after implementation. Problems are almost always inevitable. In this article, learn about two well-known Eclipse techniques for problem determination, tracing and debug, for patterns and transformations. And explore standard practices for pattern authoring and packaging, to enable you to help yourself and to assist support teams when necessary.
This content is no longer being updated or maintained. The full article is provided "as is" in a PDF file. Given the rapid evolution of technology, some content, steps, or illustrations may have changed.