(34.226.234.102) 您好!臺灣時間:2021/05/12 09:56
字體大小: 字級放大   字級縮小   預設字形  
回查詢結果

詳目顯示:::

我願授權國圖
: 
twitterline
研究生:湯佳天
研究生(外文):Chia-Tien Tang
論文名稱:問題單處理與專案派工系統之整合與實作
論文名稱(外文):Integration of issue tracking and task assignment tool
指導教授:留忠賢留忠賢引用關係蔡明達蔡明達引用關係
指導教授(外文):Chung-Shyan LiuMing-Ta Tsai
學位類別:碩士
校院名稱:中原大學
系所名稱:資訊工程研究所
學門:工程學門
學類:電資工程學類
論文種類:學術論文
論文出版年:2009
畢業學年度:97
語文別:中文
論文頁數:33
中文關鍵詞:專案派工缺失報告問題單處理
外文關鍵詞:Task assignmentIssue TrackingDefect report
相關次數:
  • 被引用被引用:0
  • 點閱點閱:850
  • 評分評分:系統版面圖檔系統版面圖檔系統版面圖檔系統版面圖檔系統版面圖檔
  • 下載下載:0
  • 收藏至我的研究室書目清單書目收藏:0
目前大部分問題單處理的工具,通常都需要以人工的方式填入實際工時等資訊,不但容易錯誤,有些比較複雜或需要多人處理的問題,不僅不容易追蹤控管,每位成員的實際工時也很難精確地計算出來。同時在資源分配方面,也常必頇使用不同的工具,因此管理階層對於問題單處理,派工及資源分配三方面,也很難有一個通盤的考量。
在本篇論文中,我們整合了問題單處理軟體 Jira及可用於派工的軟體 XPlanner。當使用者將問題單填入 Jira 之後,能將必要的欄位匯出到 XPlanner中,此時可以透過 XPlanner 進行分工計畫,派工及進度追蹤。然後在問題解決並確認結案之後,將實際工時匯回 Jira,並將每一個處理問題的成員的實際工作時數,加總後匯到一個工時匯報系統中。
Most existing issue tracking tools still require users to manually fill in actual efforts for resolving issues and other related information. This is error prone. It is also difficult to monitor and control complex issues or issues that need to be handled by more than one people, as it is usually not easy to compute precisely the efforts of each member in resolving such issues. Furthermore, different software tools are needed for resource allocation. Therefore, it is difficult for a manager to have a comprehensive view regarding issue tracking, task assignment and resource allocation.
In this thesis, we will present a system that integrated an issue tracking tool, Jira, with XPlanner, which can also be used as a task assignment tool. When an issue is reported by a user using Jira, the related fields will be exported to XPlanner. A manager can then use XPlanner for work breakdown, task assignment and progress monitoring. After an issue is resolved, the actual efforts will be computed by the XPlanner and then reported back to Jira.
目錄
中文摘要 ..................................................................................................... I
Abstract ...................................................................................................... II
致謝 ........................................................................................................... III
目錄 .......................................................................................................... IV
圖形目錄 ................................................................................................. VII
表格目錄 ................................................................................................. VII
第一章 簡介............................................................................................... 1
1.1 前言 ............................................................................................... 1
1.2 動機與目的 ................................................................................... 3
1.3 章節概述 ....................................................................................... 5
第二章 背景知識 ...................................................................................... 6
2.1 問題單處理 ................................................................................... 6
2.2 Jira: 問題單處理及追蹤系統 ...................................................... 8
2.3 XPlanner........................................................................................ 9
第三章 系統架構設計 ............................................................................ 11
3.1 系統架構 ..................................................................................... 11
3.2 狀態轉換 ..................................................................................... 12
第四章 系統實作 .................................................................................... 15
4.1 實作方法 ..................................................................................... 15
4.2 操作流程 ..................................................................................... 16
4.3 討論 ............................................................................................. 21
第五章 結論與未來展望 ........................................................................ 22
參考文獻 ................................................................................................... 23
附錄一 (Appendix A) ....................................................................... 24
A. 程式說明文件 .............................................................................. 24
作者簡介 ................................................................................................... 26

圖形目錄
圖1. 問題單處理狀態 ................................................................ 6
圖2. XPlanner Domain Model ................................................. 10
圖3. 整合系統架構 .................................................................. 13
圖4. 整合XPlanner的處理流程 ............................................ 13
圖5. Jira同步到XPlanner的片段程式 .................................. 17
圖6. XPlanner同步到Jira的片段程式 .................................. 18
圖7. JIRA issue同步到XPlanner ........................................... 19
圖8. 同步後XPlanner產生一工作 ......................................... 19
圖9. 在XPlanner完成工作 ..................................................... 20
圖10. JIRA問題單取得工時記錄 ............................................ 20
圖11. 系統整合循序圖 ............................................................. 24

表格目錄
表格 1. JIRA狀態轉換及XPlanner工作項目對照 ................ 14
[1] J. Anvik. Automating Bug Report Assignment. In Proc. ICSE 2006,
May 2006, pp. 937-940.
[2] J. Anvik, L. Hiew and G. C. Murphy. Who Should Fix This Bug? In
Proc. ICSE 2006, May 2006, pp. 361-370.
[3] N. Bettenburg, S. Just, A. Schröter, C. Weiss, R. Premraj and T.
Zimmermann. What Makes a Good Bug Report? In Proc. ACM
SIGSOFT 2008/FSE-16, November 2008, pp. 308-318.
[4] G. Canfora and L. Cerulo. Where is Bug Resolution Knowledge
Stored? In Proc. MSR 2006, May 2006, pp. 183-184.
[5] Extreme Programming, June 2008.
http://www.extremeprogramming.org/.
[6] Hibernate, June 2008. http://www.hibernate.org/.
[7] JIRA, June 2008. http://www.atlassian.com/software/jira/.
[8] B. Kenmei, G. Antoniol and M. Di Penta. Trend Analysis and Issue
Prediction in Large-Scale Open Source Systems. In Proc. CSMR
2008, April 2008, pp. 73-82.
[9] C. Prause, M. Scholten, A. Zimmermann, R. Reiners and Markus
Eisenhauer. Managing the Iterative Requirements Process in a
Multi-National Project using an Issue Tracker. In Proc. IEEE ICGSE
2008, August 2008, pp. 151-159.
[10] Spring, June 2008. http://www.springsource.org/.
[11] M. Storey, J. Ryall, R. Bull, D. Myers and J. Singer. TODO or To
Bug: Exploring How Task Annotations Play a Role in the Work
Practices of Software Developers. In Proc. ICSE 2008, May 2008, pp.
252-260.
[12] Struts, June 2008. http://struts.apache.org/.
[13] D. Wahyudin, A. Schatten, D. Winkler, A. Tjoa and S. Biffl. Defect
Prediction using Combined Product and Project Metrics: A Case
Study from the Open Source Apache MyFaces Project Family. 34th
Euromicro Conference Software Engineering and Advanced
Applications, September 2008, pp. 207-215.
[14] WebWork, June 2008. http://opensymphony.com.
[15] C. Weiß, R. Premraj, T. Zimmermann and A. Zeller. How Long will
it Take to Fix This Bug? In Proc. MSR 2007, May 2007, pp. 1-10.
[16] XPlanner, June 2008. http://www.xplanner.org/.
[17] A. Zeller. Why Programs Fail. Morgan Kaufmann, 2005.
QRCODE
 
 
 
 
 
                                                                                                                                                                                                                                                                                                                                                                                                               
第一頁 上一頁 下一頁 最後一頁 top
系統版面圖檔 系統版面圖檔