I finished up Tuesday at the conference with Bill Rosser‘s “Creating a Business Architecture”. I found his enterprise architecture models to be a bit inconsistent: at one point, he includes application architecture in information architecture; later, he splits them out as most of us would tend to do. He did make a great point about architecture up front: architecture is not creating the design, it’s creating the environment/boundary/envelope in which the design can be created. Since many people don’t make the distinction between architecture and design (or even, in some extreme cases, architecture and coding), this was valuable as an explicit statement.
What I did find about Rosser’s talk, like all the other non-BPM “special interest” sessions that I attended (Six Sigma, business rules), is that he failed to make an adequate linkage back to BPM in the presentation. I’ve given presentations on enterprise architecture and BPM in the past, (as well as ones that involve Six Sigma and business rules tied to BPM) and it’s very easy to make a strong link between them, so I consider the lack of tie-in to BPM a critical failing of Rosser’s presentation.