臺灣博碩士論文加值系統

近年來隨著IT及相關技術、產業電子化之概念逐步發展，已有越來越多的企業開發與導入各項系統來使各部門間的流程與儲存的資料能全面電子化。這些系統常基於不同的環境與需求所設計，且各組織或各部門多採用自訂的軟體系統，因而造成異質平台及異質資料庫下，資訊如無法快速流通、同步，便會直接影響行政效率進而影響整個公司的競爭力。因此一個能使不同應用程式與系統間彼此互相溝通與分享資料，並具有彈性、標準的架構模式的需求便油然而生。
Service-oriented architecture (SOA)提供一個良好的異質平台間溝通的設計架構，讓異質系統整合變得容易，程式再用度也提高，且不受限於特定廠商的產品功能或是平台，達到真正的開放性。然而在實行SOA時，卻有著複雜的WF-*標準、未能如期的讓業務流程與IT整合且沒有相當樂觀的ROI等缺點。因此需要一個更簡單與直接的方式來達到SOA的功效。隨著Web 2.0的發展與興起，出現了以網路資源為導向、由下而上建造的Web-oriented architecture (WOA)，是邁向SOA架構較好的一條路徑。
WOA，即是結合了SOA的核心單元設計與Web2.0中的分享與Mashup概念，將整個網際網路視為一個全球性的SOA，每一個網頁與Web Service都是這全球性SOA當中的資源與服務項目，企業可將每一個資源加以整合與重用，快速的產生出更多、更新的資訊、服務，創建出全新的價值。
在理論上，WOA確實提供了一個簡單又直接的方式來達到SOA的成效，但卻還未有實際的例子來套用與驗證WOA的架構。此外，隨著網路三維的發展，用三維技術可以呈現更加友善的使用者介面與豐富使用者的經驗。因此，在本論文中，我們期望建立與開發一個以三維場景建構使用者介面的WOA典範與實例，使想投入WOA的企業們能夠瞭解WOA的方法與情境，並加以實行，以達到企業們快速建立服務與整合資源的需求，滿足顧客、員工與合作伙伴的期望，並透過更好的使用者介面，來豐富使用者的互動經驗。

Due to the rapid development of Information Technology (IT) and the broadening of electronic business concept, an increasing number of enterprises have adopted and executed systems to digitize all business processes, customer relationships and store data. Most of these systems were designed according to different environments and demands, with each organization or department adopting its own system and making changes to meet its needs. It makes heterogeneous platforms not be interoperable and directly effect enterprises’ efficiency. Thus, a flexible and standardized architecture is required to better support the connection of various applications and the data sharing.
Service-oriented architecture (SOA) does provide a great communicative architecture between heterogeneous platforms, which can easily integrate heterogeneous systems and let each program be more reusable, to achieve real open. However, while to implement SOA, CIOs and system architects face the complex WS-* standards. And the result of SOA is not optimistic ROI projections and the lack of business alignment. Hence enterprises need simpler and more straightforward methods to reach purpose of SOA. Via the way of the concept of Web 2.0 and mashup, the web-oriented architecture (WOA) seems a better route to the service-oriented architecture.
WOA merges the core design of SOA, the user sharing of Web 2.0, and the functionalities of mashup. It regards the Internet as the global SOA, every website, web service, or web page is the resource or item of this global SOA. Users can share, integrate, and reuse all of these to create new functionalities on the Internet in a loosely-coupled and interoperable way. These new functionalities are not only accessed independently but also are the resources or items of this global SOA again and then can be separated, integrated and reused to create other functionalities.
In theory, WOA does provide simpler and more straightforward methods for the implementation of SOA. Yet there are few examples implementing WOA in practice. In addition, Web 3D technology provides intuitive User Interfaces and immersive user experiences. Thus, in this reach, we try to develop a prototype of Three Dimension Web Service Platform (3WSP) to serve as a paradigm for WOA implementation. Companies can realize the scenarios and approach of WOA and then adapt it to their own situations. Simultaneously, companies may develop web services efficiently with the benefit of SOA but with simpler and more straightforward methods. Moreover, via a greater interface, we can enrich user experiences.

Acknowledgements i
摘 要 ii
Abstract iv
Contents vi
List of Tables viii
List of Figures ix
Chapter 1 Introduction 1
1.1 Background and Motives 1
1.1.1Service-oriented architecture (SOA) 2
1.1.2 Web 2.0 4
1.1.3 Web-oriented architecture 6
1.1.4 Web 3D 7
1.2 Research Objective 9
1.3 Research Overview 12
Chapter 2 Literature Review 13
2.1 Service-oriented architecture (SOA) 13
2.1.1 The definition of SOA 13
2.1.2 The Pros and Cons of SOA 16
2.2 Web 2.0 19
2.2.1 The origin of Web 2.0 19
2.2.2 The concept and definition of Web 2.0 20
2.2.3 Ajax 23
2.2.3 Mashup 25
2.3 Web-oriented architecture 28
2.3.1 The concept and definition of WOA 28
2.3.2 The differences between traditional SOA and WOA 31
2.4 Web 3D 33
2.4.1 Extensible 3D (X3D) 34
2.4.2 The advantages of 3D interface 36
2.4.3 3D applications in the Web 2.0 37
2.5 Electronic Learning 39
2.5.1 E-learning 2.0 40
2.5.2 The applications of E-learning 2.0 42
2.6 Summary of Literature Review 44
Chapter 3 Research Methodology 46
3.1 The 3WSP Framework 46
3.1.1 Data Access Layer 47
3.1.2 RESTful web service 48
3.1.3 User Interface Layer 49
3.2 System Architecture 50
3.2.1 The Architecture of User Interface Layer 52
3.2.1.1 User Interface 53
3.2.1.2 Ajax Engine 54
3.2.2 Data Access Layer 55
3.2.2.1 Data Repository 56
3.2.2.2 Web or XML Server 56
3.3 Proposed Scenarios 58
3.3.1 Scenario 1: Hosts’ Perspective - establishing platform 58
3.3.2 Scenario 2: Firm’s Perspective - implementing WOA 60
3.3.3 Scenario 3: Customer Perspective – participating in platform 61
Chapter 4 Implementation 64
4.1 Hardware Configuration 64
4.2 Software Configuration 65
4.2.1 Front-end Configuration 65
4.2.2 Back-end Configuration 66
4.2.3 RESTful Services 67
4.3 Prototype 68
4.3.1 Web Interface Design 68
4.3.2 Functional Design 69
4.3.3 RESTful web service design 74
4.4 Database Design 77
4.5 Scenario 1 Demonstration 79
4.6 Scenario 2 Demonstration 88
4.7 Scenario 3 Demonstration 91
Chapter 5 Concluding remarks and future works 96
5.1 Conclusions 96
5.2 Future works 98
Reference 99

1.王弘文, “網際網路上產品資訊傳達之認知差異研究,” 工業設計研究所, 國立雲林科技大學, 2000.
2.向建均, “SOA在數位圖書館中的應用,” SOA在數位圖書館中的應用, SOA在數位圖書館中的應用 第十期, 2007年10月, 維普資訊網-中文科技期刊資料庫, 2007, pp. 70~80.
3.周世雄, “三層式架構技巧速成,” 1998; http://www.borg.com.tw/Eip/books/doc/run9811.htm
4.林立綺, “IBM運用學習2.0促進企業之創新與合作,” IBM運用學習2.0促進企業之創新與合作, 330, 2008.
5.林立綺，「DELL：企業學習2.0 運用學習2.0」，intelligent time，第330期，2008年12月1日。
6.林立綺, “他山之石 德、日、韓 e-Learning v.s. u-Learning 應用分享,” 他山之石 德、日、韓 e-Learning v.s. u-Learning 應用分享, 330, 2008.
7.林立綺, “數位學習發展之整合創新趨勢 The Integration and Innovation Trend of e-Learning Development,”數位學習發展之整合創新趨勢 The Integration and Innovation Trend of e-Learning Development, 330, 2008.
8.林伯峰, “Web 2.0 之創新應用服務與經營模式之研究,” 企業管理學所, 國立中山大學, 2007
9.張慈韡、鐘世凱, “從X3D的發展談網站的三維立體空間呈現,” 多媒體動畫藝術研究所, 國立台灣藝術大學, 2003
10.曹承礎, “Web 2.0 開拓新桃花源,” Web 2.0 開拓新桃花源, 392, 2007, pp. 22-23.
11.陳品均, “Web 2.0 應用服務策略行動之研究-以Yahoo!、Google、MSN 為例,” 商學研究所, 國立台灣大學, 2006.
12.曾憲雄、蘇俊銘, “數位學習之介紹Introduction to digital learning technology,” 網路學習之理論與實務, 2007.
13.資訊工業策進會, “Web 2.0新世代網路應用發展趨勢,” Web 2.0新世代網路應用發展趨勢, 2006.
14.劉明修, “以夥伴關係管理概念建構一SOA之電子化採購系統,” 資訊經營研究所, 大同大學, 2008.
15.鄧文焯, “Web Services介紹,” http://www.iiiedu.org.tw/knowledge/knowledge2
0021231_1.htm
16.戴嘉宏、白明弘、馬偉雲、劉興寰、蔡瑜方, “具有新詞辨識能力的中文斷詞系統,” http://ckip.iis.sinica.edu.tw/CKIP/wordsegment.htm.
17.簡西村, “服務導向架構 (Service Oriented Architecture) 應用,” 2004; http://www.microsoft.com/taiwan/msdn/columns/soa/SOA_overview_2004112901.htm
18.A. Mesbah, and A.v. Deursen, “A component- and push-based architectural style for ajax applications,” J. Syst. Softw., vol. 81, no. 12, 2008, pp. 2194-2209.
19.Amazon; http://www.amazon.com/
20.Amazon, “Amazon Web Service,” http://aws.amazon.com/
21.B. Lublinsky, “Defining SOA as an architectural style,” 2007; http://www.ibm.com/developerworks/webservices/library/ar-soastyle/index.html?S_TACT=105AGX52&S_CMP=cn-a-ws.
22.C. Matthew MacKenzie, Ken Laskey, Francis McCabe, Peter F Brown and Rebekah Metz, “Oasis—Reference Model for Service Oriented Architecture 1.0,” 2006.
23.C. Gross, 實做Ajax-網頁程式的最佳方案, 旗標, 1997.
24.C. Schroth, Janner, T, “Web 2.0 and SOA: Converging Concepts Enabling the Internet of Services,” IEEE Journal, vol. 9, no. 3, 2007, pp. 36 – 41
25.Cetia4; https://cetia4.dev.java.net/.
26.Cult3D; http://www.cult3d.com/.
27.D. Hinchcliffe, “Making the Most of the Web: Creating Great Mashups,” 2006; http://web2.socialcomputingmagazine.com/making_the_most_of_the_web_creating_great_mashups.htm.
28.D. Hinchcliffe, “The SOA with reach: Web-Oriented Architecture,” 2006; http://blogs.zdnet.com/Hinchcliffe/?p=27.
29.D. Hinchcliffe, “A bumper crop of new mashup platforms,” 2007; http://blogs.zdnet.com/Hinchcliffe/?p=111.
30.D. Hinchcliffe, “Mashups: The next major new software development model?,” 2007; http://blogs.zdnet.com/Hinchcliffe/?p=106.
31.D. Hinchcliffe, “Web 2.0 success stories driving WOA and informing SOA,” 2008; http://blogs.zdnet.com/Hinchcliffe/?p=168.
32.D. Hinchcliffe, “What Is WOA? It''s The Future of Service-Oriented Architecture (SOA),” 2008; http://hinchcliffe.org/archive/2008/02/27/16617.aspx.
33.Dapper; http://www.dapper.net/.
34.Dave Crane, Eric Pascarello, and Darren James, Ajax in Action, 2006
35.ebay; http://www.ebay.com/.
36.EveryScape; http://www.everyscape.com..
37.E ON-Reality; http://www.eonreality.com/.
38.Flickr; http://www.flickr.com/.
39.Gartner, “Whoa! We''ve got WOA,” 2005; http://blog.gartner.com/blog/index.php?itemid=400.
40.GOO3D; http://www.goo3d.com/Community/.
41.Google; http://www.google.com/.
42.Google, “Blogger,” http://www.blogger.com/.
43.Google, “Google Code,” http://code.google.com/.
44.Google, “Google Earth,” http://earth.google.com/.
45.Google, “Google Lively,” July 8, 2008 ~ December 31, 2008; http://www.lively.com/html/landing.html.
46.Google, “Google Maps,” http://maps.google.com/.
47.Google, “Google Web Toolkit,” http://code.google.com/intl/zh-TW/webtoolkit/.
48.H. Panetto, and A. Molina, “Enterprise integration and interoperability in manufacturing systems: Trends and issues,” Computers in Industry, vol. 59, no. 7, 2008, pp. 641-646.
49.IBM, “IBM Survey: SOA Discussion Moves From IT Staff Roundtables to Executive Agenda,” IBM Survey: SOA Discussion Moves From IT Staff Roundtables to Executive Agenda, 2007,
50.IBM, “當 SOA 遇見 Second Life,” http://www-01.ibm.com/software/tw/sf/hn/7th_soa_secondlife.html.
51.IETF, “Uniform Resource Identifier (URI): Generic Syntax,” 2005; http://tools.ietf.org/html/rfc3986.
52.J.A. Scott M. Glen, “A practical application of SOA,” 2007; http://www.ibm.com/developerworks/webservices/library/ws-soa-practical/?S_CMP=cn-a-ws&S_TACT=105AGX52.
53.J.B. Horrigan, “Home Broadband Adoption 2006,” Home Broadband Adoption 2006, 2006, Pew Internet & American Life Project, 2006, pp. p10
54.J.J. Garrett, “Ajax: A New Approach to Web Applications,” 2005.
55.John Musser with Tim O''Reilly and the O''Reilly Radar Team, Web 2.0 Principles and Best Practices, 2006.
56.JQuery; http://jquery.com/.
57.K.Y.Y. Kei-Hoi Cheung, Jeffrey P Townsend, Matthew Scotch, “HCLS 2.0/3.0: Health care and life sciences data mashup using Web 2.0/3.0,” Journal of biomedical informatics, 2008.
58.Li Xiao and Subhasish Dasgupta, “User Satisfaction with Web Portals: An Empirical Study,” Idea Group Inc, 2005.
59.Linden Lab; http://lindenlab.com/.
60.Linden-Lab, “SecondLife,” http://secondlife.com/.
61.M. Bell, Introduction to Service-Oriented Modeling’, Service-Oriented Modeling: Service Analysis, Design, and Architecture, Wiley & Sons, 2008.
62.M. Nichols, “E-Primer Series - E-Learning in Context,” Laidlaw College, Auckland, New Zealand, 2008.
63.M. Pesce, “VRML: The First Ten Years,” 2004; http://www.3d-test.com/intervie
ws/mediamachines_2.htm.
64.Meez, “VRML: The First Ten Years,” http://www.meez.com.
65.Nucleus Research, “SOA’s ROI in the Enterprise is MIA, Nucleus Research Survey Finds,” 2007; http://www.businesswire.com/portal/site/google/index.jsp?
ndmViewId=news_view&newsId=20070820005598&newsLang=en.
66.P. Graham, “Web 2.0,” 2005; http://www.paulgraham.com/web20.html.
67.Prototype; http://www.prototypejs.org/.
68.R. Fielding, UC Irvine, J. Gettys, Compaq/W3C, J. Mogul, Compaq, H. Frystyk, W3C/MIT, L. Masinter, Xerox, P. Leach, Microsoft, T. Berners-Lee, IETF RFC 2616, “Hypertext Transfer Protocol - HTTP/1.1,” 1999.
69.R.R. Kodali, “What is service-oriented architecture?,” 2006; http://www.javaworld.com/javaworld/jw-06-2005/jw-0613-soa.html?page=1.
70.R. Thomas, “Architectural Styles and the Design of Network-based Software Architectures,” Department of Information and Computer Science, California University, 2000.
71.R. Smith, “A Simpler Approach To SOA - Web-oriented architectures are easier to implement and offer a similar flexibility to SOA,” 2008; http://www.informationweek.com/news/software/soa/showArticle.jhtml?articleID=209904293.
72.Restlet; http://www.restlet.org.
73.Ruby On Rails (ROR); http://rubyonrails.org/.
74.SalesForce.com, “Force.com is Cloud Computing for the Enterprise,” http://www.salesforce.com/platform/.
75.SearchSAP.com, “What is SOA?,” 2005; http://searchsap.techtarget.com/generic
/0,295582,sid21_gci1124303,00.html.
76.Service-architecture.com, “Service-oriented architecture (SOA) definition,” 2000; http://service-architecture.com/web-services/articles/service-oriented_architecture_soa_definition.html.
77.Sherif, “Why Mashups = (REST + ‘Traditional SOA’) * Web 2.0,” http://blog.sherifmansour.com/?p=187.
78.Shockwave3D; http://www.shockwave3d.com.
79.Shout3d; http://shout3d.net.
80.SmallWorlds; http://www.smallworlds.com.
81.T. Erl, Service-oriented Architecture: Concepts, Technology, and Design, Upper Saddle River: Prentice Hall PTR, 2005.
82.T. O''Reilly, “What Is Web 2.0? Design Patterns and Business Models for the Next Generation of Software,” 2005; http://www.oreillynet.com/pub/a/oreilly/ti
m/news/2005/09/30/what-is-web-20.html.
83.V. Vizzaccaro, “Firefox Share Tops 20% for November,” 2008; http://www.netapplications.com/newsarticle.aspx?nid=45.
84.Viewpoint; http://www.viewpoint.com.
85.Virtools; http://www.virtools.com/.
86.W3C, “Document Object Model (DOM),” http://www.w3.org/DOM.
87.Web 3D Consortiumm; http://www.vrml.org/.
88.Wikipedia, “Ajax,” http://en.wikipedia.org/wiki/Ajax_(programming).
89.Wikipedia, “BES,” http://en.wikipedia.org/wiki/BlackBerry_Enterprise_Server.
90.Wikipedia, “CORBA,” http://en.wikipedia.org/wiki/Corba.
91.Wikipedia, “DCOM,” http://en.wikipedia.org/wiki/Distributed_Component_Obj
ect_Model.
92.Wikipedia, “Electronic learning,” http://en.wikipedia.org/wiki/Electronic_learnin
g.
93.Wikipedia, “Mashup,” http://en.wikipedia.org/wiki/Mashup_(web_application_h
ybrid).
94.Wikipedia, “Representational State Transfer,” http://en.wikipedia.org/wiki/RES
T.
95.Wikipedia, “Rich Internet application,” http://en.wikipedia.org/wiki/Rich_Intern
et_application..
96.Wikipedia, “Service-oriented architecture,” http://en.wikipedia.org/wiki/Service-
oriented_architecture.
97.Yahoo pipes; http://pipes.yahoo.com/pipes/.
98.Yahoo! UI; http://developer.yahoo.com/yui/.
99.YouTube; http://www.youtube.com.
100.ZK; http://www.zkoss.org.