The classifi cation is based on the granularity of the service and the ability of services to
combine into larger ones. Composite services can be created from elementary services
and process services can be created from elementary and composite services.
Reasons for choosing this classifi cation scheme are:
• Combining components into larger objects is a natural way of thinking.
Consider the assembly of car parts such as tires and engines from small
components, and the assembly of entire cars from these car parts. This is
a natural way of differentiating between screws and bolts, a cylinder,
and a Volkswagen Golf.
• Guidelines and implementation choices differ between these service types.
For example, different error-handling mechanisms are required for longrunning
process services than for short-running composite services. Another
example is the programming language used to implement services. It is not
a good idea to program an elementary service in BPEL or XPDL; a more fi t
choice is Java, .NET, .PHP, or any other generic programming language.
• Its simplicity. Classifi cations can be elaborated into more dimensions, more
layers, and more details that altogether provide more information, but more
clutter as well. This is needs-based service classifi cation.
There is no one true classifi cation scheme to structure services. You can choose
other aspects to classify services based on your needs – what do you want or what
do you need to highlight using a classifi cation? Perhaps you are the organization's
security offi cer and security is the main concern you need highlighted in the
classifi cation model.
Other classifi cati
The classifi cation is based on the granularity of the service and the ability of services tocombine into larger ones. Composite services can be created from elementary servicesand process services can be created from elementary and composite services.Reasons for choosing this classifi cation scheme are:• Combining components into larger objects is a natural way of thinking.Consider the assembly of car parts such as tires and engines from smallcomponents, and the assembly of entire cars from these car parts. This isa natural way of differentiating between screws and bolts, a cylinder,and a Volkswagen Golf.• Guidelines and implementation choices differ between these service types.For example, different error-handling mechanisms are required for longrunningprocess services than for short-running composite services. Anotherexample is the programming language used to implement services. It is nota good idea to program an elementary service in BPEL or XPDL; a more fi tchoice is Java, .NET, .PHP, or any other generic programming language.• Its simplicity. Classifi cations can be elaborated into more dimensions, morelayers, and more details that altogether provide more information, but moreclutter as well. This is needs-based service classifi cation.There is no one true classifi cation scheme to structure services. You can chooseother aspects to classify services based on your needs – what do you want or whatdo you need to highlight using a classifi cation? Perhaps you are the organization'ssecurity offi cer and security is the main concern you need highlighted in theclassifi cation model.Other classifi cati
การแปล กรุณารอสักครู่..
