個案中的TALEWU公司業務策略的調整及組織的重整，內部系統間需要複雜的業務資訊整合，因此資訊部門面臨到典型的應用系統開發及系統整合的挑戰。個案內容描述了 TALEWU公司採用服務導向架構(Service Oriented Architecture, SOA)方法進行企業內系統架構的過程，期待利用產業上的SOA成功經驗及方法，來精進資訊單位與業務單位更有效率地達成業務上的合作，讓資訊系統能夠更有效的協助在業務策略及營運管理決策上搶得先機。
個案公司開始針對SOA進行評估，從瞭解SOA到過程中面臨到採用SOA的常見問題，透過SOA 概念性的驗證(Prove of Concept, POC)過程的團隊摸索學習，逐漸瞭解SOA 的相關技術與概念。個案過程在實踐的過程中把可能的問題提出來，慢慢也引導出SOA建置與治理工作的重要性。透過個案的SOA實踐經驗，再延伸到嚴謹的 SOA 相關執行方法論。經由個案與方法論之間的對照，讓大家在採用SOA決策前，能夠有更全面的瞭解採用SOA的最佳實踐方式並避免可能遭遇的問題。

Due to business strategy of organization reengineering, TALEWU Company　finished many complex　internal information system integration processes. In order to overcome the challenge of unexpected and rapid business model transition, information technology (IT) department required to develop various applications and further integrated numerously existing applications. This case described the adoption process of Service Oriented Architecture (SOA) for building enterprise applications. TALEWU Company expected to leverage the successful experience for the software development practices of SOA; therefore, the company could improve the operation efficiency and made timely important business strategies and operation management decisions.
TALEWU Company started to adopt SOA methodology by assessing the problems existed in the adoption process of SOA. Through the team learning process of prove of concept (POC) project of SOA, the related technique and concept became clear to IT department. The case also described the potential problems when the company carried out the SOA. The importance of SOA governance issue was also described in the case. Not only the case described the experience and the practices of the SOA adoption, but also this case extended to introduce the related methodologies and theories of SOA. In comparison with the theory and the practices of the adoption of SOA of the case, readers could more comprehensively understand the best practices and avoid potential pitfalls in the adoption of SOA.

1. 康明義，「跨國企業資訊集中化策略之探討 - 以個案公司為例」，國立政治大學-經營管理碩士學程(EMBA)論文(2003)
2. 蔡明田，張淑昭，施佳玫等，「企業電子化程度、資訊部門策略性角色、跨功能部門整合與組織績效關係之研究」，國立空中大學管理與資訊學系管理與資訊學報，民 93，9 期，229-251 頁(2004)
3. 李佳蓉(Chia-Jung Lee)，SOA方法在企業系統的發展現況探討(A Study of Major Currents of SOA Approaches in Enterprise Systems)，國立中央大學博碩士論文(2008)
4. “ ServiceDesignPatterns-Fundamental Design Solutions for SOAP/WSDL and RESTful Web Services”，Robert DaigneauAddisonWesleyOct。(2011)
5. "SOMA: A method for developing service-oriented solutions"，IBM SYSTEMS JOURNAL，VOL 47，NO 3，(2008)
6. “Business Process Management: A Platform for Innovation”，Howard Smith，November 17，14(2005)
7. Arsanjani，A.，Zhang，L。-J.，Ellis，M.，Allam，A.，and Channabasavaiah，K.，“S3: A Service-Oriented Reference Architecture” IEEE Computer Society on IT Professional，Vol。9，No。3，May-June 2007，pp。10-17.(2007)
8. Design an SOA solution using a reference architecturehttp://www.ibm.com/developerworks/library/ar-archtemp
9. Enterprise Service Bus，http://nl.wikipedia.org/wiki/Enterprise_service_bus
10. Effective SOA Governance ，https://www14.software.ibm.com/webapp/iwm/web/signup.do?source=sw-app&S_PKG=esg
11. Introduction to SOA governance and service lifecycle management，ftp://ftp.software.ibm.com/software/soa/pdf/IBMSGMMOverview.pdf
12. Using ESB for Enterprise Application Integration, http://blog.krawler.com/tag/hub-and-spoke/
13. NIH Enterprise(ESB) Pattern, https://enterprisearchitecture.nih.gov/Pages/EnterpriseServiceBusPattern.aspx