One of the most interesting and difficult challenges of Business Architecture is creating the capability model for an enterprise. Fortunately, the efforts of the Business Architecture Guild have started to produce value in the form of Reference Models.
Content Metamodel Chapter Contents At each phase within the ADM, a discussion of inputs, outputs, and steps describes a number of architectural work products or artifacts, such as process and application.
The content metamodel provided here defines a formal structure for these terms to ensure consistency within the ADM and also to provide guidance for organizations that wish to implement their architecture within an architecture tool.
Subsequent sections then go on to discuss each area of the metamodel in more detail. Contents of this section are as follows: Core content metamodel concepts see This section introduces the core concepts that make up the TOGAF content metamodel, through the following subsections: Core and Extension Content provides an introduction to the way in which the TOGAF framework employs a basic core metamodel and then applies a number of extension modules to address specific architectural issues in more detail Core Metamodel Entities introduces the core TOGAF metamodel entities, showing the purpose of each entity and the key relationships that support architectural traceability Core and Extension Content The role of the TOGAF framework is to provide an open standard for architecture that is applicable in many scenarios and situations.
In order to meet this vision, it is necessary to provide a fully featured Enterprise Architecture metamodel for content and also to provide the ability to avoid carrying out unnecessary activities by supporting tailoring.
The metamodel must provide a basic model with the minimum feature set and then support the inclusion of optional extensions during engagement tailoring. TOGAF Content Metamodel and its Extensions The core metamodel provides a minimum set of architectural content to support traceability across artifacts.
Additional metamodel concepts to support more specific or more in-depth modeling are contained within a group of extensions that logically cluster extension catalogs, matrices, and diagrams, allowing focus in areas of specific interest and focus. All extension modules are optional and should be selected during the Preliminary Phase of the architecture development to meet the needs of the organization.
Additionally, the extension groupings described by the content metamodel are only a suggestion and further tailoring may be carried out to suit the specific needs at the discretion of the architects.
The following core terms are used: Some of the key relationship concepts related to the core metamodel entities are described below: Process should normally be used to describe flow A process is a flow of interactions between functions and services and cannot be physically deployed.
All processes should describe the flow of execution for a function and therefore the deployment of a process is through the function it supports; i. Function describes units of business capability at all levels of granularity The term "function" is used to describe a unit of business capability at all levels of granularity, encapsulating terms such as value chain, process area, capability, business function, etc.
Any bounded unit of business function should be described as a function.
Business services support organizational objectives and are defined at a level of granularity consistent with the level of governance needed A business service operates as a boundary for one or more functions.
The granularity of business services is dependent on the focus and emphasis of the business as reflected by its drivers, goals, and objectives. Business services are deployed onto application components Business services may be realized by business activity that does not relate to IT, or may be realized through IT.
Business services that are realized through IT are implemented onto application components. Application components can be hierarchically decomposed and may support one or more business services.In government, IT planning is often fragmented and doesn't align with business strategy.
Enterprise architecture and IT portfolio management should mutually reinforce one another and guide IT investment selection, control and evaluation.
Blog Title. Author. Date. BPC Topic Area. Dependent Tasks in Business Planning and Consolidation NW (BPC) pfmlures.com Kumar. Dec. 31, Security. Tip on Using Data Manager Package IMPORT_USING_FTP in SAP BusinessObjects Planning and Consolidation, version for NetWeaver.
Steps to maximize brand architecture: take stock of your brand portfolio from the perspective of customers because their view is the foundation for your strategy; do “brand relationship mapping” to identify the relationships and opportunities between brands across your portfolio.
SAP BPC Architecture. SAP BPC Architecture. It uses various business rules and script logics for doing the planning. The key components in BPC architecture are shown in the image below.
A Comprehensive Approach to Application Portfolio Rationalization • Cognizant Insights business-aligned portfolio can enable operational agility and flexibility; however, it may necessitate experts would agree that strategic planning should be at the heart of the IT leader’s.
An Oracle White Paper in Enterprise Architecture—Architectural Strategies for IT Optimization: From Silos to Clouds 3 Executive Overview In business and IT, there is .