slide presentation ca's business driven architecture

State of CaliforniaState of CaliforniaXYZ DepartmentXYZ Department

Business Driven Architecture (BDA)Business Driven Architecture (BDA)Dave McAfeeDave McAfee

May 12, 1999May 12, 1999

2

Introduction

The Department and their partners, Grant Thornton LLP, have developed a Business Driven Architecture(BDA)

Based on MetaGroup's enterprise-wide technical architecture framework - from planning and definition to execution and implementation.

The presenter will "walk-thru" the phased process used to develop the architecture, highlighting the key points to achieve success.

3

Business-Driven Architecture Contents

I. A Little Kipling

II. Overview

III. Project Scope

IV.Timeline

V. Example Telephony

VI.Conclusion

4

Business-Driven Architecture I. Kipling’s Elephant Child

I keep six honest serving men

They taught me all I knowTheir names are What and Where and

When and How and Why and Who.

5

The Enterprise The User

What Blueprint for the deployment oftechnology divided into Governance,Data, Applications, Infrastructure andSecurity

A guide to better utilize IT in day today business from an Enterpriseperspective.

Where Enterprise wide application ofPrinciples, Best Practices, DesignPrinciples, Standards, and ProductsLists

Enterprise wide, and interfacingwith partners and providers

When Formal start first quarter 98, in progress,to maintenance in second quarter 99

When first iteration is complete andcontinuing on in to the future

How Staff (both CIT and DIT), using acontractor, and a industry research firmdeveloped initial architecture papers.

Standardized technologies, thatinterface in a predetermined just-in-time basis

Why IT has become an integral part ofEnterprise business. Support costs(TCO) and complexities are growingexponentially

IT supports the business, becomingmore usable while controlling costsand reducing complexities

Who Applies to Enterprise, adopted by theDepartment Executive Staff,

Enterprise staff and thosedeveloping partnerships with IT

Business-Driven Architecture I. Kipling’s Elephant Child

6

Business-Driven Architecture II. Overview - Background

The Business-Driven Architecture (BDA) defines the XYZ Department’s (XYZ) Enterprise-wide Technical Architecture (EWTA). This architecture project is broad-based, covering the Department’s entire Information Technology (IT) environment including:• Governance

• Applications

• Infrastructure

• Data

• Security The direction for this effort came from the IT Strategic Plan.

7

Business-Driven Architecture II. Overview - Architecture Definition

A Business-Driven Architecture:• Is derived from business requirements

• Is understood and supported by Department executives and lines of business

• Guides the engineering of the Department’s information systems and technology infrastructure across the various component architectures

• Is based upon a logically consistent set of principles and practices

• Serves as a template for minimizing the costs of deploying and supporting technology.

Ultimately, the Architecture enables the development of a rich information environment capturing and sharing information throughout the XYZ, with other government agencies, and with partners/customers.

8

Business

Driven

Architecture

IT

Systems

Planning InfrastructureEngineering

Application/InformationEngineering

Enterprise

Business

Policy

Strategic/

Tactical

Plans

Legislature

Technology

CustomerExpectations

Enterprise

Business

Policy

Strategic/

Tactical

Plans

Legislature

Technology

CustomerExpectations

Before

After

E-Mail

IT

Systems

Planning

ProjectArchitectures

Multiple Technologies

Business-Driven Architecture II. Overview - IT Architecture

9

Business-Driven Architecture II. Overview - Approach

XYZ’s Business-Driven Architecture (BDA) follows the META Group’s Enterprise-wide Technical Architecture methodology. The approach process is shown in Figure 3 below.

Fig. 3 - Approach Process

Phase 0:Phase 0:

BUSINESS

DRIVERS

REQUIREMENTS

FOR TECHNICAL

ARCHITECTURE

“GAP”

ANALYSIS

MIGRATION

PLANNING

IMPLEMEN

T

BASELINE OF EXISTING TECHNOLOGY INFRASTRUCTURE

• Applications• Data• Process Knowledge• Repositories

• Hardware• Software• Networks• Interfaces

• Standards• Methods• Organization• Skillset

AWARENESS OF TECHNOLOGY TRENDS

Phase III:Phase II:Phase I:

PROJECT PLANNING• Business Case• Communications

Plan• Project Plan• Project Proposal



Concept. Arch.• Principles

• Best Practices

Arch. Defin.• Standards• Products(Apps./Platforms)

10

Business-Driven Architecture II. Overview - Stakeholders

Active participation by all stakeholders (illustrated in Figure 4 below) is necessary to realize the fullest potential of XYZ’s Business-Driven Architecture.

Fig. 4 - XYZ’s Stakeholders

External Technology Providers

IT

Technology Units

ITDivision Chiefs

XYZ Business/Program Areas

IT

Executive

Internal Technology Providers

Decentralized IT(Business Area IT)

TechnologyVendors

ServiceProviders

(Data Centers etc)

XYZ Executive Staff

11

Business-Driven Architecture III. Process Scope - Business Case

Deliverables for Phase 0 included:• Project Plan

• ID of stakeholders

• Communications Plan

• Internal Sales Document

Phase 0:Phase 0:

BUSINESS

DRIVERS

REQUIREMENTS

FOR TECHNICAL

ARCHITECTURE

“GAP”

ANALYSIS

MIGRATION

PLANNING

IMPLEMEN

T












• Best Practices


12

Business-Driven Architecture III. Process Scope - Business Focus

Deliverables for Phase I included:• Business Drivers (BD)

• Technology Trends (TT)

• Architectural Requirements (AR)

• Architecture Requirements Matrix (BD x AR)

Phase 0:Phase 0:

BUSINESS

DRIVERS

REQUIREMENTS

FOR TECHNICAL

ARCHITECTURE

“GAP”

ANALYSIS

MIGRATION

PLANNING

IMPLEMEN

T












• Best Practices


13

Business-Driven Architecture III. Process Scope - Technical Focus

Phase 0:Phase 0:

BUSINESS

DRIVERS

REQUIREMENTS

FOR TECHNICAL

ARCHITECTURE

“GAP”

ANALYSIS

MIGRATION

PLANNING

IMPLEMEN

T











• Best Practices


Deliverables for Phase II are:• Conceptual Architecture

• Conceptual Architecture Matrix (AR x BP)

• Domain Components Architecture (CA)

• Product Selection Process Report

• Existing (Baseline) Architecture Report

• Gap Analysis Report

14

Business-Driven Architecture III. Project Scope -Technical Focus (con’t.)

The following diagram depicts the relationship of XYZ’s five major architectural domains: Governance , Applications , Infrastructure, Data, Security. These domains have been decomposed into sample 13 architecture components (See Figure 5 below).

Fig. 5 - Domain Model

2.2 Intra/Internet

2.3 Middleware 2.4 Groupware

2.1 Application Development

4.1 Transaction Data

1.0 Governance

3.1 Platform

3.3 Systems Management

3.2 Network 3.4 Telephony

4.2 Information

3.0 Infrastructure

4.0 Data

2.0 Application

5.3 SupportTechnologies

5.2 System and Data Integrity

Technologies

5.1 EnforcementTechnologies

5.0Security

15

Business-Driven Architecture III. Project Scope - Migration Plan

The deliverables for Phase III are:• Migration Strategy Report

• Governance Guidelines

Phase 0:Phase 0:

BUSINESS

DRIVERS

REQUIREMENTS

FOR TECHNICAL

ARCHITECTURE

“GAP”

ANALYSIS

MIGRATION

PLANNING

IMPLEMEN

T












• Best Practices


16

Business-Driven Architecture III. Project Scope - What the BDA Does Not Include

The three phases of the BDA did not include the following: • Implementation Plans for particular projects or systems designs

• The BDA is analogous to a building code,not a specific building plan.

• Redesign or reengineering of XYZ’s business processes

• Complete configurations and products (buy-lists) for all architectural components

– This is accomplished over time and revisited through the architectural review process.

• Project or physical architectures– These are derived or applied uses of the BDA components and products.

17

Business-Driven Architecture IV. Timeline

Fig. 6 - Project Timeline

Six Weeks Seven Weeks Twelve Weeks Five Weeks

Figure 6 below identifies the approximate timeframes for each phase of the

BDA.

Phase 0:Phase 0:

BUSINESS

DRIVERS

REQUIREMENTS

FOR TECHNICAL

ARCHITECTURE

“GAP”

ANALYSIS

MIGRATION

PLANNING

IMPLEMEN

T












• Best Practices


Platforms

InetApplications

28-30 Weeks2-3 Weeks

4-8 Weeks

18

Background and Introduction• The Telephony Component defines the technical components of the

telecommunications infrastructure which support the Department’s voice applications and systems.

• XYZ’s customers demand direct access to information and services that are easy to understand and use. Telephone systems are used increasingly to provide responsive customer care in large organizations with large customer bases. Therefore, the Department requires a complete telephony architecture in order to exploit the latest telephony technology to better serve its customers.

Business Driven ArchitectureV. Example - Telephony Component

19

Business Driven ArchitectureV. Example - Telephony Component

Telephony subcomponents include:• Call Center

• Office Telephony

• Cabling

• Wireless Telephony

• Video Conferencing

• Computer Telephony

• Communications Fabric

20

Business-Driven Architecture VI. Conclusion

The Business-Driven Architecture:• Allows Information Technology to act as a business enabler

• Permits the lines of business to concentrate their efforts on improving processes and providing outstanding customer service

• Enables the fulfillment of XYZ’s vision to work better, faster and smarter.

More Information?

David McAfeeTelephone - 654-8374

- 653-4240

http://www.lanset.com/dmcafee

[email protected]

21

Business Driven ArchitectureOther Presentations

The Road to Getting an Architecture Process Started• Where - Convention Center, 2nd Floor, Room 204.

• Who - Dale Morgan, EDD Senior Architect

• When - Thursday, May 13, 1999 from 10:00 to 11:00am

“Planning Your Enterprise Architecture Project - initial steps to get your EA started”• Where - EDD Auditorium 722 Capitol Avenue

• Who - Chris Eaves, Senior Architect - Grant Thornton, LLP

• When - Wednesday, May 26, 1999, 9:30 to 10:30 a.m.

22

2.0 Application2.2 Intra/Internet

2.2.1 Browser2.2.2 Intranet Server Software2.2.3 Search Engine Software2.2.4 Firewall Software2.2.5 Authoring tools2.2.6 Development Languages2.2.7 Development Tools2.2.8 Intraware

2.3 Middleware

2.3.1 Program to Program Middleware2.3.2 Low Level Communication API2.3.3 Inter-Process Comm. (IPC)2.3.4 Message Passing2.3.5 Message Oriented Middleware2.3.6 Remote Procedure Call (RPC)2.3.7 Object Request Brokers (ORBs)2.3.8 TP Monitors2.3.9 Object Transaction Monitors2.3.10 Message Brokers2.3.11 Database Gateways

2.4 Groupware

2.4.1 Content Exchange2.4.2 Electronic Mail2.4.3 Calendaring and Scheduling2.4.4 Elect. Doc. Mgmt.2.4.5 Workflow Mgmt.2.4.6 Intelligent Agents2.4.7 Desktop Publishing2.4.8 Video-conferencing

2.1 Application Development

2.1.1 Meth./Process Mgmt.2.1.2 Project Mgmt.2.1.3 Version Control2.1.4 App. Dev. Repository2.1.5 Modeling Tools2.1.6 CASE Tools2.1.7 Devel. Languages2.1.8 Development Tools2.1.9 Multimedia Devel.

2.1.10 Testing2.1.11 Mainframe Utilities2.1.12 COTS Software:

Pers. Product. Suite Desktop Database Flowcharting Tools 3270 Emulation2.1.13 Ent. Resource Plan2.1.14 Specialized Utilities

3.0 Infrastructure3.1 Platform

3.1.1 Client Platform3.1.2 Server Platform

File/Print Application Database Internet/Intranet

UNIX Servers Mainframe Servers3.1.3 Network Printer

3.3 Systems Management

3.3.1 Service Desk3.3.2 Configuration Management3.3.3 Operations Management Network Management Framework Virtual Data Center3.3.4 Storage Management 3.3.5 Perform. Monitoring & Tuning3.3.6 Security 3.3.7 Disaster Recovery3.3.8 Enterprise Architecture Lab

5.0Security

5.1 EnforcementTechnologies

5.1.1 Identification5.1.2 Authentication 5.1.3 Authorization5.1.4 Access Control Firewall

5.2.1 Encryption 5.2.2 Non-Repudiation5.2.3 Virus Detection & Prevention5.2.4 Op. Recovery Disaster Recovery5.2.5 Config. Mgmt.

5.2 System and Data IntegrityTechnologies

5.3.1 Security Admin.5.3.2 Auditing

5.3 SupportTechnologies

4.0 Data4.2 Information

4.2.1 Data Extraction, Cleansing &Transformation Tools4.2.2 Enterprise Data Warehouse

4.2.3 Data Repository4.2.4 Data Marts4.2.5 Decision Support Tools

3.2 Network

3.2.1 Local Area Network Topology Protocols Switches Hubs Cabling Wireless Internet Access Remote Access

3.2.2 Wide Area Network Protocols Customer Premise Eqpt. Router, CSU/DSU FRAD, ATM Switches Carrier Services Internet Access Remote Access3.2.3 Network-centric Computing

4.1 Transaction Data4.1.3 Data Repository4.1.4 Data Modeling

4.1.1 Data Support4.1.2 Data Management File Processing System DBMS- PreRelational, Relational and Object

1.0 Governance

BackgroundBDA Domain Model

3.4 Telephony

3.4.1 Call Center3.4.2 Office Telephony3.4.3 Cabling3.4.4 Wireless Telephony3.4.5 Video Conferencing3.4.6 Computer Telephony3.4.7 Communications Fabric