Defining the Top-Level Model
During the use case definition activities, the use case model was divided into packages. During analysis, the same package hierarchy could be used to model the structural view of the system. It has been my experience, however, that the hierarchy of the dynamic view of the system (use cases) may provide an initial start but usually falls short for defining the structural view of the system (classes). The reason is that certain objects likely participate in a large number of use cases and packages and logically can't be assigned to a single use case package.
At the highest level, the packages are often the same; at the lower levels of the hierarchy, however, there are often better ways of dividing the packages. For ...
Get Building Web Applications with UML now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
