Term
|
Definition
| Illustrates Concept: Objects |
|
|
Term
| Feature: Bob's date of birth is June 1, 1980, gender: male, and hair: black. |
|
Definition
| Illustrates Concept: Properties |
|
|
Term
| Feature: Bob is an instance of the Programmer class. |
|
Definition
| Illustrates Concept: Class (in classical OOP) |
|
|
Term
| Feature: Bob is based on another object, called Programmer. |
|
Definition
| Illustrates Concept: Prototype (in prototypal OOP) |
|
|
Term
| Feature: Bob holds data (such as birth_date) and methods that work with the data (such as calculateAge()). |
|
Definition
| Illustrates Concept: Encapsulation |
|
|
Term
| Feature: You don't need to know how the calculation method works internally. The object might have some private data, such as the number of days in February in a leap year. You don't know, nor do you want to know. |
|
Definition
| Illustrates Concept: Information Hiding |
|
|
Term
| Feature: Bob is part of a WebDevTeam object, together with Jill, a Designer object, and Jack, a ProjectManager object. |
|
Definition
| Illustrates Concept: Aggregation and composition |
|
|
Term
| Designer, ProjectManager, and Programmer are all based on and extend a Person object. |
|
Definition
| Illustrates Concept: Inheritance |
|
|
Term
| You can call the methods Bob.talk(), Jill.talk(), and Jack.talk() and they'll all work fine, albeit producing different results (Bob will probably talk more about performance, Jill about beauty, and Jack about deadlines). Each object inherited the method talk from Person and customized it. |
|
Definition
| Illustrates Concept: Polymorphism and method overriding |
|
|
