Most of the discussion centered on the role of design techniques and modeling languages and the way we design software.

Brian showed a list of items spanning two slides that should be
accessible as objects.

How to factor services? Domain Specific LanguagesMartin held a session
on DSLs, asking people for their experiences. A lot has been said about
"code that is worth reading" to quote Ward Cunningham. As I hand rolled
the all parts of the system, I kept the syntax very simple.

The attendee roster sported the usual industry heavyweights, i. Contract
first development: A contract is not just a WSDL document, but an
abstract domain model.

Kent Beck's opening remark stating that he reread Structured Design to
prepare for the panel was a reliable indicator of more good things to
come. These questions rarely come up in the world of synchronous,
object-oriented applications. For example, is a method allowed to look
at the hours or minutes of a Calendar that is passed in? The process
should be able to change without having to change the capabilities. When
another application needs to reference that data it sends a query to the
owning application and waits for the response before it continues
processing.

When someone asked me recently how I keep up on all the happenings in
the software world I realized that I do a good portion of it by hanging
out around the people who know a lot more than I do.

Make sure the boundaries are clear and somewhat consistent.

Dick Gabriel even created an unofficial schedule because the official
once was nearly impossible to figure out. While thinking out loud what
we would talk about I told Mario to better start recording because good
ideas were popping out left and right. As expected we ended up with a
wide spectrum of ideas, which we then sorted into categories.

The workshop format gave participants a chance to present their current
work, followed by numerous ad-hoc workshops and discussions in larger
and smaller groups.

Experience shows that this time tends to be a lot shorter than
anticipated.

Another worry of his is that creating too many languages will cause a
new class of problems: What if my domain changes, which causes me to
change my domain specific language? As soon as the user interface
changes, chances are that the integration is broken. Well, I can simply
put Sanjiva on the spot. So Amazon decided to avoid direct database
access from the application and instead wraps all core business logic
behind a ser of services. Can it assume that they would also be
zero?

Immediately, good discussions and suggestions erupted.

The semantics of the interaction, however, are not much decoupled.
Regardless, many products are still a year or two away from GA. 1 will
include our Loan Broker example. There seemed to be a general sentiment
in the audience that programming is getting harder and harder as opposed
to simpler. Let's look at a few obvious choices:A very simple approach
assigns each component its own channel.

Essentially, the API provides a single method called hllc.

I was lucky enough to attend one of his workshops and write some code
against the library.

Because the customer management is never queried for address data it
never becomes a bottleneck even as the system grows and the demands for
address data multiply.

This observation also explains why UML Class Diagrams tend to be more
popular then Collaboration Diagrams.