Enterprise architecture past, present and
In a very broad sense, an enterprise architect needs to bridge the gap between ‘what is’ and ‘what is needed’ in an IT landscape. These days, increasing data volumes, emerging data types, (hybrid) integration platforms, and new IT users and devices make this gap even more pronounced. As a result, organizations without a proper enterprise architecture are as helpless as a feather in the winds of change.
The question is: how can we create an IT landscape that is able to withstand tomorrow’s fickleness without investing enormous amounts of money? Until fairly recently, IT was a pretty straightforward affair. First, you had the mainframe, which didn’t really require any configuration. Then came the all-in-one megalithic business suites that covered pretty much every aspect of the business. Today, most companies work with a ‘best-in-breed’ IT landscape. Here, every aspect of the business is covered by a niche solution – often with its own data model. In this context, establishing seamless and smooth collaboration across solutions is a lot more challenging, and there are way more dots to connect. But it’s not impossible either, you just need to find the right approach.