Because we've changed the names of our classes, and because we've decided to make at least the business objects we've designed so far stateless, we ought to change the name of the Rose packages (and later the COM+ applications) they live in as well.
Starting with our present model, let's take a look at the stateful package view we've already seen. Figure 8-10 includes the main business package, named Persistent Entity And Set Classes, which doesn't exactly match the contents of the package anymore.
Figure 8-10. A stateful view of an application, containing the package Persistent Entity And Set Classes.
The new name of the package is Entity Management Classes, which better matches the content. Had we opted for the Suppliers name convention, we would probably have called the package Entity Supplier Classes or something like that. Anyway, Figure 8-11 is the diagram we wound up with.
Figure 8-11. To highlight the stateless features of this model, the main business package now bears the name Entity Management Classes.