1. Object Oriented Concepts Recap OOP

2. The four Pillars of OOP Abstraction Encapsulation Inheritance Polymorphism

3. Abstraction A process that has the designer ask what instead of how – What is it you want to do with the data – What will be done to the data The designer does not consider how the class's methods will accomplish their goals The client interface is the what The implementation is the how

4. Encapsulation Hides the fine detail of the inner workings of the class – The implementation is hidden – Often called "information hiding" Part of the class is visible – The necessary controls for the class are left visible – The class interface is made visible – The programmer is given only enough information to use the class

5. 1-5 Inheritance Inheritance allows a software developer to derive a new class from an existing one The existing class is called the parent class, or superclass, or base class The derived class is called the child class or subclass As the name implies, the child inherits characteristics of the parent That is, the child class inherits the methods and data defined by the parent class

6. Polymorphism The term polymorphism literally means “having many forms” A polymorphic reference is a variable that can refer to different types of objects at different points in time The method invoked through a polymorphic reference can change from one invocation to the next All object references in Java are potentially polymorphic

7. Polymorphism Suppose we create the following reference variable Occupation job; Java allows this reference to point to an Occupation object, or to any object of any compatible type This compatibility can be established using inheritance or using interfaces Careful use of polymorphic references can lead to elegant, robust software designs

8. Inheritance Basics When creating a new class – Look for classes which already have some of what you need – Use definition of that class in the new class This is called inheritance – New class inherits properties and behaviors of existing class

9. Inheritance Basics A class can have only one superclass – Vehicle is superclass to AirVehicle A class can have many subclasses – Jet and Kite are subclasses to AirVehicle Inheritance defines an “is-a” relationship – A Wagon object “is-a” LandVehicle object

10. Inheritance 1-10 Inheritance relationships are shown in a UML class diagram using a solid arrow with an unfilled triangular arrowhead pointing to the parent class Proper inheritance creates an is-a relationship, meaning the child is a more specific version of the parent

11. Inheritance Basics Figure 16-5 A hierarchy of classes

12. 1-12 Inheritance A programmer can tailor a derived class as needed by adding new variables or methods, or by modifying the inherited ones Software reuse is a fundamental benefit of inheritance By using existing software components to create new ones, we capitalize on all the effort that went into the design, implementation, and testing of the existing software

13. 1-13 Deriving Subclasses Java uses the reserved word extends to establish an inheritance relationship class Car extends Vehicle { // class contents }

14. 1-14 Words.java //******************************************************************** // Words.java Java Foundations // // Demonstrates the use of an inherited method. //******************************************************************** public class Words { //----------------------------------------------------------------- // Instantiates a derived class and invokes its inherited and // local methods. //----------------------------------------------------------------- public static void main (String[] args) { Dictionary webster = new Dictionary(); System.out.println ("Number of pages: " + webster.getPages()); System.out.println ("Number of definitions: " + webster.getDefinitions()); System.out.println ("Definitions per page: " + webster.computeRatio()); }

15. 1-15 Book.java //******************************************************************** // Book.java Java Foundations // // Represents a book. Used as the parent of a derived class to // demonstrate inheritance. //******************************************************************** public class Book { protected int pages = 1500; //---------------------------------------------------------------- // Pages mutator. //---------------------------------------------------------------- public void setPages (int numPages) { pages = numPages; } //---------------------------------------------------------------- // Pages accessor. //---------------------------------------------------------------- public int getPages () { return pages; }

16. 1-16 Dictionary.java //******************************************************************** // Dictionary.java Java Foundations // // Represents a dictionary, which is a book. Used to demonstrate // inheritance. //******************************************************************** public class Dictionary extends Book { private int definitions = 52500; //----------------------------------------------------------------- // Prints a message using both local and inherited values. //----------------------------------------------------------------- public double computeRatio () { return definitions/pages; } (more…)

17. 1-17 Dictionary.java //---------------------------------------------------------------- // Definitions mutator. //---------------------------------------------------------------- public void setDefinitions (int numDefinitions) { definitions = numDefinitions; } //---------------------------------------------------------------- // Definitions accessor. //---------------------------------------------------------------- public int getDefinitions () { return definitions; }

18. 1-18 Class Diagram for Words

19. 1-19 The protected Modifier Visibility modifiers affect the way that class members can be used in a child class Variables and methods declared with private visibility cannot be referenced by name in a child class They can be referenced in the child class if they are declared with public visibility – but public variables violate the principle of encapsulation There is a third visibility modifier that helps in inheritance situations: protected

20. 1-20 The protected Modifier The protected modifier allows a child class to reference a variable or method directly in the child class It provides more encapsulation than public visibility, but is not as tightly encapsulated as private visibility A protected variable is visible to any class in the same package as the parent class The details of all Java modifiers are discussed in Appendix E Protected variables and methods can be shown with a # symbol preceding them in UML diagrams

21. 1-21 The super Reference Constructors are not inherited, even though they have public visibility Yet we often want to use the parent's constructor to set up the “parent's part” of the object The super reference can be used to refer to the parent class, and often is used to invoke the parent's constructor

22. 1-22 Words2.java //******************************************************************** // Words2.java Java Foundations // // Demonstrates the use of the super reference. //******************************************************************** public class Words2 { //----------------------------------------------------------------- // Instantiates a derived class and invokes its inherited and // local methods. //----------------------------------------------------------------- public static void main (String[] args) { Dictionary2 webster = new Dictionary2 (1500, 52500); System.out.println ("Number of pages: " + webster.getPages()); System.out.println ("Number of definitions: " + webster.getDefinitions()); System.out.println ("Definitions per page: " + webster.computeRatio()); }

23. 1-23 Book2.java //******************************************************************** // Book2.java Java Foundations // // Represents a book. Used as the parent of a derived class to // demonstrate inheritance and the use of the super reference. //******************************************************************** public class Book2 { protected int pages; //---------------------------------------------------------------- // Constructor: Sets up the book with the specified number of // pages. //---------------------------------------------------------------- public Book2 (int numPages) { pages = numPages; } (more…)

24. 1-24 Book2.java //---------------------------------------------------------------- // Pages mutator. //---------------------------------------------------------------- public void setPages (int numPages) { pages = numPages; } //---------------------------------------------------------------- // Pages accessor. //---------------------------------------------------------------- public int getPages () { return pages; }

25. 1-25 Dictionary2.java //******************************************************************** // Dictionary2.java Java Foundations // // Represents a dictionary, which is a book. Used to demonstrate // the use of the super reference. //******************************************************************** public class Dictionary2 extends Book2 { private int definitions; //----------------------------------------------------------------- // Constructor: Sets up the dictionary with the specified number // of pages and definitions. //----------------------------------------------------------------- public Dictionary2 (int numPages, int numDefinitions) { super(numPages); definitions = numDefinitions; } (more…)

26. 1-26 Dictionary2.java //----------------------------------------------------------------- // Prints a message using both local and inherited values. //----------------------------------------------------------------- public double computeRatio () { return definitions/pages; } //---------------------------------------------------------------- // Definitions mutator. //---------------------------------------------------------------- public void setDefinitions (int numDefinitions) { definitions = numDefinitions; } //---------------------------------------------------------------- // Definitions accessor. //---------------------------------------------------------------- public int getDefinitions () { return definitions; }

27. 1-27 The super Reference A child’s constructor is responsible for calling the parent’s constructor The first line of a child’s constructor should use the super reference to call the parent’s constructor The super reference can also be used to reference other variables and methods defined in the parent’s class

28. 1-28 Multiple Inheritance Java supports single inheritance, meaning that a derived class can have only one parent class Multiple inheritance allows a class to be derived from two or more classes, inheriting the members of all parents Collisions, such as the same variable name in two parents, have to be resolved Java does not support multiple inheritance In most cases, the use of interfaces gives us aspects of multiple inheritance without the overhead

29. 1-29 Multiple Inheritance

30. 1-30 Overriding Methods A child class can override the definition of an inherited method in favor of its own The new method must have the same signature as the parent's method, but can have a different body The type of the object executing the method determines which version of the method is invoked

31. 1-31 Messages.java //******************************************************************** // Messages.java Java Foundations // // Demonstrates the use of an overridden method. //******************************************************************** public class Messages { //----------------------------------------------------------------- // Creates two objects and invokes the message method in each. //----------------------------------------------------------------- public static void main (String[] args) { Thought parked = new Thought(); Advice dates = new Advice(); parked.message(); dates.message(); // overridden }

32. 1-32 Thought.java //******************************************************************** // Thought.java Java Foundations // // Represents a stray thought. Used as the parent of a derived // class to demonstrate the use of an overridden method. //******************************************************************** public class Thought { //----------------------------------------------------------------- // Prints a message. //----------------------------------------------------------------- public void message() { System.out.println ("I feel like I'm diagonally parked in a " + "parallel universe."); System.out.println(); }

33. 1-33 Advice.java //******************************************************************** // Advice.java Java Foundations // // Represents some thoughtful advice. Used to demonstrate the use // of an overridden method. //******************************************************************** public class Advice extends Thought { //----------------------------------------------------------------- // Prints a message. This method overrides the parent's version. //----------------------------------------------------------------- public void message() { System.out.println ("Warning: Dates in calendar are closer " + "than they appear."); System.out.println(); super.message(); // explicitly invokes the parent's version }

34. 1-34 Overriding A method in the parent class can be invoked explicitly using the super reference If a method is declared with the final modifier, it cannot be overridden The concept of overriding can be applied to data and is called shadowing variables Shadowing variables should be avoided because it tends to cause unnecessarily confusing code

35. 1-35 Overloading vs. Overriding Overloading deals with multiple methods with the same name in the same class, but with different signatures Overriding deals with two methods, one in a parent class and one in a child class, that have the same signature Overloading lets you define a similar operation in different ways for different parameters Overriding lets you define a similar operation in different ways for different object types

36. Class Hierarchies 1-36 A child class of one parent can be the parent of another child, forming a class hierarchy

37. 1-37 Class Hierarchies Two children of the same parent are called siblings Common features should be put as high in the hierarchy as is reasonable An inherited member is passed continually down the line Therefore, a child class inherits from all its ancestor classes There is no single class hierarchy that is appropriate for all situations

38. 1-38 An Alternate Class Hierarchy

39. The Class Object Figure 16-6 Object is an ancestor class of all other classes

40. The Class Object Class Object defines some methods which all classes inherit – Example: toString and equals Usually these must be redefined for a given class to do what is desired – Method equals defined by Object looks for two objects being identical

41. 1-41 The Object Class A class called Object is defined in the java.lang package of the Java standard class library All classes are derived from the Object class If a class is not explicitly defined to be the child of an existing class, it is assumed to be the child of the Object class Therefore, the Object class is the ultimate root of all class hierarchies

42. 1-42 The Object Class The Object class contains a few useful methods, which are inherited by all classes For example, the toString method is defined in the Object class Every time we define the toString method, we are actually overriding an inherited definition The toString method in the Object class is defined to return a string that contains the name of the object’s class along with some other information

43. 1-43 The Object Class The equals method of the Object class returns true if two references are aliases We can override equals in any class to define equality in some more appropriate way As we've seen, the String class defines the equals method to return true if two String objects contain the same characters The designers of the String class have overridden the equals method inherited from Object in favor of a more useful version

44. The Class Object New class must “redefine” what is intended by equals Figure 16-7 joyce1 is identical to its alias joyce3, but joyce1 equals joyce2

45. 1-45 Abstract Classes An abstract class is a placeholder in a class hierarchy that represents a generic concept An abstract class cannot be instantiated We use the modifier abstract on the class header to declare a class as abstract: public abstract class Product { // contents }

46. 1-46 Abstract Classes An abstract class often contains abstract methods with no definitions (like an interface) Unlike an interface, the abstract modifier must be applied to each abstract method Also, an abstract class typically contains non- abstract methods with full definitions A class declared as abstract does not have to contain abstract methods – simply declaring it as abstract makes it so

47. 1-47 Abstract Classes The child of an abstract class must override the abstract methods of the parent, or it too will be considered abstract An abstract method cannot be defined as final or static The use of abstract classes is an important element of software design – it allows us to establish common elements in a hierarchy that are too generic to instantiate

48. 1-48 An Abstract Class in UML Abstract classes and methods are shown in italics font.

49. 1-49 Interface Hierarchies Inheritance can be applied to interfaces as well as classes That is, one interface can be derived from another interface The child interface inherits all abstract methods of the parent A class implementing the child interface must define all methods from both the ancestor and child interfaces Note that class hierarchies and interface hierarchies are distinct (they do not overlap)

50. 1-50 Visibility Revisited It's important to understand one subtle issue related to inheritance and visibility All variables and methods of a parent class, even private members, are inherited by its children As we've mentioned, private members cannot be referenced by name in the child class However, private members inherited by child classes exist and can be referenced indirectly

51. 1-51 Visibility Revisited Because the parent can refer to the private member, the child can reference it indirectly using its parent's methods The super reference can be used to refer to the parent class, even if no object of the parent exists

52. 1-52 FoodItem.java //******************************************************************** // FoodItem.java Java Foundations // // Represents an item of food. Used as the parent of a derived class // to demonstrate indirect referencing. //******************************************************************** public class FoodItem { final private int CALORIES_PER_GRAM = 9; private int fatGrams; protected int servings; //----------------------------------------------------------------- // Sets up this food item with the specified number of fat grams // and number of servings. //----------------------------------------------------------------- public FoodItem (int numFatGrams, int numServings) { fatGrams = numFatGrams; servings = numServings; } (more…)

53. 1-53 FoodItem.java //----------------------------------------------------------------- // Computes and returns the number of calories in this food item // due to fat. //----------------------------------------------------------------- private int calories() { return fatGrams * CALORIES_PER_GRAM; } //----------------------------------------------------------------- // Computes and returns the number of fat calories per serving. //----------------------------------------------------------------- public int caloriesPerServing() { return (calories() / servings); }

54. 1-54 8.4 – Pizza.java //******************************************************************** // Pizza.java Java Foundations // // Represents a pizza, which is a food item. Used to demonstrate // indirect referencing through inheritance. //******************************************************************** public class Pizza extends FoodItem { //----------------------------------------------------------------- // Sets up a pizza with the specified amount of fat (assumes // eight servings). //----------------------------------------------------------------- public Pizza (int fatGrams) { super (fatGrams, 8); }

55. 1-55 8.4 – FoodAnalyzer.java //******************************************************************** // FoodAnalyzer.java Java Foundations // // Demonstrates indirect access to inherited private members. //******************************************************************** public class FoodAnalyzer { //----------------------------------------------------------------- // Instantiates a Pizza object and prints its calories per // serving. //----------------------------------------------------------------- public static void main (String[] args) { Pizza special = new Pizza (275); System.out.println ("Calories per serving: " + special.caloriesPerServing()); }

56. Interface Imagine! Java: Programming Concepts in Context by Frank M. Carrano, (c) Pearson Education - Prentice Hall, 2010

57. Contents Java Interfaces – Writing an Interface – Some UML Details – Implementing an Interface – An Interface as a Data Type – Casting and Interfaces Polymorphism and Interfaces Inheritance Basics – The Class Object – Overriding the Method equals – Polymorphism and Inheritance The Comparable Interface

58. Objectives After studying this you should be able to – Write a Java interface – Represent interfaces and classes using UML notation – Implement an existing Java interface – Use a Java interface as a data type – Describe the concept of polymorphism – Define and use an inner class – Describe the concept of inheritance

59. Objectives After studying this, you should be able to – Describe the class Object – Describe overriding a method definition – Override Object’s method equals within a class – Implement the Comparable interface – Describe some tools that designers use for identifying the classes required to solve a problem – Describe the role of a use case diagram in designing classes

60. Java Interfaces Two parts of a class definition – Client interface – Implementation Figure 16-1 Client communicates with class’s hidden implementation through interface

61. Java Interfaces In definition of a class – Interface and implementation are combined Also possible to create separate Java interface – Contains some or all of headers of methods – Can include public named constants Then different classes can be created to implement the interface

62. Writing an Interface Begins with reserved word interface Contains any number of headers – Followed by a semicolon File name end with.java Must not have constructors View interface Measureable, Listing 16-1Listing 16-1 View interface NameInterface, Listing 16-2 Listing 16-2.htm code listing files must be in the same folder as the.ppt files for these links to work

63. Some UML Details UML declaration for interfaces similar to that of classes – Precede name with > Figure 16-2 UML notation for the interface Measurable

64. Some UML Details Figure 16-3 UML notation for the interface NameInterface

65. Implementing an Interface Begin with implements clause – If implementing multiple classes, specify with comma separated list Design of interface specifies methods for another programmer Implementing interface is a guarantee that certain methods have been defined

66. Implementing an Interface Figure 16-4 A UML class diagram for the ShapesDemo program

67. Implementing an Interface View source code of implementation Listing 16-3 Listing 16-3 – Class Square implements Measurable Consider another implementation of Measureable, Listing 16-4Listing 16-4 – Class Circles Now view program which uses both classes, Listing 16-5 Listing 16-5

68. An Interface as a Data Type Possible to use an interface as a data type Ensures method’s argument able to receive calls to all methods declared in NameInterface. Implementation must use same method header

69. An Interface as a Data Type View example class, Listing 16-6Listing 16-6 – Class ShapeWriter – A class to display any object which implements Measurable Note program which uses this display class, Listing 16-7 Listing 16-7

70. Casting and Interfaces Conversion from a class type to an interface type is legal Conversion from an interface type to a class type requires a cast

71. Polymorphism and Interfaces Consider the declaration Measurable shape; Variable shape is a reference variable Can reference – Any object, of any class – That implements Measurable Dynamic binding ensures – shape “knows” what type it is pointing to

72. Overriding versus Overloading Overridden methods have same signature and return type Overridden methods must be in different classes that are related by inheritance. Overloaded methods have different signatures but same name. Overloaded methods are in either same class or different classes related by inheritance.

73. Overriding Method equals Making equals foolproof

74. Polymorphism and Inheritance When a class defines its own version of a method – It overrides the inherited method Polymorphism guarantees that the correct version of a method is used – The reference variable pointing to the object “knows” which type of object it points to – Accomplished via dynamic binding

75. Extending an Interface Possible to define a new interface using inheritance – “Extend” a previously defined interface A new interface may extend multiple other interfaces

76. The Comparable Interface Any class with method compareTo implements the following interface View implementation in class Circle Listing 16-8 Listing 16-8