[Home]OOPSLA 2002

Architecture Patterns Home | RecentChanges | Preferences | Page List | All Links | Help

Difference (from prior major revision) (no other diffs)

Changed: 1,513c1,95



OOPSLA 2002 Workshop: Patterns for Software Architecture =


Overview ===

Many authors cite the development of better software architecture as one of the key elements in improving the practice of software development. This is especially true for large-scale systems. Patterns have also emerged as a useful technique to document recurring software designs and the tradeoffs and forces that lead to these designs.

The intent of the workshop is to improve the state of the art and practice for software architecture patterns. Specifically we will discuss how software patterns relate to software architecture, organize the existing architecture patterns in to categories, and identify missing patterns for software architecture. This discussion will be a continuation of an effort begun at ChiliPlop 2002 and available at
http://www.crystalclearsoftware.com/cgi-bin/arch_patterns/wiki.pl.

In 1996 the book Pattern Oriented Software Architecture (POSA1) defined an architecture pattern as: "expressing a fundamental structural organization schema for software systems. It provides a set of predefined subsystems, specifies their responsibilities, and includes rules and guidelines for organizing the relationships between them."[1] The book describes 8 architectural patterns that mostly follow this definition. The Patterns Almanac [2] lists 79 architectural patterns. Not all of these patterns meet the POSA1 definition.

There are many open questions about how patterns are best applied to the practice of software architecture. These include understanding which patterns are "architecturally significant", how to effectively use patterns in the development of a software architecture, and how various architecture patterns are related. Some questions that the group will attempt to address include:

* How is this list of patterns related to the actual needs of a software architect/development team?
* Are all of these architectural patterns?
* How to handle large systems that use many architectural patterns together?
* What is the relationships between and classifications of these patterns?
* example: layering patterns
* example: component patterns
* What architecture patterns are missing?
* example: patterns for reuse/integration of off-the-shelf architectures (CORBA, JavaBeans, etc)
* example: runtime organization patterns
* How do we effectively document the use of patterns in the architecture?
* What is the relationship between patterns and component designs that are often used to develop architectures?

Also included will be a brainstorming session to uncover missing architectural patterns.

Preparation of Workshop Paper




Workshop participants will be asked to review the current organization of the architecture patterns Wiki at http://www.crystalclearsoftware.com/cgi-bin/arch_patterns/wiki.pl. Then they will write a position paper outlining missing architecture patterns, novel patterns organizations, or critical analysis of the current organizations. The papers should be sent to mailto:jeff@crystalclearsoftware.com

Participant position papers will be reviewed and made available for the other participants via the web site prior to the workshop.

Workshop Agenda




At the start of the workshop, the organizer will present a brief description of the goals and agenda for the workshop. Each workshop participant will then present a 5-10 minute synopsis of his or her position paper. Following the presentations, and based partially on their content, will be a discussion of the following:

* the use of patterns in the development of software architectures
* the definition of an architectural pattern
* the relationships between existing architectural patterns and actual software architectures
* organization of architectural patterns into groups
* the mapping of relationships between software architecture patterns

Since this is the beginning of a broad discussion of this topic, the workshop is likely to uncover additional areas of exploration as submitted by participants.

Post Workshop Activities




The output of the workshop will be to capture at least some of the following:

* definition for categorization of a pattern as an architecture pattern (perhaps same as POSA1, perhaps not)
* a list of missing architecture patterns that need to be developed
* a map of classifications of architecture patterns
* a diagram of relationships between architecture patterns
* a list of suggestions for application of patterns to architecture

The goal will be to capture the workshop results in the Wiki which can be used to continue the discussion after the workshop is completed.

Expected Participants




Ideally 5-10 practicing software architects and developers that are familiar with at least some of the architectural patterns, development of software architectures, and application of patterns.

Workshop Organizers




Richard Anthony
Senior Architect
Object Computing Inc.
Phoenix, Az
mailto:anthony_d@ociweb.com

Robert Gamoke
Instructor of Management Information Systems
Winona State University
Winona, MN
mailto:rgamoke@winona.edu

Jeff Garland (Primary Contact)
President & CTO
CrystalClear Software, Inc
Phoenix, Az
mailto:jeff@crystalclearsoftware.com

Robert Hanmer
Consulting Member of Technical Staff
Lucent Technologies
Lisle, Il
mailto:hanmer@lucent.com



For Questions or To Participate Contact: mailto:jeff@crystalclearsoftware.com

/position papers

OOPSLA 2002 Workshop: Patterns for Software Architecture

Overview

Many authors cite the development of better software architecture as one of the key elements in improving the practice of software development. This is especially true for large-scale systems. Patterns have also emerged as a useful technique to document recurring software designs and the tradeoffs and forces that lead to these designs.

The intent of the workshop is to improve the state of the art and practice for software architecture patterns. Specifically we will discuss how software patterns relate to software architecture, organize the existing architecture patterns in to categories, and identify missing patterns for software architecture. This discussion will be a continuation of an effort begun at ChiliPlop 2002 and available at http://www.crystalclearsoftware.com/cgi-bin/arch_patterns/wiki.pl.

In 1996 the book Pattern Oriented Software Architecture (POSA1) defined an architecture pattern as: "expressing a fundamental structural organization schema for software systems. It provides a set of predefined subsystems, specifies their responsibilities, and includes rules and guidelines for organizing the relationships between them."[1] The book describes 8 architectural patterns that mostly follow this definition. The Patterns Almanac [2] lists 79 architectural patterns. Not all of these patterns meet the POSA1 definition.

There are many open questions about how patterns are best applied to the practice of software architecture. These include understanding which patterns are "architecturally significant", how to effectively use patterns in the development of a software architecture, and how various architecture patterns are related. Some questions that the group will attempt to address include:

Also included will be a brainstorming session to uncover missing architectural patterns.

Preparation of Workshop Paper

Workshop participants will be asked to review the current organization of the architecture patterns Wiki at http://www.crystalclearsoftware.com/cgi-bin/arch_patterns/wiki.pl. Then they will write a position paper outlining missing architecture patterns, novel patterns organizations, or critical analysis of the current organizations. The papers should be sent to mailto:jeff@crystalclearsoftware.com

Participant position papers will be reviewed and made available for the other participants via the web site prior to the workshop.

Workshop Agenda

At the start of the workshop, the organizer will present a brief description of the goals and agenda for the workshop. Each workshop participant will then present a 5-10 minute synopsis of his or her position paper. Following the presentations, and based partially on their content, will be a discussion of the following:

Since this is the beginning of a broad discussion of this topic, the workshop is likely to uncover additional areas of exploration as submitted by participants.

Post Workshop Activities

The output of the workshop will be to capture at least some of the following:

The goal will be to capture the workshop results in the Wiki which can be used to continue the discussion after the workshop is completed.

Expected Participants

Ideally 5-10 practicing software architects and developers that are familiar with at least some of the architectural patterns, development of software architectures, and application of patterns.

Workshop Organizers

Richard Anthony

 Senior Architect
 Object Computing Inc.
 Phoenix, Az
 mailto:anthony_d@ociweb.com

Robert Gamoke

 Instructor of Management Information Systems
 Winona State University
 Winona, MN
 mailto:rgamoke@winona.edu

Jeff Garland (Primary Contact)

 President & CTO
 CrystalClear Software, Inc
 Phoenix, Az
 mailto:jeff@crystalclearsoftware.com

Robert Hanmer

 Consulting Member of Technical Staff
 Lucent Technologies
 Lisle, Il
 mailto:hanmer@lucent.com

For Questions or To Participate Contact: mailto:jeff@crystalclearsoftware.com

/position papers


Architecture Patterns Home | RecentChanges | Preferences | Page List | All Links | Help
This page is read-only | View other revisions
Last edited January 8, 2005 11:02 (diff)
Search: