Queensland University of Technology CRICOS No. 000213J Introduction to the Unit Prof. Alistair Barros INB/N 205 Enterprise Architecture Lecture 1

Queensland University of Technology

CRICOS No. 000213J

Introduction to the Unit

Prof. Alistair Barros

INB/N 205 Enterprise ArchitectureLecture 1

a university for the worldrealR

INB/N 205 Teaching Team

• Unit Coordinator: Prof. Alistair Barros– Consultation times, Fri 10-11am– Tel: 3138 1199– Office: Room 506, Level 5, 126 Margaret St.– Email: [email protected]

• Lecturer/tutor: Dr. Bhuva Lakshminaryan• Lecturer/tutor: Ayed Alwaidain• Plus guest lecturers


Objectives of unit

• To provide a holistic and integrated view of complex enterprises, integrating business practice and IT, through enterprise architecture frameworks

• To provide insights in different enterprise architecture methodologies

• To develop skills in modelling techniques and languages at the different layers of enterprise architectures


Objectives of unit

• To consolidate on software application design skills through use of integrated modelling techniques and languages


Outcomes of unit

• Explain what an enterprise architecture consists of

• Contrast different enterprise architecture methodologies and their relative strengths and weaknesses

• Apply techniques for analysis at the business level and designing a software solution. This will include integrated data and process modelling and software service mapping;


Outcomes of unit

• Undertake an enterprise architecture use case

• Communicate an architecture at different levels for different stakeholder audiences


What is an Architecture?

•Architecture is the fundamental organization of a system embodied in its components, their relationships to each other, and to the environment, and the principle guiding its design and evolution. IEEE Standard 1471-2000


Why?

• These frameworks integrate the multiple dimensions and views of complex organisations

&• Give you a coherent appreciation of alternative

modelling techniques used by different sets of professionals designing, implementing and maintaining business planning & operations, business applications and IT infrastructure


Because

• These concepts are foundational for all IT professionals, for regardless of what you design, develop, administer, procure or govern

• Your work impacts a whole organisation – the Enterprise – not just IT


Top 10 Technology Priorities 2010

1. Business Intelligent Applications

2. Enterprise applications3. Legacy application

modernization4. Networking, voice and data

communications5. Server and storage

technologies (virtualization)

6. Security technologies7. Service oriented architectures8. Technical infrastructure

management9. Documents management10. Collaboration technologies

Source: Gartner EXP (February 2007)


Business and CIO Priorities

Business Near Term Expectations of IT•Improve business process•Control enterprise cost structures•Attracting retaining and growing customers•Improve workforce effectiveness•Grow Revenue

CIO Near Term Strategies for IT• Improve the quality of IT

services• Improve IT governance• Improve the link between

business and IT• Demonstrating the business

value of IT• Building business skills in IT

Source: Gartner EXP (February 2007)


Top Tech Jobs 2010

1. SAP, Oracle and Peoplesoft specialists

2. PHP developers

3. C++/CORBA developers

4. Unix network administrators

5. Business analysts

6. Java and J2EE developers

7. Lotus Notes specialists

8. C# developers

9. .NET developers

10. Senior testers

Data compiled based on information from Ambit Recruitment Group, The Olivier Group, Macro Recruitment, Hays Information Technology, the Department of Employment and WorkPlace Relations, and ZDNet Research 2010


Professional roles related enterprise architecture

Macro-level in enterprise

•Business analyst•Solution manager•Product manager•Information manager•Enterprise architect•IT Governance Manager

Micro-level in enterprise

•Project Manager•Solution architect•Systems architect•Technical architect•Developer/architect


Business and IT Dependencies

Organisationstructure

Businessservices

Businessprocess

Businessproducts

Businessinformation

Softwareapplication IT Platform

Computinginfrastructure

End-userdevices

Business level

IT level


Sample Complexity in Organisation• Defence

– 3427 information systems– 200 in inventory

management, warehouse and distribution alone!

– 3 Enterprise Systems!• Peoplesoft for HR• SAP R/3 for Finance• Mincom’s Mims for

Logistics– 3 Different platforms, each

with its own technical support and application support staff

– Several different WAN• Operational• Administration• Public

– 100,000 PC’s

• Queensland Health• 13th largest in Australia • Information Systems Portfolio

– 45 corporate systems• 1 Enterprise System delivering

Financial System Support (SAP)• 1 HR System delivering HR

support (AURION)– 4,000 local systems

• Technical Environment– 400 networked sites– 700 servers– 22,000 desktops – 28 sizable “data centres”– 250 PABXs– 290 videoconferencing sites– 150 satellite television sites


University example – stove pipe applications

• Enrollments and Billing

• Developed separately, for different people, for different purposes.

• What information do they need to share?• What are some problems if they are on different

systems (e.g. IBM mainframe and Dell server?)• How do they connect (network issues, security issues)• What are some issues related to privacy of data (e.g.

addresses, telephone numbers, ages …)

A stand-alone program. It implies an application that does not integrate with or share data or resources with other applications


Other Examples

• QUT– http://www.its.qut.edu.au/qutinfosys/– Student information system project

• Ipswich City Council– http://www.zdnet.com.au/insight/toolkit/businessapps/erp/soa/

Ipswich_City_Council_plans_IT_led_transformation/0,39028255,39215929,00.htm

– 750 application systems for 1200 employees• Many Access DB and Excel Spreadsheets• EventPro (for event management) 3 different versions

– http://www.itwire.com.au/content/view/2172/49/ – http://www.cio.com.au/pp.php?id=683917670&fp=512&fpid=128555889


Ipswich City Council

• “Ipswich City Council plans to embark on a major enterprise resource planning (ERP) implementation after signing Fujitsu Australia to help deliver a AU$37 million business transformation project. The council has signed a four year contract with the services vendor -- encompassing supply of hardware and software, provision of consulting resources and expert methods -- to assist in the business project, which includes the ERP implementation.

• Ipswich City Council information technology board chairman councillor Paul Tully said the total project budget over its lifespan would exceed AU$37 million.

• The contract builds on a series of projects between the council and Fujitsu over the past 12 months.”

http://www.zdnet.com.au/insight/toolkit/businessapps/erp/soa/

Ipswich_City_Council_plans_IT_led_transformation/0,39028255,39215929,00.htm


And in Information Management

John Zachman in the preface to Introduction to Enterprise ArchictecturesScott Barnard


Also in Information Systems ….

John Zachman in the preface to Introduction to Enterprise ArchictecturesScott Barnard


So to become relevant & ensure continued relevance

John Zachman in the preface to Introduction to Enterprise ArchitecturesScott Barnard


Enter Enterprise Architecture


Conceptual Layers of Enterprise

Strategic(mission,goals,policies)

Tactical(policies, capabilities,functions)

Operational(business channels, business services,Business processes, business info, org. resources/roles)

IT Operational(end user devices, software applications, middleware platforms,computing infrastructure, networking)


IT Service-Oriented Architecture

Externalweb services

Web servicesorchestration

Internalweb services

Company A Company B

Web serviceschoreography

Business objects

. . .

Application adapters

Legacy applications



DATA Implementation

DATAWhat

FUNCTIONHow

NETWORKWhere

e.g. Data Definition

Entity = FieldRel. = Address

e.g., Physical Data Model

Entity = Tables/Segments/etc.Rel. = Key/Pointer/etc.

e.g., Logical Data Model

Entity = Data EntityRel. = Data Relationship

e.g., Semantic Model

Entity = Business EntityRel. = Business Relationship

List of Things - Important to the Business

Entity = Class ofBusiness Thing

List of Processes -the Business Performs

Function = Class ofBusiness Process

e.g., Application Architecture

Process.= Application FunctionI/O = User Views

e.g., System Design

Process= Computer FunctionI/O =Data Elements/Sets

e.g. Program

Process= Language StatementI/O = Control Block

FUNCTIONImplementation

e.g., Business Process Model

Process = Business ProcessI/O = Business Resources

List of Locations -in which the Business Operates

Node = Major BusinessLocation

e.g., Logistics Network

Node = Business Location Link = Business Linkage

e.g., Distributed System Architecture

Node = IS FunctionLink = Line Characteristics

e.g., Technical Architecture

Node = Hardware/System SoftwareLink = Line Specifications

e.g. Network Architecture

Node = AddressesLink = Protocols

NETWORKImplementation

MOTIVATIONWhy

TIMEWhen

PEOPLEWho

e.g. Rule Specification

End = Sub-conditionMeans = Step

e.g., Rule Design

End = ConditionMeans = Action

e.g., Business Rule Model

End = Structural AssertionMeans =Action Assertion

End = Business ObjectiveMeans = Business Strategy

List of Business Goals and Strategies

Ends/Means=Major BusinessGoal/Critical Success Factor

List of Events -Significant to the Business

Time = Major Business Event

e.g., Processing Structure

Time = System EventCycle = Processing Cycle

e.g., Control Structure

Time = ExecuteCycle = Component Cycle

e.g. Timing Definition

Time = InterruptCycle = Machine Cycle

SCHEDULEImplementation

e.g., Master Schedule

Time = Business EventCycle = Business Cycle

List of Organizations -Important to the Business

People = Class of People andMajor Organizations

e.g., Work Flow Model

People = Organization UnitWork = Work Product

e.g., Human Interface Architecture

People = RoleWork = Deliverable

e.g., Presentation Architecture

People = UserWork = Screen/Device Format

e.g. Security Architecture

People = IdentityWork = Job

ORGANIZATIONImplementation

STRATEGYImplementation

e.g., Business Plan

SCOPEPlanner

SYSTEM MODELDesigner

TECHNOLOGYCONSTRAINED

MODELBuilder

DETAILEDREPRESEN-

TATIONSSubcontractor

ENTERPRISE MODEL

Owner

contextual

conceptual

logical

physical

out-of-context

FUNCTIONINGENTERPRISE

perspectives

abstractions

Zachman Framework for Enterprise Architecture


27

Designer’s View

Primitives to Work Products

Described as Single-variable

Model

The cells contain primitives

Node = Business Location Link = Business Linkage

e.g., Logistics Network

LOGICAL

ARTIFACTS

DATA

Artifact

DATA

ArtifactFUNCTION

Artifact

FUNCTION

ArtifactNETWORK

Artifact

NETWORK

Artifact

PEOPLE

Artifact

PEOPLE

ArtifactTIME

Artifact

TIME

ArtifactMOTIVATION

Artifact

MOTIVATION

Artifact

(How)(How)(What)(What) (Where)(Where) (Who)(Who) (When)(When) (Why)(Why)

Artifacts containmodel data

NETWORK

Artifact

(Where)

NETWORK

Artifact

(Where)

Logical Components

LogicalPackages Logical

Interactions

LogicalScenarios

Composite Models are the

Work Products


28

Business Concepts Example Model

Beta:ProjectName = <unspecified>Organization = <unspecified>Description = <unspecified>

Alpha:ProjectName = <unspecified>Organization = <unspecified>Description = <unspecified>

Systems Engineering:"Business Unit"Description = <unspecified>

TASC:"Architectural Description"Description = <unspecified>

Enterprise Architecture:SectionDescription = <unspecified>

Acme Business:CustomerDescription = <unspecified>

TASC:CompanyDescription = <unspecified>

<<entity>>

<<entity>>Project

+ Name : char+ Organization : char+ Description : char

persistent

<<entity>>Architectural Description

+ Description : char

persistent

<<entity>>Customer


persistent

<<entity>>Business Unit


persistent

Company


persistent

<<entity>>Section


persistent

UML Class Diagram