Transcript 2011-205-Lect-1-Introduction

INB/N 205
Enterprise Architecture
Lecture 1
Introduction to the Unit
Prof. Alistair Barros
CRICOS No. 000213J
Queensland University of Technology
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
a university for the
real world
R
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
a university for the
real world
R
Objectives of unit
• To consolidate on software application design
skills through use of integrated modelling
techniques and languages
a university for the
real world
R
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;
a university for the
real world
R
Outcomes of unit
• Undertake an enterprise architecture use case
• Communicate an architecture at different levels
for different stakeholder audiences
a university for the
real world
R
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
a university for the
real world
R
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
a university for the
real world
R
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
a university for the
real world
R
Top 10 Technology Priorities 2010
1. Business Intelligent
Applications
2. Enterprise applications
3. Legacy application
modernization
4. Networking, voice and data
communications
5. Server and storage
technologies (virtualization)
6. Security technologies
7. Service oriented architectures
8. Technical infrastructure
management
9. Documents management
10. Collaboration technologies
Source: Gartner EXP (February 2007)
a university for the
real world
R
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)
a university for the
real world
R
Top Tech Jobs 2010
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
SAP, Oracle and Peoplesoft specialists
PHP developers
C++/CORBA developers
Unix network administrators
Business analysts
Java and J2EE developers
Lotus Notes specialists
C# developers
.NET developers
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
a university for the
real world
R
Professional roles related enterprise
architecture
•
•
•
•
•
•
Macro-level in
enterprise
Business analyst
Solution manager
Product manager
Information manager
Enterprise architect
IT Governance
Manager
a university for the
real world
R
•
•
•
•
•
Micro-level in
enterprise
Project Manager
Solution architect
Systems architect
Technical architect
Developer/architect
Business and IT Dependencies
Business level
Business
services
Business
process
Organisation
structure
Business
products
Business
information
IT level
End-user
devices
a university for the
Software
application
real world
R
IT Platform
Computing
infrastructure
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
a university for the
real world
R
•
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
A stand-alone
program. It implies
an application that
does not integrate
with or share data or
resources with other
applications
• 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 university for the
real world
R
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_Coun
cil_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
a university for the
real world
R
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
a university for the
real world
R
And in Information Management
John Zachman in the preface to
Introduction to Enterprise Archictectures
Scott Barnard
a university for the
real world
R
Also in Information Systems ….
John Zachman in the preface to
Introduction to Enterprise Archictectures
Scott Barnard
a university for the
real world
R
So to become relevant & ensure continued
relevance
John Zachman in the preface to
Introduction to Enterprise Architectures
Scott Barnard
a university for the
real world
R
Enter Enterprise Architecture
a university for the
real world
R
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)
a university for the
real world
R
IT Service-Oriented Architecture
...
Company A
Company B
Web services
choreography
External
web services
Web services
orchestration
Internal
web services
Business objects
Application adapters
Legacy applications
a university for the
real world
R
a university for the
real world
R
Zachman Framework for Enterprise Architecture
abstractions
perspectives
DATA
FUNCTION
NETWORK
PEOPLE
What
How
Where
Who
MOTIVATION
Why
List of Things Important to the Business
List of Processes the Business Performs
List of Locations in which the Business Operates
List of Organizations Important to the Business
List of Events Significant to the Business
List of Business Goals
and Strategies
Entity = Class of
Business Thing
Function = Class of
Business Process
Node = Major Business
Location
People = Class of People and
Major Organizations
Time = Major Business Event
Ends/Means=Major Business
Goal/Critical Success Factor
e.g., Semantic Model
e.g., Business Process Model
e.g., Logistics Network
e.g., Work Flow Model
e.g., Master Schedule
e.g., Business Plan
Node = Business Location
Link = Business Linkage
People = Organization Unit
Work = Work Product
Time = Business Event
Cycle = Business Cycle
End = Business Objective
Means = Business Strategy
SCOPE
Planner
contextual
ENTERPRISE
MODEL
Owner
conceptual
Entity = Business Entity
Rel. = Business Relationship
Process = Business Process
I/O = Business Resources
e.g., Logical Data Model
e.g., Application Architecture
e.g., Distributed System
Architecture
e.g., Human Interface
Architecture
e.g., Processing Structure
e.g., Business Rule Model
Entity = Data Entity
Rel. = Data Relationship
Process.= Application Function
I/O = User Views
Node = IS Function
Link = Line Characteristics
People = Role
Work = Deliverable
Time = System Event
Cycle = Processing Cycle
End = Structural Assertion
Means =Action Assertion
e.g., Physical Data Model
e.g., System Design
e.g., Technical Architecture
e.g., Presentation Architecture
e.g., Control Structure
e.g., Rule Design
Entity = Tables/Segments/etc.
Rel. = Key/Pointer/etc.
Process= Computer Function
I/O =Data Elements/Sets
Node = Hardware/System
Software
Link = Line Specifications
People = User
Work = Screen/Device Format
Time = Execute
Cycle = Component Cycle
End = Condition
Means = Action
e.g. Data Definition
e.g. Program
e.g. Network Architecture
e.g. Security Architecture
e.g. Timing Definition
e.g. Rule Specification
Entity = Field
Rel. = Address
Process= Language Statement
I/O = Control Block
Node = Addresses
Link = Protocols
People = Identity
Work = Job
Time = Interrupt
Cycle = Machine Cycle
End = Sub-condition
Means = Step
SYSTEM
MODEL
Designer
logical
TECHNOLOGY
CONSTRAINED
MODEL
Builder
physical
DETAILED
REPRESENTATIONS
Subcontractor
out-of-context
FUNCTIONING
ENTERPRISE
DATA
FUNCTION
NETWORK
ORGANIZATION
SCHEDULE
STRATEGY
Implementation
Implementation
Implementation
Implementation
Implementation
Implementation
a university for the
real world
R
Primitives to Work
Products
e.g., Logistics Network
The cells contain
primitives
Node = Business Location
Link = Business Linkage
Artifacts contain
model data
NETWORK
Artifact
(Where)
Described as
Single-variable
Model
LOGICAL
ARTIFACTS
Composite Models
are the
Work Products
a university for the
real world
DATA
FUNCTION
NETWORK
PEOPLE
TIME
MOTIVATION
Artifact
Artifact
Artifact
Artifact
Artifact
Artifact
(What)
(How)
(Where)
(Who)
(When)
(Why)
Designer’s View
Logical
Components
Logical
Scenarios
Logical
Packages
Logical
Interactions
R
27
Business Concepts Example Model
<<entity>>
Customer
<<entity>>
Company
+ Description : char
+ Description : char
persistent
persistent
TASC:Company
Description = <unspecified>
UML Class Diagram
Acme Business:Customer
Description = <unspecified>
Systems Engineering:"Business Unit"
Description = <unspecified>
<<entity>>
Business Unit
Alpha:Project
Name = <unspecified>
Organization = <unspecified>
Description = <unspecified>
+ Description : char
<<entity>>
Project
+ Name : char
+ Organization : char
+ Description : char
persistent
Enterprise Architecture:Section
Description = <unspecified>
Beta:Project
Name = <unspecified>
Organization = <unspecified>
Description = <unspecified>
persistent
<<entity>>
Architectural Description
<<entity>>
Section
+ Description : char
+ Description : char
persistent
persistent
a university for the
real world
TASC:"Architectural Description"
Description = <unspecified>
R
28