Chapter 9Technical Analysis Drives End-State Architecture Structural Decomposition
There is no shortage of technical implementations and installed products in a production environment. And there is no dearth of sub-architectures in a sizeable end-state architecture. The design styles could be spotted anywhere. But with increasing product deployments, the variations of sub-architecture styles are growing as well. Not all patterns, however, of enterprise asset arrangements on a network could be classified. In fact, many formations are not even understood by production engineers. This inability to categorize sub-architectures only increases operational confusion and creates business continuity perils.
The chief technical analysis mission then would be to decompose an end-state architecture into sub-architectures buy classifying them. This process may be applied to a proposed enterprise grand design or an operating production landscape. Ascertaining how the various products and technologies carry business functionality would then be a good starting point. In other words, the end-state decomposition effort ought to be driven by technical capabilities.
Remember, here we do not pursue sub-architecture classification and end-state architecture decomposition from a business perspective.
Technical capabilities demonstrate the power of the technologies driven by enterprise architecture to provide solutions. Only a technical analysis could delve into sections of an end-state architecture ...
Get Incremental Software Architecture now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.