1. An Approach to Developing IT Architectures
A. L. Steenkamp
John (Zongjun) Li
Lawrence Technological University
Michigan
United States

2. PRESENTATION FORMAT
Introduction
Architectural Approach
The Enterprise Mobility Viewpoint
Conclusions

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

4. Definitions
Several definitions used for
Enterprise architecture
IT (technical, technology) architecture
Viewpoints, Views
Framework

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. Definition - Architecture
IEEE P 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. 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
Note that the architecture exists within an environmental context and involves the platforms and infrastructure besides the views of the systems of the architecture

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. 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

10. ARCHITECTURE APPROACH
The key tenets
Architectural principles
Architectural framework
Architectural process model
Architectural methodology
Architectural continuum
Reusable assets, reference models
Solutions continuum
Reusable solution patterns

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. Architectural Principles

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
Criteria:
Understandable – intention of principle is unambiguous and clear
Robust – enable good quality decisions about architectures and plans to be made
Complete – every important principle governing management of IT for organization is defined
Consistent – principles should not be contradictory
Stable – principles should be enduring, yet accommodate change

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

15. ARCHITECTURE FRAMEWORK
Model Portfolio
Modeling language
Purpose
Concern/Principle
Stake-
holder
Content
Layer
Aspect
Standard
Tool
Application
Data
Infra-structure
Comm. Eng
Quality
Security
Mobility

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.

17. TOGAF 8.1 ADM Process Model

18. Strategic Planning and Architecture Processes

19. Key Tenet 3 Architecture Process Model

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
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. 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. 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. Key outcomes of pedagogy
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
SPECIFIC OUTCOMES
Informational outcomes: leading-edge technologies for designing and deploying a portal architecture
Managerial and technical competencies: problem and process analysis, architecture modeling, documentation and teamwork
Best practices: international and industry standards
Ability to define, apply criteria to evaluate benefits and weaknesses of approaches, methodologies, and tools promoted by industry
Various levels, types of integration and alignment of project level outcomes with IT strategic objectives

24. Team Projects Research on Enterprise Mobility Viewpoint
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

25. The Enterprise Mobility Viewpoint
John Li
The Enterprise Mobility is one of the EA viewpoints in TOGAF 8.1, which has not been developed.
Lawrence Technological University
Michigan
United States

26. Agenda Introduction Enterprise Mobility
The Enterprise Mobility Viewpoint
Mobile Enterprise Architecture Research
Conclusions

27. Introduction North America Europe APAC Latin America
Number teleworkers1
28M
W. Europe 19M
Japan 9M
APAC 11M NA
Number mobile subscribers2
193M
551M
549M
162.3M
Mobile phone penetration1
58% US
98% UK
45% Russia
76% S Korea
25% China
37% Brazil
Needs of the Mobile Enterprise Vary Worldwide
There is almost one mobile phone for every person in much of the developed world, according to new figures from the OECD. In Luxembourg, phones outnumber people, since many people who live in neighbouring countries have a second handset for use within its borders. Despite their enthusiasm for PCs and broadband links, Canada and the United States have been slower to adopt mobile phones than other rich countries.
Avaya, Data for 2004

28. Mobile Enterprise Vision
Roaming
Nomadic
Enterprise
Four groups:
LAN: Deskbound
WLAN: Teleworking
WWAN: Nomadic
WMAN: Roaming
Deskbound
Teleworking

29. What is Enterprise Mobility ?
Is it a mobile phone ?
Is it a PDA?
Is it speech access ?
Is it a softphone ?
Is it a laptop ?
Is it a hot desk ?
Enterprise mobility is all the above, and more
80-90% of employees are mobile to varying degrees
Fixed
Mobile
Semi-Mobile
Less than 20%
deskbound
Less than 30% road warriors
Definition of Enterprise Mobility (EM)
The difference of ME and EM
Information
Communication
Business
Roaming
Nomadic
Deskbound
Teleworking

30. VME Mobile Systems
Virtual Mobile Enterprise – VME

31. Conceptual MEA Model Updated from IEEE P1471-2000
Mobile Enterprise can be defined as a system, the conceptual architecture model is updated from IEEE P
The Mobility Viewpoint is one of the most important parts in the MEA model which has many views classified in four areas: MBA, MDA, MAA, and MIA. In the research, Security and Quality were considered as two special viewpoints which have very close relationship with mobility viewpoint.
Updated from IEEE P

32. Problem Modeler -Stakeholder Concerns
Mobile
Business
Users,
Planners,
Business Management
Data
Database Designers,
Administrators,
System Engineers
Application
System and
Software Engineers
Infrastructure
Acquirers, Operators,
Managers

33. The ME Viewpoints and Views
Stakeholders
Users,
Planners,
Business Management
Database Designers, Administrators,
System Engineers
System and
Software Engineers
Acquirers, Operators,
Administrators,
Managers
Mobility Sub-Viewpoints
m-Business
Sub-Viewpoint
m-Data
m-Applications
m-Infrastructure
Views
Strategy Objectives and Goals
Process, Workflow, Function, Services, Location, Usability
Performance
Rules, Events
m-Information
m-Communication People (enterprise chart), Finance
m-Data Entity, m-Data Flow (Mobile Enterprise Data Use),
Logical Data
Software Engineering,
m-Applications Interoperability,
Software Distribution
Mobile Computing/ Hardware,
m-Communication
Engineering, Processing, Cost
Special Viewpoints
m-Security Viewpoint
m-Quality Viewpoint
This slide shows the relationships of among different stakeholders, viewpoints and views in different area.
This table is similar to the example Taxonomy of Architecture Views in TOGAF 8.1 Developing Architecture Views in Table 1 (6/11)
The view or views will be the key components in the ME.
Confused concepts: Viewpoints, Views, and Sub-Viewpoints.

34. Research on MEAF
My research on “Enterprise Goes Mobile” - an MEA Framework in this slide, can be easily mapped to TOGAF ADM as shown in next slide.
This conceptual framework is elaborated in the following four aspects:
Key framework components
Three-level enterprise structure
MEA approach
Top-down flow and the bottom-up flow

35. TOGAF ADM and MEAF
Three levels: Enterprise – Business Units – IT/Mobile Department
Security Architecture is the first/ most important part in the mobile solutions for all the enterprise adopting emerging mobile technologies. Although it can be considered as part of DA, AA, and IA. For the MEA, we separated it.

36. Mobility TRM
Similar to the TOGAF TRM, Mobility TRM can be presented as shown in this slide, which presents the service categories of the ME environment from m-Communication, m-Information, and m-Business.
Discussion:
Mobile Security and Quality are the services, are they viewpoints? How about m-Information?

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
To demonstrate the enterprise mobility viewpoint, we created some models related to the views demonstrated previously. Some of the models created by Proforma ProVision tool which is a complete Enterprise modeling tool for Business Process Improvement, Simulation, and EA development. The modelers and Objects of ProVision are organized around the fundamental dimensions of an Enterprise: Who, What, Why, Where, When, and How.

38. Requirement Modeler -VME System Requirements

39. Global Roaming Requirements

40. Mobile Technology Requirements

41. MEAF Principles

42. MEAF Goals

43. Five Stage MEA Process Model

44. MEA Value Web

45. MEA Stage Activities

46. MEA Deployment Model

47. VME m-Information Criteria

48. m-Business Process Improvement Pilot Project

49. State Modeler -VME Strategy Process Model

50. Strategy Modeler - m-Business Process Improvement Pilot Project

51. Problem Modeler -Mobile Solution Variances

52. MEAF Deliverables

53. Impact Modeler -Mobile Technologies Impact

54. MEA Mobile Initiative Process
This is very important process model for all the mobile (IT) initiatives. It can be used to simulate the investment, monitor the execution processes and help the management team make decision based on the results generated from this model. Analyzing data can input to each elements in this model, the ROI and other diagrams and tables can be automatically generated by executing the simulation function provided by the tool.

55. Modeling Tool – Proforma ProVision
ProVision v5.0.3a Enterprise
Website:
MEA with TOGAF
Modeling tools –
Rational Rose, Microsoft Visio, and this Proforma ProVision

56. Model Inventory
Modelers and Models

57. Object Inventory

58. Conclusions
This presentation is based on the research of “Enterprise Goes Mobile” and focuses on following areas in the last few years:
The Concept of Mobile Enterprise (ME)
The Concept of Enterprise Mobility (EM)
The TOGAF and MEAF
The Concept of MEA Model
Enterprise Mobility Viewpoint and Its Views
Five Stage MEA Process Model
Models with ProVision

59. Q&A
Thanks!