跳到主要內容

臺灣博碩士論文加值系統

(3.231.230.177) 您好!臺灣時間:2021/07/27 10:48
字體大小: 字級放大   字級縮小   預設字形  
回查詢結果 :::

詳目顯示

: 
twitterline
研究生:蕭鈞源
研究生(外文):Chun-Yuan Hsiao
論文名稱:動態專案式知識框架
論文名稱(外文):A Knowledge Framework for Dynamic Project
指導教授:李保志李保志引用關係
指導教授(外文):Pao-Jhy Lee
學位類別:碩士
校院名稱:國立雲林科技大學
系所名稱:資訊管理系碩士班
學門:電算機學門
學類:電算機一般學類
論文種類:學術論文
論文出版年:2004
畢業學年度:92
語文別:中文
論文頁數:100
中文關鍵詞:動態專案式知識框架合作設計鏈生老病死分合思維動態分合機制
外文關鍵詞:Collaborative design chain.Knowledge framework for dynamic projectSeparate&Combine ThinkingBirth、Age、Illness、DeathDynamically Separate&Combine mechanism
相關次數:
  • 被引用被引用:6
  • 點閱點閱:244
  • 評分評分:
  • 下載下載:32
  • 收藏至我的研究室書目清單書目收藏:3
過去的十年間,許多供應鏈的研究多半著重於檢視採購模式與產品加值等等之活動,往往忽略了產品研發、產品設計在整個產品製造網路中之重要性。雖然已經有不少研究先進針對設計鏈的議題進行探討,但多半傾向於策略性建議與管理方式探討,即使多數研究都有提到合作平台與機制之重要性,卻少見能夠提出實際之運作框架模型。

現今框架模型在社會系統中之所以無法非常適用,主因是多數框架的研究專注於專案開發的部分,致力於發展開發工程的技術、程序與觀念,忽略了專案生命週期的重要性。此外,還牽涉到一個重要的因素-「動態」;社會系統中是由許多獨立的個體(人)所組成,這些個體會隨著需求與刺激的變化而不斷調整。若無法解決「動態」的問題,則框架模型的成果與產出便會隨著時間的演進與真正的需要越差越遠。本研究所提出的框架是以「生、老、病、死」與「分合思維」兩大核心觀念之結合,提出具備「動態分合機制」的設計鏈運作模式,將社會系統中的各項動態事物之請求與變化以合作設計鏈的方式加以解決。

本研究期望以此造模過程達到三項目的:
1. 提出動態專案式知識框架協助製造業(OEM)、文件、軟體系統等專案式作業之運作。
2. 建立動態分合機制。
3. 透過「木屐寮社區之緊急應醫療專案」驗證知識框架模型之可行性
Over the last decade, Supply Chain Management(SCM)’ study always focus on purchasing and adding value, et al.. Some important issue of whole product manufacture network such as development, design, and collaboration was been ignored. Although the research of Design Chain(DC) was increasing little by little, but those almost trending to discuss management strategy and suggest. Many research pointed out the framework and mechanism to collaboration, but only few research actually make a feasible framework.
Today, Most frameworks couldn’t work very well, because those frameworks ignored the importance of life cycle to project. Those research focus just on the project development such as process, technique, and engineering. Besides, the framework research need to consider another factor -「Dynamic」. Society system was composed of many individual(human), and those individual will keep changing and adjusting to content environment’ need all the time. If the framework couldn’t solve the problem of dynamic, then the product and outcome will never fit with real needs. This research expect use 「Birth、Age、Illness、Death」 and 「Separate&Combine Thinking」to make DC dynamically work, and let every thing could be solve by collaborative design chain.

This research hopes to achieve three goals:
1. Making a knowledge framework to support dynamic project operation.
2. Constructing dynamically Separate&Combine mechanism
3. Using double case to validate the framework.
目錄
中文摘要 i
英文摘要 ii
誌謝 iii
目錄 iv
表目錄 vi
圖目錄 vii
第一章、緒論 1
1.1 研究動機 1
1.2 研究目的 2
1.3 研究方法 3
1.4 研究流程 4
1.5 研究範圍與限制 5
1.6 名詞解釋 6
第二章、文獻探討 7
2.1 文獻探討-PMI 8
2.2 文獻探討-ISO 11
2.3 文獻探討-RUP 14
2.4 文獻探討-ICS 18
第三章、理想的運作模式 20
3.1 外在(整體觀) 21
3.1.1【一粒細胞見世界(不易)】 21
3.1.2【層層負責(簡易-個體)】 22
3.1.3【動態分合(變易-整體)】 24
3.2 內在(個體觀) 26
3.2.1【專案式運作】 26
3.2.2【全面品管】 28
3.2.3【循環-Iteration】 30
3.2.4【快速應變/彈性調整】 31
3.3 未來理想運作模式之評估表 33
第四章、現況研究 34
4.1 PMI之缺口分析 34
4.2 ISO 9001之缺口分析 36
4.3 RUP之缺口分析 38
4.4 現行框架標準之探討 40
第五章、共通性專案知識框架之造模 42
5.1 共通性專案知識框架之核心意涵 42
5.1.1【生、老、病、死】 43
5.1.2【分合思維】 44
5.1.3【動態分合機制】 45
5.2 共通性專案知識框架之設計 46
5.2.1 生命週期-「生、老、病、死」 46
5.2.2 單層次專案運作 52
5.2.3 動態分合設計鏈式之專案運作 59
5.3 本研究框架之運用方式 65
第六章、專案框架模型之驗證 66
6.1南投縣木屐寮社區的災害防治 66
6.1.1 木屐寮社區「緊急醫療專案」概述 68
6.1.2緊急醫療專案之工作事項設計(要做的事) 70
6.1.3 緊急醫療專案在整體環境中的定位 75
6.1.4 緊急醫療專案的合作設計鏈運作 77
6.2 資訊業之軟體開發專案 78
6.2.1資訊業之「軟體開發專案」概述 79
6.2.2軟體開發專案之工作事項設計(要做的事) 80
6.3 動態專案式知識框架評量 85
第七章、結論與建議 86
附錄、參考文獻 88
附錄、參考文獻
[1]大乘義章,卷三,淨影慧遠,南北朝後期。
[2]中華專案管理學會,Project Management Body of Knowledge, PMBOK,http://www.npma.org.tw。
[3]南懷瑾,1989,易經雜說-易經哲學之研究,考古文化事業公司,台北。
[4]南本涅槃經,卷十一,(中國,作者不祥)。
[5]阿毘達磨雜集論,卷六,(中國,作者不祥)。
[6]陳忠平,2002,“品質專案元件框架造模” ,國立雲林科技大學資管所,碩士論文。
[7]軟服團,2001,”提升國內軟體產業國際競爭力-資策會將引進軟體CMM技術”,軟體產業通訊,四十期,九月。
[8]趙光正,2002,“Rational 統一流程入門第二版”,維科圖書有限公司,台北。
[9]孫振聲,1981,白話易經,星光出版社,台北。
[10]張義旺,2001,“易經組織細胞模型為基礎之知識元件組態管理”,國立雲林科技大學資管所,碩士論文。
[11]廖淑瑩,2003,“智慧型細胞之供應上協議業務模型-以抗SARS動態分合專案為例”,國立雲林科技大學資管所,碩士論文。
[12]鍾雪珍,1999,“標準資料之介紹與參考諮詢服務”,國家圖書館館訊(季刊), 89年第4期。

[13]Atkinson, Colin, et al., Component-Based Product Line Engineering with UML, Addison-Wesley, 2002.
[14]Bessant, J.R., 1991, Managing Advanced Manufacturing Technology: The Challenge of the Fifth Wave, NCC Blackwell, Oxford.
[15]Boehm W.B., 1996, "Anchoring the Software Process", IEEE Software, July.
[16]Booch, Grady, Object-Oriented Analysis and Design, Benjamin / Cummings, 1994, p.230..
[17]Bruegge, Bernd and Allen H. Dutoit, 2002, Object-Oriented Software Engineering: Using UML, Patterns and Java, Second Edition , Prentice Hall.
[18]Cheesman, John and John Daniel, 2001, UML Component – A Simple Process for Specifying Component-Based Software, Addison-Wesley.
[19]Cole, Dana, 2002, The Incident Command System,National Fire Academy, Feb. 2002,p.207。
[20]CMMI Product Development Team, “CMMISM for Systems Engineering
/Software Engineering, Version 1.1 (CMMI-IPPD, V1.1)”, March 2002.
[21]Deming, W.E., 1981, “Improvement of Quality and Productivity Through Action by Management”, Nation Productivity Review..
[22]DeToni, A., Nassimbeni, G. and Tonchia, S., 1994, “Service dimensions in the buyer-supplier relationship: a case study”, International Journal of Physical Distribution & Logistics Management, Vol. 24 No. 8, pp. 4-14.
[23]Drabek, T.E. and Hoetmer, G.J. (Eds.). Emergency Management: Principles and Practice for Local Government. Washington, DC: International City Management Association, 1991.
[24]FEMA(Federal Emergency Management Agency Emergency Management Institute), Incident Command System(ICS),1998,IS-195.
[25]Goldfarb, Ted, The Art Of Incident Command,Fire Engineering,Jan. 1997。
[26]Guy, S.P. and Dale, B.G., 1993, “The role of purchasing in design: a study in the British defense industry”, International Journal of Purchasing and Materials Management, Vol. 29 No. 3, Summer, pp. 27-31.
[27]Gido, Jack, James, P.C.,1999, Successful Project Management(專案管理), 宋文娟譯,滄海書局,台北。
[28]Heppelmann, James, 2000, “Collaborative Commerce in the Design Chain”, D.H. Brown Associates, Inc., annual conference December 2000..
[29]Herzum,Peter, O. Sims,2000, Business Component Factory A Comprehensive Overview of Component-Based Development for the Enterprise, Wiley Computer Publishing (2000).
[30]Ibrahim, Linda, The Federal Aviation Administration Integrated Capability Maturity Model Appraisal Method, Version 2.0, Federal Aviation Administration, April 1999. (available at www.faa.gov/aio).
[31]ISO(International Organization for Standardization), 2001, “Introduction and Support Package:Guidance on the Process Approach to Quality Management Systems”, Document ISO/TC 176/SC 2/N544R, May 2001.
[32]Jacobson, Ivar, et al., 1992, “Object-Oriented Software Engineering:A Use-Case- Driven Approach”, Addison-Wesley.
[33]Jacobson, Ivar, et al., 1998, The Unified Software Development Process, Addison Wesley Longman..
[34]Kruchten, Phillippe, 2000, The Rational Unified Process An Introduction Second Edition.
[35]Meade, L. M. and Rogers, K. J., A Method for Analyzing Agility Alternatives for Business Processes, Proceedings of the Sixth Industrial Engineering Research Conference. Miami Beach, FL. 1997, pp. 960-965.
[36]Macbeth, D.K. and Ferguson, N., 1994, Partnership Sourcing: An Integrated Supply Chain Management Approach, Financial Times/Pitman Publishing, London.
[37]Myers, Diane, et al., The Role of Mental Health in Emergency Management and The Emergency Operation Center, Monterey, California,
[38]OMG(Object Management Group), Inc., 2002, “UML Profile for Enterprise Distributed Object Computing Specification”..
[39]Pinto J.K., Slevin D.P., 1988, “Project Success: Definition and Measurement Techniques”, Project Management Journal, Vol.19, no.1,67-72.
[40]Rensberger, Boyce,1998,一粒細胞見世界,涂可欣譯,天下遠見出版股份有限公司,台灣。
[41]Ruiz, Mercedes, et al., 2002, “A Dynamic Integrated Framework for Software Process Improvement”, Software Quality Journal, 10, 181–194, 2002
[42]Scott, E.D., Stanley, G.S., 2000, Successful Software Development 2nd Edition, Prentice-Hall, N.J. .
[43]Schreiber, Guus, et al., 2002, Knowledge Engineering and Management:
The CommonKADS Methodology 3rd Edition, Massachusetts Institute of Technology.
[44]Sommerville, Ian, 2000, Software Engineering 6th Edition, Addison Wesley Publishing Company.
[45]Twigg, David, 1998, Managing product development within a design chain, International Journal of Operations & Production Management, Vol. 18 No. 5, p.p.508-524
[46]White, Clarence, Incident Command System, http://www.firehouse.com.
QRCODE
 
 
 
 
 
                                                                                                                                                                                                                                                                                                                                                                                                               
第一頁 上一頁 下一頁 最後一頁 top