As a matter of fact, the architecture has to accommodate the fact that all organizations operate simultaneously as open and closed systems that might be used to define architectural quality.
It is an effective planning & communication tool to help the organization make seamless transformation from “as is,” to “to-be.” Business architecture needs to define the following components:
A framework: The framework is a structure or view to search underlying business laws or patterns that optimize business processes and develop the best or next practices. It describes a best practice of how things should be done from the process and documentation side, and it needs to continue to update. It is defined as a set of principles/models that underpins the establishment, governance of particular business activities.
The Architecture framework is a structure, like a chest of drawers. You can open drawers, put things in and take things out. Some are well organized; some are empty and some of the content should be replaced. But you will soon know which drawers contain the artifacts valuable to you, which drawers to keep shut and how rewarding it is to put new or improved things back into the drawers for future reuse. An effective framework clarifies logics of classification, configuration, generalization, specialization, inference & deference, to improve organizational manageability.
A Method (Cookbook): Enterprise Architecture is a series of design or management methodologies and industry-standard practices to describe what you do, why, how, where, and who derives or how to do it. Enterprise Architecture needs to develop further architecture standards to deal with the tension between standardization and change smoothly. It can be very invaluable for performing a wide array of services such as strategic positioning, business process measurement, optimization, and other business practices.
At the operational level, a technical or operational cookbook articulates operating rules and procedures comprehensively, offers a linear step-by-step manual to follow for tuning the enterprise machine and ensuring it keeps spinning to improve business efficiency. The business cookbook or manual helps to describe and share the industry best practices; describe standard operating procedures to take transactional activities for improving workforce productivity.
Enterprise architecture can create a comprehensive capability map, then use it to drive portfolio management, heat map analysis, etc. becoming an instrument for leading changes. Deliverables are of themselves reasonably easy to describe generically, but will vary dramatically in applicability, importance, and workload to complete. It greatly depends on the nature of the initiatives and the preparedness of the environment to adopt the change.
The real value of business architecture is about keeping the priorities in balance and facilitating strategic communications, to highlight changes with standardization, coherence, and visualization of business improvement. As a matter of fact, the architecture has to accommodate the fact that all organizations operate simultaneously as open and closed systems that might be used to define architectural quality. So the business management can leverage architecture as an effective tool to drive transformative changes.
0 comments:
Post a Comment