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

More documents

Recommendations

Info

DEV475 Mastering Object-Oriented Analysis and Design with UMLObjectives: Use-Case AnalysisObjectives: Use-Case Analysis• Explain the purpose of Use-CaseAnalysis and where in the lifecycle it isperformed• Identify the classes which perform a usecaseflow of events• Distribute the use-case behavior to thoseclasses, identifying responsibilities of theclasses• Develop Use-Case Realizations thatmodel the collaborations betweeninstances of the identified classesMastering Object Oriented Analysis and Design with UMLCopyright © 2003 Rational Software, all rights reserved 2Use-Case Analysis is where we identify the initial classes of our system.As the analysis classes are defined and the responsibilities are allocated to them, wewill also note the usage of architectural mechanisms, more specifically, the usage ofany analysis mechanisms defined in Architectural Analysis.The analysis classes and the initial Use-Case Realizations are the key model elementsbeing developed in this activity. These will be refined in the remaining Analysis andDesign activities.6 - 2
Module 6 - Use-Case AnalysisUse-Case Analysis in ContextUse-Case Analysis in Context[EarlyElaborationIteration][InceptionIteration (Optional)]Define a CandidateArchitecturePerformArchitecturalSynthesisAnalyze BehaviorDesignerUse-CaseAnalysisRefine theArchitecture(Optional)DefineComponentsDesign theDatabaseMastering Object Oriented Analysis and Design with UMLCopyright © 2003 Rational Software, all rights reserved 3As you may recall, the above diagram illustrates the workflow that we are using in thiscourse. It is a tailored version of the Analysis and Design core workflow of theRational Unified Process. Use-Case Analysis is an activity in the Analyze Behaviorworkflow detail.At this point, we have made an initial attempt at defining our architecture — we havedefined the upper layers of our architecture, the key abstractions, and some keyanalysis mechanisms. This initial architecture, along with the software requirementsdefined in the Requirements discipline, guides and serves as input to the Use-CaseAnalysis activity.An instance of Use-Case Analysis is performed for each use case to be developedduring an iteration. The focus during Use-Case Analysis is on a particular use case.In Use-Case Analysis, we identify the analysis classes and define theirresponsibilities. As the analysis classes and their responsibilities are defined, we willalso note the usage of any architectural (more specifically, analysis) patterns definedin Architectural Analysis. The architectural layers and their dependencies may affectthe allocation of responsibility to the defined analysis classes.The allocation of responsibility is modeled in Use-Case Realizations that describe howanalysis classes collaborate to perform use cases. The Use-Case Realizations will berefined in the Use-Case Design Model.6 - 3
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: DEV475 Mastering Object-Oriented An
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?