Abstract – Large businesses have a reputation for having hard-to-change systems. They can take from 90 to 180 days to implement the changes needed for some new product, process, channel, or regulatory change, and the unsung hero's, the DBA's, are singled out for their role on the critical path. On the other hand, Start-up companies have faster time-to-market speed, even with (or because of) limited resources and little systems investment.

The idea that the Business is always responsible for the work is a guiding principle for the architecture of enterprise systems. The Business Agility Pattern Language is a set of architecture patterns, taken from the Punch Card era, that implement that principle, scale-up from manual work to high volume web driven operations, and deliver business-in-charge support for continuous change.

Tom Evans provides business and enterprise architecture consulting, after beginning his career as a medical systems software engineer and then becoming an early adopter of object technology. Tom digs into large systems issues and help businesses gain clarity about their needs and then guides business and technology teams toward a common view and practical solutions. A theme for Tom's work is the creation of flexible systems, including solutions for Deluxe Check, Qwest, Freddie Mac, and Wells Fargo. Tom founded the Object Technology User Group and earned his Masters in Software Engineering at the University of St. Thomas.

To keep up with upcoming OTUG events, please visit our web site or join our email list: