CSE115: Introduction to Computer Science I

1. CSE115: Introduction to Computer Science I Dr. Carl Alphonce 219 Bell Hall 645-4739 alphonce@buffalo.edu

2. Phones off Signs out

3. Announcements • Exam 2 in a week and a half (10/21) • Exam 1 solution will be posted today • Installation session • next week (10/13 and 10/14) • will send e-mail with details

4. Agenda • association relationship • constructor form • accessor/mutator form • variation on a theme • capture the domain

5. Revisiting Clifford

6. Another relationship • One collar for its life…? • A dog has-a tail; the tail is a part of the dog. • We need something different to model the relationship between a dog and a collar.

7. Association • No necessary lifetime link • Two implementations: • The first is very similar to composition, but differs in one crucial respect: where the target class is instantiated. • The second, which decouples lifetimes completely, is a bit more complex but also more flexible.

8. Revisiting Clifford • Dog-Tail relationship is COMPOSITION • Dog takes responsibility for creating a Tail • Dog-Collar relationship is ASSOCIATION • Dog takes NO responsibility for creating Collar

9. First implementation 3 changes to source class: • Declaration of instance variable • Assignment of existinginstance to the instance variable • Parameter of constructor is of same type as instance variable 1 2 3

10. Dog – Collar example in Java public class Dog { private Collar _collar; public Dog(Collar collar) { _collar = collar; } } 1 3 2

11. UML • See Eclipse example

12. Essence of association • one object can communicate with another object • there is no necessary lifetime link between the two objects • the objects in the relationship can change over time

13. Lifetime issue inconstructor implementation • the source class (Dog) does not create an instance of the target (Collar) class • there is a lifetime dependency: the target (Collar) object must exist before the source (Dog) object can be created: • a Collar object must be provided in the constructor of the Dog object.

14. Lifetime issue (continued) This occurs in this particular implementation of the relationship, but is not an essential characteristic of the relationship.

15. Changing a property value • We want to be able to set a new value for the property (e.g. give Clifford a new collar). • How can we do that? • Using a “mutator” method.

16. Association relationship(take 2) • We’ve seen one implementation of “knows a”: public class Dog { private Collar _collar; public Dog(Collar collar) { _collar = collar; } } • Now we will see a more flexible implementation.

17. Association viaconstructor and mutatormethod public class Dog { private Collar _collar; public Dog(Collar c) { _collar = c; } public void setCollar(Collar c) { _collar = c; } }

18. Constructor/mutator similarity Similarity: both set the value of the instance variable. Difference: constructor sets value when Dog object is created mutatorchanges the value at some later point in time public class Dog { private Collar _collar; public Dog(Collar c) { _collar = c; } public void setCollar(Collar c) { _collar = c; } }

19. Retrieving a property value • Suppose an object wants to let other objects know the value of one of its properties? • How can we do that? • We can define an “accessor” method.

20. accessor method public class Dog { private Collar _collar; public Dog(Collar collar) { _collar = collar; } public void setCollar(Collar collar) { _collar = collar; } public Collar getCollar() { return _collar; } }

21. accessor/mutatordifferencesin function Information flowing in to method public void setCollar(Collar collar){ _collar = collar; } public Collar getCollar() { return _collar; } Information flowing out from method

22. accessor/mutator differencesin form public void setCollar (Collar collar) a.c.m. r.t.s. name parameter list public Collar getCollar () a.c.m. r.t.s. name parameter list a.c.m. = access control modifier r.t.s. = return type specification void = no value is returned by method (note difference with constructors: no r.t.s.)

23. Example 1 Shape s1 = new Shape(java.awt.Color.BLUE); Shape s2 = new Shape(java.awt.Color.RED); Shape BLUE _color s1 Shape RED _color s2

24. Example 1 Shape s1 = new Shape(java.awt.Color.BLUE); Shape s2 = new Shape(java.awt.Color.RED); s2.setColor(s1.getColor()); Shape BLUE _color s1 Shape RED _color s2

25. Example 2 Dog s1 = new Dog(new Collar()); Dog s2 = new Dog(new Collar()); Dog _collar s1 Dog _collar s2

26. Example 2 Dog s1 = new Dog(new Collar()); Dog s2 = new Dog(new Collar()); s2.setCollar(s1.getCollar()); Dog _collar s1 ??? Dog _collar s2

27. What could we do instead?