How do I relate Service Domains to an Enterprise (bank on a page) view?

A Service Domain describes an elemental business capability and the Service Landscape is a reference structure that sets out all identified Service Domains grouped into related categories to help with their selection. The Service Domains define discrete functional partitions that can be reflected in the systems of an enterprise that are employed to govern and support the execution of commercial activity. The Service Domains are specifically designed to define canonical functional partitions (i.e. the designs can be consistently interpreted in different deployments) that also encapsulate discrete/non-overlapping business capabilities. When systems recognize Service Domain boundaries in their own internal modular structure and external interfaces they benefit by reducing the redundancy and fragmentation of data and function.

A typical business application will be an assembly of many related Service Domains, and the same Service Domain may sensibly be needed in multiple Business Applications. For shared or common Service Domains the Enterprise has the option to implement shared or common systems solution elements in their application portfolio. The selection and assembly of Service Domains into an enterprise ‘blueprint’ that reflects the operational and organizational structure of a particular enterprise is a fairly complex task – it is described in the Practitioner´s Guide under the topic of the “M4Bank”.