The BIAN model offers a ‘new’ perspective of business behavior by identifying discrete business capability partitions as opposed to the more conventional process models. The most common justification for adopting a capability model when developing systems solutions is to support better service enablement. There are however ways that the discrete business capability partitions can be used to improve the legacy application portfolio. Because the Service Domains define enduring, non-overlapping partitions when the legacy applications are mapped to them this can be used to identify duplication and fragmentation in the legacy application portfolio. The Service Domains collectively define a framework that can also be used to determine master/slave associations across the application portfolio. This approach is referred to as ‘synchronization’ in the How To Guide - Applying the Standard.