Strategies for Dealing With IT Complexity - CIO.com - Business T 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. “When you reduce complexity, you increase your ability to implement new solutions,” says André Mendes, CIO of the Special Olympics. “Complexity leads to brittleness and high costs,” notes Frank Modruson, CIO of Accenture.
Service Orientated Architecture (SOA\WCF) explained and defined for Executives Service Orientated Architecture (SOA) is a big business buzzword tossed into conversations at board meetings and at executive briefings. At this level, however, SOA really refers to connecting disparate systems across application, department, corporate, and even industry boundaries. This is the “Big” SOA concept, and this is the realm of the enterprise architect, and the space of million dollar Service Bus applications, SAP systems and other wonderful products. Unfortunately the fact still remains that a chain is a strong as its weakest link, if the systems hooked up to the top of the range Service Bus are not rock solid and can not be trusted to produce the correct results all the time, then the some of the true potential of the investment is lost. In future hubs i will add the jargon and provide an insight to application architects on how to construct “Little” SOA applications that achieve the non functional specifications that many projects only play lip service to.
Learn Web Development with the Ruby on Rails Tutorial Michael Hartl Contents Foreword My former company (CD Baby) was one of the first to loudly switch to Ruby on Rails, and then even more loudly switch back to PHP (Google me to read about the drama). Though I’ve worked my way through many Rails books, this is the one that finally made me “get” it. The linear narrative is such a great format. Enjoy! Derek Sivers (sivers.org) Founder, CD Baby Acknowledgments The Ruby on Rails Tutorial owes a lot to my previous Rails book, RailsSpace, and hence to my coauthor Aurelius Prochazka. I’d like to acknowledge a long list of Rubyists who have taught and inspired me over the years: David Heinemeier Hansson, Yehuda Katz, Carl Lerche, Jeremy Kemper, Xavier Noria, Ryan Bates, Geoffrey Grosenbach, Peter Cooper, Matt Aimonetti, Gregg Pollack, Wayne E. About the author Michael Hartl is the author of the Ruby on Rails Tutorial, the leading introduction to web development with Ruby on Rails. Copyright and license Welcome to the Ruby on Rails Tutorial.
Inside Architecture : SOA and the CISR Operating Models 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). To quote from the working paper: Companies make two important choices in the design of their operations: (1) How standardized their business processes should be across operational units (business units, region, function, market segment) and (2) how integrated their business processes should be across those units. That's two variables. I've illustrated these models in this way. Many folks now believe that SOA and EA will gradually combine, so that they are two parts of the same message. Why do this? That is my goal.
SOA: How to design a service - Inside Architecture I find myself in the situation of having to set down a design standard for SOA services. The thing is: SOA Services are much more than a technical artifact. They are a solution to a business architecture requirement for shared services, and the business architecture needs to exist first, or at least be tacitly understood and described, in order for the service to have any lasting value. So, first step in designing a SOA Service is to refer to the business process diagrams that your business architect has produced. For each interaction between roles, look for the data needed to make decisions. For example, if you are looking at the process flow for a new purchasing agreement, you may see steps where three different collaborating systems need data. You are collecting data for your service contract. What is the responsibility of the service? The second question above: "how will your actors be authenticated," must be answered. OK. The data points you need for the service contract are:
Mobile Web Framework About the framework The Mobile Web Framework (MWF) provides an easy way to build UC San Diego branded, mobile-optimized web applications. MWF is a standards-based, lightweight framework that supports all mobile devices containing a mobile web browser. It provides a robust presentation layer that allows applications to define a single set of markup that degrades gracefully based on the capabilities of the user's mobile device. MWF supports iPhone, Android, Blackberry, Windows Mobile, tablets, and even T9 phones. Build a mobile web application Step 1. Review the guidelines and styles for mobile user interfaces. Step 2. Download the HTML Decorator. Step 3. Build out your application using the framework Linking from the UCSD mobile homepage Review our Governance guidelines. Service Level Agreement Please review our Service Level Agreement (SLA) which documents the service provided, the levels of response, responsibilities, and process for requesting services. Contact us with questions
Sum of the Parts: Combining SOA and BPM 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. “BPM is going to be the most important part of SOA in that it lets you combine the services as your needs change. Page 1 of 2
Service-oriented architecture See also the client-server model, a progenitor concept A Service-Oriented Architecture (SOA) is a design pattern in which software/application components provide services to other software/application components via a protocol, typically over a network and in a loosely-coupled way. The principles of service-orientation are independent of any vendor, product or technology. A service is a self-contained unit of functionality, such as retrieving an online bank statement. By that definition, a service is a discretely invokable operation. However, in the Web Services Definition Language (WSDL), a service is an interface definition that may list several discrete services/operations. Services can be combined to provide the complete functionality of a large software application. A SOA makes it easier for software components on computers connected over a network to cooperate. Definitions The Open Group's definition is: Overview SOA framework Design concept
Q&A: The Role of BPM in an SOA Strategy 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. Q: Is BPM new? A: No! Q: How does BPM complement an SOA strategy? A: BPM and SOA are really two sides of the same coin and they derive many benefits when brought together. Q: Can you do BPM without SOA? A: It is possible to do BPM without SOA however companies who choose to do this will quickly run into a steep curve of diminishing returns. Q: How should an organization approach a BPM strategy? A: Organizations often start with BPM by using process modeling as a way to gain a better understanding of core business processes.