DEV475 Mastering Object-Oriented Analysis and Design with UML ...

More documents

Recommendations

Info

DEV475 Mastering Object-Oriented Analysis and Design with UMLWhat Is Navigability?What Is Navigability?• Indicates that it is possible to navigate from aassociating class to the target class using theassociationRegistrationControllerScheduleCourseOfferingMastering Object Oriented Analysis and Design with UMLCopyright © 2003 Rational Software, all rights reserved 42• The navigability property on a role indicates that it is possible to navigate from aassociating class to the target class using the association. This may beimplemented in a number of ways: by direct object references, associative arrays,hash-tables, or any other implementation technique that allows one object toreference another.• Navigability is indicated by an open arrow placed on the target end of theassociation line next to the target class (the one being navigated to). The defaultvalue of the navigability property is true (associations are bi-directional bydefault).• In the course registration example, the association between the Schedule and theCourse Offering is navigable in both directions. That is, a Schedule must knowthe Course Offering assigned to the Schedule, and the Course Offering mustknow the Schedules it has been placed in.• When no arrowheads are shown, the association is assumed to be navigable inboth directions.• In the case of the association between Schedule and Registration Controller, theRegistration Controller must know its Schedules, but the Schedules have noknowledge of the Registration Controllers (or other classes). As a result, thenavigability property of the Registration Controller end of the association isturned off.2 - 42
Module 2 - Concepts of Object OrientationRelationships: DependencyRelationships: Dependency• A relationship between two model elementswhere a change in one may cause a change inthe other• Non-structural, “using” relationshipClassComponentClientClientDependencyrelationshipDependencyrelationshipDependencyrelationshipSupplierSupplierPackageClientPackageSupplierPackageMastering Object Oriented Analysis and Design with UMLCopyright © 2003 Rational Software, all rights reserved 43A dependency relationship is a weaker form of relationship showing a relationshipbetween a client and a supplier where the client does not have semantic knowledgeof the supplier.A dependency relationship denotes a semantic relationship between model elements,where a change in the supplier may cause a change in the client.2 - 43
Page 2 and 3:
Rational UniversityDEV475 Mastering
Page 5 and 6:
AcknowledgmentsThe development of t
Page 7 and 8:
► ► ► Module 0About This Cour
Page 9 and 10:
Module 0 - About This CourseCourse
Page 11 and 12:
Module 0 - About This CourseIntende
Page 13 and 14:
Module 0 - About This CourseRationa
Page 15 and 16:
Module 0 - About This CourseRationa
Page 18 and 19:
DEV475 Mastering Object-Oriented An
Page 20 and 21:
Page 22 and 23:
Page 24 and 25:
Page 26 and 27:
Page 28 and 29:
Page 30 and 31:
Page 32 and 33:
Page 34 and 35:
Page 36 and 37:
Page 38 and 39:
Page 40 and 41:
Page 42 and 43:
Page 44 and 45:
Page 46 and 47:
Page 48 and 49:
Page 50 and 51:
Page 52 and 53:
Page 54 and 55: DEV475 Mastering Object-Oriented An
Page 154 and 155:
Page 156 and 157:
Page 158 and 159:
Page 160 and 161:
Page 162 and 163:
Page 164 and 165:
Page 166 and 167:
Page 168 and 169:
Page 170 and 171:
Page 172 and 173:
Page 174 and 175:
Page 176 and 177:
Page 178 and 179:
Page 180 and 181:
Page 182 and 183:
Page 184 and 185:
Page 186 and 187:
Page 188 and 189:
Page 190 and 191:
Page 192 and 193:
Page 194 and 195:
Page 196 and 197:
Page 198 and 199:
Page 200 and 201:
Page 202 and 203:
Page 204 and 205:
Page 206 and 207:
Page 208 and 209:
Page 210 and 211:
Page 212 and 213:
Page 214 and 215:
Page 216 and 217:
Page 218 and 219:
Page 220 and 221:
Page 222 and 223:
Page 224 and 225:
Page 226 and 227:
Page 228 and 229:
Page 230 and 231:
Page 232 and 233:
Page 234 and 235:
Page 236 and 237:
Page 238 and 239:
Page 240 and 241:
Page 242 and 243:
Page 244 and 245:
Page 246 and 247:
Page 248 and 249:
Page 250 and 251:
Page 252 and 253:
Page 254 and 255:
Page 256 and 257:
Page 258 and 259:
Page 260 and 261:
Page 262 and 263:
Page 264 and 265:
Page 266 and 267:
Page 268 and 269:
Page 270 and 271:
Page 272 and 273:
Page 274 and 275:
Page 276:
show all

DEV475 Mastering Object-Oriented Analysis and Design with UML ...

Create successful ePaper yourself

Delete template?

Save as template?