The Three-Tier Architecture Pattern Language Workshop

OOPSLA 2001,
Tampa Bay, Florida

October 15, 2001



Submissions and Presentations

Name Affiliation  Position Paper (.pdf) Presentation (.ppt)
Brian Berenbach Siemens Corporate Research Inc. Container Based Persistence BrianBerenbach.ppt
Marco Torchiano, Letizia Jaccheri, Tor Stålhane  Norwegian University of Science and Technology Lessons learnt from developing and changing an
educational three tier system

Jim Tyhurst, Ph.D.
Tyhurst Technology Group LLC Choosing Transaction Models for Enterprise Applications JimTyhurst.ppt
Prashant Jain and Michael Kircher Siemens AG A Pattern Language for Resource Management in Three Tier Architectures PrashantJain.ppt
Klaus Wolfmaier, Thomas Ziebermayr Software Competence Center Hagenberg A Layered Distributed Application: An Experience Report
Kjell Pettersson RFV Data
Roger Larsson Incrementa AB


Usually you talk about three tiers, which are: presentation, business, data.
But to separate concerns even more, you group responsibilities into even more logical layers.

Why layers?

How many layers do you need? The following list shows the layers we agreed on, which are most common: General/Cross-cutting Forces:

General Patterns:

Discussion on Legacy Integration

Legacy Systems can be: Enterprise-Information-Systems, Back-Ends,
Mainframes (with overlap of course).

They can provide pure services, pure data access, or any combination of them.

Pattern Language Discussion

What kind of patterns is important to put into the pattern language? What kind of pattern language could we document?