Object Oriented Programming and UML Implementation modeling is “the development stage for adding fine details to a model that transcend languages. Implementation modeling is the immediate precursor to the actual implementation.”(Blaha & Rambaugh, 2005) Implementation modeling uses the following four steps: fine-tune classes, fine-tune generalizations, realize associations, and preparing for testing. Steps one and two are driven by the theory of transformations. Transformations “is a mapping from the domain of models to the range of models”(Blaha & Rambaugh, 2005) The first step in implementation modeling is fine-tuning classes. It is best to fine-tune classes before writing code because it will help to simplify development or to improve performance. If for some reason you have to alter the design first consider the following possibilities; partition a class, merge classes, partition or merge attributes, or promote an attribute or demote a class. The next step in implementation modeling is fine-tuning generalizations. It is helpful to remove generalization or to add one prior to coding. The third step is realizing associations. This is what holds the class model together by providing paths between objects. The final step is testing. “Testing is a quality assurance mechanism for catching residual errors.” (Blaha & Rambaugh, 2005) It also measures the quality of your software. “Implementation is the final development stage that addresses the specifics of programming languages.” (Blaha & Rambaugh, 2005) There are four steps to follow in the implementation model: fine-tune classes, fine-tune generalizations, realize associations, and preparing for testing. “It is relatively easy to implement an OO design with an OO language, since language constructs are similar to design constructs.” (Blaha & Rambaugh, 2005) “A major goal