The document discusses the benefits of using APIs to access data instead of traditional extract, transform, load (ETL) processes. It uses a story of a tutor trying to build an app to illustrate the complexities and inefficiencies of ETL. An API allows external users to access data through a simple interface with just one step - "Use Data". This reduces risk, complexity and innovator pain compared to ETL. Well-designed APIs also allow for centralized monitoring and metrics to improve effectiveness and efficiency of data sharing across an organization.

1. “Why API?”
What is Enterprise Architecture (EA)?
User Stories
The Promise of EA
“Why API?” (and other Architectural Anecdotes)
Colin Bell
–
Director, Enterprise Architecture
Information Systems and Technology (IST), University of Waterloo
December 3, 2013
Colin Bell– Director, Enterprise Architecture “Why API?” (and other Architectural Anecdotes)

2. “Why API?”
What is Enterprise Architecture (EA)?
User Stories
The Promise of EA
Table of contents
1 “Why API?”
The User Story
User Experience (UX)
User Interface (UI)
Effectiveness and Efficiency
2 What is Enterprise Architecture (EA)?
Level 100?
Enterprise Architecture @ Waterloo
3 User Stories
The Applicant
The Business Unit
4 The Promise of EA
The Waterloo EA Guide (EAWG)
Injury Time
Colin Bell– Director, Enterprise Architecture “Why API?” (and other Architectural Anecdotes)

3. “Why API?”
What is Enterprise Architecture (EA)?
User Stories
The Promise of EA
The User Story
User Experience (UX)
User Interface (UI)
Effectiveness and Efficiency
The User Story
I am a tutor and I want to make
a service to help any Waterloo
student. To do this I need
access to any student's class
schedule if the student wants
my service.
Colin Bell– Director, Enterprise Architecture “Why API?” (and other Architectural Anecdotes)

4. “Why API?”
What is Enterprise Architecture (EA)?
User Stories
The Promise of EA
The User Story
User Experience (UX)
User Interface (UI)
Effectiveness and Efficiency
The User Story: Setup
Tutor
Student
Today... if the Tutor can convince
the information stewards:
University of
Waterloo
Colin Bell– Director, Enterprise Architecture “Why API?” (and other Architectural Anecdotes)

5. “Why API?”
What is Enterprise Architecture (EA)?
User Stories
The Promise of EA
The User Story
User Experience (UX)
User Interface (UI)
Effectiveness and Efficiency
The User Story: Extract
Tutor
Student
University of
Waterloo
Extract
Colin Bell– Director, Enterprise Architecture “Why API?” (and other Architectural Anecdotes)

6. “Why API?”
What is Enterprise Architecture (EA)?
User Stories
The Promise of EA
The User Story
User Experience (UX)
User Interface (UI)
Effectiveness and Efficiency
The User Story: Transform
Tutor
Student
University of
Waterloo
Transform
Colin Bell– Director, Enterprise Architecture “Why API?” (and other Architectural Anecdotes)

7. “Why API?”
What is Enterprise Architecture (EA)?
User Stories
The Promise of EA
The User Story
User Experience (UX)
User Interface (UI)
Effectiveness and Efficiency
The User Story: Load
Tutor
Student
University of
Waterloo
Load
Colin Bell– Director, Enterprise Architecture “Why API?” (and other Architectural Anecdotes)

8. “Why API?”
What is Enterprise Architecture (EA)?
User Stories
The Promise of EA
The User Story
User Experience (UX)
User Interface (UI)
Effectiveness and Efficiency
The User Story: Use
Tutor
Student
University of
Waterloo
Cool New
Schedule
App
Colin Bell– Director, Enterprise Architecture “Why API?” (and other Architectural Anecdotes)

9. “Why API?”
What is Enterprise Architecture (EA)?
User Stories
The Promise of EA
The User Story
User Experience (UX)
User Interface (UI)
Effectiveness and Efficiency
The User Story: Costs
Increased Risk.
Colin Bell– Director, Enterprise Architecture “Why API?” (and other Architectural Anecdotes)

10. “Why API?”
What is Enterprise Architecture (EA)?
User Stories
The Promise of EA
The User Story
User Experience (UX)
User Interface (UI)
Effectiveness and Efficiency
The User Story: Costs
Increased Risk. (Copies of data = custodianship).
Colin Bell– Director, Enterprise Architecture “Why API?” (and other Architectural Anecdotes)

11. “Why API?”
What is Enterprise Architecture (EA)?
User Stories
The Promise of EA
The User Story
User Experience (UX)
User Interface (UI)
Effectiveness and Efficiency
The User Story: Costs
Increased Risk. (Copies of data = custodianship).
Increased Complexity.
Colin Bell– Director, Enterprise Architecture “Why API?” (and other Architectural Anecdotes)

12. “Why API?”
What is Enterprise Architecture (EA)?
User Stories
The Promise of EA
The User Story
User Experience (UX)
User Interface (UI)
Effectiveness and Efficiency
The User Story: Costs
Increased Risk. (Copies of data = custodianship).
Increased Complexity. (ETL code maintenance).
Colin Bell– Director, Enterprise Architecture “Why API?” (and other Architectural Anecdotes)

13. “Why API?”
What is Enterprise Architecture (EA)?
User Stories
The Promise of EA
The User Story
User Experience (UX)
User Interface (UI)
Effectiveness and Efficiency
The User Story: Costs
Increased Risk. (Copies of data = custodianship).
Increased Complexity. (ETL code maintenance).
Innovator pain.
Colin Bell– Director, Enterprise Architecture “Why API?” (and other Architectural Anecdotes)

14. “Why API?”
What is Enterprise Architecture (EA)?
User Stories
The Promise of EA
The User Story
User Experience (UX)
User Interface (UI)
Effectiveness and Efficiency
The User Story: Costs
Increased Risk. (Copies of data = custodianship).
Increased Complexity. (ETL code maintenance).
Innovator pain. (“I just want to make an app not ETL.”).
Colin Bell– Director, Enterprise Architecture “Why API?” (and other Architectural Anecdotes)

15. “Why API?”
What is Enterprise Architecture (EA)?
User Stories
The Promise of EA
The User Story
User Experience (UX)
User Interface (UI)
Effectiveness and Efficiency
The User Experience (UX)
How does the tutor feel?
Colin Bell– Director, Enterprise Architecture “Why API?” (and other Architectural Anecdotes)

16. “Why API?”
What is Enterprise Architecture (EA)?
User Stories
The Promise of EA
The User Story
User Experience (UX)
User Interface (UI)
Effectiveness and Efficiency
The User Experience (UX)
How does the tutor feel?
Source: http://cdn.evilautie.org/wp-content/uploads/2012/10/sadsmiley.png
Colin Bell– Director, Enterprise Architecture “Why API?” (and other Architectural Anecdotes)

17. “Why API?”
What is Enterprise Architecture (EA)?
User Stories
The Promise of EA
The User Story
User Experience (UX)
User Interface (UI)
Effectiveness and Efficiency
The User Interface (UI)
As a data user, what is the interface like?
Colin Bell– Director, Enterprise Architecture “Why API?” (and other Architectural Anecdotes)

18. “Why API?”
What is Enterprise Architecture (EA)?
User Stories
The Promise of EA
The User Story
User Experience (UX)
User Interface (UI)
Effectiveness and Efficiency
The User Interface (UI)
As a data user, what is the interface like?
Load
AppTransform
Extract
Colin Bell– Director, Enterprise Architecture “Why API?” (and other Architectural Anecdotes)

19. “Why API?”
What is Enterprise Architecture (EA)?
User Stories
The Promise of EA
The User Story
User Experience (UX)
User Interface (UI)
Effectiveness and Efficiency
The User Interface (UI)
“Extract”:
1 Download Extract File
2 Store the Extract File
“Transform”:
3 Validate and Pre-Process the Extract File
4 Reconstruct Relationships
“Load”:
5 Insert into Database
“Use Data”
Five steps just to use the data.
Colin Bell– Director, Enterprise Architecture “Why API?” (and other Architectural Anecdotes)

20. “Why API?”
What is Enterprise Architecture (EA)?
User Stories
The Promise of EA
The User Story
User Experience (UX)
User Interface (UI)
Effectiveness and Efficiency
The User Interface (UI)
Could we improve the “Data User Interface”?
Colin Bell– Director, Enterprise Architecture “Why API?” (and other Architectural Anecdotes)

21. “Why API?”
What is Enterprise Architecture (EA)?
User Stories
The Promise of EA
The User Story
User Experience (UX)
User Interface (UI)
Effectiveness and Efficiency
The User Interface (UI)
Could we improve the “Data User Interface”?
DUI
Colin Bell– Director, Enterprise Architecture “Why API?” (and other Architectural Anecdotes)

22. “Why API?”
What is Enterprise Architecture (EA)?
User Stories
The Promise of EA
The User Story
User Experience (UX)
User Interface (UI)
Effectiveness and Efficiency
The User Interface (UI)
Could we improve the “Data User Interface”?
DUI?
Colin Bell– Director, Enterprise Architecture “Why API?” (and other Architectural Anecdotes)

23. “Why API?”
What is Enterprise Architecture (EA)?
User Stories
The Promise of EA
The User Story
User Experience (UX)
User Interface (UI)
Effectiveness and Efficiency
The User Interface (UI)
The “Application Programming Interface”:
API
Colin Bell– Director, Enterprise Architecture “Why API?” (and other Architectural Anecdotes)

24. “Why API?”
What is Enterprise Architecture (EA)?
User Stories
The Promise of EA
The User Story
User Experience (UX)
User Interface (UI)
Effectiveness and Efficiency
The Application Programming Interface (API)
Load
AppTransform
Extract
API
Colin Bell– Director, Enterprise Architecture “Why API?” (and other Architectural Anecdotes)

25. “Why API?”
What is Enterprise Architecture (EA)?
User Stories
The Promise of EA
The User Story
User Experience (UX)
User Interface (UI)
Effectiveness and Efficiency
The Application Programming Interface (API)
“Use Data”
Colin Bell– Director, Enterprise Architecture “Why API?” (and other Architectural Anecdotes)

26. “Why API?”
What is Enterprise Architecture (EA)?
User Stories
The Promise of EA
The User Story
User Experience (UX)
User Interface (UI)
Effectiveness and Efficiency
The Application Programming Interface (API)
“Use Data”
... and that’s it.
Colin Bell– Director, Enterprise Architecture “Why API?” (and other Architectural Anecdotes)

27. “Why API?”
What is Enterprise Architecture (EA)?
User Stories
The Promise of EA
The User Story
User Experience (UX)
User Interface (UI)
Effectiveness and Efficiency
API Benefits
Less Risk.
Colin Bell– Director, Enterprise Architecture “Why API?” (and other Architectural Anecdotes)

28. “Why API?”
What is Enterprise Architecture (EA)?
User Stories
The Promise of EA
The User Story
User Experience (UX)
User Interface (UI)
Effectiveness and Efficiency
API Benefits
Less Risk. (Data not copied.)
Colin Bell– Director, Enterprise Architecture “Why API?” (and other Architectural Anecdotes)

29. “Why API?”
What is Enterprise Architecture (EA)?
User Stories
The Promise of EA
The User Story
User Experience (UX)
User Interface (UI)
Effectiveness and Efficiency
API Benefits
Less Risk. (Data not copied.)
Single Point of Control.
Colin Bell– Director, Enterprise Architecture “Why API?” (and other Architectural Anecdotes)

30. “Why API?”
What is Enterprise Architecture (EA)?
User Stories
The Promise of EA
The User Story
User Experience (UX)
User Interface (UI)
Effectiveness and Efficiency
API Benefits
Less Risk. (Data not copied.)
Single Point of Control. *
Colin Bell– Director, Enterprise Architecture “Why API?” (and other Architectural Anecdotes)

31. “Why API?”
What is Enterprise Architecture (EA)?
User Stories
The Promise of EA
The User Story
User Experience (UX)
User Interface (UI)
Effectiveness and Efficiency
API Benefits
Less Risk. (Data not copied.)
Single Point of Control. *
Less Complexity.
Colin Bell– Director, Enterprise Architecture “Why API?” (and other Architectural Anecdotes)

32. “Why API?”
What is Enterprise Architecture (EA)?
User Stories
The Promise of EA
The User Story
User Experience (UX)
User Interface (UI)
Effectiveness and Efficiency
API Benefits
Less Risk. (Data not copied.)
Single Point of Control. *
Less Complexity. (ETL is done once upstream.)
Colin Bell– Director, Enterprise Architecture “Why API?” (and other Architectural Anecdotes)

33. “Why API?”
What is Enterprise Architecture (EA)?
User Stories
The Promise of EA
The User Story
User Experience (UX)
User Interface (UI)
Effectiveness and Efficiency
API Benefits
Less Risk. (Data not copied.)
Single Point of Control. *
Less Complexity. (ETL is done once upstream.)
Innovator innovates.
Colin Bell– Director, Enterprise Architecture “Why API?” (and other Architectural Anecdotes)

34. “Why API?”
What is Enterprise Architecture (EA)?
User Stories
The Promise of EA
The User Story
User Experience (UX)
User Interface (UI)
Effectiveness and Efficiency
API Benefits
Less Risk. (Data not copied.)
Single Point of Control. *
Less Complexity. (ETL is done once upstream.)
Innovator innovates. (“I’m able to make my app!”)
Colin Bell– Director, Enterprise Architecture “Why API?” (and other Architectural Anecdotes)

35. “Why API?”
What is Enterprise Architecture (EA)?
User Stories
The Promise of EA
The User Story
User Experience (UX)
User Interface (UI)
Effectiveness and Efficiency
Design Feature: Single Point of Control
Monitoring
Metrics
Colin Bell– Director, Enterprise Architecture “Why API?” (and other Architectural Anecdotes)

36. “Why API?”
What is Enterprise Architecture (EA)?
User Stories
The Promise of EA
The User Story
User Experience (UX)
User Interface (UI)
Effectiveness and Efficiency
Design Feature: Single Point of Control
Monitoring / Audit - Who, What, When?
Metrics / Analytics - How?
Colin Bell– Director, Enterprise Architecture “Why API?” (and other Architectural Anecdotes)

37. “Why API?”
What is Enterprise Architecture (EA)?
User Stories
The Promise of EA
The User Story
User Experience (UX)
User Interface (UI)
Effectiveness and Efficiency
We can manage what we can measure.
Effective (adj.) adequate to accomplish a purpose; producing the
intended or expected result.
Efficient (adj.) performing or functioning in the best possible
manner with the least waste of time and effort.
Colin Bell– Director, Enterprise Architecture “Why API?” (and other Architectural Anecdotes)

38. “Why API?”
What is Enterprise Architecture (EA)?
User Stories
The Promise of EA
The User Story
User Experience (UX)
User Interface (UI)
Effectiveness and Efficiency
Effectiveness + Efficiency
Load
AppTransform
Extract
Load
AppTransform
Extract
API
Extract File Based
API Based
Colin Bell– Director, Enterprise Architecture “Why API?” (and other Architectural Anecdotes)

39. “Why API?”
What is Enterprise Architecture (EA)?
User Stories
The Promise of EA
The User Story
User Experience (UX)
User Interface (UI)
Effectiveness and Efficiency
Effectiveness + Efficiency
Load
AppTransform
Extract
Load
AppTransform
Extract
API
Extract File Based
API Based
both effective
Colin Bell– Director, Enterprise Architecture “Why API?” (and other Architectural Anecdotes)

40. “Why API?”
What is Enterprise Architecture (EA)?
User Stories
The Promise of EA
The User Story
User Experience (UX)
User Interface (UI)
Effectiveness and Efficiency
Effectiveness + Efficiency
Load
AppTransform
Extract
Load
AppTransform
Extract
API
Extract File Based
API Based
<
less efficient
Colin Bell– Director, Enterprise Architecture “Why API?” (and other Architectural Anecdotes)

41. “Why API?”
What is Enterprise Architecture (EA)?
User Stories
The Promise of EA
The User Story
User Experience (UX)
User Interface (UI)
Effectiveness and Efficiency
Effectiveness + Efficiency
Load
AppTransform
Extract
Load
AppTransform
Extract
API
Extract File Based
API Based
File = 5 steps
- duplication
- silos
- complexity
- blind to use
API = 1 step
- on-demand
- direct
- benign
- visible
<
less efficient
Colin Bell– Director, Enterprise Architecture “Why API?” (and other Architectural Anecdotes)

42. “Why API?”
What is Enterprise Architecture (EA)?
User Stories
The Promise of EA
Level 100?
Enterprise Architecture @ Waterloo
This is 100 level, why so technical?
Source: http://warriorfitness.org/wp-content/uploads/2012/05/confused.jpg
Colin Bell– Director, Enterprise Architecture “Why API?” (and other Architectural Anecdotes)

43. “Why API?”
What is Enterprise Architecture (EA)?
User Stories
The Promise of EA
Level 100?
Enterprise Architecture @ Waterloo
Fear not, you understand!
User Stories
Abstraction
Desired Outcomes
Effectiveness + Efficiency
We do not need to see the whole picture (in fact, we cannot).
Waterloo is just too complex to understand completely.
Divide and conquer!
Colin Bell– Director, Enterprise Architecture “Why API?” (and other Architectural Anecdotes)

44. “Why API?”
What is Enterprise Architecture (EA)?
User Stories
The Promise of EA
Level 100?
Enterprise Architecture @ Waterloo
Enterprise Architecture Domains
Business Architecture
Information Architecture
Applications Architecture
Technology Architecture
Colin Bell– Director, Enterprise Architecture “Why API?” (and other Architectural Anecdotes)

45. “Why API?”
What is Enterprise Architecture (EA)?
User Stories
The Promise of EA
Level 100?
Enterprise Architecture @ Waterloo
Enterprise Architecture Working Group (EAWG)
Started in 2012 at Waterloo. Findings wrapped up through IST
PDAG on May 31, 2013. We had a 9 member team.
Jay Athia, IAP
Colin Bell, IST
Pascal Calarco, Library
Chris Halonen, Secretariat
Margaret Stephenson, EAWG program lead, IST
Jonathan Woodcock/Andrea Sweet, CPA
Connie van Oostveen, IST
Robert Wallwork, IST
Shawn Winnington-Ball, IST
Colin Bell– Director, Enterprise Architecture “Why API?” (and other Architectural Anecdotes)

46. “Why API?”
What is Enterprise Architecture (EA)?
User Stories
The Promise of EA
Level 100?
Enterprise Architecture @ Waterloo
EAWG: What is EA?
Enables business transformation: current state to target state
Business and IT alignment: architectural blueprint
Common business language
Enterprise-wide, pervasive
Disciplined practice: documenting/modeling
Uncover inefficiencies and increase effectiveness, ability to
respond to change = agility
Colin Bell– Director, Enterprise Architecture “Why API?” (and other Architectural Anecdotes)

47. “Why API?”
What is Enterprise Architecture (EA)?
User Stories
The Promise of EA
The Applicant
The Business Unit
User Story: The Applicant.
Enrolled Alumni
Expired with email
readmission
120 days or IdM admin defined value reached
graduated/stopped progression
Start
Enterprise Architecture:
Identity Management Student State
Transition Diagram
Feb. 13, 2013
CB, CvO, SWB
Applied
identity
created
matriculation
reapplication
death or removal from
Quest data feed
Expired without
email
not reactivated
non-matriculation
Colin Bell– Director, Enterprise Architecture “Why API?” (and other Architectural Anecdotes)

48. “Why API?”
What is Enterprise Architecture (EA)?
User Stories
The Promise of EA
The Applicant
The Business Unit
User Story: The Business Unit using services.
University
Executive
IST
Student
Records
(RO)
Co-op
Records
(CECA)
Alumni
(ODAA)
Staff
Records
(HR)
IST
(EBI Arch)
Provide Infrastructure
Provide Infrastructure
Provide Infrastructure (Network / Servers)
Provide Infrastructure
Provide
Inquiry Tools
ODAA
IT
Provide
Software
IAP Reports
University of Waterloo
EAWG / Institutional Data Reports SIAM (future)
Version 0.1 - DRAFT
Feb 11, 2013
CB, CH, RW, JA
Authorize
Use
Authorize
Use
Authorize
Use
Authorize
Use
Colin Bell– Director, Enterprise Architecture “Why API?” (and other Architectural Anecdotes)

49. “Why API?”
What is Enterprise Architecture (EA)?
User Stories
The Promise of EA
The Waterloo EA Guide (EAWG)
Injury Time
The Promise of EA
We think architecturally every day. We are good at it.
Our abilities to manage projects and services are central
to what we do. The Enterprise Architecture will help us
capture an approximation for what we have today. We
collectively design solutions and break apart the large
problems, working to describe an ideal state for the
university. Then we begin building.
Together we enable.
Source: https://collaborate.uwaterloo.ca/connect-it/node/275
Colin Bell– Director, Enterprise Architecture “Why API?” (and other Architectural Anecdotes)

50. “Why API?”
What is Enterprise Architecture (EA)?
User Stories
The Promise of EA
The Waterloo EA Guide (EAWG)
Injury Time
The Waterloo EA Guide (EAWG)
http://ist.uwaterloo.ca/ea/
UWEnterpriseArchitectureGuide.pdf
Colin Bell– Director, Enterprise Architecture “Why API?” (and other Architectural Anecdotes)

51. “Why API?”
What is Enterprise Architecture (EA)?
User Stories
The Promise of EA
The Waterloo EA Guide (EAWG)
Injury Time
Injury Time: Governance
From: IT Savvy: What Top Executives Must Know to Go from Pain to Gain by Peter Weill and Jeanne W. Ross
Diversification Low standardization, low integration– involves platform of
shared services that supports autonomous business
activities.
Coordination Low standardization, high integration– involves building a
platform of shared data to support integrated
management decisions or a single face to the customer.
Component Reuse (Replication) High standardization, low integration–
involves building a platform of standard technologies and
business processes to define a common brand.
Converged Services (Unification) High standardization, high integration–
involves building a platform of standardized technologies,
business processes, and shared data to support global
end-to-end customer requirements.
Colin Bell– Director, Enterprise Architecture “Why API?” (and other Architectural Anecdotes)

52. “Why API?”
What is Enterprise Architecture (EA)?
User Stories
The Promise of EA
The Waterloo EA Guide (EAWG)
Injury Time
Injury Time: Zachman Framework for EA
Why How What Who Where When
Contextual
(Enterprise)
Goal List Process List Material List
Organizational
Unit & Role List
Geographical
Locations List
Event List
Conceptual
(Business)
Goal
Relationship
Process Model
Entity
Relationship
Model
Organizational
Unit & Role
Relationship
Model
Locations
Model
Event Model
Logical
(Architect)
Rules Diagram
Process
Diagram
Data Model
Diagram
Role
Relationship
Diagram
Locations
Diagram
Event Diagram
Physical
(Engineer)
Rulse
Specification
Process
Function
Specification
Data Entity
Role
Specification
Location
Specification
Event
Specification
Detailed
(Technician)
Rules Details Process Details Data Details Role Details Location Details Event Details
Colin Bell– Director, Enterprise Architecture “Why API?” (and other Architectural Anecdotes)