Title page for 965202001


[Back to Results | New Search]

Student Number 965202001
Author Meng-Shiuan Shie(謝孟軒)
Author's Email Address No Public.
Statistics This thesis had been viewed 886 times. Download 635 times.
Department Computer Science and Information Engineering
Year 2008
Semester 2
Degree Master
Type of Document Master's Thesis
Language zh-TW.Big5 Chinese
Title Design and Implementation of Goal-driven Approach to Requirements Traceability
Date of Defense 2009-07-10
Page Count 67
Keyword
  • Design
  • Goal
  • Goal-driven
  • Implementation
  • Requirements Traceability
  • Traceability
  • Abstract 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.
    Table of Content 摘要ii
    Abstractiii
    致謝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
    Reference [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.
    Advisor
  • Jonathan Lee(李允中)
  • Files
  • 965202001.pdf
  • approve immediately
    Date of Submission 2009-07-15

    [Back to Results | New Search]


    Browse | Search All Available ETDs

    If you have dissertation-related questions, please contact with the NCU library extension service section.
    Our service phone is (03)422-7151 Ext. 57407,E-mail is also welcomed.