I need you to pick 10 of the items in the EEA catalog and create a hiarchy, not write about the catalog. Can this be done?

15 Jul 2019 01:24

These are the Fowler Catelogue items:

These pages are a brief overview of each of the patterns in P of EAA. They aren’t intended to stand alone, but merely as a quick aide-memoire for those familiar with them, and a handy link if you want to refer to one online. In the future I may add some post-publication comments into the material here, but we’ll see how that works out.

Many of these diagrams demonstrate the rather poor GIF output of Visio. The nice diagrams were redrawn for me by David Heinemeier Hansson

Domain Logic Patterns: Transaction Script (110), Domain Model (116), Table Module (125), Service Layer (133).

Data Source Architectural Patterns: Table Data Gateway (144), Row Data Gateway (152), Active Record (160), Data Mapper (165).

Object-Relational Behavioral Patterns: Unit of Work (184), Identity Map (195), Lazy Load (200)

Object-Relational Structural Patterns: Identity Field (216), Foreign Key Mapping (236), Association Table Mapping (248), Dependent Mapping (262), Embedded Value (268), Serialized LOB (272), Single Table Inheritance (278), Class Table Inheritance (285), Concrete Table Inheritance (293), Inheritance Mappers (302).

Object-Relational Metadata Mapping Patterns: Metadata Mapping (306), Query Object (316), Repository (322).

Web Presentation Patterns: Model View Controller (330), Page Controller (333), Front Controller (344), Template View (350), Transform View (361), Two-Step View (365), Application Controller (379).

Distribution Patterns: Remote Facade (388), Data Transfer Object (401)

Offline Concurrency Patterns: Optimistic Offline Lock (416), Pessimistic Offline Lock (426), Coarse Grained Lock (438), Implicit Lock (449).

Session State Patterns: Client Session State (456), Server Session State (458), Database Session State (462).

Base Patterns: Gateway (466), Mapper (473), Layer Supertype (475), Separated Interface (476), Registry (480), Value Object (486), Money (488), Special Case (496), Plugin (499), Service Stub (504), Record Set (508)

located at <link is hidden> />
Assignment:
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 means of 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.

Software engineering typically establishes a design pattern hierarchy by grouping design patterns and associating them to the related problem space (<link is hidden> structural, behavioral, etc.). 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” (or EAA Catalog). This catalog of patterns is organized functionally. Familiarize yourself with the differences between architectural styles, architectural patterns, and design patterns.

In this Assignment, write a 2- to 3-page paper that addresses the following:

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.
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.

14 Jul 2019 02:45