Interpreting the BIAN Standard in Implementation
The BIAN standard is defined at the business architecture level. As explained in Section 1 of this guide it also adopts a service based perspective (a service oriented architecture SOA). In order to leverage the BIAN standard its business level representation needs to be related to different systems architecture views for systems solution design and deployment. The systems architecture views required will vary depending on the deployment approach and the target technical environment.
BIAN members tend to apply the BIAN standard in two fundamentally different deployment situations. In one the BIAN standard is used to help define well bounded or ‘targeted’ system implementation solutions. In the other the BIAN standard is used to create a much broader “enterprise blueprint” that can be used for a wide range of business and systems planning and analysis activities.
In this section the interpretation of the BIAN standard is covered as follows:
- Relating the BIAN business architecture to underlying application/systems architectures – some general considerations
- Mapping the BIAN standard to other industry standards
Applying the BIAN standard in three different technical implementation environments.
Conventional (legacy/core) application renewal/rationalization
- Host/ESB integration and application assembly
Loose coupled distributed/Cloud applications
Using the BIAN standard to define an enterprise blueprint that can be used for business and systems planning and analysis.
Note that in this document the design concepts and principles are explained in general terms. The specific guidelines and techniques used to deploy the standard are repeated in more detail the third document of the series: ‘How-to Guide - Applying the BIAN Standard.’