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