Enterprise Architecture Methodology pillars
Enterprise Architecture Methodology is based on four highly related specializations called architecture domains. From these we evolve the Enterprise Architecture Methodology four pillars:
- Country Governance Architecture
- The strategy, governance, organization, and key processes of the country governance
- Government Architecture
- A detailed plan for the government systems to be deployed, the interactions between these systems, and their relationships to the core governance processes with the frameworks for services to be exposed as government functions
- Data Architecture
- The structure of a country’s governance logical and physical data assets and the associated data management resources.
- Technical architecture
- Technology for governance, which describes the hardware, software, and network infrastructure needed to support the deployment of core, mission-critical applications
Architecture Development Method
The Architecture Development Method (ADM) is applied to develop an enterprise architecture that will meet the business and information technology needs of an organization. It may be tailored to the organization’s needs and is then employed to manage the execution of architecture planning activities. The process is iterative and cyclic. Each step checks with Requirements. Phase C involves some combination of both Data Architecture and Applications Architecture. Additional clarity can be added between steps B and C in order to provide a complete information architecture.
Performance engineering working practices are applied to the Requirements phase, and to the Business Architecture, Information System Architecture, and Technology architecture phases. Within Information System Architecture, it is applied to both the Data Architecture and Application Architecture.
The Enterprise Continuum is a way of classifying solutions and architectures on a continuum that ranges from generic foundation architectures to tailored organization-specific both within and outside the Architecture Repository. These include architectural models, architectural patterns, architecture descriptions, and other artifacts. These artifacts may exist within the enterprise and also in the IT industry at large.
The Enterprise Continuum consists of both the Architecture Continuum and the Solutions Continuum. The Architecture Continuum specifies the structuring of reusable architecture assets and includes rules, representations, and relationships of the information system(s) available to the enterprise. The Solutions Continuum describes the implementation of the Architecture Continuum by defining reusable solutions building blocks.
Despite Enterprise Architecture Methodology being considered as the de facto standard in an EA practice, it is not without its critics. In this section, I will try and predict the future criticisms of the Enterprise Architecture Methodology4G variant.
- Research evidence shows that “most Enterprise Architecture Methodology recommendations are usually found inapplicable” and not followed even in the organizations included in the list of Enterprise Architecture Methodology-users provided by. That is why Enterprise Architecture Methodology can be considered only as “a toolkit of random EA-related recommendations” and “‘using Enterprise Architecture Methodology’ can be best explained as ‘studying Enterprise Architecture Methodology and then doing something else instead’”
- Using full or entire Enterprise Architecture Methodology on any project or in any enterprise is very counter-effective. Enterprise Architecture Methodology is vast. It was never designed to be used without some serious tailoring first. Enterprise Architecture Methodology works best when it is tailored a to a specific context.
- Enterprise Architecture Methodology4G is probably a specific variant of Enterprise Architecture Methodology to evolve from it by crafty tailoring.
- Enterprise Architecture Methodology4G is envisioned as a subset of Enterprise Architecture Methodology
- Best Enterprise Architecture Methodology practitioners are the ones capable of effective refactoring of it for the particular organization and the refactoring out that for particular projects in the organizations.
- Real examples demonstrating the actual practical usage of Enterprise Architecture Methodology’s recommendations are missing. “There is a pressing need for some detailed worked examples and use cases. Although these were requested, they were not forthcoming from Enterprise Architecture Methodology trainers or ”
- I have seen dozens of very good examples where organizations have made an Enterprise Architecture Methodology friendly environment by both organizing architecture leadership and not imposing the full Enterprise Architecture Methodology on other roles in the teams.
- EA practitioners report that Enterprise Architecture Methodology can hardly be followed step-by-step. “Our initial assumptions about Enterprise Architecture Methodology were that it would be a sort of ‘methodology’ that we could follow to produce our EA. However, this turned out not to be the case”
- Enterprise Architecture Methodology is too big to be used as an effective methodology out of the box.
- It is critical to use its subset defined by resident Enterprise Architecture Methodology expert/
- Enterprise Architecture Methodology’s prescriptions are vague and inarticulate since it “only states that the ADM should be adapted without specifying how”
- “adapting the ADM” is wrong. The whole method has to be adapted by using its subset for the given context.
Better than doing nothing?
Well in the context of country governance and government that is certainly true. But in practice never the case. No government “does nothing”. But every government is constantly under monetary and political pressure to be more productive, resilient to change, and to act as a robust and efficient system.
The aim of Enterprise Architecture Methodology4G is quite clear and simple: it is a very efficient idea to start shaping up the most productive and effective government.