DEV475 Mastering Object-Oriented Analysis and Design with UML ...
DEV475 Mastering Object-Oriented Analysis and Design with UML ... DEV475 Mastering Object-Oriented Analysis and Design with UML ...
DEV475 Mastering Object-Oriented Analysis and Design with UMLExample: Describing Analysis Mechanisms (cont.)Example: Describing Analysis Mechanisms (cont.)• Analysis mechanism characteristics• Persistency for Schedule class:• Granularity: 1 to 10 Kbytes per product• Volume: up to 2,000 schedules• Access frequency• Create: 500 per day• Read: 2,000 access per hour• Update: 1,000 per day• Delete: 50 per day• Other characteristicsMastering Object Oriented Analysis and Design with UMLCopyright © 2003 Rational Software, all rights reserved 56The above is just an example of how the characteristics for an analysis mechanismwould be documented for a class. For scoping reasons, the analysis mechanisms andtheir characteristics are not provided for all of the analysis classes.6 - 56
Module 6 - Use-Case AnalysisUnify Analysis ClassesUse-Case Analysis Steps• Supplement the Use-Case Descriptions• For each Use-Case Realization• Find Classes from Use-Case Behavior• Distribute Use-Case Behavior to Classes• For each resulting analysis class• Describe Responsibilities• Describe Attributes and Associations• Qualify Analysis Mechanisms• Unify Analysis Classes• CheckpointsMastering Object Oriented Analysis and Design with UMLCopyright © 2003 Rational Software, all rights reserved 57At this point, we have a pretty good understanding of the analysis classes, theirresponsibilities, the analysis mechanisms they need to implement, and thecollaborations required to support the functionality described in the use cases.Now we must review our work and make sure that it is as complete and as consistentas possible before moving on to the architecture activities.The purpose of Unify Analysis Classes is to ensure that each analysis class represents asingle well-defined concept, with non-overlapping responsibilities.6 - 57
- Page 214 and 215: DEV475 Mastering Object-Oriented An
- Page 216 and 217: DEV475 Mastering Object-Oriented An
- Page 218 and 219: DEV475 Mastering Object-Oriented An
- Page 220 and 221: DEV475 Mastering Object-Oriented An
- Page 222 and 223: DEV475 Mastering Object-Oriented An
- Page 224 and 225: DEV475 Mastering Object-Oriented An
- Page 226 and 227: DEV475 Mastering Object-Oriented An
- Page 228 and 229: DEV475 Mastering Object-Oriented An
- Page 230 and 231: DEV475 Mastering Object-Oriented An
- Page 232 and 233: DEV475 Mastering Object-Oriented An
- Page 234 and 235: DEV475 Mastering Object-Oriented An
- Page 236 and 237: DEV475 Mastering Object-Oriented An
- Page 238 and 239: DEV475 Mastering Object-Oriented An
- Page 240 and 241: DEV475 Mastering Object-Oriented An
- Page 242 and 243: DEV475 Mastering Object-Oriented An
- Page 244 and 245: DEV475 Mastering Object-Oriented An
- Page 246 and 247: DEV475 Mastering Object-Oriented An
- Page 248 and 249: DEV475 Mastering Object-Oriented An
- Page 250 and 251: DEV475 Mastering Object-Oriented An
- Page 252 and 253: DEV475 Mastering Object-Oriented An
- Page 254 and 255: DEV475 Mastering Object-Oriented An
- Page 256 and 257: DEV475 Mastering Object-Oriented An
- Page 258 and 259: DEV475 Mastering Object-Oriented An
- Page 260 and 261: DEV475 Mastering Object-Oriented An
- Page 262 and 263: DEV475 Mastering Object-Oriented An
- Page 266 and 267: DEV475 Mastering Object-Oriented An
- Page 268 and 269: DEV475 Mastering Object-Oriented An
- Page 270 and 271: DEV475 Mastering Object-Oriented An
- Page 272 and 273: DEV475 Mastering Object-Oriented An
- Page 274 and 275: DEV475 Mastering Object-Oriented An
- Page 276: DEV475 Mastering Object-Oriented An
<strong>DEV475</strong> <strong>Mastering</strong> <strong>Object</strong>-<strong>Oriented</strong> <strong>Analysis</strong> <strong>and</strong> <strong>Design</strong> <strong>with</strong> <strong>UML</strong>Example: Describing <strong>Analysis</strong> Mechanisms (cont.)Example: Describing <strong>Analysis</strong> Mechanisms (cont.)• <strong>Analysis</strong> mechanism characteristics• Persistency for Schedule class:• Granularity: 1 to 10 Kbytes per product• Volume: up to 2,000 schedules• Access frequency• Create: 500 per day• Read: 2,000 access per hour• Update: 1,000 per day• Delete: 50 per day• Other characteristics<strong>Mastering</strong> <strong>Object</strong> <strong>Oriented</strong> <strong>Analysis</strong> <strong>and</strong> <strong>Design</strong> <strong>with</strong> <strong>UML</strong>Copyright © 2003 Rational Software, all rights reserved 56The above is just an example of how the characteristics for an analysis mechanismwould be documented for a class. For scoping reasons, the analysis mechanisms <strong>and</strong>their characteristics are not provided for all of the analysis classes.6 - 56
Change language