Talk:Service-orientation
 | This article was nominated for deletion on 30 September 2010. The result of the discussion was nomination withdrawn. |
 | This article is rated Start-class on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | |||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||
 | A member of the Guild of Copy Editors, Stfg, reviewed a version of this article for copy editing on 15 January 2012. However, a major copy edit was inappropriate at that time because of the issues specified below, or the other tags now found on this article. Once these issues have been addressed, and any related tags have been cleared, please tag the article once again for {{copyedit}}. The Guild welcomes all editors with a good grasp of English. Visit our project page if you are interested in joining! |
Perspectives[edit]
To see Service Orientation only as a construct in terms of the amalgamation of business and IT-infrastructure to optimize processes is only one perspective of what service orientation in companies can put forth. When considered in terms of attitudes in the context of human resources, service orientation can be defined as a disposition consisting of a number of traits that a customer-oriented service employee should exhibit in order to achieve customer satisfaction.
Service orientation can also refer to the way an organization is structured. Following the principle of service orientation an organization will entirely be divided into units by customers and services offered to customers, or a significant part of the organization will be a customer servicing division structured by customers and services offered. These units pretty much deliver the whole service based on their own resources, as opposed to an organization implementing services as processes crossing multiple units. Pypes (talk) 00:06, 15 September 2010 (UTC)
Stylistic deficiencies[edit]
I will probably move to delete this unless it at least gets an introduction in ordinary English. The entire article is too vague and uninformative, and generally, reads like an advertisement for a poorly defined business method:
- a design paradigm that specifies the creation of automation logic in the form of services....
- Service-orientation is the philosophical process of processes becoming more service-oriented.
- Now that's helpful.
- Service-orientation has continued to receive increased recognition as an important part of the service-oriented computing landscape and a valid design approach to achieving service-oriented architecture....
The words are just chasing their tails here; much of the article is vague and weaselly piffling in glittering generalities or uninformative tautology. - Smerdis of Tlön - killing the human spirit since 2003! 15:20, 21 September 2010 (UTC)
I've attempted to improve the first paragraph. What do you think? Marfinan (talk) 18:23, 20 April 2015 (UTC)