Software Architecture: Organizational Principles and Patterns Software Architecture: Organizational Principles and Patterns Software Architecture: Organizational Principles and Patterns Worldwide Institute of Software ArchitectsWorldwide Institute of Software Architects

Publications

   Home
   Reviews
   Publications
   Presentations
   Errata
   References
   Resources
   Search
Patterns for Managing the Rhythm of E-Commerce
Cutter IT Journal, January 2001
by David Kane, David Dikel and Jim Wilson

Abstract: Building successful e-commerce applications requires more than a clever business model, many different products and organizations must come together. A typical e-commerce transaction will traverse the Internet, client browsers, Web servers, business logic components, security systems and back-end databases. In this environment, many partners must coordinate their activities. This article examines how rhythm can have a powerful effect on keeping these separate organizations in sync. Rhythm is the recurring, predictable exchange of work products within a software development group and across their customers and suppliers. This article describes what rhythm is and how it has a significant effect on e-commerce. To illustrate how to take action to improve rhythm, we also present several organizational patterns. These patterns are similar to those found on the book Design Patterns, but focus on organizational problems instead of design problems.

Patterns presented:

  • Release Committee
  • Drop Pass
  • Synchronize Releases

Note: This article is similar to one of the chapters from our book, Software Architecture: Organizational Principles and Patterns.


Copyright © 2003 David Kane, David Dikel, and Jim Wilson


If you have questions or comments about this site, please send them to info@vraps.com