• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Tim Cooke
  • Ron McLeod
  • Jeanne Boyarsky
  • Paul Clapham
  • Liutauras Vilda
  • Henry Wong
  • Devaka Cooray
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • Al Hobbs
  • Carey Brown
  • Piet Souris
  • Mikalai Zaikin
  • Himai Minh

SOA programming model for non-programmers?

Ranch Hand
Posts: 445
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi All,

I am reading a SOA programming model series on developerWorks (SOA series).

In the first article, the authors say that:

The IBM� programming model for Service-Oriented Architecture (SOA) enables non-programmers to create and reuse IT assets without mastering IT skills. ... This article series describes a new Service-Oriented Architecture (SOA) programming model that achieves a separation of concerns so that persons with different skill levels and roles in the enterprise, not necessarily IT professionals, can create and use IT assets throughout every stage of the software development life cycle.

Is that really true? Any of your comments is highly welcome.

Posts: 33
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
It's an ambitious statement, but it is in line with some of the ultimate goals of SOA. For example, once an enterprise is comprised of an inventory of well-defined services, those with business expertise will (or should) be able to accommodate change to business processes by remodeling existing services through tools that provide a business analysis-friendly front-end while outputting "ready-to-implement" orchestration programming logic. Achieving this state, though, is dependent on improved technology, the adoption of many WS-* specs still in limbo, and a great deal of internal standardization on the organization's part.
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
    Bookmark Topic Watch Topic
  • New Topic