傳統專屬主機資訊系統在網路與電腦設備尚未普及與發達的年代，是以高可靠性、高安全性、強大運算能力與多人多工等優點，扮演著企業核心業務運作的重要角色。但是在相對於高可靠性與高安全性的另一方面，便是使用者必須支付昂貴的成本來維持專屬主機資訊系統的運作。從主機硬體、作業系統、再到使用者所使用的程式語言編譯器與所開發的商業應用系統，全都必須仰賴此專屬主機資訊系統供應商所提供的設備與解決方案。面對現今資訊系統開放潮流，與企業強調業務敏捷性與反應力之下，單獨的專屬主機資訊系統已經難以快速滿足企業的業務需求。再者傳統專屬主機資訊系統的人才培養不易，維護現有的資訊系統已經是捉襟見肘，
更遑論以資訊科技創新達成業務模式的創新。相較之下，新的開放式平台資訊系統，擁有友善的開發環境與使用者介面，外部多樣性的支援與不同輔助工具選擇，都可以直接或間接提昇資訊系統的服務品質與企業所需的敏捷性。
本論文的主要目的是描述如何將個案公司所擅長的專屬主機資訊系統，在極短的時間內與不同專業類型的人員努力之下，迅速轉換成一般業界標準的開放式平台。以硬體架構、系統軟體、商業程式開發等面向出發，經過想法、評估，規劃，實作，與回饋調整等過程，協助客戶將銀行分行系統順利轉換上線。
本論文採取哈佛式個案教學撰寫法，內容包含個案本文以及教學手冊兩部份。討論內容包括資源基礎理論、可行性分析、專案管理之溝通理論、破窗理論和組織慣性等議題，透過個案內容輔佐以學理文獻進行探討，期以實務驗證理論，並以理論帶領實務的方式，提昇組織的競爭力。

The Legacy Proprietary Information System (LPIS) played an important role when computers and internet had not been extensively utilized. The importance of LPIS in core business functionalities was supported by its high reliability and security, powerful computation ability, multi-user and multi-processing capabilities. The other side of high reliability and security was the high maintenance cost. All of mainframe hardware, operating system, programming language compiler and developed commercial program were all supplied and maintained only by LPIS system provider.
Facing the trend of openness of Information Systems and the emphasis of business agility and responsiveness, LPIS is becoming harder to satisfy enterprise business needs. Furthermore, LPIS experts are getting less and thus difficulties exist in maintaining existing LPIS. In comparison, new Open Platform Information System (OPIS) provides friendly development environment and user interface, external diversity support and a variety of complimentary tools to choose from. These characteristics can directly and indirectly enhance the service quality and agility of Information systems.
The thesis illustrates how to migrate from LPIS to OPIS in the case study company, with the help of experienced LPIS developers. The migration objects include hardware structure, system software and business program development. The migration procedures of conception, assessment, planning, implementation and feedback adjustment assist client in smoothly getting online of bank branch systems.
This thesis utilizes Harvard Business School case writing style. Its content includes case texts and teacher handbook. The discussion topics include Resource Base Theory, Feasibility Analysis, Project Management Communication Theory, Broken Windows Theory, and Organization Inertia.

一、 中文參考文獻
[1] 薩提爾(Virginia Satir)原著，吳就君譯著 (1998)，《家庭如果塑造人（The New
Peoplemaking）》，維珍尼亞。台北：張老師出版有限公司。
[2] 項志銘 (2010)，《青少年溝通理論與技巧》，（第二版）青少年生涯發展服務
培訓計劃教材套。
[3] 彼得•杜拉克(Peter F. Drucker)原著，王嘉源譯著 (2003)，《杜拉克談未來管理
Managing for the Future 》，時報出版。
[4] 蔡佩珍 (2012)，《金融資訊系統邁向營運不中斷之路》，碩士論文，國立台灣
科技大學資訊管理系。
[5] 虞邦祥 (2012)，《策略聯盟所引發的組織改變：組織慣性之化解》，博士論文，
國立政治大學企業管理學系。
[6] 胡朝翔 (2012)，《以減少壞味道為提昇學生程式碼品質之教學方法》，碩士論
文，國立台北科技大學資訊工程系。
二、 英文參考文獻
[1] Satir, Virginia.(1988),"The New Peoplemaking". Palo Alto, CA: Science and
Behavior Books. ISBN 0831400706.
[2] Microsoft Customer Research Note (2007 July),The Business Value of Legacy
Modernization.
[3] Lewin, K. (1947),"Frontiers in Group Dynamics",Human relations, Vol.1,no.1.(消弭
抗拒).
[4] Jacques Horovitz (2005),"10 Rulles to Manage your Boss"International Institute for
Management Development in Lausanne, Switzerland.
[5] James Q. Wilson and George L. Kelling (1982),"BROKEN WINDOWS: The police
and neighborhood safety".
[6] Wernerfelt, Birger (1984), "A resource-based view of the firm" Strategic Management
Journal, Vol.5, p.171–180.
[7] Berlo, D.K.(1960),"The process of communication: An introduction to the theory and
practice"[p.7]. New York: Holt,Rinehart& Winston
[8] Len Bass,Mark Klein, & Felix Bachmann (2000),"Quality Attribute Design
Primitives" Software Engineering InstituteTechnical Note.
[9] Hannan, M.T., & Freeman J. (1984),"Structural inertia and organizational
change"American Sociological Review.
[10]Martin Fowler, Ken Beck, John Brant, William Opdyke, and Don Roberts.(1999),
"Refactoring, Improving the Design of Existing Code." 1st Ed. Addison-
Wesley,ISBN: 0201485672.
[11]Erl, T.(2005), "Service-Oriented Architecture: Concepts, Technology, and Design",
Upper SaddleRiver, NJ: Pearson Education.
[12]IEEE Std. 1028-2008 (2008), "IEEE Standard for Software Reviews and Audits"
[13]SSA Research Note SPA-401-068, (12 April 1996), "'Service Oriented' Architectures,
Part 1".
[14]SSA Research Note SPA-401-069, (12 April 1996), "'Service Oriented' Architectures,
49
Part 2".
[15]C.C. Michael, Ken van Wyk, and Will Radosevich (2005),"Risk-Based and
Functional Security Testing", Cigital, Inc.
[16]Kenneth W. Thomas (May 1976), "Conflict and conflict management: Reflections
and update" Journal of Organizational BehaviorVolume 13, Issue 3, pages 265–274.
三、 網站部份
[1] W3C Web Services Activity home page：http://www.w3.org/2002/ws/
[2] MBA 智庫百科：http://wiki.mbalib.com
[3] 10 rules to manage your boss ：http://www.rediff.com/money/2005/aug/12spec.htm
[4] 專屬資訊系統製造廠商：http://www.unisys.com/
[5] Reasoning About Software Quality Attributes：
http://www.sei.cmu.edu/architecture/start/reasoning.cfm
[6] Code smell：http://en.wikipedia.org/wiki/Code_smell
[7] Service-Oriented Architecture Scenario：
https://www.gartner.com/doc/391595/serviceoriented-architecture-scenario
[8] Risk-Based and Functional Security Testing： https://buildsecurityin.uscert.
gov/articles/best-practices/security-testing/risk-based-and-functional-securitytesting#
refs
[9] MBAlib 智庫百科，衝突的概念：
http://wiki.mbalib.com/zhtw/%
E5%86%B2%E7%AA%81%E7%AE%A1%E7%90%86#