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

More documents

Recommendations

Info

DEV475 Mastering Object-Oriented Analysis and Design with UMLMultiplicity IndicatorsMultiplicity IndicatorsUnspecifiedExactly OneZero or MoreZero or MoreOne or MoreZero or One (optional scalar role)Specified RangeMultiple, Disjoint Ranges10..**1..*0..12..42, 4..6Mastering Object Oriented Analysis and Design with UMLCopyright © 2003 Rational Software, all rights reserved 40• Multiplicity is indicated by a text expression on the role.• The expression is a comma-separated list of integer ranges.• A range is indicated by an integer (the lower value), two dots, followed byanother integer (the upper value).• A single integer is a valid range, and the symbol “*” indicates "many.” That is, anasterisk “*” indicates an unlimited number of objects.• The symbol “*” by itself is equivalent to “0..*” That is, it represents any number,including none. This is the default value.• An optional scalar role has the multiplicity 0..1.2 - 40
Module 2 - Concepts of Object OrientationWhat Is Aggregation?What Is Aggregation?• An aggregation is a special form of associationthat models a whole-part relationship betweenan aggregate (the whole) and its parts.• An aggregation is an “Is a part-of” relationship.• Multiplicity is represented like otherassociations.WholePart10..1Mastering Object Oriented Analysis and Design with UMLCopyright © 2003 Rational Software, all rights reserved 41An aggregation can be defined as:A special form of association that models a whole-part relationship between anaggregate (the whole) and its parts.• Aggregation is used to model relationships between model elements. There aremany examples of aggregation: a library contains books, departments are madeup of employees, a computer is composed of a number of devices. To model anaggregation, the aggregate (department) has an aggregation association to the itsconstituent parts (employee).• A hollow diamond is attached to the end of an association path on the side of theaggregate (the whole) to indicate aggregation.• An aggregation relationship that has a multiplicity greater than one for theaggregate is called shared. Destroying the aggregate does not necessarily destroythe parts. By implication, a shared aggregation forms a graph or a tree with manyroots. Shared aggregations are used where there is a strong relationship betweentwo classes. Therefore, the same instance can participate in two differentaggregations.2 - 41
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: DEV475 Mastering Object-Oriented An
Page 152 and 153:
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?