View this PageEdit this PageAttachments to this PageHistory of this PageHomeRecent ChangesSearch the SwikiHelp Guide
Hotspots: Admin Pages | Turn-in Site |
Current Links: Cases Final Project Summer 2007

Discussion 2 - Derek DeRaps

Part 1, Question 4:

Source: http://c2.com/ppr/about/portland.html

The Portland Form is an important tool for describing systems of design patterns. A document in the Portland Form, also called a “language”, discusses many design patterns, not just one. It “collects and connects patterns so that they will be studied and understood as a whole.” The “Pattern Paragraphs” discuss each pattern in turn, first analyzing the forces that create a problem and then detailing the solution (the pattern). The summary section ties all the patterns together and provides the overarching theme to how all the patterns connect and work together – it helps define the “language.”


The Portland Form is useful because it is an alternative to more keyword-based templates. The Portland Form is highly narrative, making it much easier for some people to write and/or understand. This contributes to the spread and popularity of design patterns. It’s standardized form also makes it very easy to browse and find what you are looking for.


Part 2: The Caterpillar's Fate

Source: http://c2.com/ppr/catsfate.html

The Caterpillar’s Fate is a pattern language designed to address the problems of transitioning from analysis to implementation - “from fine analysis documents to an initial software design.” It says that too many good projects are lost in this phase of transition because of lack of standards. He uses a compilation of wisdom to formulate his pattern language. Caterpillar’s Fate turns function and design analysis into object-models. He finds the objects by looking at the information, entities, User Interface, and Dataflow.

Link to this Page