Difference between revisions 354354669 and 354354792 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)
<br/>
In order to address the above issues<ref name='Mauro'>Mauro. et al. [http://www.computer.org/portal/web/csdl/doi/10.1109/HICSS.2010.336 Service Oriented Device Integration - An Analysis of SOA Design Patterns.] [online], pp.1-10, 2010 43rd Hawaii International Conference on System Sciences, 2010. Date accessed: 
46-4-10</ref>, the Utility Abstraction design pattern dictates the separation of generic processing logic from the business process-specific logic into a separate group of services known as the utility services<ref name="SvcLayerTypes">[http://www.soamethodology.com/p5.php Service Layer Types]</ref>.

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