Enterprise architects are often challenged by the many enterprise architecture terms with conflicting interpretations. This dilemma calls for a glossary that provides concise, consistent definitions of relevant terms.
Here you'll find all the enterprise architecture terms that are used on a regular basis along with their definitions. If you want to go deeper into a particular concept, each entry includes a link to a lesson where you can learn more.
Application portfolio rationalization is the act of streamlining the existing application portfolio with an explicit goal of improving efficiency, reducing complexity, and lowering total cost of ownership (TCO) through a myriad of processes. Application rationalization sets the basis for other cost-saving endeavors, including:
Let’s review two indispensable tools for any self-respecting Enterprise Architect (EA): Inventorying and Modeling.
Both mechanisms provide unique advantages for handling complex IT ecosystems—and both present limitations which only the other can improve.
The words ‘digital transformation’ can be heard everywhere. Constantly mentioned in a business context, it may seem as if digital transformation is here to overthrow entire industries. At LeanIX, we view digital transformation as an important tool to redefine your business and catapult your organization swiftly into the digital age.
What exactly is digital transformation, and why is it key for enterprise architects to get involved?
Technology risk is any potential for technology failures to disrupt your business such as information security incidents or service outages.1
What is application portfolio management
Application portfolio management (APM) is a framework for managing enterprise IT software applications and software-based services. APM provides managers with an inventory of the company's software applications and metrics to illustrate the business benefits of each application.1
It’s no secret: Very few successful companies just work without any goal, but instead pursue a business strategy with a clear view on the future of their market. Especially in today's fast-moving environment, it is almost essential to choose an enterprise architecture approach from a business, technological, information technology and process point of view. This sounds like a mammoth task for many companies that still have to take these steps. However, with the right tools, the analysis, design, planning and implementation of the appropriate measures can become an almost pleasant task for enterprise architects, while adding business-critical value. And all this can be done in a shorter time than the 2018 World Cup season. Sounds too good to be true?
What are Business Capabilities?
Business Capability is the expression or the articulation of the capacity, materials, and expertise an organization needs in order to perform core functions. Enterprise Architects use Business Capabilities to illustrate the over-arching needs of the business in order to better strategize IT solutions that meet those business needs.1
Sometime at the beginning of the year, the Head of Infrastructure of a manufacturing company walks into the CIO’s office: “I just had Oracle on the phone. We have a problem”, he said. “Why is that?”, asks the CIO.
“We need to get off that Version 11 Database. They are going to waive premium support and the security risk is no longer acceptable”.
“Uh, ok… What does this really mean?", asks the CIO looking puzzled.
The head of infrastructure starts to explain: “The migration will have quite a few ripple effects, and the new version requires a newer server operating system. That means some of the older servers need to be replaced. I suspect that a large number of applications will be affected, and migration from the older ERP legacy systems will be tricky. I cannot promise that we will make it without any production downtime.”
With a worried expression, the CIO mutters, “I wish you would have told me that before the budget planning two months ago…” Source