• All in the Memory -- bookkeeping services
• Arabella -- a dynamic musical duo
• Bytesmiths Editions -- large, archival, fine-art photography on unusual materials
• Bytesmiths Press -- artists' services: web design/hosting, jury slides, giclee reproductions, opening announcements, brochures, etc.
• Champagne Beadworks -- handcrafted jewelry and beadwork
• Crafted By Carol -- handcrafted jewelry and beadwork
• Dana Fontaine -- unique photography-derived art
• Dymond Graphics -- note cards, pet/people photography
• Fountains & Funktini -- glass art and more from Beth Keenan and JoAnn Rawley
• Gemini Gypsy -- Carole Good-Hanson's fused glass frames
• Mary Kollman Fine Art -- lovely floral watercolor originals
• Primrose Studio -- terra cotta switch plate covers and wall art
• Ratso's Studio -- astoundingly realistic bronze sculpture
• The Spiral Gallery -- local artists exhibit in the Oregon Cascades foothills
• The Roaming Artist -- info and resources for artists "on the road"
• Van Dyke Sepias -- Jan Van Dyke's nostalgic sepia toned photography
• Veggiemog -- life and times of Kelly O'Toole's Unimog, running on biodiesel
• Village of Willamette Arts Festival -- annual visual/performing arts festival, third weekend of September
• Whitehorse Designs -- Gwen Miller's beadwork and fused glass
• West Linn Arts Commission -- city support for the arts

Spiral Prototyping Activity

If you thought the last slide was unusual, things are about to really get strange! In the spiral prototyping activity:

1. Classes and class specifications are identified from the partitioned/contracted subsystem. The class specifications are as formal as needed, and are stored in the class comment. The system browsers should be modified as needed to support special organizational specification needs, rather than require the developer to leave Smalltalk to use a different environment. These classes and class specifications identify subsystem collaborators, which may eventually be further broken down. (String is broken down as a Collection of Characters , for example.)

2. Behavior is described in terms of method names and specifications, which are stored as method comments or in method associated storage.

3. The specified classes and methods are implemented, producing functionality.

4. Functionality is tested, integrated, and reviewed in parallel, producing possible corrections that are fed back to implementation, additional subsystem partitioning/contracting information, and collaboration/responsibility criticism, as well as a product.

5. This activity is iterated as allowed by market opportunity windows and resource budgets.

[ prev | top | next ]