download 'enterprise architecture overview' .ppt (801kb)
DESCRIPTION
TRANSCRIPT
November 2006
Enterprise Architecture Overview
November 2006 3
Our Areas of Interest
• Business – HE Functional Reference Models
• Platform Standards – Taxonomy
• Architecture Governance
• What other Universities are doing in this space
• Methods/Tools being used to achieve goals of EA
November 2006 4
Where we have come from
• Organisational change – 2005 restructure
• Legacy Technology unable to support the business going forward
• Little or No standards / methodology
• No one overseeing the “bigger picture” across the organisation
• Decentralised IT
November 2006 5
Enterprise Architecture and UoN
• Very early stages
• Major business and systems change
Organisation Restructure completed early 2006
Centralised IT
Program of Works (EPMO) within IT
Formation of roles/groups (AAG, CAB, PoW, Change Office, IT Governance Committee)
• Introduction of Groups and Processes
Start of ITIL implementation, Change Office (PMO), “formalised” Project Methodology and SDLC, Architecture Governance, Standards
• Enterprise Architecture Consultant – “EA in a box”
Light inventory across Business, Information, Applications, Technology
Provided principals, some mapping between inventories, gap analysis
Current Activities/Changes/Lack of Ownership made this difficult – “hitting a moving target”
Tool - System Architect
November 2006 6
Enterprise Architecture and UoN
• 2006 Program of Works 50+ Projects with IT underpinning them
Infrastructure (network, server consolidation, etc)
Information Management (BI, ECMS)
Business (HR, Finance, Research, Students, Facilities, etc)
Teaching / Learning (Blackboard/LOMS, Academic Support)
Operational (ID Mngt, Integration,adopt mainstream technology)
Client Services (“17000” Centralised Service Desk, MOE, ITIL rollout)
NUWays: Focussed on Business Process Improvement and EPMO
• Formed
Change Office
AAG – Architecture Advisory Group
CAB – Change Advisory Board
Project Portfolio’s – Program of Works
November 2006 7
Enterprise Architecture and UoN
• Currently only used by IT Covers PoW and operations
Reaction to the amount of project work being undertaken, realisation for EA out of PoW
• AAG Membership Enterprise Applications
Solutions Architect
Infrastructure
Security
Data Services
Client Services
Web Group
(Note: No Business Representation)
• Bottom up approach to EA – driven by IT
November 2006 8
Challenges Experienced
• Current IT Inventory = 100+ Main Applications ~65% in-house developed – mainly “gap fillers” around the enterprise applications
Current upgrades will supersede some but still expected to be significant
Mixed blend of technology:
ERP, disparate systems
old and new technology
“islands of data” and “the spider web” of integration (point to point)
• Time / Resources / Size of Work for Enterprise Architecture
• Standards / Guidelines
• Expectations of Business and IT
• Implementation, Acceptance and Understanding of Enterprise Architecture within IT
• Seen as a hold up for existing processes / projects
November 2006 9
Our Enterprise Architecture Framework
Information Architecture
Application Architecture
Business Architecture
Technology Architecture
Business Model
• Business Direction
• Stakeholders
• Functions
• Information
• Data Model
• Information Flows
• Databases
• Applications
• Application Integration
• Application Technology
• Server Technology
• Network / Communications
• Platforms / Operating Systems
• Database Systems
• Security Technologies
• etc.
November 2006 10
Architecture Development Process
Cu
rrent M
od
el
T1
T2
Targ
et Mo
del
ApplicationInformation
Technical
High
Med
ium
Detai
led
Business
Business StrategyIT Strategy
Policies
Enterprise Architecture Principles
Technology Standards and Guidelines
Business and IT Strategies ensure that architectures align
with business needs and priorities
Architecture layers provide linkage between business models
and technical architecture
Principles give high level direction to enable decision making
High-level context diagrams present broader picture
Subject area models provide the linkage between the global
context and projects
Detailed models describe the subject matter at a project level
Standards and guidelines provide specific direction on implementing
architectures
Transition Plans provide the implementation “roadmap”
November 2006 11
UoN Service Delivery Model / Value ChainGet
New BusinessDevelop services
Getpaid
INVOICESTUDENTS
ATTRACTSTUDENTS
SCOPERESEARCHPROJECT
Student DESIGNPROGRAM
Deliverservices
TRANSFERLEARNING
ASSESSLEARNING
CONDUCT AND PUBLISH
RESEARCH
ResearchMARKET
RESEARCHPROJECT
PROCESSFUNDING
ENROLSTUDENTS
PROCESSPAYMENT or
FUNDINGVALIDATELEARNING
ADMITSTUDENTS
FINANCEMANAGEMENT
ACADEMICREGISTRAR
HRMANAGEMENT
CORPORATEINFORMATION
ITMANAGEMENT
LEGALCOUNSEL
FACILITIESMANAGEMENTS
up
po
rt s
ervi
ces
GRADUATESTUDIES
INTERNATIONALRESEARCHSERVICES
MARKETING/ PUBLIC
RELATIONS
Researchoutputs, papers
Degree
NUWAYS Project
November 2006 12
Student Service Delivery Model
(2) exams: includes all forms of evaluation (lab, tutorial, course work)(1) learning includes: courses, lab, tutorial, placements
Get New Business
Develop services
Getpaid
Deliverservices
ATTRACTSTUDENTS
DESIGNPROGRAM
TRANSFERLEARNING
ASSESSLEARNING
ENROLSTUDENTS
INVOICESTUDENTS
PROCESSPAYMENT or
FUNDING
Identify newprogram need
Evaluateprogram
(program review)
Providescholarships
Set up/verifyProgram
Set up/verifycourses
Set up/verifytimetable(lectures)
Set up/verifytimetable(tutorials)
Design exams (2)
Organiseexams
Conductexams
Markexams
Validate and publish results
Designlearning(1)
Deliverlearning
Set up/verifycharges
Publish feecharges
Configure feesand rules(Nustar)
Run tuitioncalculation
process (Nustar)
Receivepayment
Apply payment against
student debt
VALIDATEDEGREE
Verify degreerequirements
met
Redesignprogram
Design program
Gradepublished
Degreeconferred
Learning(1)
deliveredPaymentsreceived
Bill sentProgram/courses
/timetablespublished
Program revised,new program
outlined
ADMITSTUDENTS
Set/verifyadmission rules
Applyadmission rules
Offer/No Offerproduced
Publishprogram/courses
Run billingprocess
Promote university
Provide program information
Understand target markets
Events hosted,materials
distributed
Makeoffer
Conductceremony
Organise learning
Organiseceremony
Reconcile forcompliance
November 2006 13
Architecture Governance Model
IT Governance Committee
Senior Executive level
IT Policy, Standards & Architecture Review
IT Management level
Subject matter expertsArchitecture
Advisory
Group
IT service
delivery teams
IT development
teams
Adhoc
working groups
Vendors and
consultants
StandardsPolicies
Guidelines
ExceptionsGranted
UoNEA
Req
uest
for
Exc
eptio
n
Pro
ject
Arc
hite
ctur
e
Updates
UpdatesUpdates
Business / Projects
Arc
hite
ctur
e A
dvic
e
Rej
ecte
d E
xcep
tion,
Rec
omm
enda
tion
AAG
November 2006 14
Architecture Principles
Information Architecture
Application Architecture
Business Architecture
Technology Architecture
Application Architecture PrinciplesCommon Use ApplicationsEase of UseRe-use Before BuyingBuy Before BuildingMinimise Package ModificationsComponent-based ArchitectureChannel and Device IndependenceIntegration Services IndependenceInterfaces to External EnvironmentAdopt Web-based Technologies
Information Architecture PrinciplesSingle Customer Identification
Consistent Definition of ProductsIdentification of Customer Contact Points
Data Accessible Across University of NewcastleTimely Information
Reuse DataUse One Data Master
Single Algorithm for Each Business MeasureData Security
Common Vocabulary and Data DefinitionsCentralised Analytical Data Repositories
Technology Architecture Principles
Technical Environment for the FutureUse Proven TechnologiesDisaster Recovery / Business ContinuityInteroperabilityControl Technical DiversityA Single Integrated WAN based on IP Protocol
Consistent Office EnvironmentEnsure Enterprise-Wide Integration of IT SecurityNon-RepudiationDeploy a Perimeter Layer Protecting Internal Network AccessSecurity Infrastructure to Support Distributed UsersUse Portals to Provide Security at a Higher Level
November 2006 15
Architecture Services for Projects
PROJECT PATH
1. Preliminary consultation
BusinessCase
FunctionalSpecification
SolutionOptions
Technical Design
Specification
Business RequirementsSpecification
Business idea
Preliminary advice re: solution options &
architectural implications
Enterprise Architecture
Model
Enterprise Architecture
Principles
3. Detailed architectural analysis
(environmental scanning; gap analysis;
assessment of options etc)
Technology trends
Project Charter
Implementation of new/changed
architecture components (those not project specific)
Ente
rpris
e A
rchi
tect
Solu
tions
Arc
hite
ctPr
ojec
t M
anag
emen
t
Business trends and strategies
Ongoing advice to refine
project shape
2. Project planning
advice
Advice regarding implementation (eg cost/time) of
technology solutions
New/changed architectural components
required due to external factors
Recommended technology
solution
PTO
1.Discovery 2. Design
New/changedarchitectural components
required by project
November 2006 16
Architecture Services for Projects
PROJECT PATH
5. Architectural issues
management
Enterprise Architecture
Model
Enterprise Architecture
Principles
Ente
rpris
e A
rchi
tect
Solu
tions
Arc
hite
ctPr
ojec
t Man
agem
ent
Implementation of new/changed architecture components
(project specific)
Resolution of architectural
issues
Escalation of architectural
issues
IssuesRegister
Technical Design
Specification
4. Architectural compliance
review
Cont’d
Incorporate new/changed elements
into the Enterprise Architecture Model
Go Live
2. Design cont’d 3. Deployment
November 2006 17
Technology Architecture Components
November 2006 18
Where to from Now?
• Adoption of Use of Enterprise Architecture outside of IT
• Establish an EA group with a business focus
• Learn and improve
• Work collaboratively
• Continual Development of Enterprise Architecture with alignment to the strategic direction of UoN
• Become proactive rather than reactive
November 2006 19
Thankyou
• David Hall
Program Director – Project Office
• Stephen Bosworth
Enterprise Applications
•Carey Steller
Solutions Architect