Difference between revisions 358454154 and 358684055 on enwiki

< previous diff
next diff >
Utility Abstraction Pattern
{{notability|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 services<ref name='svc'>[http://www.whatissoa.com/p11.php Services]</ref> 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(contracted; show full)) 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
<ref name='SearchSOA'>Bernhard Borges, Kerrie Holley and Ali Arsanjani.[http://searchsoa.techtarget.com/news/article/0,289142,sid26_gci1006206,00.html Service-oriented architecture][Online].Date accessed: 17 April 2010.</ref> e.g. a wrapper service that talks to a legacy database or a service that provides data conversion functionality between different formats<ref name='DOD'>Dennis Wisnosky.[http://www.soamag.com/I25/0109-2.php Principles and Patterns at the U.S. Department of Defense][Online].Date accessed: 18 April 2010.</ref>.
<br/>
(contracted; show full)
* Susanne Patig.[http://drops.dagstuhl.de/opus/volltexte/2009/2047/pdf/09021.PatigSusanne.Paper.2047.pdf Cases of Software Services Design in Practice][Online].Date accessed: 18 April 2010.

== 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)]]