Enterprise Architecture
Enterprise Architecture - BADT Overview
Most architectural frameworks centre around at least four inter-related domains (see diagram above), from which hangs off ever increasing organisational (enterprise) detail.
Many frameworks avoid, or at least do not treat with the same importance, the people aspect. The way people, staff, colleagues, resources, however they are referred to, are managed, collaborate and influence processes are just as important, if not more so, than the “BAD-T” jigsaw above.
Extended Enterprise Architecture
To get from an “As-Is” to “To-Be” Enterprise Architecture (or A2B) in a usually restricted time period, the core elements, even at the very top level abstracted model shown above interact with each other significantly. For interact, also read conflict!
In Business Transformation programmes, depending on who has set-up the initial plan, much focus can be placed on some or all of these elements – Business Processes, Application Architecture, Corporate Data, underlying Technology platforms and staff resources (the glue and the oil that keeps it all working).
The key to effective planning around these domains is to blend the main objectives of the transformation into a reasonable understanding of the traditional BAD-T set-up. This will give the top level activities and goals that need to be driven into to extract more detail and issues.
Focusing on only one or two areas, for example resources and technology can leave a lot of unconsidered risk within the business transformation programme.
Advertisement
