3. 3
Architectural approach
INTRODUCTION
Enterprises and IT systems are complex
Modeling of enterprise and IT architectures is a
complex process
Teaching architectures is a challenge
Consists of a hierarchy of architectural models
Technical architectures modeled from various
perspectives
Several approaches, frameworks, methodologies,
process models
There is a comprehensive Body of Knowledge
5. 5
Definitions - Enterprise Architecture
USA Federal CIO Council: “Enterprise architecture is a strategic
information asset base which defines the business mission,
the information necessary to perform the mission, and the
transitional processes for implementing new technologies
in response to the changing mission needs”.
Meta Group: “Enterprise architecture is the holistic expression
of an organization’s key business, information, application
and technology strategies and their impact on business
functions and processes”.
The Open Group: “Enterprise architecture is about
understanding all of the different elements that go to make
up the enterprise and how those elements inter-relate”.
6. 6
Definition - Architecture
IEEE P1471-2000 Definition:
“An architecture is the fundamental
organization of a system embodied in its
components, their relationships to each
other, and to the environment, and the
principles guiding its design and evolution”.
7. 7
IT architecture
A pragmatic, coherent, and elegant structuring of a
collection of IT components that support business
processes the “user”, in conformance with factors
such as:
External constraints
User/Client requirements
Internal constraints
Technological constraints
Financial constraints
Legal constraints
8. 8
IT System
An IT system consists of a combination of
IT resources (HW, SW, infrastructure) and
the services they deliver for an enterprise
Developed following the systems approach
which focuses on the system as a whole
A system is a set of elements so connected or
related as to perform a unique function not
performable by the elements alone
9. 9
ARCHITECTURE APPROACH
The IT architecture must
Meet the strategic goals and objectives of the
enterprise
Represent the IT strategy of the enterprise
Enable the organization to respond to new trends,
drivers, technologies, i.e. be agile
Be designed based on sound principles
Must be well documented
11. 11
Key Tenet 1
ARCHITECTURAL PRINCIPLES
Enterprise principles (overarching) provide basis for decision-
making
Derived from enterprise mission, goals
Influenced by external constraints, trends
Existing systems and technology
Guides the enterprise strategy
Used to define the architecture governance process
Apply to all architectural projects
Examples:
Interoperability
Vendor independence
Manageability
Scalability
Commonality of applications
12. 12
Architectural Principles
Principles
Enterprise Architecture
Strategic
Plans
Business
Needs
IT Vision
Requirements &
Practices
Implications Actions
EA Policies &
Guidelines
-Development
-Use
-Maintenance
-Compliance
Systems Life Cycle
-Systems Migration
-Technology Insertion
-Dual Operations
-Deployment Plans
Capital Planning &
Investment Control
-Project Selection
-Project Control
-Project Evaluation
-Return on Investment
13. 13
IT ARCHITECTURE PRINCIPLES
Provide guidance on use and deployment of all IT
resources and assets across enterprise
Viewpoint specific principles
Apply when designing the architectural views for the
viewpoints of concern
TOGAF template for principles
Name
Statement
Rationale
Implications
Criteria of sound principles
14. 14
Key Tenet 2
ARCHITECTURE FRAMEWORK
A comprehensive analytical model that facilitates
consideration of all relevant factors when modeling
architectures
The enterprise viewpoint: principles, concerns, standards, guidelines,
stakeholders/actors
Architecture viewpoints:
Application
Data
Infrastructure
Communications Engineering
Enterprise Quality of Service
Enterprise Security
Enterprise Mobility
16. 16
The Views
Purpose- whether it aids by Informing, for Deciding, or for
Designing.
Content - characterized by the three abstraction levels
where it resides: Details, Coherence, and Overview.
Layer - where the view fits: Business, Application, and
Technology.
Aspect - what the view depicts: Structure, Behavior, and
Information.
Viewpoint language - the modeling notation or
representation scheme used.
Standards - the best practices adopted when modeling a
view.
Tool - automated capability used to model a view.
20. 20
mapping between TOGAF 8.1 ADM and APM
TOGAF 8.1 ADM Stage (APM) Stage
Preliminary: Framework and
Principles
Pre-architectural
Architecture Vision IT Strategy
Business Architecture Information / Business Systems
Architecture
Information Systems
Architecture
Information / Business Systems
Architecture
Technical Architecture Architecture:
IT Analysis Phase
Build IT Architecture Phase
Opportunities and Solutions Architecture: IT Analysis Phase
Migration Planning Deployment
Implementation Governance IT Strategy, Deployment
Architecture Change
Management
Maintenance
21. 21
Key Tenet 4
IT ARCHITECTURE METHODOLOGY
Methods, techniques, procedures to support the
architectural processes
Methodology prescribes representation schemes,
notations for modeling respective viewpoints for
Technical Architecture
Context
Structure
Behavior
22. 22
TEACHING IT SYSTEMS ARCHITECTURES
The Pedagogy – suited to adult learners; working
professionals
Measurable goals and objectives
Objectives
Explore leading edge approaches to development of
architectures
Encourage awareness of de jure standards
Enhance systemic thinking skills
Enhance problem solving through systematic application of an
architectural approach
Assure quality of architecture
Align project-level outcomes with strategic IT objectives
Theoretical and practical outcomes
23. 23
SUMMARY
Key outcomes of pedagogy
Understand and apply architecture approach
Technical modeling competencies
Enhanced managerial skills
Improved interpersonal communication and collaborative
skills
Ability to plan and develop an integrated architectural
solution to a complex real-world problem
24. 24
Team Projects
Applied Architecture Approach
Adopt Team approach
Based on real world case studies
Project Sponsor
Teams have developed several viewpoints
Information
Business Systems
Application
Physical IT Infrastructure
Communications engineering viewpoint
Enterprise Data
Quality of Service
Research on Enterprise Mobility Viewpoint
28. 28
Mobile Enterprise Vision
LAN
Enterprise LAN
Workstation
VPN Gateway
Authentication Server DHCP
Enterprise System
Mobile Application Servers
Firewall
DMZ Firewall
Database
Database
Web Server
Enterprise Wired/
Wireless LAN
Local Mobile Clients
Internet
Remote Wireless
LAN
Public Hotspot
Mobile Client
Carrier Network
Wireless Gateway
Mobile Clients
Enterprise
29. 29
What is Enterprise Mobility ?
Is it a softphone ? Is it a hot desk ?
Is it a laptop ?
Is it a PDA?
Is it a mobile phone ? Is it speech access ?
Enterprise mobility is all the above, and more
Roaming
Nomadic
Deskbound Teleworking
80-90% of employees are mobile
to varying degrees
Fixed Mobile
Semi-
Mobile
Less than 20%
deskbound
Less than 30%
road warriors
36. 36
Mobility TRM
Modified Technical Reference Model from TOGAF
Gra
phic
s &
Ima
m-
Dat
a
m-
Dat
a
Syst
em
&
Net
wor
Glo
bal
Roa
Loc
atio
n &
Dire
m-
Sec
Mob
ile
Use
r
Tra
nsa
ctio
m-Infrastructure
Applications
m-Business
Applications
Soft
war
e
m-Application Programming Interface
Mobile
Graphics
&
Imaging
Services
m-Data
Management
Services
Mobile Network Services
Mobile Operating Systems
m-Communication Infrastructure Interface
m-Communication Infrastructure
m-Data
Interchange
Services
Global
Roaming
Services
Mobile
User
Interface
(MUI)
Services
Location
&
Directory
Services
Mobile
Transaction
Processing
Services
Mobile
System
&
Network
Management
Mobile
Security
Software
Engineering
Services
37. 37
MEA Models
MEA Requirements Models
MEAF Principles
MEAF Goals
Five Stage MEA Process Model
MEA Value Web
MEA Deployment Models
MEAF Deliverables
MEA Stage Activities
MEA Mobile Initiative Process
More Models Created in Proforma ProVision
