Business Architecture Repository

One of the most important deliveries of business architect is to build the following repository:

• Business Vocabulary Repository
• Business Domain Model Repository
• Business Rule Repository
• Business Process Repository
• Business Event Repository

These repositories should be independent of individual project repository. Business architect should take pieces of business rules, processes and etc. from each project to contribute to the related repository. Each project should in turn take reference from these repositories. This is another instance of the so called “Plan and Harvest” paradigm.

The repositories can be organized by each business segment, for instance, retirement solutions segment, life insurance segment, and group protection segment.

It significantly reduces the power of any documents if they are not readily and easily accessible by every team member, not easily searchable, and don’t allow comments and feedbacks. A very common practice in many IT shops is to write documents in word document and put them in shared drive. This practice has severe limitations.

I will propose to utilize so called Enterprise Social Software such as wiki (I will post another blog, “Enterprise Social Software as an IT Project Platform” soon) to facilitate the celebrative creation and consumption of these repositories.