What's changed: Initial version
4.2Enterprise architecture (EA)
Covers EA (enterprise architecture), a representative means of achieving enterprise optimization, understood as the four domains business (BA), data (DA), application (AA), and technology (TA); the procedure of drawing the target To-Be from the current As-Is and bridging them with a migration plan; the role of reference models; and the judgment of pinpointing "which domain (layer) a given issue belongs to."
The representative technique that systematizes the previous section's enterprise-optimization policy into an actual blueprint is EA (enterprise architecture). EA visualizes an enterprise's operations and systems by dividing them into four domains (layers)—business, data, application, and technology—clarifies the gap between the current state (As-Is) and the target (To-Be), and bridges them with a migration plan. For an IT strategist, the practical crux of EA is correctly pinpointing "which of the four layers a currently faced issue belongs to" and designing "how to reach the To-Be step by step as a migration plan rather than realizing it all at once." This section covers the division of roles among the four domains and the As-Is/To-Be/migration relationship, framed as the judgment of a strategist leading enterprise optimization.
4.2.1EA's four domains (BA/DA/AA/TA)
Continue reading — free sign-up
You're reading the free preview. Sign up free to read this section in full, plus every chapter (including 4+) and all questions.