Published on

  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide


  1. 1. TAO Applicability Focus on IT technology providers
  2. 2. Index of the Approach <ul><li>Common Items: </li></ul><ul><li>Legacy systems problems and TAO Solution  Get audience interested since the first minute. First slides are crucial!! </li></ul><ul><li>Semantic Web  Brief introduction, main concepts and so on. 2-3 slides, no more!! </li></ul><ul><li>Legacy Systems  Concept, flaws </li></ul><ul><li>Custom Items: </li></ul><ul><li>Applicability  Depending the vertical sector </li></ul>
  3. 3. How to solve them? <ul><li>Define a low-cost route to transitioning legacy systems to open semantic Service-Oriented Architectures (SOAs): </li></ul><ul><ul><li>Research Topics: </li></ul></ul><ul><ul><ul><li>Bootstrapping Methodology to aid the transitioning process </li></ul></ul></ul><ul><ul><ul><li>Semi-automatic creation of ontologies </li></ul></ul></ul><ul><ul><ul><li>Automated methods for metadata creation and augmentation of legacy content </li></ul></ul></ul><ul><ul><ul><li>Distributed semantic repositories </li></ul></ul></ul><ul><ul><li>Transitioning Infrastructure </li></ul></ul><ul><ul><li>2 case studies to validate the RTD developments </li></ul></ul>Legacy systems: Main Problems <ul><li>Enterprise Applications Integration (EAI) … </li></ul><ul><li>Built with languages and data models that are now out-dated </li></ul><ul><li>Badly structured and difficult to maintain </li></ul><ul><li>Badly documented and understood </li></ul><ul><li>Run on expensive and less effective platforms </li></ul><ul><li>Difficult to integrate with each other and with new systems </li></ul><ul><li>Lots of redundancy </li></ul>TAO
  4. 4. Legacy Systems: General Concepts <ul><li>Definition </li></ul><ul><li>“ A large software system that is vital to our organisation, but resist modification and evolution to meet new and constantly changing business requirements” </li></ul>
  5. 5. Legacy Systems: General Concepts <ul><li>Environment has an impression on the organisation and changes in the organisation call for alterations in the legacy system. </li></ul>
  6. 6. Legacy Systems: General Concepts <ul><li>Strategy layer  management, value of SW </li></ul><ul><li>User layer  support to business, usability </li></ul><ul><li>Technical layer  maintenance, technical factors. </li></ul>
  7. 7. Legacy Systems: General Concepts <ul><li>Problems to fix: </li></ul><ul><li>Changes in the environment  changes in the business  changes in Information Systems. </li></ul><ul><li>Flexibility  maintenance and modification. </li></ul><ul><li>Hard, expensive or impossible to modify </li></ul>
  8. 8. Design strategies for legacy system involvement in SOA solutions <ul><li>Main objective : understand the challenges of business transformation using TAO in legacy environments. </li></ul><ul><li>Open architectures are at the heart of many business-transformation efforts. </li></ul><ul><li>IT systems participate as service providers. </li></ul><ul><li>TAO solution not only delivers an infrastructure as a means to aid transformation, but also to ensure that enterprise-wide business operations remain robust and compliant. </li></ul>
  9. 9. Approaches for legacy system modernization through TAO <ul><li>Part of a business strategy and core-competency analysis that involves legacy. </li></ul><ul><li>Alignment of enterprise architecture and creation of a service-based IT infrastructure. </li></ul><ul><li>Transformation and/or extension of existing legacy systems. </li></ul>
  10. 10. Applicability TAO as a transformational value proposition tailored by: - marketplace - business sector - client Enterprise IT infrastructure is usually a bunch of different agents trying to collaborate in global goals.
  11. 11. Applicability. IT Provider <ul><li>Creation of a sustainable competitive advantage in terms of efficiency issues </li></ul><ul><li>Solutions for Operational Transformation included in: </li></ul>Nº1 Nº2 Nº3
  12. 12. Applicability: IT Provider <ul><li>Legacy Content is mainly found in: </li></ul><ul><ul><li>Traditional Mainframe processing (diverse applications) </li></ul></ul><ul><ul><li>ERP applications (root application) </li></ul></ul><ul><ul><li>Internal and External Web applications (diverse applications) </li></ul></ul><ul><ul><li>Workflow Applications (diverse application) </li></ul></ul><ul><ul><li>Scanning and Printing Systems (commonality) </li></ul></ul>
  13. 13. Applicability: IT Provider <ul><li>It is a fact that semantic integration provides value proportional to the number and importance of the databases and legacy applications that are integrated. </li></ul>Applications that support collaboration are only as valuable as the size and activity of the communities that collaborate. Semantic Technologies are disruptive
  14. 14. Applicability: IT Provider <ul><li>So, markets in which semantics unique capabilities provide value, and TAO helps, are: </li></ul><ul><ul><li>E-Commerce </li></ul></ul><ul><ul><li>Technical Help Desk </li></ul></ul><ul><ul><li>Enterprise adopting SOA </li></ul></ul><ul><ul><li>(see Design strategy slide) </li></ul></ul>
  15. 15. Open discussion <ul><li>Other approaches? Work on more business-oriented presentation. </li></ul><ul><li>Self-contained presentation? Distribute diverse material? Video, tutorial, presentation … </li></ul><ul><li>Feedback about content distribution of Web Page? </li></ul><ul><li>Business Event: Where? When? Within ESWC’08 scope? Would be great opportunity, but hard to introduce a draft of TAO Suite. Indeed, good point to speak to industry. </li></ul>