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

More documents

Recommendations

Info

DEV475 Mastering Object-Oriented Analysis and Design with UMLWhat Is a Scenario?What Is a Scenario?• A scenario is an instance of a use case.Mastering Object Oriented Analysis and Design with UMLCopyright © 2003 Rational Software, all rights reserved 16A scenario is an instance of a use case. It is one flow through a use case.Each use case has a web of flow of events with a scenario being an instance of aparticular flow of events. The scenario may involve the basic flow and any number ofalternative flows in any number of combinations.In the example, the bold lines highlight some possible scenarios for the basic andalternative flows previously described.How many scenarios are needed?As many as one needs to understand the system being developed. You mustelaborate the scenarios of the interesting and high-risk use cases. Scenarios can beused to understand, as well as to validate, the use-case flows of events. Some peoplewrite scenarios first and extract use cases, while others find use cases first and validatethose use cases by writing scenarios.Scenarios make excellent test cases.3 - 16
Module 3 - Requirements OverviewWhat Is an Activity Diagram?What Is an Activity Diagram?• An activity diagram in the Use-Case Model can be used tocapture the activities in a use case.• It is essentially a flow chart, showing flow of control fromactivity to activity.Flow of EventsThis use case starts when the Registrar requests that thesystem close registration.1. The system checks to see if registration is in progress. If itis, then a message is displayed to the Registrar and the usecase terminates. The Close Registration processing cannotbe performed if registration is in progress.2. For each course offering, the system checks if a professorhas signed up to teach the course offering and at least threestudents have registered. If so, the system commits thecourse offering for each schedule that contains it.Activity1Activity2Activity3Mastering Object Oriented Analysis and Design with UMLCopyright © 2003 Rational Software, all rights reserved 17• The workflow of a use case describes what needs to be done by the system toprovide the value that the served actor is looking for.• It consists of a sequence of activities that, together, produce something for theactor.• The workflow often consists of a basic flow and one or several alternative flows.• The structure of the workflow can be described graphically with the help of anactivity diagram.3 - 17
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: DEV475 Mastering Object-Oriented An
Page 180 and 181:
Page 182 and 183:
Page 184 and 185:
Page 186 and 187:
Page 188 and 189:
Page 190 and 191:
Page 192 and 193:
Page 194 and 195:
Page 196 and 197:
Page 198 and 199:
Page 200 and 201:
Page 202 and 203:
Page 204 and 205:
Page 206 and 207:
Page 208 and 209:
Page 210 and 211:
Page 212 and 213:
Page 214 and 215:
Page 216 and 217:
Page 218 and 219:
Page 220 and 221:
Page 222 and 223:
Page 224 and 225:
Page 226 and 227:
Page 228 and 229:
Page 230 and 231:
Page 232 and 233:
Page 234 and 235:
Page 236 and 237:
Page 238 and 239:
Page 240 and 241:
Page 242 and 243:
Page 244 and 245:
Page 246 and 247:
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 ...

Create successful ePaper yourself

Delete template?

Save as template?