臺灣博碩士論文加值系統

個人軟體流程(Personal Software Process, PSP)是在1995年由美國Carnegie Mellon大學軟體工程研究所(CMU/SEI) Watts s. Humphrey領導開發，用於控制、管理和改進個人工作方式的自我改善過程。借助PSP，我們能瞭解自己的流程能力，例如：專案大小預估的能力和專案所需花費時間預估的能力。此外，我們能依照歷史資料預估新的專案需花費多少時間，而且能藉由系統化的方法，減少缺失發生的機率，改善開發系統的品質。

PSP雖然立意良好，可是在現實環境中仍然有很多問題。其最大的問題點就是需要手動填寫很多的表格，因此有很多電腦輔助系統工具(例如：Hackystat)被開發，用來減少使用PSP所需花費的時間。

然而，這些工具只適合某些特殊的開發語言(例如：Java)，不能適用於所有開發環境上。為了解決這個問題，我們擬訂定一個PSP方法論的協定及格式，開發工具若能遵循此協定，就能讓我們更容易收集PSP資料。此外，我們遵循我們所制定的協定，開發一個PSPA-Eclipse系統，它是一個結合於Eclipse上的PSP輔助工具。並且，利用此系統來驗證我們的協定。

Personal Software Process (PSP) was developed by Watts s. Humphrey leader''s development at U.S.A. Carnegie Mellon university Software Engineering Institute (CMU/SEI) in 1995. PSP is a self-improvement course which control, manage and improve personal software development. By using PSP, we can understand our own process capability such as size estimation capability and effort estimation capability. Moreover, we can predict the effort for a new project by our historical data and improve the quality of developed system by reducing the defects in a systematic way.

Though PSP is a good idea, there are still a lot of problems in an actual environment. The most serious problem is that people need to fill in many forms by hand. Therefore, there are many computer-aided tools developed to reduce the effort of using PSP, for example, Hackystat.

However, these tools are developed for a specific developing language (such as Java) and can’t be used for all development environments. To resolve this problem, in this research we develop a protocol and data format for PSP methodology. If the development tools can follow this protocol, we can collect data more easier. In addition, we develop a system called PSPA-Eclipse which is a PSP-Assistant tool embedded in Eclipse, based on our protocol. We validate our protocol by this PSPA-Eclipse tool.

摘 要 ………………………………………………………i
ABSTRACT …………………………………………………ii
致 謝 ……………………………………………………iii
目 錄………………………………………………………iv
圖 目 錄 …………………………………………………vi
表 目 錄…………………………………………………vii
第一章 緒論 ………………………………………………1
1.1 大綱……………………………………………………1
1.2 研究背景及動機………………………………………1
1.3 研究目的………………………………………………4
1.4 研究產出………………………………………………5
1.4.1 PSPA-Protocol的優點 ……………………………5
1.4.2 PSPA-Eclipse的優點………………………………6
第二章 文獻探討 …………………………………………7
2.1個人軟體流程 …………………………………………7
2.2 PSP流程演進 …………………………………………8
2.3 PSP程序的結構………………………………………10
第三章 PSP協定 …………………………………………12
3.1協定的內容……………………………………………12
3.1.1 PSPA Client-Server協定 ………………………14
3.1.2 PSPA Client-Development Tool協定 …………25
3.2資料格式………………………………………………29
第四章 PSPA-Eclipse系統設計…………………………31
4.1系統描述………………………………………………31
4.2系統需求………………………………………………31
4.2.1 Eclipse Agent子系統……………………………31
4.2.2 PSPA Client子系統………………………………32
4.2.3 PSPA Server子系統………………………………32
4.3系統規格與介面………………………………………34
4.3.1介面…………………………………………………34
4.3.2 Eclipse Agent子系統……………………………34
4.3.3 PSPA Client子系統………………………………34
4.3.4 PSPA Server子系統………………………………35
4.4軟體架構………………………………………………36
4.5資料庫設計……………………………………………37
4.5.1客服端之PSP資料庫架構 …………………………37
4.5.2伺服器之PSP資料庫架構 …………………………41
4.6 類別設計 ……………………………………………46
4.6.1 Eclipse Agent子系統……………………………46
4.6.2 PSPA Client子系統………………………………47
4.6.3 PSPA協定 …………………………………………49
4.6.4 PSPA Server子系統………………………………51
4.6.5 PSPA-Eclipse系統流程 …………………………53
4.7範例說明………………………………………………54
4.8 PSPA Eclipse系統特性 ……………………………65
4.8.1 PSPA Eclipse系統有以下五個功能 ……………65
4.8.2 PSPA Eclipse系統有以下三個特色 ……………65
第五章 結論與未來研究方向……………………………66
5.1結論……………………………………………………66
5.2未來研究方向…………………………………………67
參 考 文 獻………………………………………………68
附 錄 ……………………………………………………70
附錄A：安裝說明…………………………………………70
附錄B：操作說明…………………………………………72

[1]A. Babar, J. Potter, “Adapting the personal software process (PSP) to formal methods,” Proceedings on Software Engineering Conference, pp. 192-201, 2005.
[2]W.S. Humphrey, “Introduction to the Personal Software Process(sm),” Addison-Wesley Professional, 1996.
[3]W.S. Humphrey, The Complete PSP Book: “A Discipline for software Engineering,” Addison-Wesley Professional, 1994.
[4]W.S. Humphrey, “Pathways to Process Maturity: The Personal Software Process and Team Software Process,” SEI Interactive, 1999.
[5]I. Jonathan Maletic, Anita Howald, Andrian Marcus, “Incorporating PSP into a Traditional Software Engineering Course: An Experience Report,” Software Engineering Education and Training, pp. 89-97, 2001.
[6]Dashboard URL：http://processdash.sourceforge.net./
[7]Hackystat URL：http://hackydev.ics.hawaii.edu/hackyDevSite/home.do
[8]P. M. Johnson, H. Kou, J. Agustin, C. Chan, C. Moore, J. Miglani, S. Zhen; W.J. Doane, Beyond the Personal Software Process: “Metrics collection and analysis for the differently disciplined,” Proceedings of the 25th International Conference on Software Engineering, pp. 641-646, 2003.
[9]A. Sillitti, A. Janes, G. Succi, T. Vernazza, “Collecting, integrating and analyzing software metrics and personal software process data,” Proceedings of the 29th Euromicro Conference, pp. 336-342, 2003.
[10]W. Hayes, “Using a Personal Software Process SM to Improve Performance,” METRICS, Fifth International Symposium on Software Metrics, pp. 61-71, 1998.
[11]M. Morisio, “Applying the PSP in Industry,” IEEE Software, pp. 90-95, 2000.
[12]E. James, “Scientific Management Meets the Personal Software Process,” IEEE Software, pp. 12-14, 2003.
[13]R.F. Grove, “Using the personal software process to motivate good programming practices,” ACM Press, pp. 98-101, 1998.
[14]L. Hou, J. Tomayko, “Applying the Personal Software Process in CS1: An Experiment,” ACM SIGCSE Bulletin, pp. 322-325, 1998.
[15]C. Wohlin, A. Wesslèn, “Understanding Software Defect Detection in the Personal Software Process,” Ninth International Symposium on Software Reliability Engineering, pp. 49-58, 1998.
[16]W.S. Humphrey, “Using A Defined and Measured Personal Software Process,” IEEE Software, pp. 77-88, 1996.