:::

詳目顯示

回上一頁
題名:建構未來輪輔助軟體發展之需求擷取--以某電腦軟體服務業公司為例
書刊名:企業管理學報
作者:薛義誠 引用關係劉樺蓉陳啟揚
作者(外文):Shiue, Yih-chearngLiu, Hua-jungChen, Chi-yang
出版日期:2014
卷期:100
頁次:頁13-38
主題關鍵詞:未來輪未來研究方法論需求擷取軟體開發Future wheelFuture research methodologyRequirement elicitationSoftware development
原始連結:連回原系統網址new window
相關次數:
  • 被引用次數被引用次數:期刊(0) 博士論文(0) 專書(0) 專書論文(0)
  • 排除自我引用排除自我引用:0
  • 共同引用共同引用:0
  • 點閱點閱:14
專案管理機構研究報告指出,50%以上軟體專案無法達到預期目標,超過70%軟體專案皆失敗,美國電子電機工程師學會及主計處統計調查更指出:導致專案失敗的兩大主因是需求的不確定造成認知差異和需求變更頻繁。為解決此問題,由於未來輪之易用性、周延思考和組織性,能應用於系統分析領域,因此導入未來輪為需求擷取之輔助工具,提供明確化需求流程、可用性和執行建議。採用個案研究法,針對個案進行詳細的研究,結合文獻內容分析與專家訪談進行探討,針對訪談結果提出研究命題、流程驗證及調整。本研究具體貢獻包括建立導入未來輪之需求擷取流程,描述各階段該如何執行。透過專家訪談資料,驗證流程可用性並提出研究命題,並提出流程執行建議。
The American Institute of Electrical and Electronics Engineers found that cognitive differences caused by uncertain requirement and frequently changing requirement were the two main reasons leading to project's failure. The Project Management Institute also found 50% of software projects cannot meet customers' expectations, and over 70% or more software projects fail. A method of future research methodology is future wheel, which can solve this problem, containing the easy accessibility, sustainability, and organized, could be applied in system analysis domain. Moreover, introducing the future wheel as an added tool to create a requirement process. It evaluates process' availability and practice's instructions. Individual case study method is adopted and is oriented by the logic of exploring, discovering and inducing. The prepositions, process' verifications, and alteration by concluding the references and expert's recommendations in interview are proposed. The contributions include building the process by future wheel in requirement elicitation, and providing instructions of the process. Finally, this research possibility of future wheel in assisting requirement elicitation, model adjustment, project goals setting.
期刊論文
1.Gibbs, W. W.(1994)。Software’s chronic crisis。Scientific American,271(3),72-81。  new window
2.Pimentel, J.、Santos, E.、Castro, J.、Franch, X.(2012)。Anticipating Requirements Changes-Using Futurology in Requirements Elicitation。International Journal of Information System Modeling and Design,3(2),89-111。  new window
3.Telem, M.(1988)。Information requirements specification I: Brainstorming collective decision-making approach。Information processing & management,24(5),549-557。  new window
4.Eisenhardt, Kathleen M.(1989)。Building Theories from Case Study Research。Academy of Management Review,14(4),532-550。  new window
圖書
1.吳仁和、林信惠(2010)。系統分析與設計--理論與實務應用。台北:智勝文化事業有限公司。  延伸查詢new window
2.Davis, A. M.(1993)。Software requirements: objects, functions, and states。Prentice-Hall。  new window
3.Glenn, J. C.(1994)。The futures wheel。Washington, DC:United Nations University。  new window
4.Glenn, Jerome C.、Gordon, Theodore J.(2009)。Futures Research Methodology。The Millennium Project。  new window
5.Kotonya, G.、Sommerville, I.(1998)。Requirements engineering: processes and techniques。John Wiley & Sons, Inc.。  new window
6.McManus, J.、Wood-Harper, T.(2003)。Information systems project management: Methods, tools and techniques。Pearson Education。  new window
7.Wiegers, K.(1998)。Software Rquirements。Addison-Weskey。  new window
8.Minichiello, V.、Aroni, R.、Hays, T. N.(2008)。In-depth interviewing: Principles, techniques, analysis。Pearson Education。  new window
9.Yin, R. K.(2002)。Case study research: Design and methods。Thousand Oaks, CA:Newbury Park:San Diego, CA:Sage:Sage Publications。  new window
其他
1.林文遠(2009)。政府機構資訊系統委外管理實務調查報告,http://www.dgbas.gov.tw/public/DataZ9103113525071.pdf, 2013/04/20。  延伸查詢new window
2.Johnston, S.(2004)。Rational UML Profile for business modeling. IBM Developer Works,http://www.ibm.com/developerworks/rational/library/5167.html, 2013/07/22。  new window
 
 
 
 
第一頁 上一頁 下一頁 最後一頁 top
QR Code
QRCODE