University of California, Irvine CUMREC, 2004 Enterprise Architecture Implementation: Practical Steps Using Open Source Tools Marina Arseniev Enterprise

CUMREC, 2004

University of California, Irvine

Enterprise Architecture Implementation: Practical Steps Using

Open Source Tools

Marina ArsenievEnterprise Architect, Assistant Director

Administrative Computing Services, UC [email protected]

Copyright Marina Arseniev, 2004.

This work is the intellectual property of the author. Permission is granted for this material to be shared for non-commercial, educational purposes, provided that this copyright statement appears on the reproduced materials and notice is given that the copying is by permission of the authors. To disseminate otherwise or to republish requires written permission from the author.

CUMREC, 2004

University of California, Irvine (Administrative Computing Services)

AgendaAgendaChallengesEnterprise Architecture - An OverviewThe desired result…Practical Steps – how we got to where we are

today…Enterprise Architecture Framework: Zachman FrameworkModeling, Knowledge Base and Ontology Tool: ProtégéAnd more…

Results

CUMREC, 2004


UC Irvine Campus Overview

UC Irvine Campus Overview

Year Founded: 19652004 Enrollment: 24K studentsCarnegie Classification: Doctoral/Research – ExtensiveExtramural Contracts & Grants Awarded: $235M for 2002 –

2003Significant enrollment growth expectedCalifornia State budgetAdministrative systems must adapt

CUMREC, 2004


What is EA all about? A riddle!

What is EA all about? A riddle!

If the bowling pins are the IT solutions you provide for your customers, what is the ball?

Hint: Objective is to knock down maximum pins with one ball...

Your IT organization a bowling alley?

CUMREC, 2004


Our ChallengesOur ChallengesHundreds of systems - IBM Mainframe, Solaris, Windows

CICS/Cobol, Powerbuilder, Web/Java Applications, Vendor packagesVSAM, DB2, Oracle and Sybase

Lack of Real-timeIntegration based on FTP = Time lagsData inconsistency and quality issues = High technical and business

labor costs for repair or reconciliationUsers use disparate systems, user interfaces = TrainingNew compliance regulationsSecurity threats

CUMREC, 2004


Our Challenges (cont’d)Our Challenges (cont’d)Sophisticated business community that understands potential of

technology to make serious business improvements.Growing queue of projects.

Increasing complexity and technology choices for solutions. Workflow, Imaging...

Complex project management became critical to missionProject justification, selection, prioritization, sequencingExtraction of common requirements for horizontal, reusable solutions

Enterprise Architecture (EA) Initiative identified

CUMREC, 2004


UC Irvine’s EA ObjectivesUC Irvine’s EA ObjectivesImprove Planning

Help make more informed IT decisions

Reduce ComplexityLifecycle management - To establish a process that is focused on

building, maintaining, acquiring, and retiring technology

Improve IT to Business alignmentFacilitate the adaptation of technology to changing business needs

and pressures in campus administrationWhich technology solutions solve which business needs, and how?

CUMREC, 2004


Overview: What is EA?Overview: What is EA?

B u s in ess P roce ssesa n d F un c tio ns

In fo rm ationa n d D a ta

T e ch no lo gy

T ra n sit io na l P ro ce sse s th a t ke e p a ll a lig n ed

A blueprint of an organization to analyze and plan changes. The structure of (Enterprise) components, relationships, and

principles and guidelines governing their evolution over time.A strategic asset repository which defines the current and

target architecture environments.

CUMREC, 2004


Overview: What is EA?Overview: What is EA?

New application?What do we have already in place?

Impact?

CUMREC, 2004


Enterprise Architecture at UC Irvine


Desired result… “Perfect” world...goals articulatedroadmap, projects linkedtechnology linkedchange strategy

Irvine’s modelBased on Zachman

Framework

CUMREC, 2004


EA Planning Consists ofEA Planning Consists ofA standard methodology or frameworkA modelA repository of knowledge (populated model)A change management process

Business needs define application and required infrastructure change

Project-oriented approach to EAProjects = Change

CUMREC, 2004


What is EA Planning all about?


If the bowling pins are the IT solutions you provide for your customers, what is the ball?

The ball is the project(s) that you pick strategically and organize into a roadmap for change!

Objective is to knock down maximum pins with one ball...Before you can do that, you must understand your EA -

business processes, information/data, and technology.How?

CUMREC, 2004


Steps to start with EASteps to start with EA1: Create a list of specific questions, focusing on

critical areas.2: Identify senior technical and business people to

gather knowledge from; their roles and responsibilities in the EA process.

3: Develop change impact analysis methodology4: Choose an Enterprise Architecture Framework

CUMREC, 2004


Steps to start with EASteps to start with EA5: Choose a tool to model and populate Enterprise

Architecture Asset RepositoryGoal: easily accessible and maintainable repository

6: Plan communication methods7: Document Technical Reference Architecture

Principles, standards, and governance 8: Enforce architectural control

Choose key technologies and standardize. Constrain new development.

CUMREC, 2004


The step that never ends…The step that never ends…Step 9: Incremental EA model development and populationCreate and populate model as defined by questionsDefine As-is:

Business model and processes.Applications, data, components.How IT systems support the business processes. Project life cycle, SDLC

Identify desired enhancements to business as projects. For complex enhancements, organize projects into roadmaps.

Communicate, assess and track impact of change up, down, and across.

CUMREC, 2004


How were these steps handled

at UC Irvine?

How were these steps handled

at UC Irvine?

CUMREC, 2004


Step 1: Specific QuestionsStep 1: Specific QuestionsOur critical problems:

Life cycle management, governanceLink business goals, projects, and justificationControl proliferation and retirement of technology

Extraction of “Common Vision Requirements” across projects into patterns for reusable, horizontal components.

Application and data security for HIPAA and California State Bill 1386 compliance.

CUMREC, 2004


Step 1: Specific questionsStep 1: Specific questionsHow should we prioritize our projects and assign resources?Why are we doing project X? How can we “assemble” applications by implementing common

requirements across projects into reusable, tested components? How much reuse do we have today?How many reporting tools do we own? What are they used for?What technology should I use today for a web app and database? When

will it be retired from our organization?What data is subject to HIPAA or State Bill 1386 compliance?Which applications use this data and how secure are they?What technologies does this project use? What projects does this

technology support? Touch points between components?

CUMREC, 2004


Step 2: Identify owners of knowledge, roles and

responsibilities

Step 2: Identify owners of knowledge, roles and

responsibilitiesIdentified key IT people who also know the business.People from business units (e.g: Human

Resources)Agreed on roles and responsibilities.

CUMREC, 2004


Step 3: Develop Change Impact Analysis

Methodology

Step 3: Develop Change Impact Analysis

MethodologyNeed a change… How do you know which one,

when, and how?Analyze and articulate impact of change to business or

technology.Measure impact of moving from a current to targeted

practice. Freely available Sloan School of Management’s

“Matrix of Change” tool. (http://ccs.mit.edu/MoC).

CUMREC, 2004

University of California, Irvine (Administrative Computing Services)Example: Establish GUI Team

Example: Establish GUI Team

CUMREC, 2004


Step 4: Enterprise Architecture Framework

Step 4: Enterprise Architecture Framework

Need direction and guidance?Many frameworks to choose from. Comparison at:

http://www.opengroup.org/architecture/togaf8-doc/arch/p4/others/others.htm

Adopted the Zachman Framework (http://www.zifa.com)What is it?

A language that helps people think about complex concepts and communicate in non-technical terminology.

Planning tool

CUMREC, 2004


Zachman Framework Intro

Zachman Framework Intro

Planner

Owner

DesignerBuilder

As built

What How Where Who When WhyData Function Network/ People/ Time/ Motive Node Work Cycle

Rule design

Business logistics

Logical data

model

Semantic model

System design

Business locations

Human interfac

e

Timing definition

Business plan

Important things

Business functions

People and

groups

Events and

cycles

Goals and strategy

Process model

Work Flow

model

Master schedul

eApplicatio

n archDistributed system

Processing

structure

Business rule

modelPhysical

data model

Tech arch

GUI arch Control structure

Data definition

Code Network arch

Security arch

Rule repository

Question

View

CUMREC, 2004

University of California, Irvine (Administrative Computing Services)Step 5: Model and Repository Management

Tool

Step 5: Model and Repository Management

ToolHow do I model and collect information for the EA?

Zachman Framework - powerful thinking tool lacks technology for putting it into practice.

Storing redundant lists of “stuff” in Word, Excel, Visio was difficult. Application lists, security information, critical business cycles

Stanford’s Protégé Knowledgebase and Ontology Tool Auto generates forms for collecting information based on ontology

and class definitions.Generates HTML outputOpen source at http://protege.stanford.edu/

CUMREC, 2004


Step 6: Plan Communication

Step 6: Plan Communication

Protégé minimizes redundancy, increases consistency Meets Zachman Framework vision of storing an enterprise

artifact in a single place. Protégé and Zachman Perspectives (Rows)

Plug-in produces XML output. XML processed using XSLT into appropriate presentations,

per Zachman Perspectives (audience).Open source XML and XSLT available as Xerxes and

Xalan from http://www.apache.org

CUMREC, 2004


Examples:Examples:

Example of how we use Protégé to collect information for Zachman Framework.

Example of how we report from Protégé using XML/XSLT.

CUMREC, 2004


CUMREC, 2004


CUMREC, 2004


Example: ProtegeExample: Protege

CUMREC, 2004


Example: ProtegeExample: Protege

CUMREC, 2004


Step 7: Technical Reference Architecture

Step 7: Technical Reference Architecture

Documented principles, guidelines, and best practices of Architecture Domains:

Lifecycle Management Adopt the “4 year/16 Quarter Sliding Window Methodology” Identifies technologies that are “Approved”, “Maintained but not Upgraded”,

in “Sunset”, “Retired”, or “By Approval Only”.

Developed Apps Vendor/ASP Apps Security Network Database Operations

Common Conceptual Architectural Principles

CUMREC, 2004


CUMREC, 2004


Step 8: Enforce Architectural Control

Step 8: Enforce Architectural Control

Standardized onJ2EE & Expresso - an Open Source Java Application Development

Framework - Apache Struts and MVC. (http://www.jcorporate.com)LDAP Directory Services (http://www.openldap.org)Open Source JA-SIG uPortal software. A Java-based portal

developed by Higher-Ed for Higher-Ed. (http://www.ja-sig.org)Single sign-on based on Web-ISO and Kerberos for campus-wide

web applications.

Immediate benefits - reuse of components and metrics. Reduced skill sets and solution choices.

CUMREC, 2004


Step 9 – Putting it all together

Step 9 – Putting it all together

Examples of how we use ProtégéZachman Physical Perspective (Row 3) - Technology Life

CycleAlignment of IT to Business: Link from Goal to Project to

Technology, justifying investment and identifying gaps.Tracking HIPAA and California State Bill 1386 Security

Compliance

CUMREC, 2004


StatusStatus

Use Protégé to model and collect organizational information. Track security compliance.Track common requirements across projects. Justify investment decisions and vendor selection. Create links between our goals, roadmaps, projects, and

technologies. Determine “touch points” between projects and technologies

to assess impact of change.

CUMREC, 2004


Realized ValueRealized ValueTechnologies retired

Database servers consolidatedMS IIS Web Server (except where required by vendor) - 2003Clipper - February, 2004

Reduced required IT skill setsOracle DBA – due to limited resources, migrated off of OracleJava focus

Applications are database neutral (Expresso/JDBC)Reduced development costs

Code reuse: Expresso objects, SSO Java lib shared between IBM, Solaris, Windows platforms, shared user objects.

Common infrastructure for development: LDAP, Workflow

CUMREC, 2004




Desired result…the perfect world

Reduce IT complexity (and cost)

Reduce queue and increase timeliness of projects

Facilitate a strategic road map for change with careful project selection and planning.

CUMREC, 2004




If the bowling pins are the IT solutions you provide for the customers, what is your ball?

The bowling ball is the project(s) that you pick strategically and organize into a roadmap for change!

Game objective: knock down maximum pins with one ball...

CUMREC, 2004




Who (or what) makes the bowling ball (your IT projects)

roll at precisely the right spot in the lane and at optimal speed?

Your Enterprise Architecture!Before you can bowl with projects, you must understand your EA

- business processes, information/data, and technology.Using the tools shown today you can start bowling tomorrow!

CUMREC, 2004


Q & AQ & A

UC Irvine’s EA Web Site: apps.adcom.uci.edu/EnterpriseArchZachman Framework: www.zifa.com/Sloan School of Management’s “Matrix of Change”: ccs.mit.edu/

MoCOntology and Knowledgebase: protege.stanford.edu/UC Irvine’s Administrative Portal: snap.uci.edu uses JA-SIG

uPortal software: www.ja-sig.org/Reporting using XML/XSLT: www.apache.orgJava Application Dev. Framework: www.jcorporate.com/LDAP: www.openldap.org/

Documents

University of California, Irvine CUMREC, 2004 Enterprise Architecture Implementation: Practical Steps Using Open Source Tools Marina Arseniev Enterprise