“As companies undertake Web services projects and build out service-oriented architectures, they will find that tools that manage and map relationships among software development assets, including existing applications, are essential for maintaining the flexibility and agility of the architecture, as well as saving significant time and money,” said Jason Bloomberg, senior analyst with ZapThink, LLC. “Logidex 2.0 enables enterprises to map assets directly to key business processes, which is a critical capability for an enterprise service-oriented architecture. Logidex 2.0′s integration directly within IDEs is also an essential feature that all enterprise application development tools must have in a service-oriented environment.”
Read more at: LogicLibrary Press Release“Hundreds of companies are embracing Web services projects, squeezing value out of every software asset to reduce development costs significantly,” said Jason Bloomberg, ZapThink Analyst and author of the report. “Forward-looking enterprises are working to broadly leverage these initiatives and tools like Logidex are essential for creating and keeping SOA models current and complete.”
Read more at: LogicLibrary Press ReleaseDownload File
“The greatest challenge facing IBM’s tools strategy is ease of use,” said Jason Bloomberg, an analyst with ZapThink LLC, a Cambridge, Mass., market research firm.
“Visual Basic .Net is winning the usability battle, actually attracting Java developers to .Net. IBM’s WSAD [WebSphere Studio Application Developer], on the other hand, is a difficult tool to use, and Rational’s tools, including the XKE and ClearCase, are also a challenge to learn and use. IBM now has a comprehensive tools offering, but they will continue to lose ground to Microsoft if they don’t improve usability.”
Read more at: eWeekFrom its inception through 2002, the primary application for Web Services in the enterprise was to simplify point-to-point integration between systems, thereby reducing the cost of integration. This application of Web Services, however, only scratches the surface of the true potential of Web Services — enabling companies to build agile business processes and IT systems that can respond to change through the use of loosely coupled, standards-based Service-oriented architectures.
The business value of such architectures in terms of the business agility they provide is substantial, but as of early 2003, only a few early adopter enterprises have built such architectures, partly because few tools for building Service-oriented architectures are available on the market, and furthermore, there is little understanding of the best practices companies should follow to build such architectures. This report seeks to clarify the requirements for realizing the value of Web Services by providing a set of emerging best pra
From its inception through 2002, the primary application for Web Services in the enterprise was to simplify point-to-point integration between systems, thereby reducing the cost of integration. This application of Web Services, however, only scratches the surface of the true potential of Web Services — enabling companies to build agile business processes and IT systems that can respond to change through the use of loosely coupled, standards-based Service-oriented architectures.
The business value of such architectures in terms of the business agility they provide is substantial, but as of early 2003, only a few early adopter enterprises have built such architectures, partly because few tools for building Service-oriented architectures are available on the market, and furthermore, there is little understanding of the best practices companies should follow to build such architectures. This report seeks to clarify the requirements for realizing the value of Web Services by providing a set of emerging best practices as well as an analysis of the tools that are currently available for building Service-oriented architectures.
Download File
From its inception through 2002, the primary application for Web Services in the enterprise was to simplify point-to-point integration between systems, thereby reducing the cost of integration. This application of Web Services, however, only scratches the surface of the true potential of Web Services — enabling companies to build agile business processes and IT systems that can respond to change through the use of loosely coupled, standards-based Service-oriented architectures.
The business value of such architectures in terms of the business agility they provide is substantial, but as of early 2003, only a few early adopter enterprises have built such architectures, partly because few tools for building Service-oriented architectures are available on the market, and furthermore, there is little understanding of the best practices companies should follow to build such architectures. This report seeks to clarify the requirements for realizing the value of Web Services by providing a set of emerging best pra
Jason Bloomberg, an analyst with ZapThink LLC, a Cambridge, Mass., research firm, picked up on that theme: “It’s not clear that IBM’s grid computing strategy is truly service-oriented–that is, exposing heterogeneous network resources as services to customers. The story is more of an outsourced systems strategy rather than a true services story. They incorporate Web services standards in the underlying grid computing technology, but the services story is lost when presenting solutions to customers. This deficiency is somewhat surprising considering that there are parts of IBM who very strongly support service orientation.”
Read more at: eWeekRon Schmelzer, an analyst with ZapThink LLC, a Cambridge, Mass. research company, said, “Rational has a great grasp on design-time modeling and business process representation. What Web Services and service-oriented architectures introduce is the notion of run-time modeling and run-time business process configuration. This is a new area, and Rational and IBM have yet to produce anything for this area… Maybe we can expect some serious progress in working to move UML and other modeling concepts closer to support the run-time nature of SOA/Web Services.”
Read more at: eWeek
SOA Implementation Roadmap