Transcript Open Group

Lessons learned from EA in the
Belgian Commercial and
Government Sectors
Architecture, Architecting, Architectural Description
A practitioners perspective
Bart Van Passel
[email protected]
+32 477 685006
www.inno.com
Jan Wilmaers
[email protected]
+32 486 098112
© Inno.com – Heiststeenweg 131 – 2580 Beerzel - +32 15 25 82 00
Making sense of IEEE 1471 for Enterprise
Architecture
 architecture: The fundamental organization of a system embodied
in its components, their relationships to each other, and to the
environment, and the principles guiding its design and evolution.
 system: A collection of components organized to accomplish a
specific function or set of functions.
 architect: The person, team, or organization responsible for
systems architecture.
 architecting: The activities of defining, documenting, maintaining,
improving, and certifying proper implementation of an architecture.
 architectural description (AD): A collection of products to
document an architecture.
Architecture, Architect, Architecting, Architectural Description
2
In organisations we did Enterprise
Architecture related work for








European HQ of a Global Freight Forwarder
European Transport Routing Center
Local Operation of a Global Telecom Provider
Parcel and Postal Services Provider
Social Security Services Provider
Regional Adminstration
Automotive Distribution Chain
Medium Sized Financial Institution
Architecture, Architect, Architecting, Architectural Description
3
4
The system to be Architected ?
The
infrastructure,
applications
The system that designs,
develops, evolves and
maintains the IT Assets
Enterprise System
Source: Soh and Markus: How IT creates business value: a process theory synthesis
Architecture, Architect, Architecting, Architectural Description
Plenty (and increasing numbers) of architects
within the system
Architect
Builder
Owner
Planner
Subcontractor
The system that designs,
develops, evolves and
maintains the IT Assets
Enterprise System
Source: Soh and Markus: How IT creates business value: a process theory synthesis
Architecture, Architect, Architecting, Architectural Description
5
Architecting became organisationally
entangled
From: Function as frame for
organisational problem solving
Coordination : straightforward
Functional Areas
To: Process (and its
performance) as frame for
organisational problem solving
Coordindation : complex
Functional Areas
Processes
Projects
Applications
Applications
=> EA is about sorting out the organisational problem
solving structure
Architecture, Architect, Architecting, Architectural Description
6
7
Architecting just happens
 Often, mostly implicit
 On the wrong organisational level, with the wrong people
(or each of the levels independently and not coordinated)
 With a questionable problem scope (too wide, too narrow)
 With a questionable time frame (too long, too short)
 With a questionable solution space
 With a questionable effort (not enough, too much), on a
questionable moment (too early, too late (or too fast, not
fast enough))
 With a questionable business outcome as a result
 => A more explicit rational integrated
process ?!?
Architecture, Architect, Architecting, Architectural Description
8
Right question = half of the solution
What
Data
How
Function
Who
People
Where
Location
When
Time
Why
Planner
(CxO,
Corporate
Planning)
Owner
(Middle mgnt)
Architect
(EA, Business,
Information,
Solution, …)
Builder
(Analysts,
Designers)
1. Make them specific, apply
them to the situation
2. Identify key questions, key
drivers, key contraints
3. Define a path through the
questions to be answered
Realisation
(Developers,
System
Engineers)
Tools, Techniques
Identify the players
Architecture, Architect, Architecting, Architectural Description
IT Organisation
Roadmap
Decouple problem-solutions: Conceptualising
needs and means
What
Data
How
Function
Who
People
Where
Location
When
Time
Why
Planner
(CxO,
Corporate
Planning)
Owner
(Middle mgnt)
Architect
(EA, Business,
Information,
Solution, …)
Builder
(Analysts,
Designers)
Realisation
(Developers,
System
Engineers)
Tools, Techniques
Architecture, Architect, Architecting, Architectural Description
IT Organisation
Roadmap
9
10
Case 1: ICT Strategy local Telecom player
What
Data
How
Function
Who
People
Where
Location
When
Time
Why
Planner
(CxO,
Corporate
Planning)
Owner
(Middle mgnt)
Architect
(EA, Business,
Information,
Solution, …)
To Be ?
Tech
Builder
(Analysts,
Designers)
As Is ?
To Be ?
?
Realisation
(Developers,
System
Engineers)
Tools, Techniques
Architecture, Architect, Architecting, Architectural Description
IT Organisation
Roadmap
Plan
11
How, Why ?
Planner
Sales Office (5. Extranet)
Support Activities
Business Planning (2. Management Reporting)
System Support/Deployment/Training (3. Remote Access)
Commissioning / Bonus Calculation (4. Commissioning)
(Channel) Management (2. Management Reporting)
Core Activities
Sell to Customer
Prospecting
(Prospect List,
Telemarketing, …)
(8. Product
Approach Prospecting)
Sell to Customer
(Sales Pipeline,
Design, Proposal)
(6. Contact
Management,
7. Project Approach Create Proposal/Sales
Project Management,
9. Product Approach Sales Force
Automation)
Customer Installation
Create Internal
Order
(10. Create Internal
Order)
Manage Order
(Implementation
Pipeline - Internal)
(11. Manage/Track
Internal Order)
Architecture, Architect, Architecting, Architectural Description
Customer Relationship Management
Contact Management
(6. Contact
Management,
12. Customer
Interaction History)
Customer Enquiries /
Problems Management
(13. Visibility on
Different Pipelines,
14. Triggering/Injecting
in Different Pipelines,
15. Tracking/Follow up
on Actions)
What ?
Information Model
Owner
Products/
Services
HR / Agent
Management








Training
Material
Background/Profiling
Contract terms
Targets
Product Group
Product
Flavour/Service
Type
Assets



Processes/Workflow







Organisation




opportunity
order (COF)
orderline (IOF)
invoice
change request
work pack
activities/contacts/
appointments
Customer
Profiling


Spent
...
Channel
Subchannel
SalesPerson
SE, PM, ...
Customer





Architecture, Architect, Architecting, Architectural Description
legal entity
exploitation site
invoice address
contact person
commercial address
Configuration



Technical
Configuration
Billing Configuration
Contract
Router Stocks
Circuits
...
12
13
What, How ?
Applications – As IS
Bonus Payment
System
Architect, Builder
Add hoc Excell +
Access Tools
Derived Data
Commissioning
Bonus Calculation
Operational
Forecast
Business Planning
Management
Reporting
Electronic Order
System
Amyyon
Workflow
mar (KARMA)
r Spreadsheet
(NSO) Cheops
(Billing) Billing
Engine
(Marketing)
eting Database
Generate Suspect
List
m Engineers)
twork Design
Tool
TeleMarketing
nagement)
sal Tools +
Templates
Sales Pipeline
Order
Management
Workflow
Sales Project
Workflow
Installation
Service
Pipeline
Billing
Pipeline
Basic Data
t Management
System
Agent
Management
Contact
Management
Technical Design
Tool
Technical
Configuration
(Inventory)
Order Entry
Data Capturing
(Shared)
urconv.xls
Sales Force
Management
Reference
Customer List
Proposal Tools
Architecture, Architect, Architecting, Architectural Description
Technical
Configuration
(Configuration)
Finance
What, How 14?
Applications - To Be
Architect, Builder
Generic Front
CRM
Reporting Tool
End Tool
Derived Data
Commissioning
Bonus Calculation
Operational
Forecast
Management
Reporting
Business Planning
Customer Care
Front End
Workflow
Help Desk
System
Customer Care Action Pipe
Generic Workflow
Component
Generate Suspect
List
TeleMarketing
Sales Pipeline
Order
Management
Workflow
Sales Project
Workflow
Installation
Service
Pipeline
Billing
Pipeline
Billing System
Basic Data
Agent
Management
Sales Force
Management
Contact
Management
Reference
Customer List
Technical Design
Tool
Proposal Tools
Architecture, Architect, Architecting, Architectural Description
Generic Front
End Tool +
Unstructured/
Structured (XML)
Datastore
Technical
Configuration
(Inventory)
Order Entry
Data Capturing
Technical
Configuration
(Configuration)
Finance
Case 2: ICT Strategy for a European
distribution chain
What
Data
How
Function
Who
People
Where
Location
When
Time
15
Why
Planner
(CxO,
Corporate
Planning)
Owner
(Middle mgnt)
Architect
(EA, Business,
Information,
Solution, …)
To Be
To be To be
Builder
(Analysts,
Designers)
As Is
To Be
As Is
To Be
Realisation
(Developers,
System
Engineers)
Tools, TechniquesIT org,
IT Organisation
IS Gov
Architecture, Architect, Architecting, Architectural Description
Roadmap
Plan
16
How ?
Planner
Architecture, Architect, Architecting, Architectural Description
Cash
Manage
Customer
Satisfaction/Life
Cycle
Provide
Warrenty
Services
Invoice service
Provide
Maintenance
Services
Provide Repair
Services
Provide Body
and Paint
Services
Service
Manage Accounts Receivable and Payable
Setup and Manage Service Network
Manage
Customer
Satisfaction/Life
Cycle
Provide Warrenty
Services
Provide Repair
Services
Organize Service Training and Service
Support Tools
Provide
Maintenance
Services
Register Parts
Organize Service Training and Service
Support Tools
Install Accessory
Register Vehicle
Adapt and Fit
Ship parts
(Logistics)
Repeat Customer
Service
Manage Accounts Receivable and Payable
Setup and Manage Service Network
Invoice service
Cash
Ship Vehicle
Adapt/Fit Parts
(Package, Set/
Kit)
Setup and Manage Supplier relationships
(insurance, financing, ...)
Service
Manage Accounts Receivable and
Payable
Setup and Manage Service Network
Deliver
Service
Bill and Invoice
service
(settle)
Handle Customer
Enquiries/
Complaints
Provide Ongoing
Service
Ship Physical
Components
(Documents,Brochu
res)
Invoice service
setup
Setup Service
Organize Service Training and Service
Support Tools
Register Order
Manage Product
Launch
Define Channel
Strategy
Price Goods and
Services
Manage Lead
Sell
Quote/Price Deal
Forecast Sales
Make informed/valid
choice
Estimate Market Size
(Medium term sales planning)
Organise Incentive
Campaigns, Events
(promotions, ...)
Estimate Market Size
(Long term sales planning)
Create Product
Awareness
Research Market
Organize Product Training and Sales
Support Tools
Develop Offering
Manufacture
Vehicle
Manage Accounts Payable
Organize Marketing Instruments (test
drives, F1, brochures)
Market
Manufacture
Parts
Deliver
Setup and Manage Distribution
Channels
Source
Manage Order
Delivery and
Invoicing
Register Order
Estimate
Delivery Date
Quote/Price
Deal
Sell
Establish and Follow Up Marketing Budgets
Source and Manage Suppliers (media,
advertisers, ...)
Gather feedback on exisiting products
Manage Order
Delivery and
Invoicing
Register Order
Estimate Delivery
Date
Quote/Price Deal
Configure
vehicule
Deliver
Manage Accounts Receivable and Payable
Setup and Manage Distribution Channels
Setup and Manage Logistics Suppliers
Organize Product Training and Sales Support Setup and Manage Logisctics/WH Operations
Tools
Setup and Manage Parts Manufactures
Plan Logistics and Warehouse Operations
Forecast Sales
Plan Production
Return Goods - Inverse Logistics
Manage Inventory
Order Service
Market
Manage Accounts Payable
Manage Accounts Receiveble
Setup and Manage Logistics Partners
Setup and Manage Logistics/Hub Operations
Plan Logistics and Hub Operations
Schedule/Plan Production
Return Goods
Manage Inventory
Sell
Make a proposal
One-to-One
Direct Marketing
Organise
Incentive
Campaigns,
Events
Create Product
Awareness
Plan Marketing Actions/Operations
Create Toyota/
Lexus Part/
Accessory
Brand
Awareness
Launch Product,
Manage Life
Cycle
Define Channel
Strategy
Price Goods and
Services
Define End
Market Product/
Service
Source Suppliers (media, advertisers, ...)
Manage Lead
One-To-One
Direct Marketing
Organise
Incentive
Campaigns,
Events
Create Product
Awareness
Launch Product,
Manage Life
Cycle
Create Toyota,
Lexus Brand
Awareness
Define Channel
Strategy
Determine
Pricing Strategy
Design/
Europeanize Car
Model
Define EndMarket Product
Forecast Sales
Set-up and Manage Parts Suppliers
Identify Market
Needs/
Opportunities
Added Value Services
Set-up and Manage Sales Channels (Dealer,
Fleet, Retail)
Plan Marketing Actions/Operations
Order, Distribute, Invoice, Collect Marketing
Material
Customer
Deliver
Source Suppliers (media, advertisers,...)
Organize Marketing Instruments (brochures)
Long Term Product Strategy
Sell
Organize Product Training and Sales Support
Tools
Long Term Product Strategy
Estimate Market Size (Volume/Price Strategy)
Design Marketing Mix
Order
Organize Marketing Instruments (test drives,
F1, brochures, advertisement)
Establish and Follow Up Marketing Budgets
Market
Establish and Follow Up Marketing Budgets
Research Market
Gather feedback on exisiting products
Identify Market
Needs/
Opportunities
Engineer Part/
Accessory
Parts & Accessories
Design Marketing Mix
Used
Cars
Lead
Market
Order, Distribute, Invoice, Collect Marketing
Material
Estimate Market Size (Price/Volume)
Brand/Product Strategy
Gather feedback on exisiting products
Research Market
Assess Market
Needs
Vehicles
Design Marketing Mix
Cash
Product
Manage Lead
Market
Cash
Finance
Resource/Organize
R&D/Technology: ICT, ...
Plan
Procurement
Offering services through functional
capabilities
17
How ?
Planner
Product Management, Marketing
Awareness
Network Partner Management
Background for
organisational
changes,
improvent
Consideration
projects, ...
Sales Management
Delivery Management
Acquisition
Financial Settlement Management
Liability Settlement Management
Ownership
Reconsideration
Performance Management (Quality, Risk, Cost)
Architecture, Architect, Architecting, Architectural Description
Business & Information architecture
components to support functional capabilities
18
What, How ?
Architect
DATA components
Product Management, Marketing
Awareness
Network Partner Management
Consideration
Lead/Request management
Sales Management
Order
Management
Delivery Management
Delivery Management
Financial Settlement Management
Liability
Liability
SettlementManagement
Management
FO Gateway
BO Gateway
Sales Planning
Acquisition
Pricing, Invoicing
Ownership
Collection, Payment, Accounting
Reconsideration
Performance
Management (Quality,
Risk, Cost)
Management
Components
Back Office
Middle Office
Front Office
Gateway is the interface to the external world and can be
realised through portal (access the system through the Web),
Architecture, Architect, Architecting,
Architectural
Description
EDI (Electronic
Data
Interchange), call centre, human, paper, …
Consumer
19
What, How ?
Data
components
Business & Information architecture Components Details
Architect
Customer data mgt
Product/Service mgt
Vehicle mgt
- Customer info
- Contact
- Profiling
- Pro-active CM
- Product / Service info
- Bill of material / service
- Price
- Product/Service configuration
- Technical information
- SSC
- Vehicle info
- Vehicle history
- Monitoring
Parts &
Accessories mgt
Service contract mgt
Sales organisation
(Dealer/NMSC)
management
- Service contract info
- Service contract history
- Monitoring
- P&A info
- P&A history
- Monitoring
SCM (Supplier)
management
- Supplier info
- Supplier agreement
- Supplier monitoring
- Dealer/NMSC info
- Dealer/NMSC agreement
- Dealer/NMSC monitoring
Added Value Service
intervention
request management
Servicing intervention
request management
Human
resource
management
Financial resource
management
Service intervention
request
Lead management
Lead info
(match cust. wish, pricing, proposal)
Core Business Process Components
Sales
forecast
Sales planning
Supply
plan
Sales
order/
cancellation
Sales
plan
Replenishment
order
Physical
inventory
reconciliation
Service Delivery
Gateway
(B2B)
Allocation
(all types of
resources)
Check
Reserve
Inventory
management
Back
(allorder
types of resources)
Shipment request
Warehouse operation instruction (PPO, PPI)
Service configuration instruction
Instruction status feedback
Legal instruction
Deliver
from
inventory
Sales
order/cancell
Availability check / ETA
Price
proposal
order
CC
Forecast data
Availability check / ETA
Price
proposal
Order
management
Reservation/cancellation
Delivery request/
cancellation
Customer contract/cancellation Sales order/cancellation
BO instruction
management
Delivery request
status feedback
Market warranty
claim
management
Product/ServiceAccepted claim
detail record (PSDR)
Vendor claim
management
Vendor warranty
claim
Sales forecasting
Service Initiation
Gateway
(B2B, B2C)
Market warranty claim
Acc
claim
Credit
check
Pricing & Tax calc
Invoice, claim, Cr/Db note
Priced/Taxed PSDR
Invoice, claim, Cr/Db note
Invoicing, claim,
Cr/Db note
handling
To be collected
To be payed
Invoice, Cr/Db note Invoice, Cr/Db note
Payment
instruction
Cash Collection
and reminders
Cash Payment
Bank
statement
Credit checking
Payment history
AR / AP / GL
Management
Process
Components
Product performance management
(profitability,...)
Product management
Market
intelligence
Performance management - Line, Middle, Top
(Quality, cost, profitabilty, throughput, ...)
Campaign
management
Supplier network management
(targets,...)
Architecture, Architect, Architecting, Architectural Description
Direct
marketing
Event
management
Marketing
Sales network management
(targets,...)
Digital info
Provisioning
Lead
generation
Network management
Service network management
(quality, capacity, distribution, ...)
Customer management
(satisfaction, retention, ...)
Complaint
management
20
What, How ?
Application Architecture - As IS
Management Components
DATA components
FO Gateway
F&A
21
Collection, Payment, Accounting
22
Management Components
DATA components
HR
23
Management Components
Distributo
r Systems
Liability Management
Liability Management
Pricing, Invoicing
Liability Management
Pricing, Invoicing
Pricing, Invoicing
Collection,
Payment, Accounting
Pricing, Invoicing
Collection, Payment, Accounting
Collection, Payment, Accounting
Collection, Payment, Accounting
Management Components
Management Components
Management Components
Management Components
Architecture, Architect, Architecting, Architectural Description
Retailer
Systems
FO Gateway
FO Gateway
FO Gateway
FO Gateway
19
Sales Planning
Order
Management
Sales Planning
Sales Planning
Order Management
Order
Management
Delivery
Management
Order Management
Delivery Management
Delivery Management
Liability Management
Delivery Management
DATA components
DATA components
DATA components
DATA components
Lead/Request
management
Lead/Request management
Lead/Request
Sales management
Planning
Lead/Request management
Sales Planning
Sales
OrderPlanning
Management
Sales Planning
Order Management
Order Management
Delivery
Management
Order
Management
Delivery Management
Delivery Management
Liability
Management
Delivery
Management
Liability Management
Liability Management
Pricing,
Invoicing
Liability
Management
Pricing, Invoicing
Pricing, Invoicing
Collection,
Pricing,Payment,
InvoicingAccounting
Collection, Payment, Accounting
Collection, Payment, Accounting
Collection, Payment, Accounting
Management Components
Management Components
Management Components
Management Components
BO Gateway
BO Gateway
BO Gateway
BO Gateway
17
18
Liability Management
Pricing, Invoicing
10
DATA components
DATA components
Lead/Request
management
DATA components
FO Gateway
FO Gateway
FO Gateway
FO Gateway
12
Sales Planning
Order Management
Delivery Management
14
13
Pricing, Invoicing
DATA components
BO Gateway
BO Gateway
BO Gateway
BO Gateway
11
Builder
Retailer
Sales Planning
FO Gateway
9
8
Management Components
10
DATA components
FO Gateway
BO Gateway
3
FO GatewayFO Gateway
6
DATA components
2
Sales Planning
Order
Management
4
Delivery Management
5
7
Pricing, Invoicing
National Distributor
Consumer
Parts Supplier
Warranty
Distribution
BO Gateway
1
Management Components
16
15
DATA components
BO GatewayBO Gateway
Vehicles
distribution
BO Gateway
HQ
21
Case 3 : EAI Selection Process – version 1
What
Data
How
Function
Who
People
Where
Location
When
Time
Why
Planner
(CxO,
Corporate
Planning)
Owner
(Middle mgnt)
Architect
(EA, Business,
Information,
Solution, …)
Builder
(Analysts,
Designers)
?
Realisation
(Developers,
System
Engineers)
?
Tools, Techniques
Architecture, Architect, Architecting, Architectural Description
IT Organisation
Roadmap
How ?
Front-Office
Architect
OCR
Channel 1
Derived
Channel 2
Statistics
Costing
Broker 2
Processes
Data
Warehouse
Broker 1
Op App 1
Op App 2
Broker 3
Op App 3
Marketing &
Sales
Integration
Patterns
Op App 0
Op App 4
Op App 5
Op App 6
Op App 7
Generieke
Interface
ERP
CustomerDB
Service Interface
Reference Data
Contract
Product
Customer
Architecture, Architect, Architecting, Architectural Description
Address
Address Info
Provider
22
Where ?
EAI building blocks
Architect
Architecture, Architect, Architecting, Architectural Description
23
24
Case 4 : EAI Selection Process – version 2
What
Data
How
Function
Who
People
Where
Location
When
Time
Why
Planner
(CxO,
Corporate
Planning)
Owner
(Middle mgnt)
Architect
(EA, Business,
Information,
Solution, …)
Builder
(Analysts,
Designers)
?
Realisation
(Developers,
System
Engineers)
?
Tools, Techniques
Architecture, Architect, Architecting, Architectural Description
IT Organisation
Roadmap
25
Case 5: Re-vitalising a strategic project
What
Data
How
Function
Who
People
Where
Location
Planner
(CxO,
Corporate
Planning)
Why
Business
Objectives
Business
Case
Requirments
Owner
(Middle mgnt)
Architect
(EA, Business,
Information,
Solution, …)
Matching ?
Builder
(Analysts,
Designers)
Realisation
(Developers,
System
Engineers)
When
Time
Techn
DB
Code
Tools, Techniques
Architecture, Architect, Architecting, Architectural Description
ICT
Objectives
Deploy
Infra
IT Organisation
Roadmap
26
What
Data
How
Function
Planner
(CxO,
Corporate
Planning)
Who
People
Where
Location
When
Time
Why
Business Vision
Owner
(Middle mgnt)
Architect
(EA, Business,
Information,
Solution, …)
Builder
(Analysts,
Designers)
Realisation
(Developers,
System
Engineers)
Information
Model
•Process Hierachie
•Function Hierachie
Evaluation
Existing
Code
Tools, Techniques
Templates
Architecture, Architect, Architecting, Architectural Description
Conceptual
Technology
Model
Objectives
Componentisation
Evaluation
Technology
Choice
Techn.
Objectives
IT Organisation
Roadmap
Scenarios
Metrics
Plan
27
What, How,
Where ?
Where ? Vision for system support
Architect
Customer
Scanning, OCR
Contact Center
Portal
Tasks
Activities
Sales
Agenda
(dispatching)
Sys
Provisioning/Servicing
Comp
Entities
Architecture, Architect, Architecting, Architectural Description
Electronic
Filing Sys
MIS
Parameterisatie
(Document)
Workflow
Reporting
Processes
Automatische
Processen
Interfaces to the Environment
28
Architectural Description = model
 Model = abstraction of reality built in the context of a specific
problem solving exercise
 Includes the aspects that are relevant to understand the problem
 Excludes the non-relevant aspects (= majority)
In order to be able to draw relevant conclusions in the context problem
 Needs to be understood by all participants involved in the
exercise (communication goes before formalism, you can add
formalism once you decide to make the step to MDA)
 Be pragmatic:
 => stop analysing when the you have the relevant information,
decission making is the issue, not analysis
 => having models up-to-date in case you need them can have an
added value to improve the process, having the capability to model
certainly has
 => be pragmatic in the decission what model data to keep up to
date, and what part to re-generate when you need it. Model data
only becomes model information in case it’s questioned from the
perspective of a specific problem.
Architecture, Architect, Architecting, Architectural Description
Idealized
architecting
process
 Design School
: process of conception
 Planning School
: a formal process
 Positioning School : an analytical process
The actual
process as
observed




Learning School : an emergent process
Power School
: a process of negotiation
Cultural School
: a collective process
Environmental School: a reactive process
 Configuration School: a process of
transformation
Source: Mintzberg – Ahlstrand – Lampel : Strategy Safari
Architecture, Architect, Architecting, Architectural Description
Descriptive
 Entrepreneurial School: a visionary process
 Cognitive School : a mental process
Prescriptive
Architecting – strategy making schools and
patterns (Mintzberg)
29
Centralised versus distributed Enterprise
architecting process
 Architect centralises
the architecture
 Does the analysis
 Conceives the
architecture vision
 Communicates the
architecture vision
 Controls the
implementation
 Preset, fixed schedule
•Easiest to sell
•Easiest to get an
architectural vision
•Most Difficult to get it
implemented
Architecture, Architect, Architecting, Architectural Description
 Architect facilitates the
architecting process:
 Frame problems
 Ask the right
questions
 Choose frameworks –
models (relevant to
the problem but also
the problem
stakeholders)
 Guides the problem
solving exercise
 Translates the shared
vision into architecting
policy
 In an ongoing process
•Most Added Value
30
Theory Of Software Evolution Applies
(MM Lehman)
Outcome of the process is
difficult (impossible) to predict !
E-type systems: systems actively used and embedded in a real world
domain
Architecture, Architect, Architecting, Architectural Description
31
Motivation , Why a more explicit rational
integrated process ? 3E’s !!!
 Improved Effectiveness (doing the
right things): a larger part of investments
should be made in areas that matter and
result in systems that perform.
 Improved Efficiency (doing the things
right): results should be achieved with
less resources.
 Improved Economy: the organisation
should get more opportunities for
investments that have a possitive net
effect
= economic engine for ICT related
activities, basis for ICT capability
based competition
Architecture, Architect, Architecting, Architectural Description
Relatively
easy to
demonstrate
To demonstrate:
Requires to make
some processes
explicit, baseline
and measure
them. Still
feasible
Criteria,
Measurement,
direction ?
Real Options
Analysis ?
32
33
Conclusions
 System: the enterprise system
 Architects: plenty of them, organisational structure not always
clear or adapted to the problem at hand
 Architecting: need an explicit rational integrated process
 Key = Conceptualisation of needs and means
 Architectural Description = model (and should be treated as
such)
 Centralised versus distributed process, the more people involved
the easier to get the vision implemented.
 Motivation for a more explicit rational integrated process :
Improved Effectiveness, Efficiency, Economy
Improved Economy = economic engine for ICT
Architecture, Architect, Architecting, Architectural Description
34
Questions, Feedback ?
?
Architecture, Architect, Architecting, Architectural Description