List of Figures

Chapter 1: A Look at How We See the World

Figure 1-1: An order form is an object that contains attributes and behaviors.

Figure 1-2: A supermarket uses a business system and business objects to restock shelves with merchandise.

Chapter 2: What Is a Class?

Figure 2-1: Real-world objects, such as a course-registration form, have attributes and behaviors.

Figure 2-2: A data type is similar to the term a case of baseballs because you and the warehouse manager know the size of a case of baseballs.

Figure 2-3: This figure shows how an instance of the RegistrationForm class reserves memory.

Chapter 3: Encapsulation

Figure 3-1: A class diagram showing attributes and procedures that are encapsulated in the Student class definition.

Figure 3-2: The GradStudent class has attributes and procedures that are the same and some that are different from the Student class.

Chapter 4: Methods and Polymorphism

Figure 4-1: The Display() method in this program is an example of polymorphism.

Chapter 5: Inheritance

Figure 5-1: Simple inheritance consists of one parent-child relationship. Here, the Student class is the parent and the GradStudent class is the child.

Figure 5-2: Multiple inheritance occurs when one class inherits from two other classes.

Figure 5-3: Level inheritance occurs when each class inherits one other class as shown here.

Figure 5-4: Use level inheritance when there is a relationship between two or more parent classes. Here a relationship between Student and Person exists because a student is a person.

Figure 5-5: Use multiple inherits when there isnt a relationship between two or more parent classes. Here there isnt a relationship between Athlete and Writer.

Chapter 6: Abstraction

Figure 6-1: The Student class is the super class and is inherited by the UndergradStudent class and the GradStudent class, which are subclasses.

Figure 6-2: Both subclasses have the same function but each has different functionality.

Figure 6-3: Subclasses must define all abstract methods of the super class.

Figure 6-4: Failure to define the abstract member in a subclass causes a compiler error.

Chapter 7: Identifying and Describing Objects

Figure 7-1: Symbols used to create a processing model

Figure 7-2: A processing model that illustrates how a student registers for a course

Figure 7-3: Class diagrams and the class hierarchy for various student classes

Figure 7-4: tionship diagram of a student entity and a course entity

Figure 7-5: The first level of the leveling diagram shows all the processes involved in how the bursar collects tuition from students.

Figure 7-6: Level 2 of the leveling diagram shows details of the Print Management Reports process from Level 1.

Chapter 8: Real-World Modeling

Figure 8-1: Start with a blank notebook page that contains a preprinted page number.

Figure 8-2: After entering Eric Carruthers on the page, we would note that there isnt a next or previous page because Eric Carruthers is the only name in the book.

Figure 8-3: When we add Rene Winston to the book, we modify Erics page by changing Next from 0

Figure 8-4: When Harry Gee is entered into the book, we modify previous pages to reflect the new addition.

Chapter 9: Collaboration

Figure 9-1: A diagram of the previously described classes

Figure 9-2: The completed sequence diagram of the registration process

Figure 9-3: A UML collaboration diagram

Figure 9-4: The CRC diagram for the Enrollments class

Chapter 10: Case Modeling

Figure 10-1: A simple use case diagram for the registration example

Figure 10-2: A simple flow diagram describing the user interface for the registration example

Figure 10-3: Boxes are used to group sets of one or more data elements.

Chapter 11: Interfaces

Figure 11-1: A typical interface diagram

Figure 11-2: This diagram shows that a class implements the interface.

Figure 11-3: A diagram showing multiple classes that implement an interface

Appendix B: Answers to Quizzes and Final Exam

Figure B-1: The relationship between the Person object and objects that are persons