Planning the Object Model

This content is no longer actively maintained. It is provided as is, for anyone who may still be using these technologies, with no warranties or claims of accuracy with regard to the most recent product version or service release.

Begin by determining how many objects and collections you need and naming all of them. You may find it helpful to draw the objects and collections in a hierarchical diagram that shows the relationships between them.

List as many of the properties, methods, and events for each object and collection that you can. Denote which properties can be simple module-level variables, which require Property procedures, and which are object properties. Also indicate whether properties should be read-write, read-only, write-only, or write-once.