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 - Chris Ronderos

Part 1 – Question 4:
The Portland Form is one organizational style for documenting design practices. Unlike other styles, the Portland Form uses complete sentences in paragraphs to form a “narrative” of the problem and the solution. This differs from most other organizational styles, which use bulleted lists or outlines to organize information about design practices.

In the Portland Form, each pattern “makes a statement” consisting of a description of the forces that cause the problem and the pattern’s solution for the problem. Other portions of the Form are used to describe the relative strengths of the forces that cause the problem, so that a designer may conserve resources and start with the most important forces to change his software engineering style. Design patterns pertaining to a common theme are related with a final paragraph describing the theme and the related patterns.

“About the Portland Form” http://c2.com/ppr/about/portland.html

Part 2:
Simple Enumeration Parameter

This design pattern allows a simple and consistent way to convey meaning while enumerating through data. The question is what to call the variable that is a reference to each piece of the data in turn. The solution, so simple yet effective, is to use the name “each.” When enumerating through a data structure, using the variable name “each” to refer to the data communicates that “each” piece of data will be subjected to the same process.

This design pattern makes a lot of sense to me. I have actually had problems in the past figuring out what to call variables when data is enumerated or iterated through, and I have a pointer that changes with each iteration. “Each” is a useful name. It can be adapted to multi-dimensional enumeration. If there are two data values simultaneously, “eachX” and “eachY” are valid names that carry the required meaning. I can see using this pattern in my coding frequently whenever I enumerate through a series or collection of data, to show that I am doing so.

“Simple Enumeration Parameter” http://c2.com/ppr/formatting.html#5

Links to this Page