2-Relationships

2-Relationships - aggregate ) to its part. TemperatureRamp

Info iconThis preview shows pages 1–10. Sign up to view the full content.

View Full Document Right Arrow Icon
Object-Oriented Programming and Design Thienne Johnson Objects and Classes relationships
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Agenda Relationships among Objects Relationships among Classes
Background image of page 2
Relationships among Objects Links Aggregation
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Links Denotes the specific association through which one object (the client) applies the services of another object (the supplier), or through which one object may navigate to another. Valve FlowController DisplayPanel 0.1:adjust
Background image of page 4
Links (cont.) Objects may play 3 roles: 1. Controller: may operate on other objects but is not operated on by another. 2. Server: it is only operated on by other objects. 3. Proxy: can both operate on other objects and be operated on by other objects
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Aggregation Denotes a whole/part relationship, with the ability to navigate from the whole (also called the
Background image of page 6
Background image of page 7

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Background image of page 8
Background image of page 9

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Background image of page 10
This is the end of the preview. Sign up to access the rest of the document.

Unformatted text preview: aggregate ) to its part. TemperatureRamp TemperatureController Heater Regulates temperature using Classes Association Inheritance Aggregation Association Most general and the most semantically weak relationship Semantic dependencies Multiplicity: One-to-one One-to-many Many-to-many Wheel Vehicle * 1 Inheritance Express generalization/specialization relationship Single inheritance Multiple inheritance Aggregation Whole/part relationship Sometimes physical containment Create a TemperatureController instance => create a Heater instance Destroy a TemperatureController object => destroy the Heater object Composition: containment by reference. Objects not tightly coupled TemperatureController Heater...
View Full Document

This note was uploaded on 02/28/2012 for the course CSC 337 taught by Professor Johnson during the Fall '11 term at Arizona.

Page1 / 10

2-Relationships - aggregate ) to its part. TemperatureRamp

This preview shows document pages 1 - 10. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online