SOA Testing

October 31, 2008 by torryharris

 

SOA Testing

Testing activities such as design, analysis, planning and execution must happen throughout the entire SOA project life cycle. Traditional software testing that focused on code-level testing has evolved with Distributed and Web Service architectures. Web application testing has introduced more testing of business logic through the application’s user interface, which has proved to be critical when deploying new solutions. With SOA, the need to test the business logic still exists; however, many SOA services will not have a user interface, which is one of the new challenges to your test organization.

 

Test Model

The V-Model is a suitable test methodology that enforces testing discipline throughout the project life cycle. The project starts with defining the Business User Requirements. The V-Model would recommend that the Business Acceptance Test Criteria for these defined requirements are defined and agreed before moving to the start of the technical design phase. Before moving to the next phase/level of technical design, the model recommends test criteria defined for that level of technical requirements, and so on. The V-Model is simply encouraging the project team to continually determine how they would successfully test the project deliverables.

 

SOA testing model

SOA testing model

The V-Model is a suitable test methodology to deliver SOA projects for some following reasons.

  •  It encourages a top-down approach with respect to defining the business process requirements, high-level functional technical design, security etc.
  • It then encourages a bottom-up test approach – test individual functions within a service, test an individual service then test a composite set of services through to testing an integrated process and finally testing a complete business system. SOA is ‘loosely’ coupled services and that is why a bottom up test approach is recommended.
  • The levels reflect different viewpoints of testing on different levels of detail.
  • The V-model encourages testing throughout the entire Software Development Life Cycle.

SOA Implementation

August 22, 2008 by torryharris

SOA Implementation

 

The information overload on SOA is largely on describing the merits of SOA, principles of SOA and the vast variety of products intended to address SOA needs. There is, however, an acute scarcity of information on SOA implementation to bridge the gap between wanting to get started and actually deploying a game plan where the rubber hits the road. This document is written to identify the factors to be considered, articulate the principles and questions to be asked that will drive the decisions within each enterprise towards creating a road map for implementation.

 

Separating reality from hype, distilling the essential from the desirable, explicitly addressing the how-to, nuts and bolts of an SOA implementation is the topic addressed in this document. It’s about getting going, showing investors the incremental rewards of SOA adoption and continuing on the straight and narrow path that links deployment of technology with business goals.

 

Whether you are contemplating SOA, are or actually committed and well along the way, a back to basics checklist is a good thing to have. This document includes a review of the following topics that will help to retain focus and direction.

 

  • Your reasons to implement SOA
  • First steps and short-term goals
  • Long term Objective
  • Products and Partnerships
  • Return on Investment
  • Impact on Business as Usual
  • A Stable approach to Change management
  • Glossary of SOA Terminology
  • Summary and Help Lines

 

Introduction

 

 

The benefits of SOA have been described and accepted. The question faced by many is: How to get started? Where to get started? Expectations that may be deemed reasonable and the return on investment (ROI) that can be demonstrated during each phase of investment have to be identified. Further questions abound regarding the choice of products, partners and ramping up of in-house IT capability. Of course, while there is no common one-for-all solution, the implementation of SOA is much like any large-scale migration, with a few notable differences, particularly regarding governance. The purpose of this document is to identify the factors to be considered, articulate the principles and questions to be asked that will drive the decisions within each enterprise towards creating a road map for implementation.

 

 

1.    Your reasons to implement SOA –Two classes

 

While there are several frustrating experiences with legacy architecture that serve to propel the drive towards SOA, the drivers usually fall into two classes of compelling reasons, that either singly or together form the impetus to actually get started with SOA.

 

1) The need to respond quickly to change in business needs

2) The need to reuse technical assets across a larger enterprise

 

Symptoms include acutely painful situations where “the business” requests rapid and seemingly endless minor changes in business processes that incessantly require significant application level code changes within time lines that seem impossible. On a less painful but equally urgent basis, mergers and acquisitions, integration with 3rd parties/partners etc. extend the borders of e-commerce to include a wider range of activity with suppliers and clients, through public information highways. These requirements, either mandated by management or simply viewed as a step to optimize development and support costs, call for the creation of standardized assets, that once created, can be run anywhere.

 

 

2.    First steps and Short term Goals

 

Once the primary driver or business reason that compels a service-oriented approach is articulated and agreed upon by all stakeholders (from the business and technical communities), it becomes relatively easier to establish the milestones that are to be reached. This approach is consistent with one of the commonly observed principles of successful SOA implementations. SOA is almost always best realized through an evolutionary process – an ongoing conversion of services that increasingly perform autonomously and thereby can be reused. This evolutionary approach does not necessarily mean a long drawn out exercise, it simply means that a sequence of steps have to be defined. The steps could become progressively larger and address a wider range of use cases, as each successful installation is completed and seen to work.

 

If your reasons to SOA happen to fall into either of the two categories described above, then here are some early steps and goals towards the realization of a flexible infrastructure:

 

1) “Which business processes are most frequently changed?” Identification of the application or sets of applications that are impacted by the most frequently required changes requested by the business. This is a first step that gives us an idea of what we will be dealing with, though in small bites. A parallel run, involving both legacy and the different versions, each incorporating progressively more services being exposed in each iteration, will be required during the transition.

 

2) Documentation of the Use cases that will be impacted by changes to these applications; this will include a study of client-based executables or interfaces, invoked by each user community. The purpose of this study is to allow a fuller view of the scope and establish a narrower set of “important victories”.

 

3) Review of server based application code with a view to identify and abstract business processes from application functionality. This exercise accomplishes the goal of allowing us to form a reasonable estimate of the work and time lines involved.

 

4) Potential latency issues are examined as a result of re-use and content heavy XML, as well as security issues in opening these assets for access. These considerations will determine the classes and types of products to be used in the enterprise architecture. Once this is done, the first sketch of the target architecture is visible.

 

5) Start building and exposing the separate functionality that is identified to be a part of one or more business processes. At this time, it is important to get started. You need a registry and/or a repository that describes the service, so incoming messages can find them. At first, the SOA could be made available within the firewall, tested, and then subsequently made available through holes in the firewall that are opened specifically with relevant security measures to allow access to nominated users.

 

These short-term goals represent a set of actions that will lead to a functioning SOA. The SOA can scale up – as we identify further functionality that can be reused, leading to a progressively larger implementation. We call this a Bottom-Up SOA effort.

 

A Top-Down effort is also required. The purpose of this is to establish some basic ground rules that the entire SOA will live by. This is much like the role-played by a Federal government. In SOA parlance, it is simply called Governance.

 

3. Long Term Objective

 

An efficient and agile technical environment is traditionally demonstrated by time and cost measures. Therefore, these measures must govern the path towards the long-term objective and determine the success of its eventual realization.

 

The success of the target architecture should be measured by:

 

1) Cost and time to develop and maintain the assets that perform the required business processes and the tangible and intangible returns from executing these business processes.

2) The implementation of automated triggers to fulfill a larger number of routine business activities.

 

The first criterion is realized through building granular components and making them available for re-use through an expanding repository, progressively made available to a larger community inside and outside the firewall. This community will include third party suppliers and partners and hence the creation and publication of these assets must adopt industry standards.

 

There are three aspects of the move to SOA that need to be better-understood in-terms of their relevance to each stage of SOA evolution. The purpose of doing so is to retain our long-term objectives within each, but not let them, individually or collectively, paralyze us or prevent us from getting off the ground.

 

Governance -

The purpose of governance is to avoid lack of conformity between applications. It is difficult to establish all the ground rules when you start. As said before, SOA is an evolving process, in terms of standards, in terms of products and its use within the enterprise. Some fundamental rules common to a federated structure will be defined at the outset and modifications are inevitable.

 

Service Granularity -

This is one of the most discussed and debated topics today. Since it refers to the scope of functionality that a service exposes, one would need to plan the grain of the service based on the current application infrastructure environment. Waiting until the “right” level of granularity is established can become a never-ending discussion with no perfect answer; hence, it is important to understand your environment and plan/implement the granularity of your services in a simple and generic way, based on your current and foreseeable needs. SOA is an evolution; coarse grains may have to be decomposed into finer grains at a later time depending on the business process that is required at the time. This fact should not deter us from getting started.

 

Tools / Products -

BPM, BAM and EDA are some of the terms associated with the realization of SOA. They form part of the second group of long-term objectives and there are a wide range of products available within these categories. It is important to note that BPM and BAM products are not an essential part of an SOA and are in fact not advisable during the early stages. An increasing awareness of their specific benefits could be developed as progress is made and they could be introduced at the right time to enhance considerably the value of an SOA.

 

 

 

 

 

 

 

SOA Governance

August 6, 2008 by torryharris

Governance

 

The purpose of Governance is to avoid lack of conformity between applications. It is difficult to establish all the ground rules when you start, SOA is an evolving process, in terms of standards, in terms of products and its use within the enterprise. Some fundamental rules common to a federated structure will be defined at the outset and modifications are inevitable.

 

SOA Governance

 

SOA Governance is about ensuring that each new and existing service conforms to the standards, policies and objectives of an organization for the entire life of that service.

 

SOA Governance plays an increasingly important role in today’s challenging business environment. It provides structure, commitment and support

SOA Governance

SOA Governance

 for the development, implementation and management of SOA, as necessary, to ensure it achieves its objectives.

 

 

 

SOA Governance provides the following benefits:

  • Realize business benefits of SOA
  • Business process flexibility
  • Improved time to market
  • Maintaining Quality of Service (QoS)
  • Ensuring consistency of service
  • Measuring the right things
  • Communicating clearly between businesses

Offshoring – The 6th Vertical

August 1, 2008 by torryharris

Abstract

The growth in offshoring of IT services started to spurt in the late Eighties. The industry spawned market valuations, investor wealth and employment in India, at a pace and scale, unparalleled in the Indian economy. IT professionals enjoy perks and salaries significantly above other wage earners with similar qualifications, even other engineering degrees. This anomaly is now normalizing, the reasons given ranging from the weak dollar to the influx of the larger MNC’s who have set up shop in India with access to the same skill base. Customer satisfaction surveys frequently indicate that service levels from providers are either mediocre or just about acceptable, and in some cases, there appears to be a fairly large gap that is growing between what is expected and what is offered, and more so in what is delivered. The answer does not seem to be in simply improving traditional parameters of service, but perhaps indicates that a new segment of clients are now seeking to embrace offshore benefits and their requirements are to be met quite differently  from the carefully designed and well documented processes that govern present delivery models. This group of clients seems to have service level requirements bound by their genre and not by their industry vertical. So much so, there is almost something elusive, almost surreal, in the expression and satisfaction of their needs. This community is therefore termed as the ‘Sixth Vertical’ and this article seeks to prove their growing widespread presence, increasing economic power, and what they almost uniformly want from their service providers.

Introduction

Traditionally, service offerings are vertical based with a separation of business units by industry. A grid allows technical skills across horizontals to service each vertical that in turn services the external client who is classified by the business he is in. Banking and financial services, followed by telecom and health care are the significant consumers of these services from India. Typically, routine services that administer these industries are transferred to India; the work includes development and maintenance of technical solutions as well as back office functions, and in some cases, data and call centers.

While cost savings that prompted this migration have been realized, there are now some questions about the sustainability of the model, in part due to rising costs in India coupled with decreasing customer satisfaction levels. This may well be because the elements that are to be outsourced are not as well understood as we would like them to be. It is not just about lack of clarity in the requirements gathering phase, but something more complex in that the subjective parts of the relationship, have now  started to more profoundly influence the payback these relationships are required to offer. Requirements are solicited by analysts, quantified and clearly articulated within development projects and service level agreements are drafted to quantify the level of service in terms of measurable units that a vendor is to provide.  The difficulty lies in the fact that the target is now a perpetually moving one, and the requirements are defined on the fly by a community of influencers that are often not in direct contact with the provider. The users are often a community removed and increasingly more powerful. Attempts to harness their power by translating their voice into the offering in real time have not met with consistent success.

User Power

 Vertical expertise in the traditional sense is no longer a rare commodity. Unfortunately, for those who have toiled long and hard to acquire it, vertical expertise becomes legacy faster and faster. Often, experience amongst the practitioners within an industry leads to rigidity, becoming a handicap, as it contorts into a barrier to thought, even preventing the use of current tools that homogenize erstwhile disparate industries. In extreme cases, it manifests itself in arrogance. The user, even a relatively inexperienced user, now has unprecedented power to shape the object that he uses, be it in design or in functionality. The Internet is the great leveler. The progressive enterprise has started to relinquish   power over its offering, becoming a vehicle that is driven by the user, evaluated frequently by the user, and in many cases just acting as the medium of expression of the user’s perception of value. Terms like Web 2.O express this concept that has extended beyond the Web in guiding the core of a business to becoming what its customers want it to be.

Emergence of the 6th Vertical,

The products in the marketplace that enable technology to satisfy the needs of business, with increasing flexibility, are seeking to allow a business to retain their differentiators. However, the service providers themselves have become less flexible, even somewhat rigid in determining how a customer should use their industry specific offerings.  

In the late Nineties and in the first part of this decade, large enterprises successfully offshored worldwide, the replicable parts of their business processes. Assembly lines were built overseas, to take advantage of labor costs and efficiencies that could be realized by a modernized assembly line, where cost per KLOC was reduced and defect density was monitored and improved. While this objective was realized, particularly in support, a vague dissatisfaction started to assert itself.

These rumblings that ‘all was not well’, took the following shapes. Firstly, customer satisfaction ratings, never really evidenced a glowing satisfaction, in fact the vast majority ranked their experiences as “somewhat satisfied”.  Secondly, increasing costs incurred by service providers, due to competition for resources, and the lower net realization due to currency exchange rates, were not compensated. Consequently, sales prices uniformly remained pretty much at the same level, despite various attempts by service providers to go up the food chain and charge premiums on consulting services. The high end business solicited by the large offshore providers, never really took off and even today accounts for a small fraction of overall revenues, and in itself, in many cases has yet to demonstrate profitability. Thirdly, and perhaps most damaging, was the fact that a variety of less structured buyers, and not just the SMB community, found the offshore experience quite disruptive and unable to fit in with their internal teams, technical or business, that were required to work closer.

This group is willing to pay the premium on higher, intimate service levels when compared to the assembly line offering. The structure required to service such a group is emerging fairly clearly.

The characteristics of this group, the 6th Vertical, that is growing by the day, and will continue to grow as service levels rise across the world, are evidenced by a variety of distinct symptoms displayed by the group, when exposed to the solutions offered by traditional service providers. These symptoms may include most or all of the following

·          Indifference and lack of excitement

·         Price discussions early and frequently with value received or provided unrecognized

·         A disquieting realization by the client that this relationship is not sufficient to guarantee business longevity

·         Supplier versus partner mentality, glimpses of mutual profiteering

·         Unwillingness to share plans

·         Slippages, lack of accountability and two way suggestions to improve

It is interesting to see that the 6th Vertical co-exists within other verticals, thereby increasing its own size. Large multinationals that require assembly line production units also require more sensitive offshore partners to work with, for their other needs. While the larger vendors set up industry based   Business Units built to service a Vertical in the traditional sense, they often find their bulk production systems do not lend themselves to think fast or change fast enough to cater to those sub sets within the larger enterprise that seek a more agile offering.

The offshore provider, who caters to this community, has a potentially larger customer base than ever before. If from the ground up, he creates a platform with this target in mind, in terms of human skills, attitude, and technical skills, he has an unprecedented opportunity to profit and grow, on a larger scale than his predecessors who built their service platforms to cater to one or more of the traditional verticals.

Their requirements are addressed by a variety of measures common to this group. The financial results of doing so from offshore are impressive. Quite naturally, the group is seeking to purchase something more, for less, when compared to the price of customer centric service within their native habitats that is extremely expensive, if at all available in terms of a 24 x7 implementation, on the scale they demand it.

 

Maslow and the hierarchy of needs as expressed in software services

Abraham Maslow, an eminent American psychologist in the middle of the last century, best known for his work on human motivation that guides behavior and consequently influences buying patterns, conceptualized the pyramid of needs of the individual.

It may be interesting to explore a parallel, substituting “the business” for the individual, and extend his theory to the present context.

Maslow stated:  Deficiency needs must be met first. Once these are met, seeking to satisfy growth needs drives personal (business) growth. The higher needs in this hierarchy only come into focus when the lower needs in the pyramid are satisfied. Once an individual (business) has moved upwards to the next level, needs in the lower level will no longer be prioritized. However, if a lower set of needs is no longer being met, the individual will temporarily re-prioritize those needs by focusing attention on the unfulfilled needs”. In the case of the business, the deficiency needs are similar to those articulated by Maslow in 1943 with reference to humans; breathing, food and water, termed as “the bread and butter” or the basics of a business model – the ability to produce somewhat efficiently and keep “churning it out”.  The first step up the pyramid would be the need for security and safety. That too is in line with business goals, once the basic model is seen to function. Rapidly, we move to the need of a business to reach “self actualization” as do humans, strikingly characterized by the very same elements, a desire to contribute, morality or the desire to do the right thing, lack of prejudice and an awareness of facts. Current business trends and growing corporate awareness, in many cases, enforced by law, demonstrate that businesses, their employees and their customers are increasingly preoccupied in satisfying these so called higher needs, as the deficiency needs are satisfied by the efficiencies of the production line. Al Gore and others occupied with sustainability, be it in the corporate model or in preservation of the world as we know it, are louder voices that are being taken seriously. Al Gore recently joined Kleiner Perkins Caufield and Byers (a prestigious VC firm in Silicon Valley) as the partner heading up their climate change solutions group. Gore is hoping to translate his standing as the top evangelist on climate change to push businesses worldwide to increase their investments in renewable energy and other projects to reduce greenhouse gas emissions (source: www.sfgate.com)

6th vertical hybrid model

Compatibility, in values, and the administration of human resources, in the client and provider environment, takes greater meaning and is no longer just a desirable trait, but a necessary one. A genuine sharing of ideology is required, with a common recognition of the joint enterprise’s changing role as they together serve a very demanding market.  A service provider therefore becomes a partner, in the fuller sense of the word, almost intuitive in his understanding of his client, and modifying his ability proactively, before receiving firm directives from his client, that may often be too late to save the relationship. The service provider must be privy to his client’s thoughts and plans early in the game.

The delivery is not contained or restricted to providing a feel good factor, it must include the real understanding and delivery of the lower level needs, the so called deficiency needs, together with the higher ones, for as Maslow pointed out seventy years ago, the lower needs have to be continuously satisfied or regression will occur. The higher needs here should not be confused with providing business consulting which is a different service and perhaps a complementary one, but not necessarily so. The needs that are to be satisfied refer to the more complete expression of the requirement within the delivery of the functionality that is contracted. The recognition of the perceived contract that may be quite different from the written one, the gradual move towards acknowledging, even nourishing mutual dependency, and developing a hard-earned and durable intimacy.

The offshore provider, who has built the assembly line to cater to deficiency needs, may find himself in the position of a start up, for he is now required to identify, acknowledge and create the environment required by this community. There are difficulties in retro fitting the distinct and increasingly clearer articulation of dissatisfaction into the mold that was never designed for flexibility.

Reusable flexible molds can be constructed, ground up, and scale can be realized, while preserving the elements required. The ability to serve a large number of seemingly disparate individuals is made easier by identifying the common traits at the top of the pyramid to which this community belongs and creating a cost effective structure to serve them. Offshore, India and China, with its vast labor force does not have to automate beyond a level where such automation erodes the custom made look and feel of the solution. Preparing the resources to serve the growing market represented by the 6th Vertical requires discipline and training not unlike the rigor of serving the other verticals, but with the focus on different elements catering to more evolved needs and consequently yielding much higher benefits in terms of return on investment.

The profile of the service provider

The growth of a provider, who identifies and creates a platform to cater to the 6th vertical, is accelerated and stabilized when a large user, who has access to traditional sources of supply, finds value in this service offering. Companies who have satisfied their primary needs and seek leadership positions through a more intuitive understanding of their existing or new customer segments, often are the first to accept and utilize this offering, since it allows them to bridge a gap they see within themselves, irrespective of their own resources. IBM is one such example. After the failure of the token ring that was cramped by proprietary policies that limited use, and was forced to abdicate its potential position as the defacto network methodology to the upstart Ethernet, IBM’s approach to partnership has changed dramatically. IBM has devised ways to promote ease of use; for partners to adopt, configure and implement their platforms. This has no doubt contributed to its continued dominance in almost all aspects of the industry. IBM’s certification process across its product range is available at a low cost, across the world, and the company itself administers several programs for these certified players to even compete with its own service divisions.  Facebook in a different marketplace achieved dizzying valuations by effectively making itself a vehicle for users to express their needs and simply allow other users to satisfy them.  The common thread here is that the service offered was not necessarily unique, but used the ‘user community’ effectively. These two examples illustrate vividly two facts. One, that the 6th Vertical exists insides those who possess and have access to large resources such as IBM to satisfy business as usual, and secondly that those who provide these user defined services, have potential to grow, and, rightly managed, could become leaders in their own spheres.

A new breed of service providers must develop to fill this need of the 6th vertical. They will not be limited or successful purely by virtue of geography, market maturity, and technology or domain expertise.  Also, one needs to take cognizance of the fact that the concept is not confined to developing the so called soft skills; however empathy, and the ability to develop and nurture it across the company, could well be the differentiator, determining the success of those who choose to enter. Empathy can be created, and there is a cost and investment in doing so. The selection criteria may have to include psychological screening to weed out closed thinking individuals, followed by training of skills across broader areas, in relation to domain and technology. Particularly an ability to cross industry verticals and seek to understand service deficiencies that stem from communication gaps, with a greater focus on cultural differences besides mere language skills. Almost all such service providers would require a domestic native front end, coupled with an offshore back end that embodies the discipline and willingness to perform repeatedly mundane tasks, especially extensive testing.

The back end must preferably be located in one of the skill set supermarkets such as those that exist in Bangalore or Shanghai where a wide range of technical skills can be sourced on demand. Such flexibility is now mandatory but the decreasing profitability forbids a large bench. How well a company bridges these conflicts and remains agile, while fostering a successful retention policy for high performers, is perhaps the barometer of longevity in the race that will be run. For example a company that has a development base in one of the Tier 1 cities where such wide skills are available could operate support centers in Tier 2 or Tier 3 cities. In these units,  the company could create a link between the city’s social well being and the company, so employees in such cities are seen by the community as those that communicate to a larger cause, and therefore fulfill in themselves a higher need that is not met purely by financial compensation, and therefore are more resistant to change.

 

Summary and a glimpse of the future landscape of the offshoring industry

The decreasing disparity in living standards and costs between the consumers and offshore providers of a service has started to force a change in the model and type of services that can be profitably provided. The decrease in the gap between supply and demand of virtually all consumer goods and the increasing difficulty in product differentiation as seen for example in the telecom industry provokes focus almost exclusively towards differentiation within the service element. Banking and financial services, including insurance are other such domains. These so called verticals are therefore in some sense becoming governed by horizontals, with service related technical and non technical assets, spread across their business implementation, determining the sustainability of the enterprise. The power of the user, faced with the widest choice in economic history, available to him at the speed of the internet, across hitherto disparate boundaries, spells life or death even quicker than ever before. The evolution of his needs, extending beyond  the basic elements of functional well being, now require a platform to deliberately identify and promote the growth of an infrastructure of people, facilities and community who will be chosen to service such higher level needs.  In many cases, such a structure cannot be created by modifying an existing model that was built for a different purpose and we may see the rise of a new genre of enterprises built ground up to satisfy the new generation of business providers who in turn require a new generation of service providers that identify closer than ever before with their changing marketplace. The rewards of doing so will be reaped at Internet speed, as the channels of providing such service are no longer constrained.

 These hybrid models of the future that could well be a composite created from India, China and the West, that blends the recognition of these needs as articulated by the Sixth Vertical, together with their realization in one seamless pyramid, will secure the future of the offshoring industry. They will coexist with the traditional providers of vertical expertise, who with optimization and tightening of the belt may continue to serve their client base. It may be difficult for the traditional providers who have built fairly rigid assembly lines based on vertical or solely industry specific knowledge domains to make the shift to the Sixth Vertical as their legacy burdens their flexibility. However with the help of radical surgery, they could mutate themselves to adapt and carve a place as they fundamentally reinvent themselves from the ground up. All in all, it will be an extremely interesting battle ground, with Goliaths battling Davids better equipped than ever before with user molded slingshots. 

 

 

What is SOA (Service Oriented Architecture)

July 29, 2008 by torryharris

Service-Oriented Architecture, or SOA, enables IT departments to make the transition from an application-centric view of the world to a process-centric view. Today, IT departments have the freedom to combine business services from multiple applications to deliver true end-to-end support for business processes. And, because the integration mechanism of SOA (usually Web Services) enables loosely coupled integration, IT departments can upgrade or change applications without impacting other applications.

 

“SOA is the architectural style that supports loosely coupled services to enable business flexibility in an interoperable, technology-agnostic manner. SOA consists of a composite set of business-aligned services that support a flexible and dynamically re-configurable end-to-end business processes realization using interface-based service descriptions.

 

 SOA benifits

 

 

 SOA Benefits and implementation principles 

 

SOA provides benefits in four basic categories:

  • reducing integration expense
  • increasing asset reuse
  • increasing business agility
  • reduction of business risk

 

These four core benefits actually offer return at many different levels and parts of the organization, depending on the set of business problems the company is applying SOA to.

 

How should companies calculate the expected returns that tangible benefits provide the organization? Only by understanding the full range of SOA value propositions, can companies begin to get a hand on calculating the ROI on SOA. Even then, it may not be possible to understand SOA’s true ROI before the project is complete, because SOA addresses issues of fundamentally unpredictable business changes.

 

The following key principles are recommended when implementing SOA:

  • Document the Business Processes. Be it bottom up or top down, availability of these Business Process documentation is critical in delivering SOA in its true self instead of say, Web Services based applications
  • SOA Implementation is an evolution – start with a pilot, deliver business value and incrementally add on
  • The SOA Implementation must be based on loosely coupled services that provide the highest flexibility and ongoing cost reduction due to reuse and lower maintenance
  • The services should have standards compliant interfaces to enable seamless integration and interoperability with other services
  • The business drives the services, and the services drive the technology
  • Business Agility is a fundamental to SOA

 

SOA, Agile and Offshoring – A Heady Cocktail

June 13, 2008 by torryharris

 

 

If you want to ride the Emerging Technology wave, then you would be interested in this unique event, organized by Torry Harris Business Solutions on Friday, July 11th 2008 along the Hudson River, New York

 

This half day event on SOA, Agile and Offshoring, organized on an afternoon cruise, will be attended by leaders in Telecom, Banking & Insurance, Manufacturing & Retail sectors.

 

Larry Fulton, a Senior Analyst at Forrester will feature as the key speaker at the event. Larry will cover typical challenges & opportunities during SOA adoption and discuss best practices & future trends in SOA along with the benefits of Offshoring in SOA projects.

To quote Larry, in his research “Defining SOA Service Life-Cycle Management“, dated January 24, 2008, “Achieving the highest levels of SOA impact requires not only that individual services be designed well, it also requires that your overall portfolio of business services is highly relevant to your current business objectives and processes, easy for consuming groups to understand and use, factored for maximum ongoing value, working with the most up-to-date representations of your business data, and of course consistently named and documented

The other keynote speaker, Thiru Sivasubramanian, the SOA Lead and Country Manager, USA at Torry Harris Business Solutions (THBS), will cover the benefits & challenges of distributed agile development & discuss a day of distributed agile in a typical SOA project.

 

SOA, Agile & Offshoring, each is known to have addressed the all important questions regarding adaptability to change and the increasing need to deliver more for less. When blended together, they provide the stability offered by a triangle that far exceeds the stability offered by the individual.

 

Among others, the event would feature discussions on topics around how these powerful elements work together without disrupting the organization and co-exist with more traditional IT structures. The challenges of applying all these techniques together in large projects and tips born from years of experience would be shared.

 

Says, Thiru, “This event is one of its’ kind, where you will hear real-world stories from industry peers & experts. With scheduled breaks & an informal setting, there will never be a dull moment on the cruise”

Whether you’re investigating or implementing SOA, Agile & Offshoring, this event packs more deep knowledge, networking time with peers in the industry, collaboration and shared experience that you could benefit from.

Register for the event by contacting soa@thbs.com.

Hello world!

June 13, 2008 by torryharris

Welcome to WordPress.com. This is your first post. Edit or delete it and start blogging!