Over the past couple of decades, software engineers have recognized the value of moving up from code reuse to the reuse of higher-level items. Design patterns have been recognized as a valuable week for reuse, and this has led to the development of a great number of patterns over the years. With so many design patterns being recognized and developed, finding the right pattern to use or customize can be a difficult task without some method for organizing them.
Architecture modeling typically establishes a design pattern hierarchy by grouping design patterns and associating them to the related architectural pattern. A similar hierarchy applies to architectural patterns. By grouping and associating patterns in such a way, modelers can create a lattice of patterns referred to as a pattern hierarchy.
To put this concept to work, review the “ Catalog of Patterns of Enterprise Application Architecture ” (https://martinfowler.com/eaaCatalog/) (or EAA Catalog). This catalog of patterns is organized functionally. Familiarize yourself with the differences between architectural styles, architectural patterns, and design patterns.
1. Create a pattern hierarchy that meaningfully organizes the EAA Catalog of patterns using one of the architectural styles from this week’s readings. Create categories and link them together in the form of a logical hierarchy. Include at least one pattern from each category in Fowler’s catalog.
2. Explain the organizing principles you employed in your pattern hierarchy. The EAA Catalog is organized functionally and not in a hierarchy. The Design Pattern Catalog has about 50 different patterns. They are now organized into 11 pattern types based on functionality. You need to use a different organizing principle.