UML Weekend Crash Course⢠- To Parent Directory
UML Weekend Crash Course⢠- To Parent Directory UML Weekend Crash Course⢠- To Parent Directory
Session 13—Modeling the Static View: The Object Diagram 147 Operations are not defined on objects because every object of the same class would have identical operations, creating redundancy in the model. Objects are connected using links. Classes are connected using associations. Links are defined with a name and optional roles. Multiplicity and constraints are not relevant with a link. QUIZ YOURSELF 1. Name two reasons for using an Object diagram. (See “Understanding the Object Diagram.”) 2. Name the two elements of the Object diagram. (See “Introducing Elements of the Object Diagram Notation.”) 3. How do you write the name of an object (See “Introducing Elements of the Object Diagram Notation.”) 4. What is a link (See “Introducing Elements of the Object Diagram Notation.”) 5. Why don’t you represent operations in an object (See “Introducing Elements of the Object Diagram Notation.”)
- Page 119 and 120: 96 Saturday Morning Attribute visib
- Page 121 and 122: 98 Saturday Morning In a modeling t
- Page 123 and 124: 100 Saturday Morning Table 9-2 Cont
- Page 125 and 126: 102 Saturday Morning Operation comp
- Page 128 and 129: SESSION 10 The Class Diagram: Assoc
- Page 130 and 131: Session 10—The Class Diagram: Ass
- Page 132 and 133: Session 10—The Class Diagram: Ass
- Page 134 and 135: Session 10—The Class Diagram: Ass
- Page 136 and 137: Session 10—The Class Diagram: Ass
- Page 138 and 139: Part II — Saturday Morning Part R
- Page 140 and 141: SESSION 11 The Class Diagram: Aggre
- Page 142 and 143: Session 11—The Class Diagram: Agg
- Page 144 and 145: Session 11—The Class Diagram: Agg
- Page 146 and 147: Session 11—The Class Diagram: Agg
- Page 148 and 149: Session 11—The Class Diagram: Agg
- Page 150: Session 11—The Class Diagram: Agg
- Page 153 and 154: 130 Saturday Afternoon or not. Each
- Page 155 and 156: 132 Saturday Afternoon 5. “Any it
- Page 157 and 158: 134 Saturday Afternoon designed to
- Page 159 and 160: 136 Saturday Afternoon Table 12-3 T
- Page 161 and 162: 138 Saturday Afternoon REVIEW The C
- Page 163 and 164: 140 Saturday Afternoon Introducing
- Page 165 and 166: 142 Saturday Afternoon Table 13-1 C
- Page 167 and 168: 144 Saturday Afternoon 28: VendorPr
- Page 169: 146 Saturday Afternoon 0..* VendorP
- Page 173 and 174: 150 Saturday Afternoon have current
- Page 175 and 176: 152 Saturday Afternoon Eat your din
- Page 177 and 178: 154 Saturday Afternoon Start and en
- Page 180 and 181: SESSION 15 Applying the Activity Di
- Page 182 and 183: Session 15—Applying the Activity
- Page 184 and 185: Session 15—Applying the Activity
- Page 186 and 187: Session 15—Applying the Activity
- Page 188: Session 15—Applying the Activity
- Page 191 and 192: 168 Saturday Afternoon Knowing the
- Page 193 and 194: 170 Saturday Afternoon A message or
- Page 195 and 196: 172 Saturday Afternoon Bill : Custo
- Page 197: 174 Saturday Afternoon REVIEW The d
- Page 200 and 201: Part III — Saturday Afternoon Par
- Page 202 and 203: SESSION 17 Applying the Sequence Di
- Page 204 and 205: Session 17—Applying the Sequence
- Page 206 and 207: Session 17—Applying the Sequence
- Page 208 and 209: Session 17—Applying the Sequence
- Page 210 and 211: SESSION 18 Modeling the Dynamic Vie
- Page 212 and 213: Session 18—Modeling the Dynamic V
- Page 214 and 215: Session 18—Modeling the Dynamic V
- Page 216 and 217: SESSION 19 Applying the Collaborati
- Page 218 and 219: Session 19—Applying the Collabora
Session 13—Modeling the Static View: The Object Diagram 147<br />
Operations are not defined on objects because every object of the same class would<br />
have identical operations, creating redundancy in the model.<br />
Objects are connected using links. Classes are connected using associations. Links<br />
are defined with a name and optional roles. Multiplicity and constraints are not<br />
relevant with a link.<br />
QUIZ YOURSELF<br />
1. Name two reasons for using an Object diagram. (See “Understanding the Object<br />
Diagram.”)<br />
2. Name the two elements of the Object diagram. (See “Introducing Elements of the<br />
Object Diagram Notation.”)<br />
3. How do you write the name of an object (See “Introducing Elements of the Object<br />
Diagram Notation.”)<br />
4. What is a link (See “Introducing Elements of the Object Diagram Notation.”)<br />
5. Why don’t you represent operations in an object (See “Introducing Elements of<br />
the Object Diagram Notation.”)
Change language