This plethora of
organizational architectures both necessitates administration of architecture portfolios and requires
governance disciplines to devise architecture formations and styles.
But the chief impediment here is the alignment between business and information technology
(IT) organizations along with the lack of standards for the integration of business and
technological assets. One of the greatest challenges is to build architectures that not only comply
with business strategies but follow the organizational business model. The enterprise architecture1
paradigm provides such guidance. It is a practice that originated in the 1980s, one that
offered models and frameworks that described organizational business imperatives from various
perspectives, such as processes, behaviors, personnel accountabilities, and lines of business.
In 1987, John Zackman, an influential proponent of the enterprise architecture paradigm,
wrote2: ???To keep the business from disintegrating, the concept of an information systems architecture
is becoming less of an option and more of a necessity.??? His enterprise architecture framework,
known as the Zackman Framework for Enterprise Architecture, introduced a common vocabulary
and models for describing various perspectives of business and technology enterprise systems.
Other well-known enterprise architectural frameworks, such as the U.S. Department of Defense
Architecture Framework (DODAF)3 and the Federal Enterprise Architecture (FEA),4 were devised
to help government agencies create their own architectures.
Pages:
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304