企业架构一套更好的路径
Introduction
Defining an Enterprise Architecture
History of Enterprise Architectures
Public Sector Case Studies
Private Sector Case Studies
Complexity
Modeling Complexity
Partitioning
Iteration
Partitioned-Iteration
Existing Enterprise ArchitectureFrameworks
Advantages of the Partitioned-IterativeApproach
Rules for Success
Conclusion
Glossary
References
1 Introduction
When enterprise architectures work well, they are atremendous asset in finding effective ways to better use technology. When theydon't work well, they can be a huge counterproductive drain on preciousorganizational resources. All too often, it is the latter case that isrealized.
You can't afford to ignore the potential benefits of awell-done enterprise architecture. These benefits include decreased costs,increased revenues, improved processes, and expanded business opportunities.But you also can't afford to ignore the risks of getting mired in a badenterprise architecture. These include astronomical expenses, technologicalgridlock, and diminished executive credibility.
But don't despair: You can have the benefits and avoidthe problems. This paper will show you how. I'll discuss some important cluesas to how to approach an enterprise architecture from two unrelateddisciplines: probability theory and war strategy.
From probability theory, we learn some important lessonsabout the nature of complexity. The failure to manage complexity is, I believe,the key reason so many attempts at creating enterprise architecture go awry.Few existing methodologies for enterprise architectures address the managementof complexity in any meaningful way. And the architectures of today'sorganizations are highly complex.
So how do you manage complexity? The answer comes fromthe unlikely field of war strategy. You will see how a lesson learned byfighter pilots who were trying to survive dogfights fifty years ago contains animportant clue for building complex enterprise architectures today.
Finally, I'll put it all together into a series ofguidelines for developing a good enterprise architecture that will be acritical organizational asset rather than an embarrassing and expensiveliability.