|
Service-orientation is a design paradigm for computer software in the form of services. The principles of service-orientation design stress the separation of concerns in the software. Applying service-orientation results in units of software partitioned into operational capabilities, each designed to solve an individual concern. These units qualify as services. Service-orientation has received a lot of attention since 2005 due to the benefits it promises. These include increased return on investment, organisational agility and interoperability as well as a better alignment between business and IT. It builds heavily on earlier design paradigms and enhances them with standardisation, loose coupling and business involvement. ==History of service-orientation principles and tenets== In technology, different vendor SOA platforms have used different definitions of service-orientation. Some vendors promote different principles and tenets over others, but a fair amount of commonality exists.〔Liebhart, Daniel. ''SOA goes real''. Hanser, 2007, p. 22〕 Don Box of Microsoft was one of the first to provide a set of design guidelines referred to as his "four tenets of service-orientation" which he described primarily in relation to the Microsoft Indigo (subsequently Windows Communication Foundation) platform that was emerging at the time: # Boundaries are explicit # Services are autonomous # Services share schema and contract, not class # Service compatibility is based on policy These tenets have since become fundamental design guidelines for related Microsoft-based documentation, such as the ("Service Orientation and Its Role in Your Connected Systems Strategy" ) article published on MSDN in 2004. An article in the December 2005 edition of the (IBM System Journal ) (by (Cherbakov, Galambos, Harishankar, Kalyana, Rackham )) entitled ("Impact of service orientation at the business level" ) provided a study of how the service-orientation paradigm relates to fundamental componentization and the IBM Component Business Model (CBM). Further, in a published article entitled (“SOA Simplified” ), IBM Vice President for Strategy (Sandy Carter ) emphasized the importance of service-orientation and its relevance to attaining true reuse. Paul Allen wrote a book in which Service Orientation is defined as a paradigm, with three main components: # Business architecture # SOA # Software oriented management Allen's book defines seven Service-Oriented Viewpoints (labelled SOV7): #Transparence # *Smoothness of customer’s experience in using the service. #Customer fit # *Ability to tailor offerings to variations in customer needs. #Partner connectivity # *Ability to use 3rd parties for performing commodity services # *Ability to offer a service to different partners #Adaptation # *Adapting to the changes in the marketplace. #Multi-channel capability # *Support the customer end-to-end through process, using different channels to achieve continuity. # *Offering same service through different channels. #Optimization # *Offering services in real time at high performance levels. #One-stop experience # *Catering to different needs of the customers through one set of services. The viewpoints do have a more high-level approach, and are not as specific and interlinked as the Service Orientation Principles of Erl. Allen uses them as starting point for stating questions during the design process. 抄文引用元・出典: フリー百科事典『 ウィキペディア（Wikipedia）』 ■ウィキペディアで「Service-orientation」の詳細全文を読む スポンサード リンク
|