In the course of two days of sessions here at the Gilbane Conference it is
clear that, when it comes to compliance, we’ve overloaded the word
"architecture." We have had a fair amount of talk in some of the
conference sessions about "compliance architectures." We have also
seen different technology architectures used to support compliance systems.
It is easy to understand why at least some of the people in the audience
could get all of this confused. Sometimes it seems that even the speakers
have the two "architectures" confused and wrapped around each
other. The bad result that comes from this goes beyond a few confusing
conversations. If there is enough confusion, the consequence is a
misdirected approach to addressing compliance issues in individual
organizations.
So… I’ll take a crack at getting the terms and ideas unwound from each
other. Think of these as "first cut" definitions–aimed at
helping people who are just now coming to terms with compliance lingo to
understand what is going on. If you can help out here–improving the
definitions–please add some comments.