Please enable JavaScript.
Coggle requires JavaScript to display documents.
IT Architecture - Coggle Diagram
IT Architecture
What?
as DNA of IT system
Irreversible
Imprints their traits
Influence how they can and cannot evolve
The prohibitive costs make it almost impossible to change
Constrain tomorrow's strategic flexibility
as Universal Translator
translate between business-speak and technology-speak
foster a shared purpose
Primary source of complexity in a firm’s IT portfolio
if not a catalyst for agility, then it is impediment (hindrance)
The Architecture's Three Layers
Infrastructure
consume > 50% of corporate IT budgets
firm's digital plumbing
must be reliable but economical
key architectural choice
how much to decentralize IT infrastructure
how much to centralize IT infrastructure - costlier to build but cheaper to run
App
consist of 3 pieces building blocks of functionality
app logic
interaction functionality
data storage
how to divide the three pieces between a centralized server and user devices
common app architecture
cloud architecture
puts all three pieces on a central server
centralized its weakness and strength
:arrow_up: vulnerability, needs strong internet connectivity
client-server architecture
locates the interaction and app logic functions on user devices and centralizes only data storage
most common app architecture used
custom developed client-server apps are competitively more valuable - costly
peer-to-peer architecture
takes the stand-alone architecture, connects all user devices using the Internet
recommended only for apps that require very high levels of scalability but demand absolutely no control by a firm over user devices.
software programs that undergrid the functionality of a hardware device
Example
Smartphone
PC
Tablet
Data
be careful about fragmentation of data across apps
fragmented data silos are integrated using data warehouses
access to firm-wide data that provide a stepping-stone
business processes innovation
business analytics initiatives
Integrated firm-wide data is the foundation of IT
Consequences?
Strategic
Scability- cost effective in supporting growth needs
Evolvability – can it adapt to things that it was never designed to do
Operational
Fitness of purpose – how responsive is it (speed) and can you count on it (reliability).
Security
Maintainability – how cost effective is to make it run smoothly