The Banking Industry Architecture Network (BIAN) is an independent organization that was created in 2008 to define standards and best practices for service-oriented architecture in the banking industry. BIAN’s main goal is to reduce the integration costs that banks incur when they combine software obtained from multiple sources. BIAN’s members include leading banks, vendors of banking applications, and service providers.
In my SDN article Getting Started with the Banking Industry Architecture Network (BIAN), which elaborates on BIAN’s value proposition for the banking industry and outlines the organizational structure, I mentioned that BIAN is breaking down banking functionality into discrete modules, and defining service interfaces to those modules. BIAN calls this breakdown the Service Landscape. Let’s examine what the Service Landscape looks like.
The figure below is a high-level schematic of the Service Landscape that BIAN is in the process of defining. BIAN is working on an updated Service Landscape that will be working its way through the ratification process.
The figure reveals that the Service Landscape is structured a hierarchical, functional decomposition of banking functionality. The highest level of the hierarchy is Business Area. A Business Area is a very broad grouping of banking application functionality. Business Areas are broken down into Business Domains. A Business Domain is a coherent set of capabilities and responsibilities.
Business Domains break down into Subdomains. For example, the Markeing Business Domain of the Sales & Service Business Area breaks down into the following Subdomains:
- Campaign management (plan and manage campaigns)
- Campaign automation (support campaign execution)
- Lead management (define lead criteria, supply leads)
The Business Area / Business Domain / Subdomain structure helps to make the Service Landscape more manageable than it would be if it were simply a flat space of functional modules.
BIAN services define interfaces to Subdomains; in other words, a Subdomain is a module that exposes service interfaces. The Servce Landscape is being built up gradually, and a lot of work is going on to define services for the Subdomains that have already been identified.
It’s important to know that a service of one Subdomain can depend on a service of another Subdomain. Thus, although the Business Area / Business Domain / Subdomain breakdown is strictly hierarchical, cross-dependencies among Subdomains are allowed and in fact are necessary to support cross-domain business processes. Also, note that the Service Landscape is not itself a breakdown of processes or of organizatinal structure.
In future blogs, we’ll take a look at how BIAN defines services for Subdomains. We’ll also examine how BIAN goes about modeling business objects and message exchange, and how those models fit into the Service Landscape.