1 / 4

Günter Böckle Siemens AG

Convergence – The ‘must haves’ - Software interoperability, profiles, building blocks, architectures and middleware. Günter Böckle Siemens AG. Many things are converging:. Telephony and internet (voice and data  + video: triple play ), fixed and mobile, TDM and IP, services, devices, ….

wan
Download Presentation

Günter Böckle Siemens AG

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Convergence –The ‘must haves’ - Software interoperability, profiles, building blocks, architectures and middleware Günter Böckle Siemens AG

  2. Many things are converging: • Telephony and internet (voice and data  + video: triple play), fixed and mobile, TDM and IP, services, devices, … Source: Gartner ITXpo, November 2004

  3. EU Economy Business Services Comprehensive View Trust - Dependability Business Domain 1 Business Domain 2 Business Domain n NESSILandscape Cross business Collaborations (Business level Services) NESSI Adoption Practices and Usages Regulatory Governance Architecture and Engineering Core Services Semantic Layer Security Interoperability Management Services NESSI Framework Service Integration Layer Open Standards - Open Source - Quality - Connectivity - Federation Infrastructure Layer NESSI Holistic View

  4. Discussion Topics • Software interoperability is the goal • Profiles help to understand requirements • Building blocks: different approaches– do they need standardization? • Architecture: there are styles and patterns – do they need standardization? • Middleware: lots of approaches for standards, many overlaps – how to clear the jungle? • Additionally: business process modeling – where to standardize?

More Related