設計與實作以目標驅動之需求追溯方法

以作者查詢圖書館館藏

、以作者查詢臺灣博碩士

、以作者查詢全國書目

、勘誤回報

、線上人數：18

、訪客IP：18.222.100.35

姓名

謝孟軒(Meng-Shiuan Shie) 查詢紙本館藏

畢業系所

資訊工程學系

論文名稱

設計與實作以目標驅動之需求追溯方法
(Design and Implementation of Goal-driven Approach to Requirements Traceability)

相關論文

★ 移動代理人監控系統之設計與實作	★ 以正規表式法為基礎之地理編碼服務設計與實作
★ Android應用程式開發之持續整合系統	★ 基於設計矩陣之需求追溯關係建立方法
★ 點對點移動代理人之設計與實作與於車資通訊之應用	★ 網頁內容叢集分類法之設計與實作
★ 設計與實作於行動裝置上以XUL為基礎之介面呈現	★ Android平台上以OSGi為基礎之服務遞送
★ 利用網頁內容結構之區塊擷取方法以呈現新聞服務	★ 設計與實作以感測器為中心的查詢機制
★ 針對路徑規劃服務之Web 2.0系統設計與實作	★ 整合OSGi與RESTful服務之BPEL引擎
★ 利用文件相似度以轉換網路內容為OSGi Bundles	★ 量測Java類別的耦合關係
★ 轉換Android應用程式為OSGi Service	★ 物聯網應用之Context塑模方法

檔案

[Endnote RIS 格式]

[Bibtex 格式]

[相關文章]

[文章引用]

[完整記錄]

[館藏目錄]

[檢視]

[下載]

本電子論文使用權限為同意立即開放。
已達開放權限電子全文僅授權使用者為學術研究之目的，進行個人非營利性質之檢索、閱讀、列印。
請遵守中華民國著作權法之相關規定，切勿任意重製、散佈、改作、轉貼、播送，以免觸法。

摘要(中)

需求追溯關係與變更影響分析在軟體開發上越來越受到重視，然而龐大的系統有著大量且關係複雜的文件，以人工方式維護追溯關係是一件複雜且麻煩的事，因此如何使用一個系統化的、有步驟的方式來管理與建立追溯關係為軟體開發之重要議題。
本篇論文將延伸「以目標趨動之需求追溯方法」之研究，將需求追溯擴充至設計模型與程式碼層級。在設計階段，使用目標驅動使用案例之系統候選與設計結構矩陣產生之使用案例分割區塊進行系統架構設計與細部設計。並進一步使用設計結構矩陣建立使用案例與系統設計的追溯關係。於系統實作階段，我們剖析程式碼並於設計結構矩陣中自動建立設計模型與程式碼的追溯關係。我們並將此方法設計與實作成一個系統，提供一個系統化的、有步驟的方式操作系統管理需求追溯關係。

摘要(英)

In software development, more and more people pay attention to requirement traceability and change impact analysis. However, in a large system, it is hard to manage a large number of traceability relations between documents manually. Therefore, we need a systematic approach to handle traceability relations and perform change impact analysis when requirements change.
In this paper, we use design structure matrix (DSM) to manage traceability relations between use cases, design models and codes. In design phase, we use alternatives of GDUC and use case blocks generated from DSM partitioning to design system architecture and perform system detail design. We then use DSM to establish the traceability relations from use cases to design models. In implementation phase, we can parse the codes and establish the traceability relations between design models and codes in DSM automatically. We also design and implement a system that can be used to handle traceability relations and requirement changes.

關鍵字(中)

★ 實作
★ 設計
★ 需求追溯
★ 追溯
★ 目標驅動
★ 目標

關鍵字(英)

★ Goal-driven
★ Traceability
★ Requirements Traceability
★ Design
★ Implementation
★ Goal

論文目次

摘要 ii
Abstract iii
致謝 iv
目錄 v
表目錄 vii
圖目錄 viii
第一章、緒論 1
1-1 背景 1
1-2 動機 2
1-3 論文架構 2
第二章、背景知識介紹 4
2-1 設計結構矩陣(Design Structure Matrix) 4
2-1-1 分割(Partitioning) 6
2-2 目標驅動使用案例(Goal-Driven Use Cases) 7
2-3 以目標趨動之需求追溯方法(A Goal-Driven Approach to Relations Traceability) 9
2-4 組織使用案例(Organize the Use Cases) 13
第三章、以目標驅動之需求追溯方法 16
3-1 建立設計模型(Design Model Establishment) 20
3-1-1 分析系統目標階層與使用案例分割區塊(Analyze Goal Hierarchy and Use Case Blocks) 21
3-1-1-1 功能區塊(Functional Blocks) 21
3-1-1-2 系統候選(Alternatives) 23
3-1-2 建立設計模型(Establish Design Model) 24
3-1-3 透過分析模型檔案辨識出追溯關係(Identify Traceability Relations by Parsing Model Files) 26
3-2 實作系統與撰寫程式碼(Implementation) 28
3-2-1 產生程式碼樣板(Generate Code Template) 28
3-2-2 實作系統(Implement System) 29
3-2-3 透過分析模型檔案辨識出追溯關係(Identify Traceability Relations by Parsing Model Files) 30
第四章、系統設計與實作 31
4-1 系統架構 31
4-1-1 系統目標與使用案例追溯關係分析服務系統(Goal and Use Case Traceability Analyzing Service) 32
4-1-2 使用案例與系統設計模型追溯關係分析服務系統(Use Case and Design Model Traceability Analyzing Service) 36
4-1-3 系統設計模型與程式碼追溯關係分析服務系統(Design Model and Code Traceability Analyzing Service) 37
4-1-4 追溯關係與設計結構矩陣同步化服務系統(Traceability-DSM Synchronization Service) 38
第五章、案例分析 41
5-1 案例介紹 41
5-2 模型化與公式化系統目標(Formulate and Analyze Goals) 41
5-3 建立使用案例(Establish Use Case) 42
5-4 使用DSM計算系統目標之間的相互關係(Evaluate Goals Interaction Using DSM) 44
5-4-1 分析使用案例之間的關係(Identify Relation between Use Cases) 44
5-4-2 計算使用案例與系統目標之間的關係(Evaluate Relation from Use Case to Goal) 46
5-4-3 分析系統目標之間的關係(Analyze Relation between Goals) 46
5-5 建立目標階層與使用案例分割區塊(Establish Goal Hierarchy and Use Case Blocks) 47
5-6 建立系統設計模型(Establish Design Model) 49
第六章、相關文獻 51
第七章、結論 53
7-1 貢獻 53
7-2 未來研究 53
參考文獻 55

參考文獻

[1] Wen-Tin Lee. “A Goal-driven Approach to Relations Traceability”, Ph.D. dissertation of National Central University, Taiwan, 2008
[2] Jonathan Lee, Nien-Lin Xue. “Analysis User Requirements by the Use Cases：A Goal-Driven Approach”. IEEE Software, 16(4):92–101, July/August 1999.
[3] Jonathan Lee, Nien-Lin Xue, “Structuring Requirement Specifications with Goals”, Information and Software Technology, 43(2):121–135, February 2001.
[4] Ivar Jacobson. Advanced Use Case Modeling. Addison Wesley. P243-263, 2005
[5] D. V. Steward. “The design structure system: A method for managing the design of complex systems”. IEEE Transactions on Engineering Management, 28:71–74, 1981.
[6] T. R. Browning. “Modeling and analyzing cost, schedule, and performance in complex system product development”. PhD thesis, Massachusetts Inst. Technology, Cambridge, MA, 1998.
[7] T. R. Browning. “Applying the design structure matrix to system decomposition and integration problems: A review and new directions”. IEEE Transactions on Engineering Management, 48(3):292–306, August 2001.
[8] D. V. Steward. “Partitioning and tearing systems of equations”. Journal of the Society for Industrial and Applied Mathematics: Series B, Numerical Analysis, 2(2).
[9] Jane Cleland-Huang, Raffaella Settimi, Eli Romanova, et al. “Best Practices for Automated Traceability”. IEEE Computer, Vol.40, p27-p35, 2007
[10] Giuliano Antoniol, Gerardo Canfora, Gerardo Casazza, Andrea De Lucia, and Ettore Merlo . “Recovering Traceability Links between Code and Documentation”. IEEE Transactions on Software Engineering, Vol.28, No.10, p 970-983, 2002
[11] G. Spanoudakis, A. Zisman, E. Pe’rez-Minana, and P. Krause. “Rule-based generation of requirements traceability relations”. Journal of Systems and Software, 72(2):105–127, 2004.
[12] Andrian Marcus, Jonathan I. Maletic. “Recovering Documentation-to-Source-Code Traceability Links using Latent Semantic Indexing”. IEEE In Proceedings of the 25th International Conference on Software Engineering, p125- 135, 2003 , Portland, Oregon
[13] B. Ramesh and M. Edwards. “Issues in the development of a requirements traceability model”. In Proceedings of the International Conference on Requirements Engineering, pages 256–259, Jan 1993.
[14] O. C. Z. Gotel and A. C. W. Finkelstein. “An analysis of the requirements traceability problem”. In Proceedings of the International Conference on Requirements Engineering, pages 94–101, Appril 1994.
[15] M. Jarke. “Requirements tracing”. Communications of the ACM, 41(12):32–36, December 1998.
[16] B. Ramesh, T. Powers, C. Stubbs, and M. Edwards. “Implementing requirements traceability: a case study”. In Proceedings of the Second IEEE International Symposium on Requirements Engineering, pages 89–95, March 1995.
[17] J.-P. Corriveau. “Traceability process for large oo projects”. IEEE Computer, 29(9):63–68, September 1996.
[18] R. Watkins and M. Neal. “Why and how of requirements tracing”. IEEE Software, 11(4):104–106, Jul 1994.

指導教授

李允中(Jonathan Lee)

審核日期

2009-7-15

推文