Ever wondered why you need a blueprint to make sense of it all. We breakdown the needs for a winning architecture technique with a template example based approach. Feel free to reach out to and if more details are required or you have an opportunity to explore

1. Building Enterprise Architecture

2. Benefits of Enterprise Architecture
• Finance – Better understanding of investment
decisions, cost allocations.
• Stakeholders – May change their view of risk.
• Product Development – Improved agility.
• Business and IT Relations – Removes the chasm.
• IT Planning – Improved understanding of options,
trade-offs.
• Partners, Suppliers, Vendors – Understanding of
vision and processes.

3. Planning an Enterprise Architecture
Steps to be Undertaken
• GOAL: Formulate and Realise the Technical Blueprint
– Agree architecture strategy in context of business & technical drivers
– Baseline business & technical requirements that influence blueprint
– Establish the conceptual, logical and physical frameworks
– Align Enterprise Information Model to Business requirements
– Establish a roadmap to show evolution strategy to required state
– Prioritise candidate architectural components based on estimated ROI
– Develop plans for developing and deploying technical capabilities
– Initiate “proof of concept” projects to prove capability challenges
– Assure realisation through Production Acceptance process
• i.e. ARB, Design Authority, Production Certification

4. The Enterprise Architecture Model
Integration
Information
Infrastructure
Application
Conceptual
Logical
Physical
Business Unit
Program
Project
Scope
Scope
LevelLevel
TypeType
Enterprise
Security
Security
Architecture
Integration
Architecture
Information
Architecture
Technical
Architecture
Application
Architecture
Business
Architecture
ISR?
Traceability

5. Enterprise Architecture Principles
1. Focus on the “how” part of the architecture model.
2. Justification and ROI come from “why”
3. Architecture is about the qualities of the solution, not the
functional behavior of an application.
4. Architecture is about making trade-off decisions explicit.
5. Explicit architecture models are needed to address system
complexity and delivery problems.
6. Architecture must demonstrate how the technology solutions
solve the business objectives and needs.
7. Data and application integration solutions must be driven by an
understanding of specific business process needs.

6. Focus on the “How” Part of Architecture
• Definition
– The Enterprise Architecture is a formal definition of
how standard computing components (hardware,
network, software, and data) work together to support
business processes and functions.
– In addition, the Enterprise Architecture provides
qualities required to support future business changes.
– “Architecture is the selection of, arrangement, and
connection between enterprise components and the
rationale for each.”
It is the definition of the pieces and how and why the
pieces fit together.

7. Problem with Current Technical Abstraction
• Does not accurately represent layer separations
• Does not provide guidance to implementation teams
• Does not help identify shared services/components
Shared Services and Components
Legacy Integration
Application Adapter
Technology Adapter
Data Adapter
Business Services
LRUC
Services
Application Services
Workflow
Security
Session
Technology Services
Persistence
Messaging
Events
Applications
Route
Entry
Customer
Care
Billing General
Ledger
Information BusCustomer Enforcement Billing Inventory

8. PressurePressure
Business
Driver
Business
Driver
ProgrammeProgramme
CapabilityCapabilityImpactImpact
PhasePhase
Enhanced
Capability
Enhanced
Capability
Business
Function
Business
Function
Business
Process
Business
Process
StakeholderStakeholder
Business
Process
Activity
Business
Process
Activity
Business
Entity
Business
Entity
Desired
change
Desired
change
ImplementationImplementation
Business Entity
Relationship
Business Entity
Relationship
ContextContext AttributeAttribute
Attribute
Source
Attribute
Source
ActorsActors
OrganisationOrganisation
InterfacesInterfaces
TiersTiers Architecture
View
Architecture
View
TransactionTransaction MessagesMessages
PracticePractice
FeatureFeature
ComponentsComponents
ConfigurationConfiguration
COTS ProductCOTS Product
Business Architecture
Technical Architecture
VolumemetricsVolumemetrics
Key to Implementation
1) Implementation” of a
“Business Process
Activity”
2) Business Entity
supporting a “Business
Process”
Integrate Business & Technology Architectures

9. Proposed Approach
• Part 1: Preparing for market - BCL Gateway 2
– Execute Baseline Gap analysis on LRUC IT capabilities
– Establish architecture principles and objectives
– Adjust PRL for additional Architectural requirements
– Establish Enterprise information model
– Alignment of IT blueprint to support business model
– Contribute Architectural guidance to the Procurement exercise
– Start preparing Integration, Security & Information Frameworks
• Part 2: Ensuring joined up delivery - BCL Gateway 3
– Enable Technical Delivery through Model Driven Architecture
– Development of Component Policy– plug the gaps
– Define services framework
– Architectural realisation through governance & Implementation

10. Enterprise Blueprint objectives
• Align technical procurement activities to ensure
support for the business strategy
• Mitigate technical risk through POC identification
• Provide a template for integrating capabilities
related to future direction
• Reduce redundancy between integration
components and business applications
• Enable technical capabilities for rapid response to
changing business requirements

11. Deliverables
• Architecture Blueprint - which will
– Define appropriate system integration wrappers
– Define Informational messaging model
– Define Service Integration template
– Identify required POC
• Capability framework – which will
– Define integration across the Application, Information
and Technology layers.
• Technology Roadmap aligned to Programme plan