Symbiosis of Enterprise Architecture and ICT Architecture

1
Symbiosis of Enterprise Architecture and ICT
Architecture

• J.C. Wortmann¹, D.K. Hammer², J.B.M.
  Goossenaerts¹, A.T.M. Aerts²

2
Overview

• Four architectural domains
• Six phases in enterprise architectures
• Six times the same point
• It takes two to tango
• Domain Architectures Overview
• Conclusion it takes four to tango
• All in 10 minutes !!

3
Four Architectural Domains

• enterprise architecture,
• model architecture,
• software architecture and
• ICT-platform architecture.

4
Enterprise Architecture

• Enterprises (recursively),
• their contracts,
• their structure,
• their processes
• their positions
• their controls
• their exchange (G, S, H, I, M, E) with others

5
Model Architecture

• Object models
• Resource Models
• Workflow Models
• Products Models
• Document Models
• Interaction Models
• Users and Applications,
• etcetera

6
Software Architecture

• Logical view (end-user functionality)
• Components view (development)
• Process view (run-time behavior)
• Physical view (installation)
• Usage cases and scenarios

7
ICT platform Architecture

• Structure
• Interaction
• Distribution
• Concerns
• Performance
• Stakeholders

8
Six Phases

• the functional hierarchy
• the functional hierarchy with function oriented
  automation
• the functional hierarchy with shared data base on
  mainframes
• the process oriented enterprise
• the supply chain oriented enterprise
• the web-enabled agile enterprise

9
1. Functional hierarchy - no automation

• Enterprise Architecture
• functional hierarchy -- machine bureaucracy
• focus on resources within functional silos
• Model Architecture -- hierarchy
• business processes carried by document flows
• object models implemented in files
• Software Architecture
• humans perform calculations and access files
• ICT Platform Architecture
• paper, pencil, abacus, telegraph, telephone,mail

10
Point 1

• Model architecture (hierarchy, processes)
  enables
• predictability,
• correctness,
• repeatability, and
• accountability.

11
2. Functional hierarchy silo automation

• Enterprise Architecture (same)
• Vertical communication well organized
• Horizontal communication slow and error-prone
• Model Architecture (same)
• object models passive but explicit in functional
  datastructures
• Software Architecture
• monolithic applications per functional area
• ICT Platform Architecture
• mainframe with terminals

12
Point 2

• Silo-based automation enables
• speed and
• reliability
• of all data-related activities
• and calculations.
• ..Automation enables improvement

13
3. F-hierarchy shared DB on mainframe

• Enterprise Architecture logistics
• matrix organization to co-ordinate flows
• Model Architecture
• single conceptual data model for whole enterprise
• explicit integration by process diagrams
• Software Architecture
• separation between data layer and application
  layer
• ICT Platform Architecture
• mainframes with minicomputers as satelites

14
Point 3

• Conceptual database and 3 schema architecture
  bridge gap between enterprise and ICT-domain
• Automation problem of functional hierarchy is
  solved!
• ICT-solution is cast in concrete while business
  requires change business process re-engineering

15
4. process-oriented enterprise

• Enterprise Architecture
• Business Units value-adding processes become
  leading principle rather than functional units
• Model Architecture
• Workflow plays the dominant role in modeling
• Object-orientation emerges
• Software Architecture
• Best-of-breed standard integration rather than ad
  hoc
• separation of UI, business logic and data access
• ICT Platform Architecture
• 2 tier client-server LAN open platforms

16
Point 4

• Client-server enables internal integration
• in a more flexible way than ad-hoc integration
• ideal tool for BPR
• But .. Enterprise needs are already moving
  towards external integration over the supply chain

17
5. SC process oriented enterprise

• Enterprise Architecture
• cross-enterprise business processes
• re-definition of roles in the supply chain
• Model Architecture
• federated models of heterogeneous origin
• semantic mapping and explicit SC modeling
• Software Architecture
• asynchronous message-based integration
• mapping and transaction services rich UI
• ICT Platform Architecture
• WAN 3-tier CS Distributed data and processing

18
Point 5

• Enterprise application integration technology
  enables supply chain integration
• Enterprises leverage these technologies to move
  forward towards more responsiveness and agility

19
6. Agile process-oriented enterprisethe supply
chain is the enterprise

• Enterprise Architecture
• differentiation scope globalization
• collaboration
• Model Architecture
• task-based UI self-descriptive data scope and
  roles
• executable models distant users differentiated
• Software Architecture
• thin client mobile agents alert and launch
• ICT Platform Architecture
• ubiquituous asynchronous, heterogeneous computing
  

20
Point 6

• ICT developments enable enterprises to make
  progress in directions where they would like to
  go collaborativeness
• Enterprises leverage ICT developments as soon as
  they occur -- when there is a market opportunity
  e-business

21
Domain architecture - overview
22
Point 7

• Modularity occurs within a domain
• Performance is defined within a domain
• Integration covers several domains
• Breakthrough occurs in several domains
• Architecting requires several domains

23
Conclusion

• Enterprise architectures and ICT architectures
  move forward in symbiosis
• It takes four to tango