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

More documents

Recommendations

Info

DEV475 Mastering Object-Oriented Analysis and Design with UMLCreate Use-Case RealizationsArchitectural Analysis Steps• Key Concepts• Define the High-Level Organization ofSubsystems• Identify Analysis mechanisms• Identify Key Abstractions• Create Use-Case Realizations• CheckpointsMastering Object Oriented Analysis and Design with UMLCopyright © 2003 Rational Software, all rights reserved 32A use-case realization represents the design perspective of a use case. It is anorganization model element used to group a number of artifacts related to the usecasedesign. Use cases are separate from use-case realizations, so you can manageeach individually and change the design of the use case without affecting the baselineuse case. For each use case in the Use-Case Model, there is a use-case realization inthe design model with a dependency (stereotyped «realize») to the use case.5 - 32
Module 5 - Architectural AnalysisReview: What is a Use-Case Realization?Review: What is a Use-Case Realization?Use-Case ModelDesign ModelUse CaseUse-Case RealizationSequence DiagramsCollaboration DiagramsUse CaseClass DiagramsMastering Object Oriented Analysis and Design with UMLCopyright © 2003 Rational Software, all rights reserved 33A use-case realization is the expression of a particular use case within the DesignModel. It describes the use case in terms of collaborating objects. A use-caserealization ties together the use cases from the Use-Case Model with the classes andrelationships of the Design Model. A use-case realization specifies what classes mustbe built to implement each use case.In the UML, use-case realizations are stereotyped collaborations. The symbol for acollaboration is an oval containing the name of the collaboration. The symbol for ause-case realization is a “dotted line” version of the collaboration symbol.A use-case realization in the Design Model can be traced to a use case in the Use-Case Model. A realization relationship is drawn from the use-case realization to theuse case it realizes.Within the UML, a use-case realization can be represented using a set of diagramsthat model the context of the collaboration (the classes/objects that implement theuse case and their relationships — class diagrams), and the interactions of thecollaborations (how these classes/objects interact to perform the use cases —collaboration and sequence diagrams).The number and types of the diagrams that are used depend on what is needed toprovide a complete picture of the collaboration and the guidelines developed for theproject under development.5 - 33
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: DEV475 Mastering Object-Oriented An
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 ...

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?