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 UMLUnify Analysis ClassesUnify Analysis ClassesRegisterForCoursesFormRegistrationControllerCourseCatalogSystemRegisterForCoursesFormRegistrationControllerRegister forCoursesCourseOfferingScheduleStudentCourseOfferingStudentCloseRegistrationCloseRegistrationFormBillingSystemCourseOfferingCloseRegistrationControllerCourseCatalogSystemStudentScheduleCourseCatalogSystemCloseRegistrationFormCloseRegistrationControllerScheduleBillingSystemMastering Object Oriented Analysis and Design with UMLCopyright © 2003 Rational Software, all rights reserved 58Before the Design work can be done, the analysis classes need to be filtered to ensurethat a minimum number of new concepts have been created.Different use cases will contribute to the same classes. In the example above, theclasses CourseCatalogSystem, CourseOffering, Schedule and Student participate inboth the Register for Courses and Close Registration use cases.A class can participate in any number of use cases. It is therefore important toexamine each class for consistency across the whole system.Merge classes that define similar behaviors or that represent the same phenomenon.Merge entity classes that define the same attributes, even if their defined behavior isdifferent; aggregate the behaviors of the merged classes.When you update a class, you should update any “supplemental” use-casedescriptions (described earlier in this module), where necessary. Sometimes anupdate to the original Requirements (that is, use cases) may be necessary, but thisshould be controlled, as the Requirements are the contract with the user/customer,and any changes must be verified and controlled.6 - 58
Module 6 - Use-Case AnalysisEvaluate Your ResultsEvaluate Your ResultsDesign ModelGlossarySupplementarySpecificationAnalysis ClassesUse-Case ModelMastering Object Oriented Analysis and Design with UMLCopyright © 2003 Rational Software, all rights reserved 59We now have a pretty good feeling about our Analysis Model. Now it is time toreview our work for completeness and consistency.Be sure to:• Verify that the analysis classes meet the functional requirements made on thesystem.• Verify that the analysis classes and their relationships are consistent with thecollaborations they support.It is very important that you evaluate your results at the conclusion of the Use-CaseAnalysis.The number of reviews, the formality of the reviews, and when they are performedwill vary, depending on the process defined for the project.6 - 59
- 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 264 and 265: 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
Module 6 - Use-Case <strong>Analysis</strong>Evaluate Your ResultsEvaluate Your Results<strong>Design</strong> ModelGlossarySupplementarySpecification<strong>Analysis</strong> ClassesUse-Case Model<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 59We now have a pretty good feeling about our <strong>Analysis</strong> Model. Now it is time toreview our work for completeness <strong>and</strong> consistency.Be sure to:• Verify that the analysis classes meet the functional requirements made on thesystem.• Verify that the analysis classes <strong>and</strong> their relationships are consistent <strong>with</strong> thecollaborations they support.It is very important that you evaluate your results at the conclusion of the Use-Case<strong>Analysis</strong>.The number of reviews, the formality of the reviews, <strong>and</strong> when they are performedwill vary, depending on the process defined for the project.6 - 59
Change language