Why bother having a Business Architecture document?
A common challenge on starting down the “SOA” path is the question of “what services should I have” this is most often driven from a technical level and results in the identification of mainly low-level services. The challenges of most programs in businesses however tend to come at the start with the lack of a clearly defined scope or reason for the project, and a difficulty in breaking down the problem in to different and discreet elements that can be tracked and managed separately. It is this problem that Business Architecture documentation aims to address by breaking down challenging business problems into the services required to deliver them, thus providing a common way for package vendors to meet business objectives, and providing a simple way for organizations to agree on how to collaborate.
