Frameworks, Subsystems, and Systems

You can use the ‚ «framework ‚ » stereotype to signify that the contents of a given package, taken together, represent an architectural pattern that provides an extensible template for applications within a domain.

Figure 9-15 shows an example of a framework.

Figure 9-15: Framework

The Customer Interfaces collaboration represents the View portion of the pattern, Order Processing represents the Controller portion, and Accounting Database and Inventory represent the Model portion.

The ‚ «subsystem ‚ » stereotype signifies that the associated package represents an independent part of the system being modeled . The ‚ «systemModel ‚ » stereotype signifies that the package contains a collection of models that, taken together, model the entire system. Figure 9-16 shows three examples of subsystems "rolling up" to the system as a whole.

Figure 9-16: Subsystems