Difference between revisions 351029351 and 351029510 on enwiki

< previous diff
next diff >
Utility Abstraction Pattern
{{New unreviewed article|source=ArticleWizard|date=March 2010}}

'''Utility Abstraction''' is a [[Design_pattern_(computer_science)|design pattern]], applied within the [[service-orientation]] [[Design_paradigm|design paradigm]], which advocates designing [http://www.whatissoa.com/p11.php services] that provide cross-cutting<ref name="cross-cutting">Functionality that is based on logic which is not related to any particular business process e.g. the requirement (contracted; show full)ts of business services (services that contain business process-specific logic) and then developing the required functionality represented by a meaningful functional context<ref name="FunctionalContext">The kind of the functionality provided. The service boundary of a service is represented by a particular functional context.</ref>. The functional contexts of utility services would tend to be more technology oriented as compared to entity services<ref name="SvcLayerTypes"
 /> as utility services mostly provide technology interfacing functionality e.g. a wrapper service that talks to a legacy database or a service that provides data conversion functionality between different formats.
<br/>
(contracted; show full)
* [http://www.soapatterns.org/ SOA Patterns]

== External links ==
* [http://www.whatissoa.com/ SOA Concepts]
* [http://www.soaglossary.com/ SOA Terms Glossary] 
* [http://www.soapatterns.org SOA Design Patterns]
 
[[Category:Service-oriented (business computing)]]