Upload
niranjan-selvadurai
View
127
Download
1
Tags:
Embed Size (px)
Citation preview
EAO-IN-CONFIDENCE
Adopting an Enterprise Architecture Reference Framework
Enterprise Architecture Office
Work in Progress Final
01 August 2011
Version 0.3
This document is for distribution within the Enterprise Architecture Office (EAO) only and must be handled as In-Confidence. It contains draft strategies and concepts that have not undergone socialisation or consultation and must not be distributed outside
the EAO.
EAO-IN-CONFIDENCE
Adopting an Enterprise Architecture Reference Framework Enterprise Architecture Office
Page 2 of 16 EAO-IN-CONFIDENCE DRAFT Version 0.1
Document Purpose
This document outlines the position proposed by the Enterprise Architecture Office (EAO), in relation to the need, selection, application and evolution of a common Enterprise Architecture Reference Framework within DEEWR.
Document Users
This document is for the use of the enterprise Architecture team, all EAO clients and stakeholders.
Definitions
TERM DEFINITION
Artefact Reusable items that support the enterprise architecture practice such as principles, models and standards.
Business Domain
Business Scenario
EAO Enterprise Architecture Office
TOGAF The Open Group Architecture Framework
Document Control
VERSION DATE CHANGE DESCRIPTION AUTHOR
0.01 DRAFT 17 June 2011 Initial draft under development Niranjan Selvadurai
0.02 DRAFT 27 June 2011 Review edits Paula Halstead, Niranjan Selvadurai
0.02 DRAFT 01 August 2011 Revised after EAO Peer Review by Vudaya Vasiraju
Niranjan Selvadurai
0.XX DRAFT Dd month yyyy Technical Writer formal review First Surname
NOTE: This is a controlled document in its electronic form only. Paper copies of this document are not controlled and should be checked against the electronic version prior to use. © 2009 Commonwealth of Australia. This work is copyright. Apart from any use permitted under the Australian Copyright Act, 1968,
EAO-IN-CONFIDENCE
Adopting an Enterprise Architecture Reference Framework Enterprise Architecture Office
Page 3 of 16 EAO-IN-CONFIDENCE DRAFT Version 0.1
no part may be reproduced by any process without the permission of the Department of Education, Employment and Workplace Relations.
Document Sign Off
This document has been endorsed by:
Name: Susan Monkley
Position: Group Manager, Technology Solutions Group
Signature: Date:
This document has been approved by:
Name:
Position: Lead Architect
Signature: Date:
Name: Jeff Kitchener
Position: Enterprise Solutions Architect
Signature: Date:
Name: Chris Mewett
Position: Enterprise Security Architect
Signature: Date:
Name: Niranjan Selvadurai
Position: Enterprise Business Architect
Signature: Date:
Name: Vudaya Vasiraju
Position: Enterprise Applications Architect
Signature: Date:
EAO-IN-CONFIDENCE
Adopting an Enterprise Architecture Reference Framework Enterprise Architecture Office
Page 4 of 16 EAO-IN-CONFIDENCE DRAFT Version 0.1
Contents
1 Introduction ............................................................................................................................ 5
2 Business value of a Reference Framework............................................................................ 5
3 Benefits of a Reference Framework ...................................................................................... 6 3.1 For effective communication .................................................................................... 6
3.2 For understanding the magnitude of change ............................................................. 6
3.3 For managing complexity ......................................................................................... 6
3.4 For promoting a uniform approach ........................................................................... 6
4 Expectations of a Reference Framework............................................................................... 7
5 Evaluation and Selection Approach....................................................................................... 7
6 DEEWR Enterprise Architecture Reference Framework ....................................................... 8 6.1 Overview................................................................................................................. 8
6.2 Reference Models .................................................................................................... 9
6.2.1 Conceptual Model ............................................................................................ 9
6.2.2 Business Reference Model (BRM): ..................................................................... 9
6.2.3 Service Reference Model (SRM):........................................................................ 9
6.2.4 Technology Reference Model (TRM): ............................................................... 10
6.2.5 Information Reference Model (IRM): ............................................................... 10
7 Concluding Summary ........................................................................................................... 10
8 Appendix A – DEEWR Business Reference Model Diagram................................................ 12
9 Appendix B – DEEWR Service Reference Model Diagram .................................................. 13
10 Appendix C – DEEWR Technology Reference Model Diagram ........................................... 14
11 Appendix D – DEEWR Information Reference Model Diagram .......................................... 15
12 Appendix E – Conceptual Model Example (Enterprise Architecture Office)...................... 16
EAO-IN-CONFIDENCE
Adopting an Enterprise Architecture Reference Framework Enterprise Architecture Office
Page 5 of 16 EAO-IN-CONFIDENCE DRAFT Version 0.1
1 Introduction
The function of an Enterprise Architecture Reference Framework (EARF) is to provide a structured approach to define business information. By adopting an EARF, artefacts used to construct and evolve the enterprise architecture can be developed, arranged and presented logically. This document describes the approach taken by the EAO to develop DEEWR’s EARF. In developing the DEEWR EARF, the EAO posed the following questions:
What approach fits our needs best? What constructs can be borrowed from other approaches?
Do we need to develop our own constructs to supplement the framework? This document outlines the core elements of the EARF for DEEWR. It emphasises that the baseline frameworks adopted need to be customised, enriched and evolved to meet the changing requirements of an improving level of organisational maturity.
2 Business value of a Reference Framework
A reference framework provides a starting point for defining the right business information through a structured approach. It enables the definition of a problem context from multiple dimensions such as business, information and technology. By following a consistent and accurate approach to scope definition the right business information necessary for a strategic change initiative can be identified. Without the right business information, it is challenging to get the optimal delivery timing, minimum cost to the tax payer and a result of required quality. All these contribute towards the delivery of a right government outcome as illustrated in Diagram 1 below.
Diagram 1 – Business value through right business information
EAO-IN-CONFIDENCE
Adopting an Enterprise Architecture Reference Framework Enterprise Architecture Office
Page 6 of 16 EAO-IN-CONFIDENCE DRAFT Version 0.1
3 Benefits of a Reference Framework
An EARF adds significant value to the development, implementation and evolution of architectures supporting DEEWR business goals. It provides the foundation for sound, repeatable, improvable, measurable, evidence based and reportable Information and Communications Technology (ICT) solutions within DEEWR. The benefits broadly fall into the four areas outlined below.
3.1 Effective communication
Senior management and business buy-in are critical to the success of an enterprise architecture practice. It is essential that architectural view points are communicated effectively using a consistent and logical structure for classifying and organising business and technology concepts. An EARF not only provides a vehicle for communicating a clear message to the stakeholder community but also gives a platform for generating discussion, consensus building and understanding of DEEWR business. The reference framework also promotes consistency of language and ensures all participants have a common definition of content, scope and purpose of the architecture .
3.2 Understanding the magnitude of change
Moving from a current state to a desired target state requires planned organisational change. Enterprise Architecture identifies opportunities to drive change involving people, processes, IT solutions, financial resources and organisational structure. An EARF provides a platform for clarifying the magnitude of the change required and increasing DEEWR’s ability to manage change through clear scope and impact definition.
3.3 Managing complexity
Enterprise architecture encompasses multiple dimensions and needs to be viewed from several perspectives (eg: business, information, technology). When defining a solution there is a need to reconcile and unify different architectural view points. An Enterprise Architecture practice needs to have tools that provide the ability to zoom in and zoom out at different levels of abstraction when discussing complex scenarios. The EARF facilitates conceptualisation by including hierarchically structured reference models. Complex scenarios can be viewed from different levels of abstraction. It allows users to take in or hide details, identify patterns and then present those patterns in a clear and coherent manner. This provides an effective means of managing complexity.
3.4 Promoting a uniform approach
An EARF provides a common language and structure to describe and understand business and technical scenarios. Further, the top-down nature of the framework allows users to work at multiple levels of abstraction at a given time. This ensures that the artefacts produced are standardised and represent the architectures and uniform approaches used to develop solutions resulting from those architectures.
EAO-IN-CONFIDENCE
Adopting an Enterprise Architecture Reference Framework Enterprise Architecture Office
Page 7 of 16 EAO-IN-CONFIDENCE DRAFT Version 0.1
4 Expectations of a Reference Framework
The following criteria were considered when defining the EARF for DEEWR:
ability to provide consistency and structure
ability to advocate top-down approach ability to support multiple levels of abstraction
ability to define the architecture development process
ability to describe artefacts produced ability promote cross-agency collaboration and delivery of solutions
intuitiveness and ease of application.
5 Evaluation and Selection Approach
The key business driver for an EARF was the need to choose an appropriate framework early and use it to guide the development and evolution of DEEWR’s enterprise architecture. Various frameworks were considered and analysed to ascertain their fit with DEEWR and suitability for use, including:
The Australian Government Architecture (AGA) containing an number of reference models
Queensland government models Zachman Framework The Open Group Architecture Framework (TOGAF).
A preliminary evaluation determined a single framework was unlikely to meet all the expectations identified. The DEEWR EARF, outlined in Section 6, was arrived at based on the following approach:
1. Choose an existing framework that is considered a good fit for DEEWR business needs. 2. Identify the limitations of this framework by applying it to business scenarios. 3. Ascertain the options to address those limitations 4. Enrich the initial baseline framework by borrowing aspects from other frameworks. 5. Where no adequate framework exists develop in-house constructs to supplement the
framework. 6. Continue testing and improving against business scenarios.
EAO-IN-CONFIDENCE
Adopting an Enterprise Architecture Reference Framework Enterprise Architecture Office
Page 8 of 16 EAO-IN-CONFIDENCE DRAFT Version 0.1
6 DEEWR Enterprise Architecture Reference Framework
Diagram 2 - DEEWR Enterprise Architecture Reference Framework (DEEWR EARF)
6.1 Overview
As a result of the analysis, it was concluded a customised EARF, using an existing reference framework baseline, would provide the best business outcome for DEEWR. To enable greater opportunity for business to work cohesively with other government agencies, the Australian Government Architecture (AGA) was selected as the baseline reference framework for the DEEWR EARF.
EAO-IN-CONFIDENCE
Adopting an Enterprise Architecture Reference Framework Enterprise Architecture Office
Page 9 of 16 EAO-IN-CONFIDENCE DRAFT Version 0.1
However, it was recognised not all aspects of the AGA reference models could be readily applied to the DEEWR environment. The AGA Reference Models, while providing a fair level of contextual understanding across business, service and technology, did not enable clarity of understanding at the conceptual level when applied to a business scenario. This is primarily because the AGA Reference Models are focused on whole-of-government whereas the DEEWR EARF would be predominantly internally focused. The differing focus challenged the intuitive and easy to use nature of the DEEWR EARF that was sought. To improve this, the Zachman Framework scope level was adopted and adjusted to suit DEEWR-specific needs for developing conceptual models. This combination resulted in more intuitive and user friendly DEEWR EARF that enabled the conceptual model to inform the development of business, service and technical views for a business scenario whilst maintaining whole-of-government relevance based on AGA models. Where necessary, the AGA models are customised to meet the specific internal needs of the DEEWR. As there is no federal government or industry Information Reference Model (IRM) appropriate for DEEWR the IRM construct of the EARF is being developed in-house. Reference Models
The DEEWR EARF initially focuses on five reference models, each with its own business purpose:
6.1.1 Conceptual Model
A conceptual model facilitates a clear understanding of the role and scope of a business domain or scenario being studied. The Zachman Framework is the baseline for developing conceptual models within DEEWR due to its intuitiveness and the ease of application.
The conceptual model attempts to answer the questions:
Why? – Value Proposition, Motivation What? – Structure, Domains
How? – Functions, Workflow
Who? – People, Interactions, competencies Where? - Locations
When? – Timeline, Scheduling
6.1.2 Business Reference Model (BRM):
The BRM is a taxonomy that identifies the lines of business and the business functions involving DEEWR. It provides a view of how DEEWR operates on an ongoing basis by facilitating services to citizens, individuals, business and other organisations.
DEEWR’s Business Reference Model (DEEWR BRM) is based on the Australian Government Architecture Business Reference Model (AGA BRM), with appropriate adjustment for DEEWR-specific needs. Any AGA lines of business outside the scope of DEEWR are excluded from the model. Further, functions deemed as core internal competencies are included to enrich the baseline DEEWR model.
6.1.3 Service Reference Model (SRM):
The SRM is a business or performance driven functional framework that classifies service components with respect to how they support business and/or perform objectives. A service is
EAO-IN-CONFIDENCE
Adopting an Enterprise Architecture Reference Framework Enterprise Architecture Office
Page 10 of 16 EAO-IN-CONFIDENCE DRAFT Version 0.1
viewed as an output for a particular focus area which requires the co-ordination of people, processes and systems.
DEEWR has selected the AGA SRM for the mapping and classification of services. No changes have been made to tailor this model to DEEWR specific needs at this time. This may change as DEEWR’s Enterprise Architecture capability matures.
6.1.4 Technology Reference Model (TRM):
This is a component driven, technical framework categorising the standards and technologies which support and enable the delivery of service components and capabilities.
Three candidate models were reviewed to determine their suitability to DEEWR. They were AGA TRM, TOGAF TRM and the Queensland Government Technology Framework. AGA TRM is the preferred model for DEEWR as it provides a whole-of-government focus and enables cross-agency collaboration and delivery of solutions. No changes have been made to tailor this model to DEEWR-specific needs at this time. This can change as DEEWR’s Enterprise Architecture capability matures.
6.1.5 Information Reference Model (IRM):
This is a hierarchical framework which provides an appreciation of the information concepts that support DEEWR.
There are no federal government or industry information reference models suitable for DEEWR business. The DEEWR IRM is being developed in-house. It is based on foundation information concepts appropriate to DEEWR, which were ascertained during the SIMR sponsored Information Management Project conducted in early 2010.
The IRM encapsulates the information concepts of DEEWR and can be used to map information to application systems, information assets and business processes.
7 Concluding Summary
i. DEEWR benefits from adopting an Enterprise Architecture Reference Framework (EARF).
ii. A single framework does not meet all the needs of DEEWR.
iii. The logical way forward is to continue to enrich the DEEWR EARF by borrowing aspects from other frameworks as appropriate to DEEWR’s business needs. If necessary, in-house constructs can be introduced to supplement the framework.
iv. The DEEWR EARF uses the following baseline models:
a. The Australian Government Architecture (AGA) reference models for the initial baseline framework of the DEEWR EARF. This provides DEEWR with greater business opportunity to work cohesively with other government agencies and to offer suitable architectures for use across government.
b. The Zachman Framework scope level, for the initial baseline framework of Contextual Models within the DEEWR EARF, because it provides greater intuitive appeal when addressing business scenarios.
EAO-IN-CONFIDENCE
Adopting an Enterprise Architecture Reference Framework Enterprise Architecture Office
Page 11 of 16 EAO-IN-CONFIDENCE DRAFT Version 0.1
v. Contextual Models, Business, Service and Technical Contexts for a business domain or scenario are defined using the DEEWR EARF.
vi. The information context for a business domain or scenario is defined using an Information Reference Model (IRM) developed in-house. This is because there is no Federal Government or industry Information Reference Model (IRM) appropriate for DEEWR.
vii. The DEEWR EARF will evolve and be enriched as the Enterprise Architecture practice in DEEWR matures and the framework is applied to business domains and scenarios.
viii. The Enterprise Architecture Office (EAO) retains the custodianship of the DEEWR EARF.
EAO-IN-CONFIDENCE Adopting an Enterprise Architecture Reference Framework Enterprise Architecture Office
Page 12 of 16 EAO-IN-CONFIDENCE DRAFT Version 0.1
8 Appendix A – DEEWR Business Reference Model Diagram
DEEWR Business Reference Model Diagram
Service Paths
Government Financial
Assistance
Information &
Knowledge
Exchange
Regulatory
Compliance &
Enforcement
Government Grants
Payment to Citizens
Rebates
Scholarships
Subsidies
Tax Incentives
ConcessionsAdvising &
Consulting
Analysis and
Reporting
Research &
Development
Knowledge
Presentation
Discussion Forums
Information &
Knowledge
Dissemination
Payments to States,
Territories & Local
Governments
Project/Competitive
Grants
State Loans
Government
Regulations
Inspection &
Aditing
Regulatory
Standards/
Reporting
Guidelines
Service for Citizens
Education & Training Employment Community Services Indigenous Affairs
Curriculum
Development
Early Childhood
Education
School Education
Tertiary Education
Vocational
Education
Overseas Skills
Recognition
Human Resource
Development
Industry Awards &
Conditions
Workplace
Agreements
Labour Markets
Community
Support
Financial
Assistance
Indigenous
Welfare
Indigenous
Health Services
Indigenous
Enterprise
Development
Services Support
GovernancePlanning &
Budgeting
Revenue Collection
Public Affairs
Management of Government Resources
Legislative
Drafting
Intergovernmental
Relations
Public
Administration
Regulation
Development
Customer Service
Government
Campaigns
Government Media
Public
Consultation
Public Relations
Debt Collection
Budget
Formulation
Enterprise
Architecture
Business
Improvement
Legal Advice
Outcomes &
Outputs
Strategic Planning
Procurement
Planning
Workforce
Planning
Information &
Knowledge
Management
Knowledge
Management
Information Security
Management
Document &
Records
Management
Business
Management
Business Change
Management
Business Services
& Process
Management
Business Risk &
Mitigation
Business Reporting
Business
Relationship
Management
Business
Partnership
Management
Administrative
Management
Facilities, Fleet &
Equipment
Management
Help Desk Services
Physical Security
Management
Financial
Management
Accounting
Financial
Reporting
Asset & Liability
Management
Management of
Public Monies
Payments
Procurement
Human Resource
Management
Employee
Performance
Management
Recruitment
Training &
Development
Remuneration
ManagementICT Management
ICT Operations & Infrastructure
Management
ICT Service Mnagement
ICT Solution Delivery & Maintenance
The DEEWR Business Reference Model is a taxanomy facilitating a functional view of DEEWR, including its internal
opearations and its services for citizens, individuals, businesses, and other organisations. It is developed and maintained
by the Enterprise Architecture Office and is based on Australian Government Architecture Business Reference Model.
Business Area
Business Line
Business Function
EAO-IN-CONFIDENCE
Adopting an Enterprise Architecture Reference Framework Enterprise Architecture Office
Page 13 of 16 EAO-IN-CONFIDENCE DRAFT Version 0.1
9 Appendix B – DEEWR SERVICE REFERENCE MODEL DIAGRAM
Customer Services
Customer Relationship
Management
Call Centre Management
Customer Analytics
Sales and Marketing
Product Management
Brand Management
Customer/Account Management
Contact and Profile Management
Partner Relationship Management
Customer Feedback
Surveys
Customer Preferences
Subscriptions
Alerts and Notifications
Customer Initiated
Assistance
Online Help
Online Tutorials
Self-Service
Reservations/Registration
Multi-Lingual Support
Assistance Request
Scheduling
Business Management Services
Management of Process
Configuration Management
Requirements Management
Program/Project Management
Governance/Policy Management
Quality Management
Business Rule Management
Risk Management
Organisational
Management
Workgroup/Groupware
Network Management
Investment Management
Strategic Planning and
Management
Portfolio Management
Performance Management
Supply Chain
Management
Procurement
Sourcing Management
Inventory Management
Catalogue Management
Ordering/Purchasing
Invoice/Requisition Tracking and
Approval
Storefront/Shopping Cart
Warehouse Management
Returns Management
Logistics and Transportation
Digital Asset Services
Content Management
Content Authoring
Content Review and Approval
Tagging and Aggregation
Content Publishing and Delivery
Syndication Management
Document Management
Document Imaging and OCR
Document Referencing
Document Revisions
Library/Storage
Document Review and Approval
Document Conversion
Indexing
ClassificationKnowledge Management
Information Retrieval
Information Mapping/Taxonomy
Information Sharing
Categorisation
Knowledge Engineering
Knowledge Capture
Knowledge Distribution and Delivery
Smart Documents
Records Management
Record Linking/Association
Document Classification
Document Retirement
Digital Rights Management
Support Services
Security Management
Identification and Authentication
Access Control
Cryptography
Digital Signature Management
Intrusion Prevention
Intrusion Detection
Incident Response
Audit Trail Capture and Analysis
Certification and Accreditation
ISM Management and Reporting
Virus Protection
Forms Management
Forms Creation
Forms Modification
Communication
Real Time/Chat
Instant Messaging
Audio Conferencing
Video Conferencing
Event/News Management
Community Management
Computer/Telephony Integration
Voice Communications
Systems Management
Licence Management
Remote Systems Control
System Resource Monitoring
Software Distribution
Issue Tracking
Collaboration
Threaded Discussions
Document Library
Shared Calendaring
Task Management
SearchQuery
Precision/Recall Ranking
Classification
Pattern Matching
Business Analytical Services
Visualisation
Graphing/Charting
Imagery
Multimedia
Mapping/Geospatial/Elevation/GPS
Computer Aided Design
Business Intelligence
Demand Forecasting/Management
Balanced Scorecard
Decision Support and Planning
Employment
Process Automation Services
Routing and Scheduling
Inbound Correspondence
Management
Outbound Correspondence
Management
Tracking and Workflow
Process Tracking
Case Management
Conflict Resolution
Analysis and Statistics
Mathematical
Structural/Thermal
Radiological
Forensics
Knowledge Discovery
Data Mining
Modelling
Simulation
Reporting
Ad Hoc
Standardised/Canned
OLAP
Back Office Services
Data Management
Data Exchange
Data Mart
Data Warehouse
Meta Data Management
Data Cleansing
Extraction and Transformation
Loading and Archiving
Data Recovery
Data Classification
Human Resources
Recruiting
Resume Management
Career Development and Retention
Time Reporting
Awards Management
Benefit Management
Retirement Management
Personnel Administration
Education/Training
Health and Safety
Travel ManagementFinancial Management
Billing and Accounting
Credit/Charge
Expense Management
Payroll
Payment/Settlement
Debt Collection
Revenue Management
Internal Controls
Auditing
Activity-Based Management
Currency Translation
Development &
Integration
Legacy Integration
Enterprise Application Integration
Data Integration
Instrumentation and Testing
Software Development
Asset/Materials
Management
Property/Asset Management
Asset Cataloguing/Identification
Asset Transfer, Allocation and
Maintenance
Facilities Management
Computers/Automation Management
Human Capital/
Workforce Management
Resource Planning and Allocation
Skills Management
Workforce Directory/Locator
Team/Organisation Management
Contingent Workforce Management
Workforce Acquisition/Optimisation
Service Domain
Service Type
Service Component
The DEEWR Service Reference Model (SRM) is a business and performance-
driven, functional framework that classifies Service Components with respect
to how they support business and/or performance objectives. The SRM is
structured hierarchically, across 6 service domains that, independent of the
business functions, can proviide a foundation for the sharing and reuse of
DEEWR applications, application capabilities, components, and business
services. It is based on the Australian Government Architecure Service
Reference model, and is maintained by the Enterprise Architecure office.
EAO-IN-CONFIDENCE
Adopting an Enterprise Architecture Reference Framework Enterprise Architecture Office
Page 14 of 16 EAO-IN-CONFIDENCE DRAFT Version 0.1
10 Appendix C – DEEWR Technology Reference Model Diagram DEEWR Technology Reference Model Diagram
Component Framework
SecurityPresentation/
Interface
Data Interchange
Business Logic
Service Interface and Integration
Service Platform and Infrastructure
Certificates/Digital
Signature
Supporting
Security Services
Platform
Independent
Platform
Dependent
Data Exchange
Static Display
Content Redering
Dynamic Server-
Side Display
Wireless/Mobile/
Voice
Integration
Middleware
Enterprise
Application
Integration
Interoperability
Data Format/
Classification
Data Types/
Validation
Data
transformation
Interface
Service Discovery
Service
Description/
Interface
Access Channels Delivery Channels Service
RequirementsService Transport
Web Browser
Wireless/PDA
Collaboration/
Communications
Other Electronic
Channels
Internet
Intranet
Peer to Peer (P2P)
Extranet
Legislative/
Compliance
Authentication/
Single Sign-on
(SSO)
Supporting
Network
Services
Service
Transport
Virtual Private
Network (VPN)
Hosting
Platform
Independent
Platform
Dependent
Wireless/
Mobile
Support Platforms Delivery
Systems
Web Servers
Application
Servers
Portal Servers
Media Servers
Database/
Storage
Database
Storage
Software
Engineering
Integrated
Development
Environment
(IDE)
Software
Configuration
Management
Test
Management
Modelling
Hardware/
Infrastructure
Servers/
Computers
Embedded
Technology
Devices
Peripherals
Wide Area Network
(WAN)
Local Area
Network (LAN)
Network Devices/
Standards
Video
Data Management
Database
Connectivity
Reporting and
Analysis
Service Access and Delivery
Service Area
Service Category
Service Standard
The DEEWR Technology Reference Model is acomponent driven framework categorising the
standards and technologies to support and enable the delivery of service components and
capabilities. It is based on the Australian Government Architecture Technology Reference Model,
and is maintained by the Enterprise Architecture Office.
EAO-IN-CONFIDENCE Adopting an Enterprise Architecture Reference Framework Enterprise Architecture Office
Page 15 of 16 EAO-IN-CONFIDENCE DRAFT Version 0.1
11 Appendix D – DEEWR Information Reference Model Diagram
EVENT
COMMUNICATION
Campaign Communication
Enquiry
Complaint
Message
Information exchange
COMMUNICATION CLASS TYPE
Internal
Minsterial
Executive
BUSINESS ACTIVITY
Transaction
Meeting
Reporting
Monetary (eg.
Payment)
Non Monetary (eg. Record maintenance)
TRANSACTION TYPE
CITIZEN CENTRIC DIRECTION
AGENDA
PROGRAMME
MEASUREMENT
RATING SCALE
PERFORMANCE
INDICATOR
BENCHMARK TYPE
International
National
State level
OUTCOMEBENCHMARK/ COMPARISON
CITIZEN SERVICE
CITIZEN SERVICE ROLE
Education
Employment
Indigenous Affairs
Justice
EDUCATION SERVICE ROLE
Early Childhood Education
School Education
Tertiary Education
Vocational Training
School- Workforce Transition
Curriculum Development
Overseas Skills Recognition
EDUCATION
SERVICE
ATTAINMENT
ENROLLMENT
JUSTICE SERVICE
LEGAL ADVICE
INDIGENOUS AFFAIRS SERVICE
GOVERNMENT RESOURCE
EQUIPMENT
INVENTORY
PROPERTYINFORMATION
Hardware
Software
Application System
DOCUMENT
IT RESOURCE
Document
IT Asset
Equipment
Reported Information
Property
GOVERNMENT RESOURCE
TYPE
LOCATION
ADDRESS
Postal Address
Electronic Address
GEOGRAPHIC
AREA
GEOGRAPHIC AREA ROLE
Country
State
Region
Electorate
Local Govt Area
Statistical Local Area
BUSINESS PROCESS
COMMUNITY DIRECTION INSTRUMENT TYPE
Policy
Regulation
Programme
Target
Strategy
Agenda
Schedule
Campaign
COMMUNITY DIRECTION
INSTRUMENT
Individual Assistance
Organisational Grants
Service Provider Funding
PROGRAMME PURPOSE
POLICY
EVIDENCE
BUSINESS RULE
CAMPAIGN
RATING SCALE ROLE
Risk
Compliance
Performance
Satisfaction
UNIT OF MEASURE
PARTY
INDIVIDUAL ORGISATION
Pre- Schooler
School Student
Tertiary Student
Apprentice
Jobseeker
Employee
Retiree
Subject Expert
INDIVIDUAL ROLE
GOVERNMENT AGENCY TYPE
Commonwealth
State
CAC/ FMA act
SOCIAL GROUP
ORGANISATION UNIT
Business Group
Department
Committee
Service Provider
Government Agency
Family
Employer
Union
Lobby Group
NGO
ORGANISATION ROLE
SERVICE PROVIDER ROLE
Vendor
Job Service Provider
Insolvancy Practitioner
Childcare Provider
School
Tertiary Institute
TAFE College
INDIVIDUAL SKILL
SOCIAL GROUP CLASS
Homeless Indigenous
Mental Disability
Physical Disability
Low Income
Refugee
Unemployed
Youth Mature Aged
Ex- Offenders
CALD
Citizen
SERVICE AGREEMENT
CURRICULUM
Indigenous Welfare
Indigenous Health Services
Indigenous Enterprise Development
INDIGENOUS AFFAIRS SERVICE ROLE
EMPLOYMENT SERVICE ROLE
Human Resource Development
Industrial Awards & Conditions
Labour Markets
Workplace Agreements
EMPOLYMENT SERVICE
INDUSTIAL
INSTRUMENT
JOB WAGE OUTCOME
INDUSTRY
TYPE
Legal Aid
Juvenile Justice Civil Law
JUSTICE SERVICE ROLE
The DEEWR Information Reference
Model is a taxonomy facilitating a
information view of DEEWR. It is
being developed in-house, based on
foundation information concepts
appropriate for DEEWR. It is
developed and is maintained by the
Enterprise Architecture Office.
EAO-IN-CONFIDENCE Adopting an Enterprise Architecture Reference Framework Enterprise Architecture Office
Page 16 of 16 EAO-IN-CONFIDENCE DRAFT Version 0.1
12 Appendix E – Conceptual Model Example (Enterprise Architecture Office)
Conceptual Model Example – Enterprise Architecture Office
ConceptualisationRequired
Competencies
Communication
Enterprise Perspective
Consensus buildingFacilitationLeadership
Logic
Innovation
WH
EN
Time Line
Strategic Thinking
ITC Meetings
( Bi-Monthly )
EAB Meetings
(Monthly)
Enterprise Architecture Work Program
EA Initiative 1 EA Initiative 2
Impacting Periodic
Cycles
Apply Reference Framework Maintain Tools, Artefacts & Repository
Functions
HO
W
Business Viewpoint
Develop Principles and Standards
IT Investment Review
Cycle (Annual))
IT Strategic Planning
Review Cycle (Annual ?)
ITBOM Meetings
(Fortnightly )
WH
Y
Value Proposition Vision
“Enterprise Architecture will map a common path to enhance and transform DEEWR’s delivery of government policy objectives.”
Improve processes supporting DEEWR’s core capabilities.
Manage change through clear scope and impact definition.
Promote sharing and reuse of IT solutions in support of DEEWR business.
Enable timely and evidence based strategic decision making.
Promote consistency of language, approach and solutions within DEEWR.
Promote cross-agency collaboration and delivery of solutions.
Adopt Australian Government Architecture direction.
Identify Strategic
Drivers
Assess Current
State
Develop Road
MapGap AnalysisDrive Strategic Change Iterate and
RefinezDetermine Target
State
WH
OW
HA
T
Domains
Solution Architecture ConsultationSolution Architect Forum Guidance
Information Architecture
Information Quality
Meta Data & Semantics
Information
Management
Information
Sharability & Usability
BI Analytics &
Reporting
Security Architecture Business Security Information Security Application Security Technology Security
Application Architecture
Service Oriented
Architecture
Application Portfolio Event
Architecture
Application Evaluation
Framework
Technology Architecture
Service Access &
Delivery
Service Platform &
Infrastructure
Service Interface &
Integration
Component
Framework
Domains
Application of EA Practice
Business Architecture
Business Strategy
Map
Business Function/
Business Process
Service Mapping
Organisation
Business Model
IT S
trat
egy
Advising and Consulting