September 1998
Intermediate to advanced
970 pages
18h 42m
English
Imagine a world where architects write volumes of prose describing their buildings instead of drawing blueprints. While such a scenario would certainly be absurd, many software engineers are quick to eschew the software developer's equivalent of blueprints: the class diagram.
Class diagrams are to software development what blueprints are to the world of architecture. Class diagrams are essential for succinctly communicating one's design to others, and Graphic Java uses class diagrams extensively for documenting the classes from the Graphic Java Toolkit and the Abstract Window Toolkit.
The class diagrams throughout Graphic Java are of the Booch variety. [1] For those of you ...
Read now
Unlock full access