Therefore, these changing business
charters require unique technologies to react to swift alterations to business directions and
organizational goals.
So which types of architectures can support organizational missions? Are these the same
types that enable the construction of enterprise core products? The mission business architecture
perspective represents architectural requirements that are not strategic and long-lasting implementations.
But neither are they tactical. Indeed, these technologies are employed to provide solutions
to changing business goals. However, they must facilitate organizational climate changes and
should last for a while.
Technical architectures of the mission type may even lead to core product implementations.
But they should be regarded as intermediate solutions that facilitate business and technology
transitions. Consider a software assets consolidation effort that is proposed for cross-enterprise cost
reduction. Imagine the difficulty involved in joining two organizations??™ operations driven by two
different business objectives. Mission architectures therefore must provide valuable solutions to
mitigate the potential risk of merging business processes and execution. This may involve technical
architectures that can consolidate software assets, increase product reusability, unify database
schemas, and facilitate a new technological strategy. Exhibit 9.
Pages:
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332