This historical presentation, circa 2010, describes strategies for moving towards Service Oriented Architecture (SOA) in enterprise application building and software architectures. It discusses how to manage it, approach it, get value and avoid issues.

1. Akiva Marks
Chief SOA Architect Consultant
March, 2010
Methodology Library

2. Akiva’s Historical Presentations
• Over years as a corporate enterprise architect, director of
enterprise architecture, and as an enterprise IT architecture
and IT management consultant, I prepared many
presentations about the leading technologies at the time…
how to use, where to value, what to avoid.
• As most concepts and technologies in software build upon
older tech sets, you may find these of value to understand
some of the foundations upon which your tech stack is
built…and perhaps identify ideas that still apply or offer
value.
• If you’d like to contact me to discuss further, I can be
contacted via akivam@gmail.com or via Linkedin -
https://www.linkedin.com/in/akivam/

3. Integration Has Become Easy
Quick and Easy
connection between systems
exposure of
transactions
spread of data
& functions
Asset
Visibility
Impact Analysis
Process
Modeling
SOA technologies enable
What did we get ?

4. SOA Approaches
Does it matter ?
For each project
expose, compose &
consume
Start with
implementation
finish with business
model
Start with business
model finish with
implementation
Top-Down Bottom-Up Middle-Out
Whichever you choose, same steps different order.
None of these approaches say “Start tool shopping…”

5. The three milestones of SOA
In a perfect world, migration to SOA would
follow three straightforward
top-down stages…
Collaborative
Modeling
Service Oriented
System Construction
Collaborative
Operation

6. The three milestones of SOA
Collaborative modeling

7. The three milestones of SOA

8. The three milestones of SOA

9. Construction implementation methodology

10. Challenges
We have a large
number of existing
systems in older
technology &
architecture models to
maintain & integrate.
SOA tech has entered
bottom-up, without
methodologies &
process, because “just
connecting things using
SOAP” is fast and easy.
We have project and
business deadlines that
don’t care about
architecture, they just want
to get it done NOW.

11. SOA Technology without
Methodology leads to…
Connection Spaghetti
Process Duplication
Reduced Reliability
Data Duplication
Major Support (Root Cause
Identification) Challenges
Hard to identify process impact,
impact of changes and system
modifications and upgrades

12. SOA Methodology Provides
Measurable Value

13. SOA Cycle
Are You Getting Value Here?
SOA
Analysis
Identify & Model
the “gold copy of data”
“business process”
the right source “system” or
“application”

14. SOA Cycle
Are You Getting Value Here?
SOA
Analysis
IT Management
for SOA
Creating
reuse incentives
services with highest likelihood of reuse
Penalties
having to adjust services in the next year
Handling of budget
issues regarding first-creator cost,
maintenance & support costs, etc

15. SOA Cycle
Are You Getting Value Here?
SOA
Analysis
IT Management
for SOA
Create SOA
Controls
Governance
Managed Service SDLC Workflow
Policy Creation, Automated Application
& Enforcement
Impact Analysis
Determine, Track, Report

16. SOA Cycle
Are You Getting Value Here?
SOA
Analysis
IT Management
for SOA
Create SOA
Controls
Coordinated SOA
Development
Consumer – Provider
contracts
Roles and responsibility
Layered QA testing
Integration into the Software
SDLC

17. SOA Cycle
Are You Getting Value Here?
SOA
Analysis
IT Management
for SOA
Create SOA
Controls
Coordinated SOA
Development
Distributed
Monitoring
Pinpoint problems
SLA control
Excess use

18. SOA Cycle
Are You Getting Value Here?
SOA
Analysis
IT Management
for SOA
Create SOA
Controls
Coordinated SOA
Development
Distributed
Monitoring
Ongoing KPI’s
for SOA
measure
the right points +
Get detailed feedback
=
Show the ROI, detailed/granular
and enterprise.

19. SOA Value: Myth or Reality?

20. Thank You