Create business capability and relate the capability with an application
Business capabilities are the abilities of an organization to do an activity to fulfill its business goals. Align your organization goals with business capabilities by creating capabilities.
시작하기 전에
Starting with the Xanadu release, the legacy business capability module has been deprecated from Enterprise Architecture (formerly Application Portfolio Management). However, if you’re an existing user of Enterprise Architecture (formerly Application Portfolio Management), you can still use the legacy business capability module. If you’re a new activation user, the legacy business capability module isn’t available.
You can leverage the same features by using the Enterprise Architecture Workspace. To learn more, see Exploring business capabilities.
Role required: sn_apm.apm_admin
이 태스크 정보
Use the Business Capability form to create and update a business capability. If you add a new capability, update an existing capability, delete a capability at a leaf node level, then the levels of all the capabilities and the leaf node in that hierarchy must be updated accordingly. Select the Update Capability Level and HierarchyID related link to update the levels in the hierarchy so that the capability map reflects the updates. The Leaf Node and the Level fields are rendered uneditable to you, yet you can view the level of the capability if it is at the leaf node and its position in the hierarchy.
Following are the conditions to update or delete a capability:
- When you add a capability, the level of the new capability in the hierarchy is automatically assigned based on the level of the parent capability that is attached.
- If a parent capability is updated in the hierarchy, then the levels of all its child capabilities are recalculated. Otherwise, a capability can only be updated of its name, description, or parent.
- While adding or updating a capability the total number of levels can’t exceed more than six in the hierarchy. For example, the levels can be from 0 to 5, where 0 is the root level.
- You can delete capabilities that are at the leaf node level only. Or, a capability that does not have a child capability of its own.
- Don’t create circular relationships. In creating a parent capability, a child capability can’t be its parent.
프로시저
다음에 수행할 작업
View capability based planning to understand the hierarchy of capabilities mapped with its related applications and plan investments in applications if the technology of the applications is at a risk.