October 2008
Beginner to intermediate
680 pages
16h 48m
English
Applying all that we've learned in this chapter about static modeling, we've produced the UML class diagram for the SRS shown in Figure 10-44. Of course, as we've said repeatedly, this isn't the only correct way to model the requirements, nor is it necessarily the "best" model that we could have produced; but it is an accurate, concise, and correct model of the static aspects of the problem to be automated.
We opted to use the "generic" many notation (* for UML) instead of specifying 0..* or 1..*; this is often adequate during the initial modeling stages of a project.
Note that we've reflected two separate many-to-many associations between the Student and Section classes: waitlisted ...
Read now
Unlock full access