Please enable JavaScript.
Coggle requires JavaScript to display documents.
CHAPTER 3 - Coggle Diagram
CHAPTER 3
Layer #3: Data Architecture
Where is your firm’s data stored?
Integrated firmwide data is the foundation for automation and analytics
Widespread problem:
Proliferation of duplicated
Inconsistent data
Two causes:
Fragmented across apps (app architecture is for individual apps)
Geographic dispersion
To pick appropriate data architectures, non-IT managers must decide:
What data should be centralized firmwide for executing your core
business processes or for analytics?
What data must be shared across your markets?
Layer #1: IT Infrastructure Architecture
Firmwide digital plumbing used by all line functions and apps
IT infrastructure architecture is their firmwide arrangement
Relatively stable
Generic commodity
Rarely a competitive differentiator
But underperformance liability
Consumes over 50% of corporate IT budgets
Must be reliable but economical
Key IT Infrastructure choice: Show how much to centralized and decentralized
Non-IT contributions and bear in mind about:
Is frugality or tailoring more important for their units?
Define “good enough” operational performance?
Layer #2: App Architecture
Choosing where to locate the three pieces
Has irreversible operational and strategic consequences
Three Arrangements ~ App Architectures
Cloud architecture
Client-server architecture
Peer-to-peer architecture
Corporate IT Architecture: The Big Picture
Describes how they fit together
Firmwide organizing logic of the three classes of IT assets (IT Infrastructure, Data and Apps)
Architecture as DNA
Architecture is the DNA of IT system
It is irreversible, imprints their traits, and influences how they
can and cannot evolve.
Architecture as a Universal Translator
Translates between business-speak and technology-speak to foster a shared purpose
