Much has been said about the strengths of object-oriented methods. Claims of higher productivity, easier development, greater robustness, and ease of maintenance are often made. However, experts often warn of the need for a “paradigm shift.” It takes a very different mindset to be comfortable with the object-oriented concepts, and people who learned to develop software in the “good old days” often have a difficult time making the transition. I found all of this to be true. After all was said and done, I like the design that resulted and am now a happy convert to object-oriented methods. But I found that the transition … the paradigm shift … IS difficult; much more so than I had expected. There were also plenty of surprises along the way. So, rather than viewing this paper as a tutorial or as yet another sales pitch for object orientation, it's better to view it as a report back from the front lines — a chronicle of one practitioner, attempting to reduce theory to practice on a non-trivial problem of real, practical interest.