Setting the record straight :-)
• Why is it all those CIO’s are saying
“we’re using CORBA” ?
• Because they are
– every enterprise-wide distributed
heterogeneous system
– Forrester says they prefer it 2:1
Lies, damn lies, and...
800
700
600
500
COM
CORBA
400
300
200
100
0
1996
1997
1998
1999
Everybody wants “integration”
• A consistent message yesterday was
integration of
– legacy
– new technologies
– glue code with less than n2 costs
• Today’s hot technology is tomorrow’s
legacy and I mean tomorrow
(“integrating today’s silver bullet
tomorrow”)
The Business Model
Sales
Engineering
Accounting
Manufacturing
Shipping/
Receiving
Inventory
Payables/
Receivables
Every application is part of your business model;
you must make them work together!
Everybody needs standards
• Vendors can amortize development costs
over large number of customers
• Users can amortize development costs over
large number of applications
• Lowers development risk for both vendors
& users
• Creates market for differentiation based on
product dimensions that matter to
customers
Standards get set how?
• De facto standardization by market
leader
– theoretically more consistent
• De jure standardization by committee
– time to market too high
• Consortium standardization by industry
consensus
– somewhere between the two
Finding the right point
De facto
De jure
Consensus, open specifications
with no reference implementation
Specification Availability
1. OMG adopts & publishes interfaces.
2. Interfaces must be commercially
available.
3. Interfaces freely available to members
and non-members alike.
4. Interfaces chosen from existing
products in competitive selection
process.
Leveraging Infrastructure
Telecommunications, Healthcare, Finance, Electronic
Commerce, Business Objects, Manufacturing,
Transportation, Life Sciences, Utilities, Analytical
Data Management, C4I, Customer Information
Systems, Retail, Space Systems…….
CORBA - UML - MOF
The OMG Process
Full lifecycle standards
Maintain
Deploy
Analyze
Design
Customers want standards across the lifecycle….
Open, consensus standards
• Open, neutral, consensus standards
enable product differentiation on
customer-critical dimensions
–
–
–
–
price, performance
quality
support
additional features, level of integration
Cooperative Vision
• Focus on consensus
• Build on existing infrastructure
• Leverage specifications built over our
first ten years history
• Use existing technology where possible
• Move quickly to fill openings
• Enable portability and interoperability