ChatDiagram
enterprise architecture · business architecture · capability mapping

Enterprise Business Capability Map

This enterprise business capability map connects external customers and partners to sales, customer-service and finance capabilities. CRM supports sales and service, while ERP supports finance. Both applications use master data as a shared information point. It is a useful early enterprise architecture view because it connects business responsibilities to application support without becoming an organizational chart or a detailed process model.

유형 블록 다이어그램표준 Ogata / standard controls textbook convention엔진 schematex-blockdiagram업데이트됨 2026. 9. 24.
Enterprise Business Capability Map
Drawing preview
요청 내용

“Create an enterprise business capability map with customers and partners, sales, customer service and finance capabilities, CRM and ERP applications, and master data.”

그렇다면Add a marketing capability connected to the CRM application.Add a supplier management capability connected to ERP.
이 도면에 담긴 내용

그 이면의 의사결정을 읽어 보세요.

01Customer scope

Start with customers and partners as external actors.

02Capability view

Separate sales, service and finance work.

03Application support

Map CRM and ERP to those capabilities.

04Shared information

Join application records through master data.

Use it for a concise business-to-application enterprise architecture view.

모든 블록 다이어그램 템플릿 보기 →

자주 묻는 질문

자주 묻는 질문

What is a business capability map?

It organizes what an enterprise needs to be able to do, independent of its current teams or systems.

Why map capabilities to applications?

The mapping shows which systems support important business abilities and where dependencies exist.

What is master data in this view?

It is shared core information, such as customers or products, used consistently across applications.