When it comes to ba stages which two of the following statements are true
Objectives | Approach | Inputs | Steps | Outputs This chapter describes the development of a Business Architecture. Show ObjectivesThe objectives of Phase B are:
ApproachGeneralA knowledge of the Business Architecture is a prerequisite for architecture work in any other domain (Data, Applications, Technology), and is therefore the first architecture activity that needs to be undertaken, if not catered for already in other organizational processes (enterprise planning, strategic business planning, business process re-engineering, etc.). In practical terms, the Business Architecture is also often necessary as a means of demonstrating the business value of subsequent Technical Architecture work to key stakeholders, and the return on investment to those stakeholders from supporting and participating in the subsequent work. The extent of the work in Phase B will depend to a large extent on the enterprise environment. In some cases, key elements of the Business Architecture may be done in other activities; for example, the enterprise mission, vision, strategy, and goals may be documented as part of some wider business strategy or enterprise planning activity that has its own lifecycle within the enterprise. In such cases, there may be a need to verify and update the currently documented business strategy and plans, and/or to bridge between high-level business drivers, business strategy, and goals on the one hand, and the specific business requirements that are relevant to this architecture development effort. (The business strategy typically defines what to achieve - the goals and drivers, and the metrics for success - but not how to get there. That is role of the Business Architecture.) In other cases, little or no Business Architecture work may have been done to date. In such cases, there will be a need for the architecture team to research, verify, and gain buy-in to the key business objectives and processes that the architecture is to support. This may be done as a free-standing exercise, either preceding architecture development, or as part of Phase A. In both of these cases, the business scenario technique (see Business Scenarios) of the TOGAF ADM, or any other method that illuminates the key business requirements and indicates the implied technical requirements for IT architecture, may be used. A key objective is to re-use existing material as much as possible. In architecturally more mature environments, there will be existing architecture definitions, which (hopefully) will have been maintained since the last architecture development cycle. Where existing architectural descriptions exist, these can be used as a starting point, and verified and updated if necessary; see The Architecture Continuum . Gather and analyze only that information that allows informed decisions to be made relevant to the scope of this architecture effort. If this effort is focused on the definition of (possibly new) business processes, then Phase B will necessarily involve a lot of detailed work. If the focus is more on the Target Architectures in other domains (data/information, application systems, infrastructure) to support an essentially existing Business Architecture, then it is important to build a complete picture in Phase B without going into unnecessary detail. Developing the Baseline DescriptionIn architecturally more mature environments, there will be existing architecture definitions, which (hopefully) will have been maintained since the last architecture development cycle. Where existing architectural descriptions exist, they can be used as a starting point, and verified and updated if necessary. Any such existing descriptions will already have been used in Phase A in developing an Architecture Vision, and this work should provide a sound basis for the Baseline Description, and may even be sufficient in itself. Where no such descriptions exist, information will have to be gathered in whatever format comes to hand. The normal approach to Target Architecture development is top-down. In the Baseline Description, however, the analysis of the current state often has to be done bottom-up, particularly where little or no existing architecture assets exist. In such a case, the architect simply has to document the working assumptions about high-level architectures, and the process is one of gathering evidence to turn the working assumptions into fact, until the law of diminishing returns sets in. Business processes that are not to be carried forward have no intrinsic value. However, when developing Baseline Descriptions in other architecture domains, architectural components (principles, models, standards, and current inventory) that are not to be carried forward may still have an intrinsic value, and an inventory may be needed in order to understand the residual value (if any) of those components. Whatever the approach, the goal should be to re-use existing material as much as possible, and to gather and analyze only that information that allows informed decisions to be made regarding the Target Business Architecture. It is important to build a complete picture without going into unnecessary detail. Business ModelingA variety of modeling tools and techniques may be employed, if deemed appropriate (bearing in mind the above caution not to go into unnecessary detail). For example:
(UML Business Class Diagram, Trade Class Model (Commercial View) is taken from the Practical Guide to Federal Enterprise Architecture.) All three types of model types above can be represented in Unified Modeling Language (UML), and a variety of tools exist for generating such models. Certain industry sectors have modeling techniques specific to the sector concerned. For example, the Defense sector uses the following models:
Although originally developed for use in the Defense sector, these models are finding increasing use in other sectors of government, and may also be considered for use in non-government environments. Enterprise ContinuumAs part of Phase B, the architecture team will need to consider what relevant Business Architecture resources are available from the Enterprise Continuum, in particular:
Gap AnalysisA key step in validating an architecture is to consider what may have been forgotten. The architecture must support all of the essential information processing needs of the organization. The most critical source of gaps that should be considered is stakeholder concerns that have not been addressed in prior architectural work. Other potential sources of gaps:
Gap analysis highlights services and/or functions that have been accidentally left out, deliberately eliminated, or are yet to be developed or procured. Gap Analysis Matrix in Phase D illustrates an example of a gap analysis matrix. The suggested steps are as follows:
When the exercise is complete, anything under "Eliminated Services" or "New Services" is a gap, which should either be explained as correctly eliminated, or marked as to be addressed by reinstating or developing/procuring the function. InputsThe inputs to Phase B are:
StepsThe level of detail addressed in Phase B will depend on the scope and goals of the overall architecture effort. New business processes being introduced as part of this effort will need to be defined in detail during Phase B. Existing business processes to be carried over and supported in the target environment may already have been adequately defined in previous architectural work; but, if not, they too will need to be defined in Phase B. Key steps in Phase B include the following: Note:The order of the following steps should be adapted to the situation at hand: in particular, determine whether in this situation it is appropriate to do Baseline Description or Target Architecture development first, as described in Introduction to the ADM .
OutputsThe outputs of Phase B are:
return to top of page Navigation The TOGAF document set is designed for use with frames. To navigate around the document:
return to top of page Downloads Downloads of the TOGAF documentation, are available under license from the TOGAF information web site. The license is free to any organization wishing to use TOGAF entirely for internal purposes (for example, to develop an information system architecture for use within that organization). A hardcopy book is also available from The Open Group Bookstore as document G063. Copyright © 1999-2006 The Open Group, All Rights Reserved TOGAF is a trademark of The Open Group What is the main objective of phase B or the business architecture?The objectives of Phase B are to: Develop the Target Business Architecture that describes how the enterprise needs to operate to achieve the business goals, and respond to the strategic drivers set out in the Architecture Vision, in a way that addresses the Request for Architecture Work and stakeholder concerns.
What is the business architecture development?Business Architecture reveals how an organization is structured and can clearly demonstrate how elements such as capabilities, processes, organization and information fit together. The relationships among the elements dictate and specify what the organization does, and what it needs to do to meet its common goals.
What could be the output of business architecture phase B in our ADM?All TOGAF ADM Phases lead you to developing the knowledge you need. The outcome of Phase B is the candidate business architecture. The business architecture domain architecture approved by the stakeholders for the problem being addressed, with a set of gaps, and work to clear the gaps understood by the stakeholders.
What is a Cisco ba?The Cisco Business Architecture Analyst is a certification program that prepares IT and line-of-business professionals to build and strengthen the bridge between technology solutions and critical business needs.
|