Enterprise Architecture HOME

Principles of Enterprise Architecture and Digital Infrastructure is a 14-chapter undergraduate textbook covering the frameworks, networks, cloud, security, AI, DevOps, ITSM, data, and green-IT practices that hold a modern enterprise together. Use this track as a daily companion while you read the chapters and complete the applied activities.

Enterprise Architecture - the 14-chapter map

Authors: Ryan Jison de la Gente, Manuel A. Uy, Richard M. Pabelona Jr. Carlos Hilado Memorial State University, 2025 (1st edition). Library of Congress / NLP cataloguing pending.

Why this book exists

Enterprise IT is no longer a single department problem. Networks, cloud, security, AI, ITSM, and sustainability all live in the same architecture diagram. This textbook trains BSIT, BSIS, and BS Information Systems undergraduates to read that diagram, defend its trade-offs, and contribute to its evolution.

How the book is organised

Fourteen chapters, each with three to six sub-sections, a Discussion and Analysis block, and an Applied Learning Activities block. Every chapter ends with a curated References list.

  Chapter 1   Architecture Frameworks (Zachman, TOGAF)
  Chapter 2   Network Infrastructure (LANs, load balancing, failover)
  Chapter 3   Internet Infrastructure (ISP, DNS, protocols, firewalls)
  Chapter 4   Modern Web and IoT (Web 2.0/3.0, IoT, PH socio-economic apps)
  Chapter 5   Digital Platforms (CMS, wikis, social media, marketing)
  Chapter 6   Cloud Computing (IaaS / PaaS / SaaS, risk, case studies)
  Chapter 7   Portals, SOA, and Mobile (e-gov, web services, mobile)
  Chapter 8   Security and Compliance (Zero Trust, privacy, RA 10175)
  Chapter 9   AI in the Enterprise (predictive, generative, governance)
  Chapter 10  Business Continuity and Disaster Recovery (RTO, RPO, HA)
  Chapter 11  DevOps and CI/CD (Agile, DevOps, CI/CD, Git, BPO model)
  Chapter 12  ITSM and ITIL (service lifecycle, incident, SLA)
  Chapter 13  Data Management (RDBMS, NoSQL, warehouses, lakes, ETL)
  Chapter 14  Green IT and Sustainability (PUE, lifecycle, sustainable cloud)

What every chapter gives you

• Concept exposition - definitions, models, diagrams
• Worked examples - quantitative and qualitative
• Discussion and Analysis - frame the trade-offs
• Applied Learning Activities - what to actually do
• References - primary and secondary sources

Six worked numerical examples (selected chapters)

  Chapter 2    High Availability arithmetic (uptime % to minutes)
  Chapter 6    Three-year TCO comparison: on-prem vs PaaS
  Chapter 10   RPO / RTO budget allocation
  Chapter 12   SLA breach penalty calculation
  Chapter 14   PUE calculation and improvement forecast
  Chapter 7    REST endpoint in Python Flask
  Chapter 9    RAG (retrieval-augmented generation) prompt construction
  Chapter 11   GitHub Actions CI/CD pipeline
  Chapter 13   SQL JOIN and MongoDB aggregation

Recommended study order

1. Read Chapter 1 to establish the framework vocabulary.
2. Read Chapters 2-4 to ground the network and web layers.
3. Read Chapter 6 (cloud) BEFORE Chapter 8 (security) so the trust boundary discussion has context.
4. Read Chapter 10 (BCP/DR) BEFORE Chapter 12 (ITSM) - DR feeds the incident playbooks.
5. Read Chapter 11 (DevOps) and Chapter 13 (data) together if you build a system that ships changes.
6. Read Chapter 14 (sustainability) last and revisit your earlier architectures with the PUE lens.

Three habits that pay off across the whole book

• Draw before you decide. Architecture is a diagram, not a paragraph.
• Quantify the trade-off. Cost, latency, RPO, RTO, PUE - put numbers to every claim.
• Cite the framework you used. TOGAF, NIST, ITIL - never hand-wave 'best practice.'

How to use this site

Each chapter section of the textbook maps to a topic in this track. Open the section you are reading today. Read the worked exposition, attempt the applied activity, and bring questions back to your instructor.

Important: the worked examples use Philippine context (banks, e-gov, BPO, universities) on purpose. Substitute your own organisation as you adapt the patterns.