We have one object (to code) for this example challenge -- "Drawing".

This is a high level look at our work TO-DO list.

We now browse through our toolbox of available code looking for components that may help us solve the challenge.

We simply list methods for the components we need to code (our TO-DO list).

The list shows us we have one class and about ten methods to code.

From our available toolbox components, we select "Frame" and "Drawable" as viable candidates for reuse.

Duplication alert! We do not want to reinvent the duplicate methods.

We should try to use the available component "Frame".

We do yes have any ideas for reuse by composition. In the previous step, we decided that we should try to reuse a component of type "Frame".

Frame is reasonable child (ivar) of "Drawing", so we show that here in an odiagram.

We now jot down a class diagram.

We do not have any ideas for reuse by inheritance, so we note that.

Just for demo purposes if we did have inheritance in the game, we would show that something like is shown here.

A superclass (Drawing in this case) with whatever subclasses we come up with.

Here is our method listing.

Almost all our methods are delegated.

At this point, we can iterate on the document, or begin coding.

To begin coding, we would start with object structure using the object and class diagrams.