The technique protects components from outside interference and protects other components from relying on information that may change over time. Components are often encapsulated. The technique of creating applications in which the order of actions is determined by the end user or an external event as opposed to the programmer. The opposite of procedure-oriented programming. The mechanism for sharing behaviors and attributes among objects.
Some components are capable of inheritance.
A software module containing a collection of related data and procedures for operating on that data. Key characteristics of object-oriented systems are encapsulation, inheritance and polymorphism. The ability of objects to handle different types of information and different requests for actions. Components are not typically polymorphic. The traditional approach to application development, in which the sequence of actions is determined by the programmer rather than the end user or another application.