跳到主要內容

臺灣博碩士論文加值系統

(3.235.56.11) 您好!臺灣時間:2021/07/29 03:33
字體大小: 字級放大   字級縮小   預設字形  
回查詢結果 :::

詳目顯示

: 
twitterline
研究生:詹正吉
研究生(外文):Cheng-Chi Chan
論文名稱:以模型為基礎之物件導向需求工程
論文名稱(外文):A Model-based Object-oriented Approach to Requirement Engineering
指導教授:朱正忠朱正忠引用關係
指導教授(外文):William Cheng-Chung Chu
學位類別:碩士
校院名稱:東海大學
系所名稱:資訊工程與科學系
學門:工程學門
學類:電資工程學類
論文種類:學術論文
論文出版年:2007
畢業學年度:95
語文別:中文
論文頁數:53
中文關鍵詞:需求工程軟體模型物件導向
外文關鍵詞:Object-orientedrequirement engineeringsoftware model
相關次數:
  • 被引用被引用:4
  • 點閱點閱:270
  • 評分評分:
  • 下載下載:82
  • 收藏至我的研究室書目清單書目收藏:0
大部分需求文件都用模糊的自然語言以及不精確的格式來描述,如果要把這種需求文件轉換成軟體開發中的物件導向分析以及物件導向設計階段所需的文件時,將會需要投入更多的成本,而且還有不一致的狀況產生。為了解決這個問題,在這篇論文當中,我們提出以模型為基礎之物件導向需求工程,一個新的需求模型Object-oriented Requirement Model(OORM)可以幫助系統開發者有系統地擷取需求,並且可以讓接下來的分析階段,設計階段使用,而不會有不一致的情況產生。以模型為基礎之物件導向需求工程不但可以增加需求階段的效率,也可以幫助簡化軟體開發流程裡的需求階段轉換到分析、設計階段,進而解決不一致的情況產生,降低開發成本。
Most requirement documents were written in ambiguous natural language which is less formal and imprecise. Without modeling the requirement documents, the knowledge of the requirement is hard to be kept in a way, that can be analyzed and integrated with artifacts in other phases of software life cycle, e.g. UML diagrams in analysis and design phases. Therefore, maintaining the traceability as well as maintained in a consistent in UML in a system. Transforming the requirement documents into well-accepted OO modeling languages of the following analysis and design phases for software development, with expertise and experiences, would be costly and inconsistent prone. In this paper, we propose empirical Model-based Object-oriented Requirement Engineering (MORE) from an empirical viewpoint for software development. An innovative requirement model OORM is presented to systematically assist developers in producing requirement paradigms which can be used consistently in the following phases of analysis, design, and implementation. MORE is to promise not only the efficient requirement development, but also the feasibility of software evolution streamline with the integration of paradigms from all the phases of software lifecycle.
摘要 I
Abstract II
目錄 II
第一章 導論 2
1.1 前言 2
1.2 研究動機 2
1.3 研究目的 2
1.4 章節安排 2
第二章 背景知識與相關研究 2
2.1 物件導向 2
2.2 物件導向需求文件工程與需求文件工具之比較 2
2.3 物件導向模型與模糊邏輯 2
第三章 物件導向需求模型 2
3.1 軟體需求擷取流程 2
3.2 客戶需求 2
3.3 需求規格 2
3.3.1 專業知識領域資訊資料庫 2
3.3.2 相關需求文件資料庫 2
3.3.3 物件導向需求資料庫 2
3.3.4 物件導向需求模型 2
3.4 擷取需求規格 2
3.5 軟體規格 2
第四章 案例研究 2
第五章 結論與未來方向 2
參考文獻 2
1V. Harput, H. Kaindl and S. Kramer, “Extending Function Point Analysis of Object-Oriented Requirements Specifications,” the Proceedings of the 11th IEEE International Software Metrics Symposium (METRICS'05), Sept. 19-22, 2005, pp. 39.
2International Function Point Users Group. Function Point Counting Practices Manual, Release 4.1.1, 2000.
3H. Kaindl, “Is object-oriented requirements engineering of interest?,” Requirement Engineering, vol. 10, no. 1, 2005, pp. 81-84.
4J. Lee and Y.-Y. Fanjiang, “Modeling imprecise requirements with XML,” Information and Software Technology, vol. 45, no.7, 2003, pp. 445-460.
5J.E. Kasser, “Object-Oriented Requirements Engineering and Management”, the Proceedings of the SETE 2003.
6X. L. Tran and J.E. Kasser, “Towards improving the recognition and correction of poor requirements,” the Proceedings of SETE 2005, pp. 1-13.
7I. F. Hooks, “Writing Good Requirements,” the Proceedings of the 3rd NCOSE International Symposium, vol. 2, 1993.
8R.S. Carson, “Keeping the Focus During Requirements Analysis,” the Proceedings of the 11th International Symposium of the International Council on Systems Engineering (INCOSE), 2001.
9D. Xu, V. Goel and K. Nygard, “An Aspect-Oriented Approach to Security Requirements Analysis,” the Proceedings of the 30th Annual International Computer Software and Applications Conference (COMPSAC'06), 2006, pp. 79-82.
10A. Amirat, D. Meslati and M. T. Laskri, “An Aspect-Oriented Approach in Early Requirements Engineering,” the Proceedings of the IEEE International Conference on Computer Systems and Applications, 2006, pp. 1055-1058.
11P. Coad and E. Yourdon, OOA – Object-Oriented Analysis 2nd Edition, Prentice Hall, 1990.
12H. Kaindl, “Difficulties in the transition from OO analysis to design,” IEEE Software, vol. 16, no. 5, Oct., 1999, pp. 94-102.
13M. Lubars, C. Potts and C. Richter, “Developing Initial OOA Models,” the Proceedings of the Fifteenth International Conference on Software Engineering (ICSE-15), 1993, pp. 255–264.
14A.M. Salem, M.O. Darter and B. Ramanujam, “A Practical Method for Performing Object Oriented Requirement Analysis,” the Proceedings of International Conference on Computer Science, 2005.
15X. Zhu and Z. Jin, “Detecting of requirements inconsistency: an ontology-based approach,” the Proceedings of the 2005 The Fifth International Conference on Computer and Information Technology, 2005, pp.869- 875.
16V. Lamsweerde, R. Darimont and E. Letier, “Managing Conflict in Goal-Driven Requirements Engineering,” IEEE Transactions on Software Engineering, vol.24, no.12, 1998, pp. 908-926.
17A. Finkelstein, D. Gabbay, A. Hunter, J. Kramer and B. Nuseibeh, “Inconsistency Handling in Multi-Perspective Specifications,” IEEE Transactions on Software Engineering, vol. 20, no.8, 1994, pp. 569-578.
18C. Heitmeyer, R. Jeffords and D. Kiskis, “Automated Consistency Checking Requirements Specifications,” ACM Transactions on Software Engineering and Methodology, vol. 5, no. 3, 1996, pp. 231-261.
19S. Clarke, J. Murphy and M. Roantree, “Composition of UML Design Models: A Tool to Support the Resolution of Conflicts,” the Proceedings of the 5th International Conference on Object-Oriented Information Systems, 1998, pp. 464-479.
20J. Lee, and N.L. Xue, “FOOM: a fuzzy object-oriented modeling for imprecise requirements,” the Proceeding of the North American Fuzzy Information Processing Society - NAFIPS, 1998, pp. 345-349.
21J. Lee and J.Y. Kuo, “A new approach to requirements trade-off analysis for complex systems,” IEEE Transactions on Knowledge and Data Engineering, vol. 10, no. 4, pp. 551-562, 1998.
22H. Kaindl, “A practical approach to combining requirements definition and object-oriented analysis,” Annals of Software Engineering, vol. 3, 1997, pp. 319-343.
連結至畢業學校之論文網頁點我開啟連結
註: 此連結為研究生畢業學校所提供,不一定有電子全文可供下載,若連結有誤,請點選上方之〝勘誤回報〞功能,我們會盡快修正,謝謝!
QRCODE
 
 
 
 
 
                                                                                                                                                                                                                                                                                                                                                                                                               
第一頁 上一頁 下一頁 最後一頁 top
1. 許榮富、楊文金、洪振方(1990)。學習環的理論基礎及其內涵分析──物理概念教學理念的新構思。物理會刊,12(5),375-398。
2. 莊麗娟(1995)。Campione 和Brown 的「漸進提示動態評量」。高市文教,56,49-51。
3. 莊嘉坤(1995)。認知研究在科學教育的省思。屏師科學教育,1,25-29。
4. 魏麗敏(1995)。後設認知知學習理論與策略。學生輔導,38,66-75。
5. 郭金美(1999)。建構主義教學方法─影響學童光學概念學習教學模式的研究。嘉義師院學報,13,157-201。
6. 陳嘉成(1998)。合作學習式概念構圖在國小自然科教學之成效研究。教育與心理研究,21,107-128。
7. 張景媛(1998)。新學習時代的來臨:建構學習的理論與實務。教育研究資訊,6(1),52-65。
8. 張景媛(1991)。大學生認知風格、動機與自我調整因素,後設認知與學業成績關係之研究。教育心理學報,24,145-161。
9. 蘇育任(1993)。自然科學之新趨勢促進學生認知發展。國教輔導,33(1),16-18。
10. 鍾聖校(1994)。對科學教育錯誤概念研究之省思。教育研究資訊,2(3),89-110。
11. 鄭麗玉(2001)。如何改變學生的迷思概念。教師之友,39(5),28-36。
12. 潘文福(1997)。國小學生種子萌芽迷思概念之探討。屏師科學教育,6,18-27。
13. 劉伍貞(1996)。國小學生月相概念學習之研究。屏東師範學院國民教育研究所碩士論文,未出版,屏東。
14. 葉連祺、林淑萍(2003)。布魯姆認知領域教育目標分類修訂版之探討。教育研究月刊,105期,頁94-106。
15. 陳李綢(1988)。學習策略的研究與教學。資優教育季刊,29,15-24。