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

More documents

Recommendations

Info

DEV475 Mastering Object-Oriented Analysis and Design with UMLExample: Multiple AssociationsExample: Multiple AssociationsScheduleprimaryCoursesCourseOfferingalternateCoursesScheduleadd student toremove student fromCourseOfferingMultiple associations must reflect multiple roles.Mastering Object Oriented Analysis and Design with UMLCopyright © 2003 Rational Software, all rights reserved 50There can be multiple associations between the same two classes, but they shouldrepresent distinct relationships, and DIFFERENT ROLES; they should not be just forinvoking different operations.If there is more than one association between two classes then they MUST be named.It is unusual to find more than one association between the same two classes.Occurrences of multiple associations should be carefully examined.To determine if multiple associations are appropriate, look at instances of the classes.ClassA and ClassB have two associations between them, Assoc1 and Assoc2. If aninstance of ClassA has a link with two SEPARATE instances of ClassB, then multipleassociations are valid.In the above example, the top diagram is an appropriate use of multiple associations,but the bottom diagram is not. In the valid case, two associations are requiredbetween Schedule and CourseOffering, as a Schedule can contain two kind ofCourseOfferings, primary and alternate. These must be distinguishable, so twoseparate associations are used. In the invalid case, the two relationships representtwo operations of CourseOffering, not two roles of CourseOffering.Remember, Students and CourseOfferings are related via the Schedule class. Studentsare enrolled in a CourseOffering if there is a relationship between the Student’sSchedule and the CourseOffering.6 - 50
Module 6 - Use-Case AnalysisExample: VOPC: Finding RelationshipsExample: VOPC: Finding RelationshipsRegisterForCoursesForm1 1RegistrationController0..1Student1currentSchedule0..*Schedule0..10..*primaryCourses0..4CourseOfferingMastering Object Oriented Analysis and Design with UMLCopyright © 2003 Rational Software, all rights reserved 51The diagram on this slide shows classes that collaborate to perform the “Register forCourses” use case, along with their relationships. As noted earlier, this type ofdiagram is called a View of Participating Classes (VOPC) diagram.The relationships in this diagram are defined using the Interaction diagrams for theRegister for Courses use case provided earlier in this module.Rationale for relationships:• From RegisterForCoursesForm to RegistrationController: There is one controllerfor each Schedule being created (for example, each Student registration session).• From RegistrationController to Schedule. A RegistrationController deals with oneSchedule at a time (the current Schedule for the Student registering for courses).Note the use of the “currentSchedule” role name. Note: ManyRegisterForCoursesForms can be active at one time (for differentsessions/students), each with their own RegistrationController.• From Schedule to CourseOffering: Each Schedule may have up to four primaryCourse Offerings and up to two alternate Course Offerings. A particular CourseOffering may appear on many Schedules as either a primary or an alternate.• From Student to Schedule: A Student may have many schedules or none. ASchedule is only associated with a single Student and does not exist without aStudent to be associated to.6 - 51
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:
Page 56 and 57:
Page 58 and 59:
Page 60 and 61:
Page 62 and 63:
Page 64 and 65:
Page 66 and 67:
Page 68 and 69:
Page 70 and 71:
Page 72 and 73:
Page 74 and 75:
Page 76 and 77:
Page 78 and 79:
Page 80 and 81:
Page 82 and 83:
Page 84 and 85:
Page 86 and 87:
Page 88 and 89:
Page 90 and 91:
Page 92 and 93:
Page 94 and 95:
Page 96 and 97:
Page 98 and 99:
Page 100 and 101:
Page 102 and 103:
Page 104 and 105:
Page 106 and 107:
Page 108 and 109:
Page 110 and 111:
Page 112 and 113:
Page 114 and 115:
Page 116 and 117:
Page 118 and 119:
Page 120 and 121:
Page 122 and 123:
Page 124 and 125:
Page 126 and 127:
Page 128 and 129:
Page 130 and 131:
Page 132 and 133:
Page 134 and 135:
Page 136 and 137:
Page 138 and 139:
Page 140 and 141:
Page 142 and 143:
Page 144 and 145:
Page 146 and 147:
Page 148 and 149:
Page 150 and 151:
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: DEV475 Mastering Object-Oriented An
Page 276: DEV475 Mastering Object-Oriented An
show all

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

Create successful ePaper yourself

Delete template?

Save as template?