Enterprise SOA Chapter 1 An Enterprise IT Renovation Roadmap
Enterprise IT Renovation <ul><li>Try to strike a balance between immediate gains and long-range improvements </li></ul><ul...
Agony Versus Agility <ul><li>Enterprise software suffers from a lack of agility and is often inefficient </li></ul><ul><li...
Ability to Deliver Paralysis t Change Requests Green Field Change Requests reduce the agility of a system over time
Why Stagnation? <ul><li>Difficult technical changes in the code </li></ul><ul><li>Key domain experts move on to other proj...
Enterprise Software is a Different Animal <ul><li>Enterprise software is tightly coupled with the internal organization, p...
…A Different Animal <ul><li>Many requirements are conflicting </li></ul><ul><li>Many requirements are unclear </li></ul><u...
… A Different Animal <ul><li>Consider an insurance claims system: </li></ul><ul><li>Stakeholders include many different bu...
Consider Building a Word Processor <ul><li>Homogenous technical team </li></ul><ul><li>Problem space is well-defined </li>...
Importance of Enterprise SOAs <ul><li>Second law of thermodynamics:  Any closed system cannot increase its internal order ...
Requirements for an Enterprise SOA <ul><li>Simplicity  </li></ul><ul><li>Many people involved with different skills </li><...
Requirements for an Enterprise SOA <ul><li>Flexibility and Maintainability </li></ul><ul><li>Every enterprise must change ...
Requirements for an Enterprise SOA <ul><li>Reusability </li></ul><ul><li>Reusability is software’s Holy Grail </li></ul><u...
Requirements for an Enterprise SOA <ul><li>Decoupling of Functionality and Technology </li></ul><ul><li>The architecture m...
Enterprise Architecture and Standards <ul><li>1980’s – Enterprise Data Model (EDM) projects tried to define one global dat...
Enterprise Architecture and Standards <ul><li>Enterprise standardization efforts in IT have failed to produce homgenizatio...
Enterprise Architecture and Standards <ul><li>SOA slices and dices the enterprise application layer in a way that componen...
Organizational Aspects <ul><li>Many problems associated with enterprise IT are not technical but are found on the organiza...
Lifelong Learning <ul><li>Many attempts have been made to find a common denominator between business and technical concept...
Lifelong Learning <ul><li>SOA provides a unique chance to create artifacts that have an enduring value for both the busine...
Upcoming SlideShare
Loading in …5
×

Enterprise SOA Chapter 1

218 views
174 views

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
218
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
11
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Enterprise SOA Chapter 1

  1. 1. Enterprise SOA Chapter 1 An Enterprise IT Renovation Roadmap
  2. 2. Enterprise IT Renovation <ul><li>Try to strike a balance between immediate gains and long-range improvements </li></ul><ul><li>Increase the ability of an enterprise to address new business requirements </li></ul><ul><li>Should reuse existing business logic and data models </li></ul><ul><li>Provide benefits through agility </li></ul>
  3. 3. Agony Versus Agility <ul><li>Enterprise software suffers from a lack of agility and is often inefficient </li></ul><ul><li>Difficult to quickly match business requirements to underlying IT structure </li></ul><ul><li>Software systems become less agile over time </li></ul>
  4. 4. Ability to Deliver Paralysis t Change Requests Green Field Change Requests reduce the agility of a system over time
  5. 5. Why Stagnation? <ul><li>Difficult technical changes in the code </li></ul><ul><li>Key domain experts move on to other projects </li></ul><ul><li>Tight budgets </li></ul><ul><li>Loss of political clout </li></ul><ul><li>No time to do refactoring </li></ul><ul><li>Business systems have complex cross-dependencies that grow over time </li></ul>
  6. 6. Enterprise Software is a Different Animal <ul><li>Enterprise software is tightly coupled with the internal organization, processes, and business model </li></ul><ul><li>Underlies cross-departmental dependencies and external business relationships </li></ul><ul><li>An Enterprise architecture must handle large numbers of different requirements </li></ul>
  7. 7. …A Different Animal <ul><li>Many requirements are conflicting </li></ul><ul><li>Many requirements are unclear </li></ul><ul><li>Requirements are a moving target due to business change </li></ul><ul><li>Business logic is usually simple! </li></ul>
  8. 8. … A Different Animal <ul><li>Consider an insurance claims system: </li></ul><ul><li>Stakeholders include many different business units </li></ul><ul><li>Heterogeneous teams of people and political environments </li></ul><ul><li>Technology landscape is highly heterogeneous – many application and middleware platforms </li></ul><ul><li>Cross dependencies in functional environments </li></ul>
  9. 9. Consider Building a Word Processor <ul><li>Homogenous technical team </li></ul><ul><li>Problem space is well-defined </li></ul><ul><li>Application logic is self-contained </li></ul><ul><li>Few cross-dependencies </li></ul><ul><li>No roll-out – user self installs </li></ul>
  10. 10. Importance of Enterprise SOAs <ul><li>Second law of thermodynamics: Any closed system cannot increase its internal order by itself </li></ul><ul><li>In enterprise software, the architect acts as the outside influence </li></ul><ul><li>Balances different requirements while trying to create an enduring order </li></ul><ul><li>Confronted with changes that increase complexity </li></ul><ul><li>Refactoring reduces complexity </li></ul>
  11. 11. Requirements for an Enterprise SOA <ul><li>Simplicity </li></ul><ul><li>Many people involved with different skills </li></ul><ul><li>IT Coordinators with detailed business knowledge but little technical skill </li></ul><ul><li>Technical architects with little vertical business knowledge </li></ul>
  12. 12. Requirements for an Enterprise SOA <ul><li>Flexibility and Maintainability </li></ul><ul><li>Every enterprise must change or die </li></ul><ul><li>The architecture must define distinct components that can be rearranged and reconfigured </li></ul><ul><li>Local changes can’t have a global impact </li></ul><ul><li>If an external API is stable, internal change should not affect operations outside the component </li></ul><ul><li>Carefully design the interfaces to be stable and general! </li></ul>
  13. 13. Requirements for an Enterprise SOA <ul><li>Reusability </li></ul><ul><li>Reusability is software’s Holy Grail </li></ul><ul><li>We need an inventory of building blocks </li></ul><ul><li>Code and data can be reused </li></ul><ul><li>Reuse may not always be the most efficient </li></ul>
  14. 14. Requirements for an Enterprise SOA <ul><li>Decoupling of Functionality and Technology </li></ul><ul><li>The architecture must make the enterprise independent of technology </li></ul><ul><li>The architecture must weather techological innovation cycles and the lifecycles of installed technologies </li></ul><ul><li>Development of business functionality must be decoupled from the underlying technology </li></ul>
  15. 15. Enterprise Architecture and Standards <ul><li>1980’s – Enterprise Data Model (EDM) projects tried to define one global data model for an entire enterprise (generally unsuccessful) </li></ul><ul><li>1990’s – Enterprise Software Bus – an attempt to standardize middleware – agree on a ubiquitous, technology-independent, enterprise-wide standard for communication between software modules. (We now have middleware heterogeneity) </li></ul>
  16. 16. Enterprise Architecture and Standards <ul><li>Enterprise standardization efforts in IT have failed to produce homgenization and easy application integration </li></ul><ul><li>Why is SOA any different? </li></ul><ul><li>SOA is not a technology or a technology standard </li></ul><ul><li>SOA represents a technology-independent, high-level concept that provides architectural blueprints </li></ul>
  17. 17. Enterprise Architecture and Standards <ul><li>SOA slices and dices the enterprise application layer in a way that components are created and exposed as services </li></ul><ul><li>Services are technically independent </li></ul><ul><li>Services have a direct relationship to business functionality </li></ul><ul><li>SOA does not impose adherence to technical standards like SOAP </li></ul>
  18. 18. Organizational Aspects <ul><li>Many problems associated with enterprise IT are not technical but are found on the organizational level </li></ul><ul><li>Development and maintenance is closely tied to the end customer. (A financial reporting system will involve the finance department, other stakeholder, the CEO) </li></ul><ul><li>Many decisions are driven by business strategy and political agendas rather than technical arguments </li></ul><ul><li>This book will provide a technical and organizational roadmap to SOA </li></ul>
  19. 19. Lifelong Learning <ul><li>Many attempts have been made to find a common denominator between business and technical concepts </li></ul><ul><li>SQL – Can be used by business analysts to analyze data directly </li></ul><ul><li>Still most entities in a relational database are too fine-grained to have meaning on a business level </li></ul><ul><li>A key goal of SOA is to provide services that have a concrete meaning on the business level </li></ul>
  20. 20. Lifelong Learning <ul><li>SOA provides a unique chance to create artifacts that have an enduring value for both the business and technology side </li></ul><ul><li>SOA provides a way for an organization to learn and preserve knowledge over time in a way that is reusable </li></ul>

×