|
參考文獻 一、中文部份 中華民國品質學會(民90),軟體技術指引手冊(網路版),http://www.cisanet.org.tw/ doc/(2005/10/09) 任光德、李正龍(民93),軟體開發專案的風險管理研析,2004年中華民國危機處理學會學術研討會 林信惠、黃明祥及王文良合著(民92),軟體專案管理(Software project management),台北市:智勝文化事業有限公司 馬敬文著(民92),企業專案管理的關鍵時刻,慧泉專案管理顧問公司。網址:www.jmac.com.tw/file/ch/EPM.doc(2005/11/07) 許成績、林政、王長峰及肖文毅著(民93),現代專案管理教材(Modern Project Management),台北縣;博碩文化股份有限公司 張紹勳著(民93),研究方法(精華本),台中市:滄海書局 蕭瑞麟(民89),不先改善組織流程,資訊變革可能失敗,http://www.chinamgt. com/ harment/mm/0104/inf.htm,哈佛企業管理顧問公司(2006/3/20) 賴士葆、謝龍發、陳松柏著(民94),科技管理,台北市;華泰文化。
二、英文部份 Alavi, M. and Carlson, P.(1992), A Review of MIS Research and Disciplinary Development Implications for Deans Administrators, Journal of Management Information Systems, 8, 45-62. Boehm, B. W.( 1991), Software Risk Management: Principles and Practices, IEEE Software, 8(1), 32-41 Boehm, B. W. & DeMarco T.( 1997), Software Risk Management, IEEE Software, 14( 3), 17-19. Boehm, B. W.(2002), Software Risk management: overview and recent developments, COCOMO/SCM Forum #17 Tutorial, Center for Software Engineering, University of Southern California. Brooks, F. P., Jr. (1987), No Silver Bullet: Essence and Accidents of Software Engineering, IEEE Computer, 20 (4): 10-19. Brooks, F. P., Jr.著,錢一一譯(2004),人月神話:軟體專案管理之道,城邦(香港)文化事業股份有限公司。 Department of Defense Dictionary of Military and Associated Terms Joint Pub 1-02 (DOD Joint Staff Publication No. 1-02) (1994) , Telecommunications terms and definitions and established for use by all DOD Components, which will use the terms and definitions so designated without alteration unless a distinctly different context or application is intended. Defense Acquisition University(2001), Systems Engineering Fundamentals, Fort Belvoir, Virginia, Department of Defense, USA. Defense Acquisition University(2003), Risk Management Guide for DOD Acquisition Fifth Edition(Version2.0), Fort Belvoir, Virginia, Department of Defense, USA. Department of Defense(1998), Military Handbook881[MIL-HDBK-881], Work Breakdown Structure, Department of Defense HandBook, USA. DeMarco, T. & Lister, T.著,錢一一譯(2004),與熊共舞-軟體專案的風險管理,城邦(香港)文化事業股份有限公司。 Field, T.(1997), When bad things happen to good projects, CIO Magazine, p.55~p.62. Gilb, T(1988), Principles of Software Engineering Management, Wokingham, England: Addison-Wesley. See particularly Chapter 6, “Estimating the Risk”. Gilb, T.(2004), Project Failure: Some Causes and Cures, Tom@gilb.com, (2006/1/30). Hillson, D.(2002), The risk breakdown structure(RBS) as an aid to effective risk management, San Antonio,Texas,USA. Hall, E.M.(1998), Managing Risk-Methods for Software Systems Development, Addison Wesley Professional. Hall, D.C.,& Hulett, D.T.(2002),Universal Risk Project—Final report, http://opim-sun .wharton.upenn.edu/~carpen/316/PMI%20Risk%20Management%20SIG%20Project%20Report.pdf ,( 2005/9/27). IEEE Computer Society(2005), Guide to the Software Engineering Body of Knowledge (SWEBOK 2004), Los Alamitos, California, USA, http://www.swebok.org/, (2005/5/30). IEEE Std 1540(2001), IEEE Standard for Software Life Cycle Processes – Risk Management, IEEE, ISBN 0-7381-2834-1 International Council on Systems Engineering; INCOSE(2006), What is Systems Engineering?, http://www.incose.org/practice/whatissystemseng.aspx?MENUID=0 (2005/12/20). International Council on System Engineering; INCOSE (2003), A Guide to the Systems Engineering Body of Knowledge; G2SEBOK v1.00, http://g2sebok.incose.org/, (2005/10/22). International Council on System Engineering; INCOSE(2006), Systems engineering, http://www.incose.org/practice/whatissystemseng.aspx(2006/2/24). Jones, C.(1994), Assessment and Control of Software Risks, Prentice Hall, ISBN 0137414064. Jones, C.(1995), Patterns of large software system: failure and success, Software productivity Research Inc., New England Executive Park, Burlinton, MA. Jaura, S. & Allan G.(2001), An Overview of Project Risk Management, http://www. tech. port.ac.uk/staffweb/allang/riskman.htm. (2005/10/18). Jiang, J. J., Klein, G. and Ellis, T. S.(2002), A Measure of Software Development Risk, Project Management Journal, 33(3). Kindinger,John P.,and John L.Darby(2000), Risk Factor Analysis—A New Qualitative Risk Management Tool. Proceedings of the Project Management Institute Annual Seminars & Symposium. Newtown Square, PA:Project Management Institute,7-16, Houston,Texas USA. Merriam-Webster online(2006), Risk, http://www.m-w.com/dictionary/risk(2005/10/26) Mirriam-Webster online(2006), System, http://www.m-w.com/cgi-bin/dictionary (2006/3/23) PMI Risk SIG website, www.risksig.com, or www.techriskmgt.com/home2link.html. Project Management Institute(2000), A Guide to the Project Management Body of Knowledge (PMBOK® Guide), Newtown Square, Pennsylvania, USA. Project Management Institute(2004), A Guide to the Project Management Body of Knowledge (PMBOK® Guide), Newtown Square, Pennsylvania, USA. Project Management Institute(2001), Practice Standard for Work Breakdown Structures, Newtown Square, Pennsylvania, USA. Quick, A.(2002), Why IT Project Fail, Article Hub, http://www.articlehub.com/ authors/ Andy Quck.html Rigby, K.(2003), Managing Standard V4.6(6.3 Definitions and general criteria for Tec- hnical Management.), http://sparc.airtime.co.uk/users/wysywig/gloss.htm (2006/1/10). Wikipedia(2006), System Engineering, http://en.wikipedia.org/wiki/System_engineering (2006/2/24). Webster, K. P. B., Oliveira K. M. de, Anquetil, N.(2005), A Risk Taxonomy Proposal for Software Maintenance, IEEE Computer Society, 21st IEEE International Confere- nce on Software Maintenance (ICSM'05), pp. 453-461 Wikipedia(2006), System, http://zh.wikipedia.org/wiki/%E7%B3%BB%E7%B5%B1 (2006/4/9). Wikipedia(2006), System Engineering, http://zh.wikipedia.org/wiki/%E7%B3% BB%9F %E5%B7%A5%E7%A8%8B(2006/3/15). Wikipedia(2006), 軟體開發,zh.wikipedia.org/wiki/软件开发,(2006/3/15). Wiegers, K. E.(1998), Know your enemy: Software risk management, Software Development magazine, www.processimpact.com( 2005/11/30). Sommerville, I.(2004), Software Engineering (7th ed. Hardback) , Addison-Wesley, Harlow, England. Tomayko, J. & Hallman, H.K.(1989), Software Project Management, SEI Curriculum Module SEI-CM-21-1.0, Carnegie Mellon University., http://www.sei.cmu.edu/ publications/documents/cms/cm.021.html(2005/9/15). The Computer History Museum, http://www.computerhistory.org/timeline/ timeline.php? timeline_year=1953. The Computer History Museum, http://www.computerhistory.org/timeline/timeline.php? timeline_year=1964. The Computer History Museum, http://www.computerhistory.org/timeline/timeline.php? timeline_year=1969. The Computer History Museum, http://www.computerhistory.org/timeline/timeline.php? timeline_year=1983. Yaneer Bar-Yam(2003),When Systems Engineering Fails-Toward Complex Systems Engineering, International Conference on Systems, Man & Cybernetics, 2003, Vol. 2, 2021- 2028, IEEE Press, Piscataway, NJ.
|