Please enable JavaScript.
Coggle requires JavaScript to display documents.
IT Architecture - Coggle Diagram
IT Architecture
A blueprint of IT assets in your IT portfolio describing what they do and how they interact
Architecture as DNA
It is irreversible and constrains how it can be changed over its life
Consequences :
Strategic
Scalability
Evolvability
Visible later
Operational
Fitness of purpose
Fast and reliable
Security
Maintainability
Immediately visible
Architecture as a Universal Translator
Translates between business-speak and technology-speak to foster a shared purpose
Enterprise IT Architecture's Three Layers
App Architecture
Choosing where to locate the
three pieces
between a centralized "server" and user devices
App logic
Data storage
Interaction
Three arrangement
A choice that app's designer make
Cloud architecture
All heavy lifting is done on the server side via the "cloud"
Client-server architecture
Centralizes only data and clients do heavy lifting
Peer-to-peer architecture
No central server therefore every client performs all app functions
Non-IT managers contributions
Rank order operational priorities for business activities
Acceptable tradeoff in operational performance to avoid a strategic penalty later ?
Data Architecture
Integrated firm-wide data is the foundation for automation and analytics
Problem : Proliferation of duplicated and inconsistent data
Causes : Dispersion of firm's data
across apps
across geographic locations
Non-IT managers contributions
What data should be centralized firm-wide for executing core business processes or for analytics ?
What data must be shared across your markets ?
IT Infrastructure Architecture
Firm's digital plumbing
Its firm-wide foundation of shared IT assets and IT services used by all line functions
Firm-wide arrangement
Include the networks through which data travels and apps are linked and the hardware on which apps run and store data
Example : computers, tablets, servers and storage devices
Non-IT managers contributions
Is frugality or tailoring more important for their units ?
Define "good enough" operational performance ?
Good Architecture
Balances economical performance today and economical changeability later
Fulfills today's requirements but plans for tomorrow's expectations