1. Sinergia entre SOA e Web 2
Sinergia entre SOA e Web 2.0: Novo contexto para as aplicações corporativas
Cezar Taurion
Gerente de Novas Tecnologias Aplicadas
Iniciativas Estratégicas
NOTE: Dave Carey, managing editor, CIO Canada, will introduce and thank you.
Thank you, Dave… And good morning everyone…I’m happy to be here with you. One of the many side-benefits of accepting invitations to speak at events like this is having the opportunity to meet and talk to my CIO peers from different companies – and being able to visit venues like this one – right next to Niagara Falls…. Pretty spectacular, huh?...
When I started planning my remarks, I was told that this assembly would use a “voting technology” – and that I should take full advantage of it to make my talk interactive. From what I know about this technology, it’s very much like being a contestant on “Who Wants to be a Millionaire?” No one mentioned anything about winning a million dollars – or that I would need a lifeline this morning....
Let’s see if this thing works…. How many of you are CIOs in this room? (WAIT FOR VOTING TECHNOLOGY & SEE RESPONSE….)
Almost all of you. How about this question. What does C-I-O stand for? (ANSWERS TO PICK FROM: A – Career Is Over, B – Chief Information Officer, C – Chief Innovation Officer) (WAIT FOR VOTING TECHNOLOGY & SEE RESPONSE….)
Interesting….
In today’s very competitive and global environment, I submit that you need to think of the CIO role as more than just the watchdog responsible for “keeping the lights on.” You need to be the next generation CIO who leverages IT to deliver business value. And that’s why the answer to the question – if you’re not already there – is that C-I-O stands for chief INNOVATION officer. That’s how you need to view your role – to guarantee success for your company – and for yourself.
Let me explain….
IM AR

2. Isto tudo faz algum sentido para vocês ?
folksonomy
AJAX
REST
Mashups
RSS
Wikis
Now, supercomputing is an area with which IBMers are very familiar.
Though we’ve certainly had competition, this company has had a large role to play in making supercomputing an everyday fact of life.
What’s really different today, however, is that you don’t need to be a big Fortune 500 company or a government to access the power of supercomputing.
It’s now available to companies of every size, in every industry – even individuals.
Social Networks
Social
Computing
IM AR

3. O Fenômeno Wikipedia
Imaginem um projeto com as seguintes características:
Aglutinar todo conhecimento humano
Autoria colaborativa
Dezenas de línguas ( verbetes em inglês e em português)
Manter histórico das atualizações, acesso rápido, flexível nas atualizações e inserções de verbetes (1500 verbetes por dia), alta demanda (um dos dez sites mais visitados)
Como gerenciar este projeto na forma tradicional?
IM AR

4. O Fenômeno das redes sociais
IM AR

5. IM AR

6. Mudanças no comportamento social…
Who do you trust? Word of mouth rank high for all
IM AR

7. Personalidade de 2006: VOCÊ!
“In 2006, the World Wide Web became a tool for bringing together the small contributions of millions of people and making them matter”
Time, December 25, 2006
A Web 2.0 está criando novas fronteiras para a colaboração e a inteligência coletiva.
The "Great Man" theory of history is usually attributed to the Scottish philosopher Thomas Carlyle, who wrote that "the history of the world is but the biography of great men." He believed that it is the few, the powerful and the famous who shape our collective destiny as a species. That theory took a serious beating this year.
To be sure, there are individuals we could blame for the many painful and disturbing things that happened in The conflict in Iraq only got bloodier and more entrenched. A vicious skirmish erupted between Israel and Lebanon. A war dragged on in Sudan. A tin-pot dictator in North Korea got the Bomb, and the President of Iran wants to go nuclear too. Meanwhile nobody fixed global warming, and Sony didn't make enough PlayStation3s.
But look at 2006 through a different lens and you'll see another story, one that isn't about conflict or great men. It's a story about community and collaboration on a scale never seen before. It's about the cosmic compendium of knowledge Wikipedia and the million-channel people's network YouTube and the online metropolis MySpace. It's about the many wresting power from the few and helping one another for nothing and how that will not only change the world, but also change the way the world changes.
The tool that makes this possible is the World Wide Web. Not the Web that Tim Berners-Lee hacked together (15 years ago, according to Wikipedia) as a way for scientists to share research. It's not even the overhyped dotcom Web of the late 1990s. The new Web is a very different thing. It's a tool for bringing together the small contributions of millions of people and making them matter. Silicon Valley consultants call it Web 2.0, as if it were a new version of some old software. But it's really a revolution.
And we are so ready for it. We're ready to balance our diet of predigested news with raw feeds from Baghdad and Boston and Beijing. You can learn more about how Americans live just by looking at the backgrounds of YouTube videos—those rumpled bedrooms and toy-strewn basement rec rooms—than you could from 1,000 hours of network television.
And we didn't just watch, we also worked. Like crazy. We made Facebook profiles and Second Life avatars and reviewed books at Amazon and recorded podcasts. We blogged about our candidates losing and wrote songs about getting dumped. We camcordered bombing runs and built open-source software.
America loves its solitary geniuses—its Einsteins, its Edisons, its Jobses—but those lonely dreamers may have to learn to play with others. Car companies are running open design contests. Reuters is carrying blog postings alongside its regular news feed. Microsoft is working overtime to fend off user-created Linux. We're looking at an explosion of productivity and innovation, and it's just getting started, as millions of minds that would otherwise have drowned in obscurity get backhauled into the global intellectual economy.
Who are these people? Seriously, who actually sits down after a long day at work and says, I'm not going to watch Lost tonight. I'm going to turn on my computer and make a movie starring my pet iguana? I'm going to mash up 50 Cent's vocals with Queen's instrumentals? I'm going to blog about my state of mind or the state of the nation or the steak-frites at the new bistro down the street? Who has that time and that energy and that passion?
The answer is, you do. And for seizing the reins of the global media, for founding and framing the new digital democracy, for working for nothing and beating the pros at their own game, TIME's Person of the Year for 2006 is you.
Sure, it's a mistake to romanticize all this any more than is strictly necessary. Web 2.0 harnesses the stupidity of crowds as well as its wisdom. Some of the comments on YouTube make you weep for the future of humanity just for the spelling alone, never mind the obscenity and the naked hatred.
But that's what makes all this interesting. Web 2.0 is a massive social experiment, and like any experiment worth trying, it could fail. There's no road map for how an organism that's not a bacterium lives and works together on this planet in numbers in excess of 6 billion. But 2006 gave us some ideas. This is an opportunity to build a new kind of international understanding, not politician to politician, great man to great man, but citizen to citizen, person to person. It's a chance for people to look at a computer screen and really, genuinely wonder who's out there looking back at them. Go on. Tell us you're not just a little bit curious.
IM AR

8. O que é a Web 2.0?
Economic
Social
Technology
Web 2.0
Web 2.0 is a set of economic, social, and technology trends that collectively form the basis for the next generation of the Internet - a more mature, distinctive medium characterized by user participation, openness, and network effects.
Source: Web 2.0 Best Practices and Principles, O’Reilly Radar
IM AR

9. O que é a Web 2.0?
Web 1.0 was about connecting computers and making technology more efficient for computers.
Web 2.0 is about connecting people,
and making technology efficient for people.
Web 2.0 changes the way businesses interact with customers
Expanding from dozens of markets with millions of people to millions of markets of dozens of people
IM AR

10. O contexto da evolução da internet
Web 1.0
Web 2.0
Web 3D
Acesso
Busca
Participar
Colaborar
Co-Criação
Páginas informativas com texto e gráficos
Usuários gerando conteúdo, blogs, wikis, mashups visando compartilhar
Ambiente altamente social, criado pelo usuário
Conteúdo
Desenvolvimento de Produtos/ Serviços, Otimização do Trabalho, Educação, Comunidades
Comunicação, RH, Compras, Marketing, Treinamento
Colaboração, Treinamento , Marketing
Negócios
Tecnologia Colaboração Pessoas
IM AR

11. Evolução das comunidades
(Limitada pela geografia)
Comunidade 1.0
(Web interface)
Comunidade 2.0
(Social computing)
Software development
RCS
SourceForge
SubVersion
Rational Jazz
Professional development
Conference
Community of Practice
Virtual conference
Blackboards
Collaboration
In-person
Tele-conf
Video Conf
E-meetings IM
Jam
As communication is mediated by technology, more people can work effectively at a distance, and some even feel a “sense of community”
Collaboration within communities is an important aspect of why we form communities.
Initial communities (0.0) characterized by geographic co-location
Current age (1.0) characterized by interaction of individuals, over the Web, with a server
The emerging community 2.0 will be characterized by the interaction of people with people over the Web.
Communities have been evolving in their “degree of digitization”, as shown by the arrows.
Not all segments are equally evolved (can draw with the end points of arrows at somewhat different points in the spectrum)
It might even be interesting to note that "old" technology like MMOGs is probably pretty far along the spectrum, while most collaboration software is not.
RCS
The Revision Control System (RCS) manages multiple revisions of files. RCS automates the storing, retrieval, logging, identification, and merging of revisions. RCS is useful for text that is revised frequently, including source code, programs, documentation, graphics, papers, and form letters.
RCS was first developed by Walter Tichy at Purdue University in the early 1980s. RCS design was an improvement from its predecessor Source Code Control System (SCCS) (see GNU CSSC). The improvements include an easier user interface and improved storage of versions for faster retrieval. RCS improves performance by storing an entire copy of the most recent version and then stores reverse differences (called "deltas"). RCS uses GNU Diffutils to find the differences between versions.
Source Forge
SourceForge is a collaborative software development management system. SourceForge is proprietary software and is sold by VA Software. It provides a front-end to a range of software development lifecycle services and integrates with a number of open source applications (such as PostgreSQL and Subversion).
SourceForge.net is a centralized location for software developers to control and manage open source software development, and acts as a source code repository. SourceForge.net is hosted by VA Software and runs a version of the SourceForge software. A large number of open source projects are hosted on the site (it had reached 125,090 projects and 1,352,225 registered users as of July 2006), although it does contain many dormant or single-user projects.
The SourceForge software, which was originally itself open source software was commercialized by a closed-source license. The latest available version of SourceForge, version 2.5 from the CVS repository, was forked by the GNU project as Savane. It was also later forked as GForge by one of the SourceForge programmers.
SubVersion
Subversion is an open source application for revision control. Also commonly referred to as svn or SVN, Subversion is designed specifically to be a modern replacement for CVS and shares a number of the same key developers.
Projects using Subversion include the Apache Software Foundation, KDE, GCC, Python, Samba, Mono, PuTTY, Zope, Xiph, GnuPG, CUPS, Wireshark, TWiki, Ruby on Rails, Django, Bioconductor and many others. Many projects have migrated to Subversion due to the comprehensive project management solution Trac, which originally required Subversion. SourceForge now also provides Subversion hosting for its open source projects, and the new Google Code uses it exclusively.
Education
Classroom
Distance
E-learning
Virtual Univ
Peer-to-peer learning
Comunidades
Marketplace
Bricks & Mortar
Online Shopping
eBay
Amazon
Games
Board
Video
Computer
Internet
MMOGs
Digitalização
IM AR

12. Web 2.0 : Internet como “The Platform”
Tools: RSS, AJAX, PHP, Ruby
Techniques: Mash-up, wiki, tagging, blogging
Standards: REST, XHTML
The Web as
“The Platform”
Light-weight programming models
Rich user experiences
Finally here is a depiction of Web 2.0 as a growing cultural organism with the tools, standards and techniques enabling it in blue on the top and some of the key characteristics of the organism on the bottom
- simplicity (light-weight prog. models)  Only easy things will continue to propagate (PHP)
- community-development is represented here in “software that gets better with the more people use it” and “harnessing the collective intelligence”
- move to web services that are published on the web, not hardened and shrink wrapped
- assembly of consumable pieces which enable architectural participation from end-users and the community
- again bandwidth, graphics, and graphic app models are driving users to demand rich user experiences - drag and drop, location based visualizations,  the end of command line text windows!
====================
Google, by contrast, began its life as a native web application, never sold or packaged, but delivered as a service. Customer paid for the service, directly or indirectly
No scheduled software releases, just continuous improvement. No licensing or sale, just usage. No porting to different platforms so that customers can run the software on their own equipment, just a massively scalable collection of commodity PCs running open source operating systems plus homegrown applications and utilities that no one outside the company ever gets to see.
At bottom, Google requires a competency: database management, not a collection of software tools, it's a specialized database. Without the data, the tools are useless; without the software, the data is unmanageable. Software licensing and control over APIs--the lever of power in the previous era--is irrelevant because the software never need be distributed but only performed, and also because without the ability to collect and manage the data, the software is of little use.
In fact, the value of the software is proportional to the scale and dynamism of the data it helps to manage.
Much like a phone call, which happens not just on the phones at either end of the call, but on the network in between, Google happens in the space between browser and search engine and destination content server, as an enabler or middleman between the user and his or her online experience.
Small pieces loosely joined, or “re-mixed”
Software that gets better as more people use it
Services, not packaged software
Harnessing collective intelligence
Architectural participation
IM AR

13. O conceito da Cauda Longa...
The Long Tail
Targeting niche markets - expanding from dozens of markets of millions of people to millions of markets of dozens of people
Examples: Google, Netflix, Amazon
Network Effects
Product or service is more valuable the more people that use it (e.g telephone, , instant messaging…)
Examples: eBay, MySpace, Craigslist…
IM AR

14. Long-tail & Software : Situational Applications
Enterprise Application Long-tail
Situational Applications
Applications
Built to Last
Mission Critical WS
WS CE & Open Source
Be specific about where Zero plays
IM AR

15. Definition: Situational Applications
Situational application development involves aggregating, customizing, or extending an existing collection of simple web services
Built to solve an immediate, specific business problem
Typically performed by non-traditional programmers (e.g., business professionals, analysts, other IT staff, etc.)
Makes use of pre-existing software components or services such as spreadsheets, report generators or vertical business applications already in use
Manipulates static and increasingly dynamic content – information-centric
Accelerated by a community-based development approach
This is what we see emerging … Situational applications. Let’s define this term at least in terms of its characteristics.
Built out of assembling pre-written applications/ or web services to
- meet an immediate business need (e.g. tracking sales of particular items based on weather conditions)
- huge increase in number of people creating apps (students creating apps to locate cheapest gas prices)
- reusing and remixing pre-existing apps thereby increasing their versatility and broadening their use
- instrumenting applications that manipulate massive amounts of static and dynamic content
- leverages components already built by the community and leverages the wealth of knowledge resident in the community
The simplicity of integration, rapid data transmission, and connectivity of the web is enabling integration to be done at the edges of the web on a global scale (We are familiar with integration being done at the central office – this new paradigm permits integration at the edges – closer to the customer. The resources that are drawn upon may be available anywhere on the web, i.e., globally
Integration is pushed to the edges and on a global scale
IM AR

16. The Accelerating Evolution of Software
Situational application development paradigms are emerging which will challenge traditional IT development
New tools and approaches to develop situational applications – applications built with simplicity, efficiency, and just enough function to solve the business problem at hand – are emerging
Proliferation of easy-to-use software, tools and techniques (e.g., Web 2.0, LAMP, PHP)
Wide availability of domain-specific web services (e.g., Google maps, UPS, NoAA)
Simple application paradigms to manipulate, integrate, and publish dynamic content (e.g., QEDWiki)
The rapid growth in computer literacy and non-traditional programmers
These trends will result in significant challenges for enterprise IT environments
Supporting and enabling community-based development within the enterprise
Refactoring interfaces to enterprise applications as consumable web services
Dealing with the growing heterogeneity in the IT environment
Facilitating the development, deployment, and management of situational applications
Situational application development approaches will fundamentally change the way applications are developed and deployed, accelerating the proliferation of consumable web services
Software development is currently going through a period of rapid evolution enabled by availability and ease of use of the web.
New was of developing applications to meet specific “situational” needs are emerging which will ultimately create new challenges for traditional IT
The new development approaches are based around simplicity and efficiency of assembling pre-written apps into new situational applications that have just enough function to meet the business issue that is being addressed.
Enabling this are
SW tools (LAMP , PHP)
availability of web services (Google maps)
application assembly tools which provide greater function with more ease (QEDWiki)
And significantly by the web fueled growth of computer literacy
These trends are happening and healthy growing enterprise IT environments will have to react and embrace these changes by :
supporting community based development approaches
making enterprise apps accessible by web community as web services
managing the increased heterogeneity of this environment
facilitating emergence of situational apps
The simplest, most efficient development approaches will naturally proliferate by user communities on the web thereby further accelerating the move to web services
IM AR

17. Evolution of Enterprise Applications
Applications built by LOBs and end-users, customizing and aggregating services as needed
Applications initially prototyped by LOBs, then rebuilt by IT departments
Enterprise applications built by IT departments
Enterprise Application Evolution
Web Services Enabled World
Here we look at the evolution of enterprise applications with a development and system lens.
Initially applications ran on mainframes and they were built by IT depts. End-users interacted with a customer service rep who worked directly with the application.
Then we moved into the client-server era where LOBs had compute power on their desk top and could prototype apps which were later hardened by IT depts. End-users began to have self-service interactions with enterprise apps via web (e.g. checking flight information)
Now we are moving into an era where web services are the platform and applications are built and deployed by LOBs and end-users on an as needed basis. Enabled by open standards, common architectures, rapid connectivity and accessibility
==============================
Mainframe world is also an agent-enabled world and end-users interacted with such systems via a CSR
The client-server world from the end-user point of view is also the web-based self-service world
In the web-services world, end-users can customize and integrate applications
Note: The client-server world was characterized by disaggregated systems and lack of central control that created chaos and management nightmare. The new web services world as the following characteristics that mitigate:
Open standards
Data model
Common architecture
Client-Server World
Mainframe World
Time
60’s-80’s
90’s-00
00-10’s
IM AR

18. Situational Application Example – Scipionus.com
Legend:
– events
– changes
– 50 latest
Here is a situational app that is indicative of how immediate needs/issues can be handled.
Scipionus.com launched three days after Katrina
has become a giant visual "wiki" page, attracting tens of thousands of visitors who collaborated in creating a public document of astonishing detail to locate and track people in need during the disaster.
Built in one day, one engineer with community information
"Corner of 1077 and Brewster. Lots of trees down, but no water damage. No electricity and no phone at the moment 8/31 2:00pm," reads one of hundreds of entries.
Leverages Google maps made available as a Web Service
Google maps garners 10% share of online maps – 2x ahead of Microsoft’s MapPoint
Situational applications have played a large role in enabling Internet speed adoption of maps
Est. number of “applications” leveraging Google maps ~ 600
Authored by end users - a majority in JavaScript
Application built by one person in one day, leveraging Google maps web service
IM AR

19. Situational Applications: The primordial mashup
craigslist
Google Maps + =
IM AR

20. Mashups: Script, scrape, shred, snip, mash, map…
Mashups: Script, scrape, shred, snip, mash, map…. That is the new programming fashion. .
Mashups like Coffee integrate disparate data sources through simple scripting tools by combining existing web services into entirely new applications
Typically sourced from a third party via a public interface using Web feeds (e.g. RSS or Atom) and JavaScript
IM AR

21. AccuWeather™ Overview
“(Web 2.0) Widget-delivered weather information allows our clieants to be more productive in utilizing AccuWeather data to identify and exploit business opportunities while at the same time helping clients manage risks imposed by adverse weather conditions.”
Overview
SMB company that aggregates weather content, crushes forecasts that are consume by diverse businesses
ProfessionalPlus staff that assembles custom forecast models for businesses
ModelPlus - suite of advanced forecast modeling solutions such as StormTimer
Example: CSX - sends train route information to AccuWeather - compares with severe weather to “message” CSX systems of severe, situational conditions
AccuWeather Opportunity
Backlog of custom dashboards growing fast
Customers asking for “flexible” mash-ups to meet ongoing changing business needs
Customize costs high given current technology foundation
Extend current weather content subscription to enabling user-customizable dashboards
Seeing growing number of weather widgets, branded with AccuWeather - with poor quality - potential reflection on company
Key take aways:
IBM direction is to embrace and support Web 2.0 Technology and Behaviors. We’re investing here.
IBM is better positioned than current Web 2.0 players due to our SOA experience and portfolio.
IM AR

22. Porque as empresas precisariam de Web 2
Porque as empresas precisariam de Web 2.0? Because the Landscape has changed
Causa
The World is Flat
Information Overload
Business Changes faster than IT can respond
CIOs can’t afford to serve the “long tail”
Efeito
Empowerment and independence of Knowledge worker
Knowledge Worker is now the Situational Application Assembler.
Web 2.0 enables the Knowledge worker to collaborate and create “good enough” solutions that satisfy their ever changing needs
Issues
Productivity of Knowledge worker – Tools for new programming models
Reliability and Manageability of decentralized IT applications
Search capabilities to enable reuse of long-tail solutions
IM AR

23. IT buyers view the Web 2.0 concept favorably
“Which of the following best describes your reaction to the term ‘Web 2.0’?”
Strongly Negative,0%
3% Ï’ve not heard the term Web 2.0 before
Negative, 3%
20% Strongly Positive
Neutral,29%
Positive, 44%
Base: 275 IT decision-makers at US companies with 500 or more employees
Note: “Don’t know” responses excluded
Source: Forrester Research, June 2007 United States Web 2.0 Online Survey
IM AR

24. “How businesses are using Web 2.0: A McKinsey Global Survey”
IM AR

25. Tecnologias que compõem a Web 2.0
Embora ainda estejamos na fase do “Hype Cycle” precisamos entender o assunto e (re)agir!
Visibility
Post
Press conf
Phone
Fax
Tecnologias que compõem a Web 2.0
Search Engine Opt.
Blogs
Direct mail
Word of Mouth
Wikis
newsgroup
RSS
Social networks
Webcasts
database
Podcasts
Citizen journalism
Instant messaging
Tech
Trigger
Peak of inflated
expectation
Slope of enlightenment
Plateau of productivity
IM AR

26. Types Of Enterprise Web 2.0 Apps
July 2007 “Developing Enterprise Web 2.0 Applications”
Types Of Enterprise Web 2.0 Apps
IM AR

27. Junção dos mundos SOA e Web 2.0
Web 2.0-class Apps
Web 2.0 technologies & services - defacto standards
Content/data focused
Outward-Facing
Very Loosely Coupled
Security: Assume Everything is a Threat
SOA-class Apps
Standards-based (WS-*,…, SCA)
Normalized Transactions
Inward-Facing
Somewhat loosely Coupled
Security: “lockdown”
Gartner™
IM AR

28. Reshaping of Enterprise Software
Enterprises Putting Web 2.0 to Work
Focus on Simplicity - empowering content-centric developers
Data Driven - business value centered on content
Remixability - new business opportunities to COMBINE content
OpenAPIs - building/extending ecosystems both with ISVs & customer COLLABORATION
Rich Internet Applications - improved EXPERIENCE leads to improved revenue
User Generation Content - active participation & self organization to influence product development
IM AR

29. Web 2.0 permite criar uma Global SOA
Enterprises are exposing more services and feeds to the Web …and consuming more services and feeds from the Web
Exposing Enterprise Services to the Web extends your enterprise globally and simplifies:
Development
Composition of Services
Deployment and accessibility
QoS: Performance, Scale, Security
IM AR

30. SOA e Web 2.0: Mudanças no contexto: processos, tecnologias, skills…
Traditional (Transactional)
Structured design and programming
Code Review
Function test
Quality test
Performance test
Handful of large applications on 100s of machines
Often dedicated – several machines per application
Careful, formal change management
Slowly evolving applications
Changes are major
Model
Situational (Collaborative)
Unstructured programming
Little discipline
No formal test process – using the application is test
Thousands of small applications on handful of machines
Each machine has hundreds of applications
Change management is a huge challenge
Rapidly changing applications
Changes generally minor
Assemble
Deploy
It is important to note that situational applications are not appropriate for all applications. We will still have the need for traditional, transactional to build robust, mission critical applications.
Note: In traditional enterprise environments, we run a small number of apps on 100s of machines. Sit apps will give rise to an environment where 1000s of apps may run on a small number of machines. This changes how applications are deployed and managed.
Manage
IM AR

31. SOA e Web 2.0: Mudanças no contexto: processos, tecnologias, skills…
Increasingly, applications will be developed or modified in departments and LOBs, not just in IT shops
Situational applications are being developed in simple ways (e.g., Web 2.0), and will integrate and run across different development environments (J2EE, LAMP, .Net, …)
Situational applications will integrate components from within the enterprise and from the outside (other enterprises, internet)
The new demands are derived from systems optimized for 1000’s of transactions/s through 2-3 apps  3 transactions/s through 1000 applications
100 new apps a day, some of which may disappear very quickly. A few may be sticky enough to remain for some time. These will be adopted by IT depts. In which case, the issue of change management, configuration, compatibility between existing and new (traditional vs situational) applications)
“Everyone is a programmer” – and can develop programs using simple tools by aggregating available components and services. And then re-aggregating again.
Therefore, corporate IT will be challenged to facilitate the development, integration, and management of situational and enterprise applications
IM AR

32. SOA e Web 2.0: Mudanças no contexto: processos, tecnologias, skills…
Model
Gathering business requirements, discovering available services and components, and simulating the desired business processes
Compose applications that use services residing in different environments using natural metaphors (e.g., access EJB or web service from PHP)
Testing – provide the developer with an environment that resembles the deployment environment (e.g., testing solutions across multiple environments)
Assemble
Deploy
Configure distributed applications so that different pieces can run in their associated environments
Coordinate upgrades of dependent pieces across heterogeneous environments using a common set of tools
Model: Designing, gathering business requirements, running simulations
Assemble: Development and composition of components and services
Deploy: Configure, coordinating upgrades
Manage: problem determination, change management, tuning, load balancing
Today, upgrades must be done piecewise using different mechanisms for each environment
Today, each vendor console is able to collect and display run-time information only from that particular environment
Manage
Facilitate problem determination in a mixed environment (e.g., stitching together traces and logs from different application environments)
Autonomic resource management (e.g., tuning and load balancing optimized across application environments)
IM AR

33. Obrigado pela Atenção! Cezar Taurion
Gerente de Novas Tecnologias Aplicadas
Iniciativas Estratégicas
Visitem meu blog em:
NOTE: Dave Carey, managing editor, CIO Canada, will introduce and thank you.
Thank you, Dave… And good morning everyone…I’m happy to be here with you. One of the many side-benefits of accepting invitations to speak at events like this is having the opportunity to meet and talk to my CIO peers from different companies – and being able to visit venues like this one – right next to Niagara Falls…. Pretty spectacular, huh?...
When I started planning my remarks, I was told that this assembly would use a “voting technology” – and that I should take full advantage of it to make my talk interactive. From what I know about this technology, it’s very much like being a contestant on “Who Wants to be a Millionaire?” No one mentioned anything about winning a million dollars – or that I would need a lifeline this morning....
Let’s see if this thing works…. How many of you are CIOs in this room? (WAIT FOR VOTING TECHNOLOGY & SEE RESPONSE….)
Almost all of you. How about this question. What does C-I-O stand for? (ANSWERS TO PICK FROM: A – Career Is Over, B – Chief Information Officer, C – Chief Innovation Officer) (WAIT FOR VOTING TECHNOLOGY & SEE RESPONSE….)
Interesting….
In today’s very competitive and global environment, I submit that you need to think of the CIO role as more than just the watchdog responsible for “keeping the lights on.” You need to be the next generation CIO who leverages IT to deliver business value. And that’s why the answer to the question – if you’re not already there – is that C-I-O stands for chief INNOVATION officer. That’s how you need to view your role – to guarantee success for your company – and for yourself.
Let me explain….
IM AR