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

More documents

Recommendations

Info

DEV475 Mastering Object-Oriented Analysis and Design with UMLSupplement The Use-Case DescriptionUse-Case Analysis Steps• Supplement the Use-Case Description• 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 6The purpose of the Supplement the Descriptions of the Use Case is to captureadditional information needed in order to understand the required internal behaviorof the system that may be missing from the Use-Case Description written for thecustomer of the system. This information will be used as input to the rest of the stepsin Use-Case Analysis and is used to assist in the allocation of responsibility.Note: In some cases, we may find that some requirements were incorrect or not wellunderstood.In those cases, the original use-case flow of events should be updated(for example, iterate back to the Requirements discipline).6 - 6
Module 6 - Use-Case AnalysisSupplement the Use-Case DescriptionSupplement the Use-Case Description• The systemdisplays alist ofcourseofferings.• The systemretrieves anddisplays a list ofcurrent courseofferings from thecourse cataloglegacy database.Mastering Object Oriented Analysis and Design with UMLCopyright © 2003 Rational Software, all rights reserved 7The description of each use case is not always sufficient for finding analysis classesand their objects. The customer generally finds information about what happensinside the system uninteresting, so the use-case descriptions may leave suchinformation out. In these cases, the use-case description reads like a “black-box”description, in which internal details on what the system does in response to anactor’s actions is either missing or very summarily described. To find the objects thatperform the use case, you need to have the “white box” description of what thesystem does from an internal perspective.For example, in the case of the Course Registration System, the student might preferto say ”the system displays a list of course offerings.” While this might be sufficient forthe student, it gives us no real idea of what really happens inside the system. In orderto form an internal picture of how the system really works, at a sufficient level ofdetail to identify objects, we might need additional information.Taking the Register for Courses use case as an example, the expanded descriptionwould read as: “The system retrieves a list of current course offerings from the coursecatalog legacy database.” This level of detail gives us a clear idea of what informationis required and who is responsible for providing that information.6 - 7
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: DEV475 Mastering Object-Oriented An
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?