|
<<< Previous speaker
|
next speaker >>>
|
CTO, Rational Software Martin Nally, IBM
Martin Nally is an IBM Fellow and currently the Chief Technology Officer for the Rational Software division of IBM. Martin joined IBM in 1990 with 10 years' prior industry experience. He has held several architecture and development positions in IBM including lead architect and developer for IBM VisualAge/Smalltalk and VisualAge/Java. Martin was one of a team of three that launched the IBM project that later became the Eclipse framework and he led the architecture, design and development of WebSphere Studio, IBM?s flagship Eclipse-based developer tool-suite that later evolved into Rational Application Developer
|
Presentation: "The impact of Enterprise 2.0 on application development"
Time:
Monday 15:40 - 16:30
Location:
Kammermusik
Abstract: Evolution towards more dynamic, collaborative enterprises enabled by web technologies will have a profound effect on software development. One trend will be increased use of rapid development of "situational" applications using web technologies such as mashups. The techniques of collaboration on the internet that are changing the way people approach innovation and value creation in business will also significantly impact the processes of development of all software. The general trend towards complex value-chains across companies that has been greatly accelerated by the internet will profoundly alter the economic models of software development and deployment. This talk will discuss these trends and briefly describe some of the new products that IBM is developing in response.
Presentation: "SDO and SCA: Technologies for writing and deploying service-oriented software"
Time:
Tuesday 14:40 - 15:30
Location:
Musikhuset Nr. 222
Abstract: While there are many standards for describing the interfaces between services or components in a system, standards for configuring and deploying the implementations services and components have been specific to particular implementation languages or middleware environments. Service Component Architecture - SCA - defines a standard for describing the implementations of components and services and for configuring and deploying them in a way that is independent of the implementation technology. This significantly reduces the difficulty of assembling and deploying service-oriented or component-oriented applications that are composed of elements implemented in multiple technologies.
Service Data Objects (SDO) simplify data access and representation for a wide range of service-oriented software. SDO sidesteps technology churn "the rewriting of applications to keep up with shifting technology" by encapsulating data access details to insulate business applications from technology changes. This talk will describe SCA and how it is used, and will cover SDO's wide use in Service Oriented Architecture (SOA), web services, relational data access, XML, messaging, the enterprise service bus, connectors and adapters, and model-driven architecture.
|
|
|