高级软件开发技术(PPT1).ppt

* The above are the remaining classes from the Register for Courses VOPC. The complete VOPC was too big to fit on a single slide, so some of the classes are shown above and the remaining were shown on the previous slide. The relationships were defined based on the interaction diagrams for the “Register for Courses” use case provided earlier in this module. Rationale for relationships: From Schedule to Course Offering: Each Schedule may have up to four primary Course Offerings, and up to two alternate Course Offerings.A particular Course Offering may appear on many Schedules, as either a primary or an alternate. Association classes, ScheduleOfferingInfo and PrimaryScheduleOfferingInfo: Status information must be maintained for each CourseOffering on each Schedule, and for primary CourseOfferings, the Student’s grade in the CourseOffering must be maintained. Thus, the ScheduleOfferingInfo class was created because status will need to be maintained for alternate Course Offerings, as well as primary Course Offerings, with the only difference being that Students can only be enrolled in and receive a grade in a Primary Course Offering. Thus, generalization was used to model the commonality amongst the different types of CourseOffering information. * Packages are just a general grouping mechanism for grouping elements into semantically related groups. Packages can be used in the Use-Case Model to reflect order, configuration, or delivery units in the finished system. Allocation of resources and the competence of different development teams may require that the project be divided among different groups at different sites You can use use-case packages to: Structure the use-case model in a way that reflects the user types Preserve secrecy in areas where it is needed. In the UML, a package is represented as a tabbed folder. * Emphasize that the focus of this course will be on how the Use-Case Model affects the development of the Design Model. Remember, use-case-drive