:::

詳目顯示

回上一頁
題名:中小型軟體公司之規範式軟體程序模式建構
書刊名:交大管理學報
作者:黃仁伯 引用關係楊千 引用關係
作者(外文):Huang, Jen-borYang, Chyan
出版日期:1997
卷期:17:3
頁次:頁125-145
主題關鍵詞:軟體危機軟體工程軟體程序工程軟體程序軟體發展程序程序模式程序模式化能力成熟度模式軟體發展能力評估模式生命週期模式程序週期Software crisisSoftware engineeringSoftware process engineeringSoftware processSoftware development processProcess modelProcess modelingCMMBootstrapSPICESDCMMLife-cycle modelProcess cycle
原始連結:連回原系統網址new window
相關次數:
  • 被引用次數被引用次數:期刊(1) 博士論文(0) 專書(0) 專書論文(0)
  • 排除自我引用排除自我引用:1
  • 共同引用共同引用:0
  • 點閱點閱:28
     由於對管理、品質及生產力的要求,軟體開發方法的發展由生命週期模式逐漸轉 變為軟體程序模式,並強調在品質與持續改進的重要,許多研究機構陸續提出各種不同的軟 體程序模式以為各家軟體公司參考使用,目前較普遍的有 CMM、Bootstrap 和 SPICE。 現存的軟體程序模式大都龐大、複雜,評估方式不夠彈性,導致中小型軟體公司不易參考遵 循,臺灣軟體公司又大多屬於中小型企業,因而經濟部工業局在其「軟體工業生產力提昇五 年計畫」中即召集工作小組展開制定合適中小型軟體公司遵循的軟體程序。經歷制定、實地 評估、修改等階段共一年半時間,完成第一個版本的軟體程序,定名為「軟體發展能力評估 模式」。 透過對業者的實地評估及業者採行的意見回饋,本發展評估模式將持續調整模式內容、評估 方式及問卷內容,以確實能協助業者提昇軟體發展的品質與生產力。
     Because of the desire of management, quality, and productivity, the software development method is shifting from life-cycle model to software process model gradually. It emphasizes the significance of quality and continuous improvements. Many different processes have been developed and adopted by research institutes, examples include CMM, Bootstrap, and SPICE. Most models are bulkily and complex. Its evaluation methods are inflexible as well. Small and medium companies are hard to adopt. Most of the software companies are small and medium in Taiwan; therefore, the Industrial Development Bureau of Ministry of Economics Affair convened a task force under "Five years plan for software industry productivity improvement" to develop a suitable software process model for them. It had taken one and half a year to perform the first version by passing through the development, field evaluation test and modification stages. This model is called "Software Development Capability and Measurement Model." According to the results of field evaluation and the feedback of opinions of practitioners, the task force will adjust the content, evaluation method and the questionnaires continuously to insure to assist software companies to move up the quality and productivity of software development.
期刊論文
1.Bannert, J.(1991)。New SEI Maturity Model Targets Key Practices。IEEE Software,8(6),78-79。  new window
2.Basili, V.、Caldiera, G.(1995)。Improve Software Quality by Reusing Knowledge and Experience。Sloan Management Review,1995(Fall),55-69。  new window
3.Billings, C.、Clifton, J.、Kolkhorst, B.、Lee, E.、Wingert, W.(1994)。Journey to a Mature Software Process。IBM Systems Journal,33(1),46-61。  new window
4.Boehm, B. W.(1976)。Software Engineering。IEEE Transactions on Computers,25(12),1226-1241。  new window
5.Boehm, W.(1988)。A Spiral Model of Software Development and Enhancement。Computer,21(5),61-72。  new window
6.Boehm, W.(1996)。Anchoring the Software Process。IEEE Software,13(4),73-82。  new window
7.Bollinger, T. B.、McGowan, C.(1991)。A Critical Look at Software Capability Evaluations。IEEE Software,8(4),25-41。  new window
8.Curtis, B.、Kellner, M.、Over, J.(1992)。Process Modeling。Communications of the ACM,35(9),75-90。  new window
9.Curtis, B.、Paulk, M.(1993)。Creating a Software Process Improvement Program。Information and Software Technology,35(6/7),381-386。  new window
10.Deephouse, C.、Mukhopadhyay, D.、Kellner, M.(1995)。Software Processes and Project Performance。Journal of Management Information Systems,12(3),187-215。  new window
11.Dorling, A.(1993)。SPICE: Software Process Improvement and Capability Determination。Information and Software Technology,35(6/7),404-406。  new window
12.Genuchten, M.(1993)。Analysis and Improvement of Software Engineering Processes。Information and Management,25,43-49。  new window
13.Johnson, D.、Brodman, I.(1996)。Realities and Rewards of Software Process Improvement。IEEE Software,13(6),99-101。  new window
14.Heineman, J. E.、Botsford, G.、Caldiera, G. E.、Kaiser, M. I.、Kellner, N. H.、Madhavji, N.(1994)。Emerging Technologies that support a software process life cycle。IBM Systems Journal,33(3),501-529。  new window
15.Haase, V.、Messnarz, R.、Koch, G.、Kugler, H.、Decrinis, P.(1994)。Bootstrap: Fine-Tuning Process Assessment。IEEE Software,11(4),25-35。  new window
16.Paulk, M. C.(1995)。How ISO 9001 Compares with the CMM。IEEE Software,12(1),74-84。  new window
17.Paulk, M.、Curtis, B.、Chrissis, M.、Weber, C.(1993)。Capability Maturity Model, Version 1.1。IEEE Software,10(4),18-27。  new window
18.Madhavji, N.(1991)。The Process Cycle。Software Engineering Journal,6(5),234-242。  new window
19.Koch, G.(1993)。Process Assessment: The 'BOOTSTRAP' Approach。Information and Software Technology,35(6/7),387-403。  new window
20.Thompson, K.、McParland, P.(1993)。Software Process Maturity (SPM) and the Information System Developer。Information and Software Technology,35(6/7),331-338。  new window
會議論文
1.Alavi, M.、Carlson, P.、Brooke, G.(1989)。The Ecology of MIS Research: A 20-Year Staus Review。The Tenth International Conference on Information Systems,(會議日期: Dec., 4-6),363-374。  new window
2.Feiler, P. H.、Humphrey, W.(1993)。Software Process Development and Enactment: Concepts and Definitions。International Conference Software Process。Los Alamitos, California。28-40。  new window
圖書
1.Humphrey, Watts S.(1989)。Managing the Software Process。Addison-Wesley。  new window
2.Ghezzi, C.、Jazayeri, M.、Mandrioli, D.(1991)。Fundamentals of Software Engineering。New Jersey:Prentice Hall。  new window
3.軟體產業服務團(1996)。軟體發展能力評估手冊。經濟部工業局。  延伸查詢new window
4.軟體產業服務團(1996)。軟體發展能力評估訓練手冊。經濟部工業局。  延伸查詢new window
5.軟體產業服務團(1997)。軟體發展能力評估專案訪查結案報告書。經濟部工業局。  延伸查詢new window
6.經濟部(1996)。中小企業白皮書。經濟部中小企業處。  延伸查詢new window
7.Blum, B. I.(1992)。Software Engineering: A Holistic View。Oxford university Press。  new window
8.Paulk, M.(1995)。The Capability Model: Guidelines for Improving the Software Process。MA:Addison-Wesley。  new window
9.Yourdon, E.(1992)。Decline & Fall of the American Programmer。New York:Prentice-Hall。  new window
10.Brooks, Frederick Phillips Jr.(1995)。The Mythical Man-month: Essays on Software Engineering。MA:Addison Wesley Longman, Inc.。  new window
11.Robbins, S. P.(1994)。Management。Prentice-Hall。  new window
 
 
 
 
第一頁 上一頁 下一頁 最後一頁 top
QR Code
QRCODE