Why Composition is not Development - Search WebServices
This entry was posted on Wednesday, December 20, 2006 3:57 PM and is filed under Article.
Why Composition is not Development "Developers are much like artists – no two developers produce the same application logic for the same set of requirements. In much the same way that few painters would want to paint their artwork on someone else's pre-completed canvas, most developers dislike reuse since they think they know best how to encode high-level requirements into the language that computers understand.
Composers, on the other hand, require a different mentality and social breeding. Rather than thinking in terms new application logic development, composers think in terms of configuration of existing Services as reflecting the then-current needs of the business. Composers depend on models for their basic, day-to-day operation. Since the models that drive Service composition necessarily reflect the actual requirements of the business, composers can not even accomplish their daily goals and tasks the artifacts that developers would consider unnecessary documentation. Developers desire working code over extraneous models. Composers need working models over extraneous code."
Source: Search Web ServicesWhy composition is not developmentFor more information on SOA Development see:
SOA Developer Network_________________________________________________
>> Back to Main PageGary E. Smith
BPM Architect Series
