ChiMu OO and Java Development:
Guidelines and Resources
v1.8 [mlf-980228]
Overview
This document provides guidelines and resources for developers and teams building Object-Oriented (OO) and Java based software systems. The materials include:
- An Introduction to OO terminology and concepts
- Guidelines for OO/Java systems
- Definitions for common OO terms
- References to other good OO resources
This document is meant to both provide an integration of the many resources available for OO and also to serve as a jumping point into these other resources.
Prerequisites
Some familiarity with OO and Java is required for this material to be understandable. There are many introductory books on Java that focus on different types of reader background (and new books are added every month). For OO itself you may want to consider one of the following books:
|
Designing Object-Oriented Software
|
Wirfs-Brock+WW 90 |
|
Object-Oriented Analysis and Design with Applications.
|
Booch 94 |
|
Object-Oriented Modeling and Design.
|
Rumbaugh+BPEL 91 |
|
Object-Oriented Software Engineering: A Use Case Driven Approach.
|
Jacobson+CJO 92 | For Java-oriented OO, consider:
|
Java Design: Building Better Apps & Applets
|
Coad+M 96 |
|
Understanding UML: The Developer’s Guide
|
Harmon+W 98 | There are also many materials available on the WWW. See the JavaSoft web site or Yahoo links under Java.
Related Resources
This document does not define standards but provides resources and guidelines that can be chosen as part of a team’s standards. A common approach would be to define a separate standards document — along with useful supporting materials like code templates, UML examples, and CASE templates — that priorities guidelines, makes them more concrete, and fills in gaps that are important to a development team. ChiMu uses this approach internally and recommends it to clients.
Attributions
This document collects information from several different sources, which are indicated by footnotes and citations. The Guidelines chapter aggregates several authors’ works together. To make the attribution easier to maintain after changes, the sources for a guideline is indicated underneath the guideline, with the first entry being the primary copyright owner for the particular wording. Subsequent entries are conceptual originators for the guideline. Unless otherwise noted, the original source is this document or another of ChiMu’s documents.
Special notice and thanks go to Doug Lea for allowing the inclusion of his guidelines within
this document. See
http://gee.cs.oswego.edu/dl/html/javaCodingStd.html
for the original version.
Table of Contents
Other Versions
| 
