First steps in EA: from three TU ’ s to 3TU. Bert van Zomeren Delft University of Technology

First steps in EA:First steps in EA:

from three TU’s to 3TU.from three TU’s to 3TU.

Bert van ZomerenBert van ZomerenDelft University of TechnologyDelft University of Technology

The Open Group ConferenceThe Open Group ConferenceMunich, October 2008Munich, October 2008

About 3TU. About 3TU.

• UniversitiesUniversities of Delft, Eindhoven, Twente• Federation since february 7th, 2007• Main goal: stronger international position

in education and research• 9.000 staff, > 28.000 students• Collaboration in 3TU. Graduate School• 5 joint MSC programmes (since 2006)• Considerable differences in Size, Culture,

Organizational structure, IT Governance, IT environments, applications etc.

The caseThe case

Ambition of 3TU.Graduate School:A federated DLWE, available in 2011

(whatever that may be)

Decision of IT Depts (Trojka):Facilitate 3TU.GS

Start of several IT projects3TU.wg Architecture

Achievements: ADMAchievements: ADM

Agreement on the use of architecture as enabler of change

de facto: TOGAF!

Achievements: frameworkAchievements: framework

Achievements: PrinciplesAchievements: Principles

• Integration by business services

• Use of standards• Buy before Make• No customization• Service

Orientation• Web enabling• Presentation and

function separated• Authentication

Achievements: visionAchievements: vision

• Business goals (= ambitions 3TU.GS)

• Target Architecture

website website website

Data Data Data

Functional services

Functional services

Functional services

Data

other

instititutons

website

Institution X

Functional services

Target architectureTarget architecture

Achievements: Achievements: business processesbusiness processes

• Choice of modelling language: Archimate

• Definition of processes in FLE

• A little help from our friends

• Models for processes, services and data objects

Modelling activitiesModelling activities

Achievements: Achievements: systems architecturesystems architecture

• Forbidden territory; use existing systems

• Integration via SOA• Respect institutional

independence

Achievements: data architectureAchievements: data architecture

• 3TU.Committee for services and standards (with mandate)

• Use existing standards

• Commitment of SURF in development of standards and application profiles

ChallengesChallenges

• 3TU. is a collaboration between partners who are also fierce competitors

• Individual branding remains very important

• In IT more enthusiasm than in education: growing gap

• Clash of the titans: architects versus project managers

• No experience with services

More challengesMore challenges

• No real enterprise architects in 3TU.

• No power to enforce process design or standards

• Limited authority for architects• Demarcation line between 3TU.

and local infrastructure• Facility sharing??

(do we trust each other?)

Work in progressWork in progress

• Finetuning of Target Architecture• Proof of Concept for one business

process• Choice of standard for learning

components• Mapping of services on application

landscape

ConclusionsConclusions

• A lot of work to do• Need for qualified architects• Reduce the gap between IT and

education• Introduction of SOA could work

• But, most important……

It’s great funIt’s great fun!

QuickTime™ and a decompressorare needed to see this picture.