Get flash to fully experience Pearltrees
Recently I have done a few architecture reviews at customers struggling to get their SOA efforts going. The common problem of these attempts on service-enabling legacy systems to support agile business processes have been - except from system designers not grasping that SOA is in fact a paradigm shift from invoking-operations composition thinking - that they focus solely on business process management (BPM) modeling. From this model they try to identify services without having methodology to classify services into different kinds of services (entity, activity, process) , struggling with service granularity and how to identify what goes into the message and data contracts. The problem is that modeling your business processes typically misses out on the central building block of service-oriented solutions: the data and the semantics of the data as related to the business processes. This is typical for workflow models like the 'UML Activity Diagram'.
CIO — It’s called Moore’s Flaw, the flip side of the famous axiom that has driven the furious pace of IT innovation for several decades. Moore’s Law (in one of its many formulations) states that computing capability increases 1 percent per week. Moore’s Flaw posits that keeping up with this flood tide of innovation quickly becomes too difficult (and too costly) for anyone to manage. “IT complexity acts as a significant tax on IT value,” says Bob Zukis, a partner at PricewaterhouseCoopers. It’s those organizations that “have managed complexity out of their environments that are reaping the value from their IT spends.” Even more important, businesses that successfully address complexity can be more agile because their systems don’t get in the way of business process change.
I'm begining a new series on Integration. Five parts. Clear up some of the noise on SOA. This series will refer to the set of four Operating Models described in the excellent book, "Enterprise Architecture as Strategy" from the great minds at MIT's Center for Information Systems Research (CISR), Jeanne Ross and Peter Weill. If you have not read the book, that's OK. Working Paper 359 on the CISR site will provide the right level of depth (there is a free registration on the site).
We're sorry... The requested document: www.ecommercetimes.com/story/Ax6a2LNtHYez9w/SOA-for-Dummies.xhtml is no longer archived or does not exist. You may wish to use the search box below to locate articles on a particular topic. Monday - April 1, 2013 Michael Dell, CEO of the PC maker that bears his name, may be considering a buyout offer from the Blackstone Group -- a bid that competes with a deal he put together himself -- but only with some serious strings attached. Apparently he not only wants the company to retain the Dell moniker, but also wants to remain in charge.
A technology that has gained increased attention in recent years, business process management (BPM), is starting to look a lot like another technology gaining momentum, service-oriented architecture (SOA). And this similarity is leading some CIOs to apply the techniques in concert, using SOA approaches as the delivery platform and BPM approaches as the “business smarts” platform. Both BPM and SOA require you to map out business processes and figure out how they should interact with each other, with other applications, and with data sources. “You can’t do SOA without business processes,” said Judith Hurwitz, president of the Hurwitz Associates consultancy. Yet many organizations have created an artificial separation by thinking of services as just IT functions and business processes as just business workflow functions.
Sandy Carter, Vice President, SOA Strategy, Channels and Marketing, IBM was kind enough to talk to Developer.com and Gamelan.com about how BPM (Business Process Management) fits into an SOA (Service Oriented Architecture) Strategy. Q: Business Process Management (BPM) appears to be moving to the forefront in IT circles; can you please explain the growing interest? A: There are two key drivers to the increased interest in BPM within IT circles.
There is a debate going on about the relationship between BPM (business process management) and SOA (service oriented architecture). Joe McKendrick reports on part of this debate. Also James Taylor adds a coin. Nick Malik plays his role as well and there are more. To be honest, I never realized this subject as being ambiguous. But now I do.
San Francisco – Analysts practically wear themselves out saying "service-oriented architecture is something you do, not something you buy," but during last week's Burton Group Catalyst Conference it became clear too When you register, you'll begin receiving targeted emails from my team of award-winning writers. Our goal is to keep you informed on recent service-oriented architecture (SOA) and SOA-related topics such as integration, governance, Web services, Cloud and more. many users are trying to take a shortcut to SOA by buying the latest got-to-have-it software package.
BPM: Is It SOA's Reason for Being? By Kurt Mackie 07/02/2007 A service-oriented architecture (SOA) is supposed to bring flexibility to IT resources and lower costs by letting IT personnel reuse software components instead of coding from scratch. However, some experts have suggested that reuse -- the principal justification in most cost-benefit analyses for SOA -- might amount to just 10 percent . Other analysts, such as Bill Rosser, vice president and distinguished analyst at Gartner , have said that "I think the variation is much larger than that.
Egham, UK, June 26, 2007 View All Press Releases Organisations that embark on service-oriented architecture (SOA) initiatives aimed at enterprise wide deployment must pay equal attention to technical and governance issues. Gartner today said that although the risks of SOA project failure are initially associated with bad technical implementations, risks of failure due to insufficient governance are becoming increasingly significant, as SOA scope expands. “Actual implementations are showing that SOA requires more investment in service design governance and application integration best practice than current levels in most organisations,” said Paolo Malinverno, research vice-president at Gartner.
As expected, our report on the Top 30 IT Trends for 2007 generated quite a stir among readers. The study, culled from the 13 surveys CIO Insight conducted in 2006, broke down the largest upcoming trends in IT strategy , management , security , and technology . The biggest standouts our editors uncovered? Business process improvement will remain a top priority for CIOs, many of whom already consider it their most important responsibility.
Over the Thanksgiving holiday weekend I finally had time to compile my notes on a significant new Web 2.0 in the enterprise story that emerged earlier this month from the Web 2.0 Summit. At the same time, one of the inevitable recurring debates about Web 2.0 made its rounds on the blogosphere. Both pieces of news seem to be hallmarks of important and connected emerging trends on the Internet and are worth a closer look. Taking the second one first, the term Web 2.0 itself took its latest bashing from Bill Thompson in a new article at The Register that subsequently got some good play in the blogosphere, with probably the most level-headed by our very own Dan Farber .
Reuse is the most important metric by which large companies will be measuring the success of their SOA efforts – but most don’t expect high levels of reuse to happen any time soon. A new survey commissioned by BEA Systems finds that a majority of the larges t global organizations (61%) expect no more than 30 percent of their SOA services to be eventually reused or shared across business units. In fact, only five percent expect to see more than half of their services to be reused. (Survey available from BEA here .)
I am attending webMethods Integration World this week ( ebizQ is a media sponsor) and blogging live from the sessions. Next up for me was Susan Ganeshan of webMethods talking about the Business Process Management capabilities of Fabric 7 . Processes have evolved over time with lots of patchwork systems with data and process steps moving around between systems creating a "Patchwork Process".
Hewlett-Packard will apparently need close to two months to start fulfilling backorders for the (temporarily) revived TouchPad tablet. "It will take 6-8 weeks to build enough HP TouchPads to meet our current commitments, during which time your order will then ship from this stock with free ground shipping," read an email sent to customers and reprinted in a Sept. 7 posting on the Precentral.net blog. "You will receive a shipping notification with a tracking number once your order has shipped."