The Rhythm of Software Architecture Software Development West,
April 24, 2002 by David Dikel and David KaneAbstract:
Successful investments in software architecture require more than a
clever business model, many different products and organizations must
come together. A typical application built on a shared architecture
may 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
class 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 an architecture group and across
their customers and suppliers. The instructor will describe what
rhythm is and how it has a significant effect on software
architecture. To illustrate how to take action to improve rhythm,
several organizational patterns and anti-patterns will also be
presented.
| |