Every year, Forrester puts on the Enterprise Architecture Awards. Vetted analysts performed the first round of review, the previous winners act as final judges and vote for the teams they believe had the most impact on moving their businesses forward. The companies remain unnamed during the voting process.
Business capability modeling is an technique for the representation of an organization’s business anchor model independent of the organization’s structure, processes, people or domains.
While the value of Enterprise Architecture is intuitively clear to many people, the hard numbers, in terms of dollars or euros, may be hard to grasp. How much is added IT landscape transparency worth in numbers? We created this tool to assist Enterprise Architects in justifying the investment in the EA specific tools you use, projects, and the existence of the EA team.
Maintaining data quality is an ongoing issue that affects many businesses. Millions of dollars of budget are wasted every year because of poor data quality. Companies rely on accurate data to assist their marketing, sales and customer service efforts. If the marketing department doesn’t have the right information on their customers, they could waste precious time chasing leads that don't exist.
The results are out. McKinsey reports that IT is expected to have a more strategic and dominating role in enterprises - and Enterprise Architects are at the forefront of these leaders. Enterprise Architects are rising stars of the IT department. But with this new influence comes a heightened responsibility. Enterprise Architects must raise their skills, visibility, and influence within the organization by leveraging cutting-edge technology and an agile mindset to move the business’s innovation agenda forward. This blogpost will detail the mindset of the modern Enterprise Architect.
This in-depth blog post will cover business capabilities, their attributes, use cases, and tips to use them in your daily practice.
In a previous post, we highlighted three use cases solved with Enterprise Architecture: Integration Architecture, Technology Obsolescence, and Data Compliance. For a full overview of these Enterprise Architecture use cases, and specialized EA tools may help, see this post.
This third and final installment of the 9 uses cases solved with Enterprise Architecture; we highlight the following four use-cases: Standards Governance, Monolith to Microservices, Cloud Transformation, and IoT Architecture.
The birth of Enterprise Architecture
In the 1980s, John Zachman wrote “A Framework for Information Systems Architecture,” and from there, the ideas around Enterprise Architecture were born. Zachman pointed out that with the increasing size and complexity of the implementations of information systems, it would be beneficial to construct architecture for defining and controlling the interfaces and the integration of all of the components of the system.
In a previous post, we highlighted two use cases solved with Enterprise Architecture: Post Merger Harmonization and Application Rationalization. For a full overview of these Enterprise Architecture use cases, and specialized EA tools may help, see this post.
This second installment of the 9 uses cases solved with Enterprise Architecture; we highlight the following three use-cases: Integration Architecture, Technology Obsolescence, and Data Compliance.