interfaces need arising from software engineering –disparate groups of programmers need to agree...

34
Interfaces Need arising from software engineering Disparate groups of programmers need to agree to a “contract” that spells out how their software interacts Write your own code without seeing the implementation of other classes (by other programmers) – An Interface is such a “contract” An interface declares a type of object by specifying what the object does Doesn’t care about the implementation Only what functionality is provided Specifies common operations

Upload: aubrey-scott

Post on 27-Dec-2015

217 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: Interfaces Need arising from software engineering –Disparate groups of programmers need to agree to a “contract” that spells out how their software interacts

Interfaces

• Need arising from software engineering– Disparate groups of programmers need to agree to a

“contract” that spells out how their software interacts

– Write your own code without seeing the implementation of other classes (by other programmers)

– An Interface is such a “contract”

• An interface declares a type of object by specifying what the object does– Doesn’t care about the implementation

– Only what functionality is provided

– Specifies common operations

Page 2: Interfaces Need arising from software engineering –Disparate groups of programmers need to agree to a “contract” that spells out how their software interacts

Example

Car manufacturers

Car: start, stop, accelerate, turn right, …

Guidance manufacturers

Invoke the car methods for navigation

There has to be an industry standard as to which methods should be implemented by all car manufacturers

Page 3: Interfaces Need arising from software engineering –Disparate groups of programmers need to agree to a “contract” that spells out how their software interacts

Another motivation

• Multiple inheritance– A class inherits from more than one parents

• A Dog can be both an Animal and a Speaker

• Jack can be both a Person and an Employee

– In C++, a class can inheritance from more than one classes

– In Java, multiple inheritance is done through multiple interfaces

Page 4: Interfaces Need arising from software engineering –Disparate groups of programmers need to agree to a “contract” that spells out how their software interacts

Interfaces

• A collection of constants and abstract methods – without any implementation!

• Different from abstract classes– Abstract class can also have variables and non-abstract methods

(with implementation).

public interface Animal{

int LEGS=4; // constants

public void sleep(); // abstract methods

. . .

}

Note:

• No {} in the method declaration – no implementation

• The word “abstract” is not needed

Page 5: Interfaces Need arising from software engineering –Disparate groups of programmers need to agree to a “contract” that spells out how their software interacts

Use an Interface

• Writing a class the implements an interface– Provides implementation for each method defined in the

interface

• An interface cannot be instantiated

public class Dog implements Animal{

public void sleep(){

System.out.println(“Snorrrr”);

}

}

not extends!

Page 6: Interfaces Need arising from software engineering –Disparate groups of programmers need to agree to a “contract” that spells out how their software interacts

Multiple Inheritance

interface Speaker{

public void speak();

}

interface Animal{

final int LEGS=4;

public void sleep();

}

class Dog implements Speaker, Animal {

public void speak(){

System.out.println("woof");

}

public void sleep(){

System.out.println("snorrrr");

}

public String toString(){

String s="This Dog has " + LEGS + " legs.";

return s;

}

}

Page 7: Interfaces Need arising from software engineering –Disparate groups of programmers need to agree to a “contract” that spells out how their software interacts

class Teacher implements Speaker{

private String thoughts;

public Teacher (String t) {

thoughts=t;

}

public void speak () {

System.out.println(thoughts);

}

public void repeat() {

for (int i=1; i<=3; i++)

System.out.println(thoughts);

}

}

public class ExInterfaces {

public static void main(String[] args){

Dog little = new Dog();

little.speak();

little.sleep();

System.out.println(

little.toString() );

Teacher tom = new Teacher("Do your homework");

tom.speak();

tom.repeat();

}

}

Page 8: Interfaces Need arising from software engineering –Disparate groups of programmers need to agree to a “contract” that spells out how their software interacts

Converting Between Class and Interface Types

• Very similar to the case of converting between superclass and subclass references– Converting from class to interface reference

Teacher t = new Teacher();

Speaker sp = t; //OK…

method: public void test(Speaker speaker){…} You can call this method by test(t); sp.repeat(); //Error

– Converting from interface reference to class referenceTeacher teacher = (Teacher) sp;t.repeat();

Page 9: Interfaces Need arising from software engineering –Disparate groups of programmers need to agree to a “contract” that spells out how their software interacts

Some Useful Interfaces

• Comparable– the compareTo() method:

public interface Comparable{ public int compareTo(Object o);

}

– String implements Comparable– Why is it useful? Ex: Arrays.sort(Object[] a)

• Listener– Useful for applications that handle events

– Will be discussed next week

Page 10: Interfaces Need arising from software engineering –Disparate groups of programmers need to agree to a “contract” that spells out how their software interacts

Introduction to Polymorphism

• Polymorphism– “having many forms”

– Helps build extensible systems

– Programs generically process objects as superclass objects• Can add classes to systems easily

– Classes must be part of generically processed hierarchy

– Can be done through interfaces and abstract classes

Page 11: Interfaces Need arising from software engineering –Disparate groups of programmers need to agree to a “contract” that spells out how their software interacts

Example

public class ExInterfaces {

public static void main(String[] args){

Speaker current;

current = new Dog();

current.speak();

current = new Teacher("Do your homework");

current.speak();

}

}

Different speak() method will be called depending on what type of objects the current reference points to.

The decision as to which one to call cannot be done at compile time. It has to wait until execution time.

Page 12: Interfaces Need arising from software engineering –Disparate groups of programmers need to agree to a “contract” that spells out how their software interacts

Using if-else Statements?

• if-else-based system– Determine appropriate action for object

• Based on object’s type

– Error prone• Programmer can forget to make appropriate type test

• Adding and deleting if-else statements

Page 13: Interfaces Need arising from software engineering –Disparate groups of programmers need to agree to a “contract” that spells out how their software interacts

class Animal { //...}class Dog extends Animal { public void woof() { System.out.println("Woof!"); } //...}class Cat extends Animal { public void meow() { System.out.println("Meow!"); } //...}class Example5 { public static void main(String[] args) { makeItTalk(new Cat()); makeItTalk(new Dog()); } public static void makeItTalk(Animal animal) { if (animal instanceof Cat) { Cat cat = (Cat) animal; cat.meow(); } else if (animal instanceof Dog) { Dog dog = (Dog) animal; dog.woof(); } }}

Example: using if-else and instanceof

Page 14: Interfaces Need arising from software engineering –Disparate groups of programmers need to agree to a “contract” that spells out how their software interacts

Dynamic Method Binding

• Dynamic method binding– Also called “late binding”

– Implements polymorphic processing of objects

– Use superclass reference to refer to subclass object

– Program chooses “correct” method in subclass at execution

Page 15: Interfaces Need arising from software engineering –Disparate groups of programmers need to agree to a “contract” that spells out how their software interacts

import java.util.Scanner; public class AnimalGame{      public static void main(String[] args)       {            System.out.println("Choose one of three doors by entering the number of the door you choose.");             Scanner input = new Scanner(System.in);             int doorNumber = input.nextInt();

            Animal animal = null;

            if (doorNumber == 1){                  animal = new Cat();            }           else if (doorNumber == 2){                  animal = new Dog();            }            else {                  System.out.println("Not a valid door number");                  System.exit(1);             }

            System.out.println("The animal behind your door says: " + animal.talk());     }}

Animal is an interface

Dog and Cat implement Animal

Example

Page 16: Interfaces Need arising from software engineering –Disparate groups of programmers need to agree to a “contract” that spells out how their software interacts

Dynamic Method Binding (cont.)

• Example– Superclass Shape– Subclasses Circle, Rectangle and Square– Each class draws itself according to type of class

• Shape has method draw• Each subclass overrides method draw• Call method draw of superclass Shape

– Program determines dynamically which subclass draw method to invoke

Page 17: Interfaces Need arising from software engineering –Disparate groups of programmers need to agree to a “contract” that spells out how their software interacts

Late Binding vs. Early Binding

• Early Binding– Overloaded methods/constructors

– E.g., two constructors for BankAccount class• BankAccount() and BankAccount(double)

• The compiler selects the correct constructor when compiling the program by looking at the parameters.

account = new BankAccount(); //compiler selects BankAccount();

account = new BankAccount(1.00);//BankAccount(double)

• Early Binding – decisions are made at compilation time by the compiler

• Late Binding – decision are made at run time by the java virtual machine

Page 18: Interfaces Need arising from software engineering –Disparate groups of programmers need to agree to a “contract” that spells out how their software interacts

Case Study: A Payroll System Using Polymorphism

• Abstract methods and polymorphism– Abstract superclass Employee

• Method earnings applies to all employees

• Person’s earnings dependent on type of Employee

– Concrete Employee subclasses declared final• Boss• CommissionWorker• PieceWorker• HourlyWorker

Employee

Boss CommissionWorker PieceWorker HourlyWorker

Page 19: Interfaces Need arising from software engineering –Disparate groups of programmers need to agree to a “contract” that spells out how their software interacts

Employee.java

Line 4abstract class cannot be instantiated

Lines 5-6 and 16-30abstract class can have instance data and nonabstract methods for subclasses

Lines 9-13abstract class can have constructors for subclasses to initialize inherited data

1 // Employee.java2 // Abstract base class Employee.3 4 public abstract class Employee {5 private String firstName;6 private String lastName;7 8 // constructor9 public Employee( String first, String last )10 {11 firstName = first;12 lastName = last;13 }14 15 // get first name16 public String getFirstName() 17 { 18 return firstName; 19 }20 21 // get last name22 public String getLastName()23 { 24 return lastName; 25 }26 27 public String toString()28 { 29 return firstName + ' ' + lastName; 30 }31

abstract class cannot be instantiated

abstract class can have instance data and nonabstract methods for subclasses

abstract class can have constructors for subclasses to initialize inherited data

Page 20: Interfaces Need arising from software engineering –Disparate groups of programmers need to agree to a “contract” that spells out how their software interacts

Employee.java

Line 35Subclasses must implement abstract method

32 // Abstract method that must be implemented for each 33 // derived class of Employee from which objects 34 // are instantiated.35 public abstract double earnings(); 36 37 } // end class Employee

Subclasses must implement abstract method

Page 21: Interfaces Need arising from software engineering –Disparate groups of programmers need to agree to a “contract” that spells out how their software interacts

Boss.java

Line 4Boss is an Employee subclass

Line 4Boss inherits Employee’s public methods (except for constuctor)

Line 10Explicit call to Employee constructor using super

Lines 21-24Required to implement Employee’s method earnings (polymorphism)

1 // Boss.java2 // Boss class derived from Employee.3 4 public final class Boss extends Employee {5 private double weeklySalary; 6 7 // constructor for class Boss8 public Boss( String first, String last, double salary )9 {10 super( first, last ); // call superclass constructor11 setWeeklySalary( salary );12 }13 14 // set Boss's salary15 public void setWeeklySalary( double salary )16 { 17 weeklySalary = ( salary > 0 ? salary : 0 ); 18 }19 20 // get Boss's pay21 public double earnings() 22 { 23 return weeklySalary; 24 }25 26 // get String representation of Boss's name27 public String toString() 28 {29 return "Boss: " + super.toString();30 }31 32 } // end class Boss

Boss is an Employee subclass

Boss inherits Employee’s public methods (except for constuctor)

Explicit call to Employee constructor using super

Required to implement Employee’s method earnings (polymorphism)

Page 22: Interfaces Need arising from software engineering –Disparate groups of programmers need to agree to a “contract” that spells out how their software interacts

CommissionWorker.java

Line 4CommissionWorker is an Employee subclass

Line 13Explicit call to Employee constructor using super

1 // CommissionWorker.java2 // CommissionWorker class derived from Employee3 4 public final class CommissionWorker extends Employee {5 private double salary; // base salary per week6 private double commission; // amount per item sold7 private int quantity; // total items sold for week8 9 // constructor for class CommissionWorker10 public CommissionWorker( String first, String last,11 double salary, double commission, int quantity )12 {13 super( first, last ); // call superclass constructor14 setSalary( salary );15 setCommission( commission );16 setQuantity( quantity );17 }18 19 // set CommissionWorker's weekly base salary20 public void setSalary( double weeklySalary )21 { 22 salary = ( weeklySalary > 0 ? weeklySalary : 0 ); 23 }24 25 // set CommissionWorker's commission26 public void setCommission( double itemCommission ) 27 { 28 commission = ( itemCommission > 0 ? itemCommission : 0 );29 }30

CommissionWorker is an Employee subclass

Explicit call to Employee constructor using super

Page 23: Interfaces Need arising from software engineering –Disparate groups of programmers need to agree to a “contract” that spells out how their software interacts

CommissionWorker.java

Lines 38-41Required to implement Employee’s method earnings; this implementation differs from that in Boss

31 // set CommissionWorker's quantity sold32 public void setQuantity( int totalSold )33 { 34 quantity = ( totalSold > 0 ? totalSold : 0 ); 35 }36 37 // determine CommissionWorker's earnings38 public double earnings()39 {40 return salary + commission * quantity; 41 }42 43 // get String representation of CommissionWorker's name 44 public String toString() 45 {46 return "Commission worker: " + super.toString();47 }48 49 } // end class CommissionWorker

Required to implement Employee’s method earnings; this implementation

differs from that in Boss

Page 24: Interfaces Need arising from software engineering –Disparate groups of programmers need to agree to a “contract” that spells out how their software interacts

PieceWorker.java

Line 4PieceWorker is an Employee subclass

Line 12Explicit call to Employee constructor using super

Lines 30-33 Implementation of Employee’s method earnings; differs from that of Boss and CommissionWorker

1 // PieceWorker.java2 // PieceWorker class derived from Employee3 4 public final class PieceWorker extends Employee {5 private double wagePerPiece; // wage per piece output6 private int quantity; // output for week7 8 // constructor for class PieceWorker9 public PieceWorker( String first, String last,10 double wage, int numberOfItems )11 {12 super( first, last ); // call superclass constructor13 setWage( wage );14 setQuantity( numberOfItems);15 }16 17 // set PieceWorker's wage18 public void setWage( double wage ) 19 { 20 wagePerPiece = ( wage > 0 ? wage : 0 ); 21 }22 23 // set number of items output24 public void setQuantity( int numberOfItems ) 25 { 26 quantity = ( numberOfItems > 0 ? numberOfItems : 0 ); 27 }28 29 // determine PieceWorker's earnings30 public double earnings()31 { 32 return quantity * wagePerPiece; 33 }34

PieceWorker is an Employee subclass

Explicit call to Employee constructor using super

Implementation of Employee’s method earnings; differs from that of Boss

and CommissionWorker

Page 25: Interfaces Need arising from software engineering –Disparate groups of programmers need to agree to a “contract” that spells out how their software interacts

PieceWorker.java

35 public String toString()36 {37 return "Piece worker: " + super.toString();38 } 39 40 } // end class PieceWorker

Page 26: Interfaces Need arising from software engineering –Disparate groups of programmers need to agree to a “contract” that spells out how their software interacts

HourlyWorker.java

Line 4PieceWorker is an Employee subclass

Line 12Explicit call to Employee constructor using super

Line 31Implementation of Employee’s method earnings; differs from that of other Employee subclasses

1 // HourlyWorker.java2 // Definition of class HourlyWorker3 4 public final class HourlyWorker extends Employee {5 private double wage; // wage per hour6 private double hours; // hours worked for week7 8 // constructor for class HourlyWorker9 public HourlyWorker( String first, String last, 10 double wagePerHour, double hoursWorked )11 {12 super( first, last ); // call superclass constructor13 setWage( wagePerHour );14 setHours( hoursWorked );15 }16 17 // Set the wage18 public void setWage( double wagePerHour )19 { 20 wage = ( wagePerHour > 0 ? wagePerHour : 0 ); 21 }22 23 // Set the hours worked24 public void setHours( double hoursWorked )25 { 26 hours = ( hoursWorked >= 0 && hoursWorked < 168 ?27 hoursWorked : 0 ); 28 }29 30 // Get the HourlyWorker's pay31 public double earnings() { return wage * hours; }32

HourlyWorker is an Employee subclass

Explicit call to Employee constructor using super

Implementation of Employee’s method earnings; differs from that of other

Employee subclasses

Page 27: Interfaces Need arising from software engineering –Disparate groups of programmers need to agree to a “contract” that spells out how their software interacts

HourlyWorker.java

33 public String toString() 34 {35 return "Hourly worker: " + super.toString();36 }37 38 } // end class HourlyWorker

Page 28: Interfaces Need arising from software engineering –Disparate groups of programmers need to agree to a “contract” that spells out how their software interacts

Test.java

Line 15Test cannot instantiate Employee but can reference one

Lines 18-28Instantiate one instance each of Employee subclasses

1 // Test.java2 // Driver for Employee hierarchy3 4 // Java core packages5 import java.text.DecimalFormat;6 7 // Java extension packages8 import javax.swing.JOptionPane;9 10 public class Test {11 12 // test Employee hierarchy13 public static void main( String args[] )14 {15 Employee employee; // superclass reference16 String output = "";17 18 Boss boss = new Boss( "John", "Smith", 800.0 );19 20 CommissionWorker commisionWorker =21 new CommissionWorker( 22 "Sue", "Jones", 400.0, 3.0, 150 );23 24 PieceWorker pieceWorker =25 new PieceWorker( "Bob", "Lewis", 2.5, 200 );26 27 HourlyWorker hourlyWorker =28 new HourlyWorker( "Karen", "Price", 12.5, 40 );29 30 DecimalFormat precision2 = new DecimalFormat( "0.00" );31

Instantiate one instance each of Employee subclasses

Test cannot instantiate Employee but can reference one

Page 29: Interfaces Need arising from software engineering –Disparate groups of programmers need to agree to a “contract” that spells out how their software interacts

Test.java

Line 33Use Employee to reference Boss

Line 36Method employee.earnings dynamically binds to method boss.earnings

Lines 41-55Do same for CommissionWorker and PieceWorker

32 // Employee reference to a Boss 33 employee = boss; 34 35 output += employee.toString() + " earned $" +36 precision2.format( employee.earnings() ) + "\n" +37 boss.toString() + " earned $" +38 precision2.format( boss.earnings() ) + "\n";39 40 // Employee reference to a CommissionWorker41 employee = commissionWorker;42 43 output += employee.toString() + " earned $" +44 precision2.format( employee.earnings() ) + "\n" +45 commissionWorker.toString() + " earned $" +46 precision2.format( 47 commissionWorker.earnings() ) + "\n";48 49 // Employee reference to a PieceWorker50 employee = pieceWorker;51 52 output += employee.toString() + " earned $" +53 precision2.format( employee.earnings() ) + "\n" +54 pieceWorker.toString() + " earned $" +55 precision2.format( pieceWorker.earnings() ) + "\n";56

Use Employee to reference Boss

Method employee.earnings dynamically binds to method

boss.earnings

Do same for CommissionWorker and PieceWorker

Page 30: Interfaces Need arising from software engineering –Disparate groups of programmers need to agree to a “contract” that spells out how their software interacts

Test.java

Lines 58-63Repeat for HourlyWorker

Line 59Casting is required for accessing subclass methods

57 // Employee reference to an HourlyWorker58 employee = hourlyWorker; 59 ((HourlyWorker)employee).setWage(13.75);60 output += employee.toString() + " earned $" +61 precision2.format( employee.earnings() ) + "\n" +62 hourlyWorker.toString() + " earned $" +63 precision2.format( hourlyWorker.earnings() ) + "\n";64 65 JOptionPane.showMessageDialog( null, output,66 "Demonstrating Polymorphism",67 JOptionPane.INFORMATION_MESSAGE );68 69 System.exit( 0 );70 }71 72 } // end class Test

Repeat for HourlyWorker

Casting required for accessing subclass methods

Page 31: Interfaces Need arising from software engineering –Disparate groups of programmers need to agree to a “contract” that spells out how their software interacts

New Classes and Dynamic Binding

• Dynamic binding (late binding)– Object’s type need not be known at compile time

– At run time, call is matched with method of called object

– Easy to add new classes to the class hierarchy

Read the lecture notes on the course Web site for another example on polymorphism.

Page 32: Interfaces Need arising from software engineering –Disparate groups of programmers need to agree to a “contract” that spells out how their software interacts

Recap - Interfaces

• Interfaces– A collection of constants and abstract methods– No implementation details defined

public interface Car{ final int WHEELS = 4; public void start(); public void stop(); . . .}

– Variables are implicitly defined as public static final• Implementing interfaces

public class Ford implements Car { public void start(){ . . . } public void stop(){ . . . } . . .}

Page 33: Interfaces Need arising from software engineering –Disparate groups of programmers need to agree to a “contract” that spells out how their software interacts

Interfaces

• True or false?– An interface can have private instance attributes

– A concrete class implementing an interface can implement selected methods defined in the interface

– A class can implement more than one interface

– One need to use abstract to indicate that a method is abstract in an interface

– You can create an instance (object) of an interface, just like creating an instance of a class

Page 34: Interfaces Need arising from software engineering –Disparate groups of programmers need to agree to a “contract” that spells out how their software interacts

interface Silly { public void narf(); public void poit(Silly s);}public class Bird implements Silly { public static void main(String

args[]) { System.out.println("zero"); Silly s = new SillyBird(1); Silly s2 = new Loony(); s.poit(s2); s2.poit(s); System.out.println("zymurgy"); } public Bird() { this(0); System.out.println("zircon"); } public Bird(int i) { System.out.println("zanzibar"); } public void narf() { System.out.println("zort"); } public void poit(Silly s) { s.narf(); }}

class SillyBird extends Bird {

public SillyBird(){ System.out.println("duchess"); }

public SillyBird(int i) { super(i); }

public void narf() { System.out.println("drum"); super.narf(); }}

class Loony extends SillyBird { public Loony() { System.out.println("stupendous"); } public void narf() { System.out.println("snark"); }}

What’s the output?