- Objects, Components, and COM
- Abstraction and Class Modeling
- Encapsulation
- Polymorphism
- Inheritance
- Association Relationships
- One-to-One Relationships
- One-To-Many Relationships
- Class and Object Naming Conventions
- Component-Based Development
- Component-Based Development and COM
- COM-Definable Entities
- Component Coupling
- Summary
Class and Object Naming Conventions
Throughout our discussions in this chapter, we have been alluding to a naming convention for classes and objects without having given any formal definitions. Although the naming convention is arbitrary, it is important to decide on one and adhere to it throughout all phases of the project. This will not only provide a degree of standardization across multiple developers, but also make it easier for developers and maintainers to understand the code without the need for an abundant supply of comments. Standardization is important in classes and objects because the two are often confused. In our examples and throughout the remainder of this book, we will be using an uppercase C prefix to denote a class. Similarly, we will be using an uppercase O prefix for an object. Furthermore, we will be using the same suffix for both the class and its object instances, as in the case of the CPerson class and its OPerson instances. For example:
Set OPerson = New CPerson