30 December, 2020
16 December, 2020
19 November, 2020
28 October, 2020
25 March, 2009
TOGAF 9 introduces a very appealing concept of Capability-based planning for Business People

Capabilities are in fact the building blocks of business. A business capability typically defines what a business unit‘s purpose is (goals and objectives), its core competencies, and is therefore directly bound to business objectives and strategy. Capabilities provide a black-box view of those things the business can do, i.e. working on business artifacts (e.g. Business Processes, Catalogs).
The business processes and resources involved in providing the capabilities are not exposed (business service orientation). Capabilities aren‘t isolated but form hierarchical value-networks with relationships that materialize the business processes. At a lower level, capabilities are modeled using traditional activity diagrams used for the design and implementation of IT solutions.
The key elements of capabilities-based planning are a conceptual framework, an analytical framework and a building block approach to applying the frameworks.
· A conceptual framework allows for business planning under uncertainty by emphasizing flexibility, robustness and adaptive capability
· The analytical framework provides a way to assess business capability options at the operational level and choose among capability alternatives
· A building block approach allows us to define, develop and test individual capabilities within their own business domains
Capabilities them can be developed and evaluated within smaller architecture domains from phase B to phase D, and then later combined to describe joint forces capabilities in Transition Architectures identified in phases E-F.
Capability Based Planning also revolves around the establishment of the capacity and ability to execute a designated set of generic tasks, bringing enormous help when entering the Opportunities & Solutions and Migration Planning phases. It is an effective way of selling the value of Enterprise Architecture to the business, without being too much theoretical…
13 March, 2008
Business Architecture and Capability Modeling
Capabilities provide a black-box view of those things the business can do, i.e. working on business artifacts. The business processes and resources involved in providing the capability are not exposed (business service orientation). Capabilities aren‘t isolated but form hierarchical value-networks with relationships that materialize the business processes. At a lower level, capabilities are modeled using traditional activities diagrams used for the implementation of IT solutions.
The key benefit that capability modeling provides over business process modeling is that it focuses on those elements of the business that are the most stable, and therefore facilitates the alignment with key IT initiatives, especially SOA adoption programs, which can leverage stable business concepts rather than process activities that are continuously evolving.
Outputs of capability modeling activities are direct inputs into the activities of service identification, definition and interface design (SOA).
Modeling effort should be done incrementally, with focus on key business initiatives first.
Capabilities modeling has proven to be particularly efficient in allowing to solve business issues not addressable in other ways. It also eases the deployment of business activity monitoring, providing the insight the business needs to adapt to environmental changes or identify new opportunities.
Modeling of Business Operations (Operational modeling), using UML diagrams:
Based on Business Artifacts (artifact-centered operational modeling), which requires:
- Key Business Artifacts identification
- Artifacts life-cycle definitions
- Business tasks identification (BPMN modeling)
- Repository building for artifacts
- Flow components




