建立一個用來評核自然語言需求品質的線上資訊系統

以作者查詢圖書館館藏

、以作者查詢臺灣博碩士

、以作者查詢全國書目

、勘誤回報

、線上人數：35

、訪客IP：3.138.36.168

姓名

劉佳惠(Chia-Hui Liu) 查詢紙本館藏

畢業系所

資訊管理學系

論文名稱

建立一個用來評核自然語言需求品質的線上資訊系統
(A Design and Development of Online Quality Evaluation System for Natural Language Based Software Requirements)

相關論文

★ 專案管理的溝通關鍵路徑探討─以某企業軟體專案為例	★ 運用並探討會議流如何促進敏捷發展過程中團隊溝通與文件化：以T銀行系統開發為例
★ 專案化資訊服務中人力連續派遣決策模式之研究─以高鐵行控資訊設備維護為例	★ 以組織正義觀點介入案件指派決策之研究
★ 應用協調理論建立系統軟體測試中問題改善之協作流程	★ 應用案例式推理於問題管理系統之研究 -以筆記型電腦產品為例
★ 運用限制理論於多專案開發模式的人力資源配置之探討	★ 應用會議流方法於軟體專案開發之個案研究：以翰昇科技公司為例
★ 多重專案、多期再規劃的軟體開發接案決策模式：以南亞科技資訊部門為例	★ 會議導向敏捷軟體開發及系統設計：以大學畢業專題為例
★ 一種基於物件、屬性導向之變更影響分析方法於差異化產品設計	★ 會議流方法對大學畢業專題的團隊合作品質影響之實驗研究
★ 實施敏捷式發展法於大學部畢業專題之行動研究 – 以中央大學資管系為例	★ 結合本體論與模糊分析網路程序法於軟體測試之風險與風險關聯辨識
★ 在軟體反向工程中針對UML結構模型圖之線上品質評核系統	★ 以模糊專家系統實作軟體專案調適準則

檔案

[Endnote RIS 格式]

[Bibtex 格式]

[相關文章]

[文章引用]

[完整記錄]

[館藏目錄]

至系統瀏覽論文 ( 永不開放)

摘要(中)

現今軟體專案開發時程日益縮短，如何在開發前期—需求擷取初期，即能有效地掌控軟體需求品質，使得後續開發流程更加順利，儼然成為組織的重要任務之一。就需求開發階段來說，許多研究建議藉由評核系統需求描述來確保其品質，並據以發展出不同的度量。此外，組織成員若能將評核知識分享於組織內，使其有效地為組織所運用，以協助日後類似需求的系統實作。因此，本研究專注於需求開發階段，設計並實作一個線上資訊評核系統—稱為Online Requirement Evaluation and Knowledge Sharing System(簡稱為OREKSS)，來讓專案相關人員輸入自然語言之需求描述，並從後續分析設計階段的使用案例模型觀點來評核該需求描述的完整度，使得專案相關人員得以掌握開發的脈絡，繼而協助提升開發效率。具體而言，OREKSS以不模糊性、必須性及可達成性等作為構成完整性之三個量測向度，並針對所輸入的需求描述依此三個向度計算其完整性指標值，再進一步提供修正建議。此外，OREKSS可讓使用者針對結果輸入意見回饋，來提供知識工程師作為優化系統之參考，以達系統永續改善之境界。

摘要(英)

Nowadays, as software project development life cycle becomes shorter and shorter, retaining quality of software project development has become a critical issue among organizations. By maintaining quality of software project development at early phase of requirement elicitation, organizations can both decrease development-related cost and increase efficiency in software project development. Furthermore, plenty of experts have proposed different methods to evaluate the quality of natural language based requirement to have more complete UML diagrams at early phase of software development; that is, system analysis. On the other hand, if members in an organization can share their knowledge of requirement evaluation with other members so that they can utilize it, organization will have better efficiency in requirement evaluation in the future. Hence, in this study, we propose an online evaluation system – Online Requirement Evaluation and Knowledge Sharing System (OREKSS), which aims at evaluating completeness of nature language requirement from relative stakeholders. In addition, completeness is consisted of three quality dimensions – unambiguity, necessity, and reachability. After relative stakeholders input their requirement description, OREKSS will provide index of unambiguity, necessity, reachability, and completeness as well as recommendation to make requirement more complete. Moreover, knowledge engineers can improve evaluation rules of OREKSS so that requirement evaluation results can meet relative stakeholders’ needs. Therefore, in software project development, OREKSS not only augments efficiency but also reduce cost at early phase by evaluating requirement completeness.

關鍵字(中)

★ 軟體工程
★ 需求萃取
★ 自然語言需求
★ 需求完整性
★ 知識分享

關鍵字(英)

★ Software Engineering
★ Requirement Elicitation
★ Natural Language Requirement
★ Requirement Completeness
★ Knowledge Sharing

論文目次

摘要 i
Abstract ii
誌謝 iii
目錄 iv
圖目錄 vi
表目錄 viii
第一章緒論 1
1.1 研究背景 1
1.2 問題描述與目的 2
1.3 研究範圍與假設 4
1.4 研究架構 5
第二章文獻探討 7
2.1 自然語言需求之完整性 7
2.2 自然語言需求完整性之評核方法 10
2.3 評核的知識分享 14
2.4 評核完整性需求品質及運用知識分享之評核系統 15
第三章系統概念設計 17
3.1 名詞定義與解釋 17
3.2 模型架構：行為觀點 20
3.3 模型架構：結構觀點 23
第四章系統實作與展示 37
4.1 系統開發架構與環境 37
4.2 系統展示 46
第五章系統成果討論 59
5.1 需求評核系統比較 59
5.2 使用者驗證 66
第六章結論 81
6.1 研究貢獻 81
6.2 研究限制與未來發展 83
參考文獻 84

參考文獻

[1] Abdelaziz, A. A., El-Tahir, Y., & Osman, R. (2015, September). Adaptive Software Development for developing safety critical software. In Computing, Control, Networking, Electronics and Embedded Systems Engineering (ICCNEEE), 2015 International Conference on (pp. 41-46). IEEE.
[2] Adolph, S., Cockburn, A., & Bramble, P. (2002). Patterns for effective use cases. Addison-Wesley Longman Publishing Co., Inc.
[3] Alexander, I. (2003). Misuse cases: Use cases with hostile intent. IEEE software, 20(1), 58-66.
[4] Arora, C., Sabetzadeh, M., Briand, L., & Zimmer, F. (2015). Automated checking of conformance to requirements templates using natural language processing. IEEE transactions on Software Engineering, 41(10), 944-968.
[5] Aurum, A., Jeffery, R., Wohlin, C., & Handzic, M. (Eds.). (2013). Managing software engineering knowledge. Springer Science & Business Media.
[6] Azadegan, A., Cheng, X., Niederman, F., & Yin, G. (2013, January). Collaborative requirements elicitation in facilitated collaboration: report from a case study. In System Sciences (HICSS), 2013 46th Hawaii International Conference on (pp. 569-578). IEEE.
[7] Berry, D. M., & Kamsties, E. (2005). The syntactically dangerous all and plural in specifications. IEEE software, 22(1), 55-57.
[8] Bhatti, S. N., Usman, M., & Jadi, A. A. (2015). Validation to the Requirement Elicitation Framework via Metrics. ACM SIGSOFT Software Engineering Notes, 40(5), 1-7.
[9] Bjarnason, E., Runeson, P., Borg, M., Unterkalmsteiner, M., Engstrom, E., Regnell, B., ... & Feldt, R. (2014). Challenges and practices in aligning requirements with verification and validation: a case study of six companies. Empirical Software Engineering, 19(6), 1809-1855.
[10] Borowsky, R., & Masson, M. E. (1996). Semantic ambiguity effects in word identification. Journal of Experimental Psychology: Learning, Memory, and Cognition, 22(1), 63.
[11] Capilla, R., Jansen, A., Tang, A., Avgeriou, P., & Babar, M. A. (2016). 10 years of software architecture knowledge management: Practice and future.?Journal of Systems and Software,?116, 191-205.
[12] Casagrande, E., Woldeamlak, S., Woon, W. L., Zeineldin, H. H., & Svetinovic, D. (2014). NLP-KAOS for systems goal elicitation: Smart metering system case study.?IEEE Transactions on Software Engineering,?40(10), 941-956.
[13] Chanda, J., Kanjilal, A., Sengupta, S., & Bhattacharya, S. (2009, December). Traceability of requirements and consistency verification of UML use case, activity and Class diagram: A Formal approach. In Methods and Models in Computer Science, 2009. ICM2CS 2009. Proceeding of International Conference on (pp. 1-4). IEEE.
[14] Chechik, M., Nejati, S., & Sabetzadeh, M. (2012). A relationship-based approach to model integration. Innovations in Systems and Software Engineering, 8(1), 3-18.
[15] Chung, L., Nixon, B. A., Yu, E., & Mylopoulos, J. (2012). Non-functional requirements in software engineering (Vol. 5). Springer Science & Business Media.
[16] Dardenne, A., Van Lamsweerde, A., & Fickas, S. (1993). Goal-directed requirements acquisition.?Science of computer programming,?20(1), 3-50.
[17] Davis, A. M., Jordan, K., & Nakajima, T. (1997). Elements underlying the specification of requirements. Annals of Software Engineering, 3(1), 63-100.
[18] Deeptimahanti, D. K., & Babar, M. A. (2009, November). An automated tool for generating UML models from natural language requirements. In?Proceedings of the 2009 IEEE/ACM International Conference on Automated Software Engineering?(pp. 680-682). IEEE Computer Society.
[19] Deifel, B. (1999). A process model for requirements engineering of CCOTS. In Database and Expert Systems Applications, 1999. Proceedings. Tenth International Workshop on (pp. 316-320). IEEE.
[20] Dermeval, D., Vilela, J., Bittencourt, I. I., Castro, J., Isotani, S., Brito, P., & Silva, A. (2015). Applications of ontologies in requirements engineering: a systematic review of the literature.?Requirements Engineering, 1-33.
[21] Ding, W., Liang, P., Tang, A., & Van Vliet, H. (2014). Knowledge-based approaches in software documentation: A systematic literature review. Information and Software Technology,?56(6), 545-567.
[22] Dolques, X., Huchard, M., Nebut, C., & Reitz, P. (2012). Fixing generalization defects in UML use case diagrams. Fundamenta Informaticae, 115(4), 327-356.
[23] Duran, A., Ruiz-Cortes, A., Corchuelo, R., & Toro, M. (2002). Supporting requirements verification using XSLT. In Requirements Engineering, 2002. Proceedings. IEEE Joint International Conference on (pp. 165-172). IEEE.
[24] Ellis-Braithwaite, R., Lock, R., Dawson, R., & King, T. (2015). Repetition between stakeholder (user) and system requirements.?Requirements Engineering, 1-24.
[25] Eloranta, V. P., Isohanni, E., Lahtinen, S., & Sievi-Korte, O. (2015, September). To UML or not to UML?: Empirical Study on the Approachability of Software Architecture Diagrams. In Proceedings of the ASWEC 2015 24th Australasian Software Engineering Conference (pp. 101-105). ACM.
[26] Fantechi, A., Gnesi, S., Lami, G., & Maccari, A. (2003). Applications of linguistic techniques for use case analysis. Requirements Engineering, 8(3), 161-170.
[27] Ferrari, A., & Gnesi, S. (2012, September). Using collective intelligence to detect pragmatic ambiguities. In 2012 20th IEEE International Requirements Engineering Conference (RE) (pp. 191-200). IEEE.
[28] Ferrari, A., Spoletini, P., & Gnesi, S. (2015, August). Ambiguity as a resource to disclose tacit knowledge. In 2015 IEEE 23rd International Requirements Engineering Conference (RE) (pp. 26-35). IEEE.
[29] Fuggetta, A., & Di Nitto, E. (2014, May). Software process. In Proceedings of the on Future of Software Engineering (pp. 1-12). ACM.
[30] Genova, G., Fuentes, J. M., Llorens, J., Hurtado, O., & Moreno, V. (2013). A framework to measure and improve the quality of textual requirements. Requirements engineering, 18(1), 25-41.
[31] Gervasi, V., & Zowghi, D. (2005). Reasoning about inconsistencies in natural language requirements. ACM Transactions on Software Engineering and Methodology (TOSEM), 14(3), 277-330.
[32] Ghobadi, S. (2015). What drives knowledge sharing in software development teams: A literature review and classification framework.?Information & Management,?52(1), 82-97.
[33] Gomaa, H. (1992, January). An object-oriented domain analysis and modeling method for software reuse. In System Sciences, 1992. Proceedings of the Twenty-Fifth Hawaii International Conference on (Vol. 2, pp. 46-56). IEEE.
[34] Gurses, S., Seguran, M., & Zannone, N. (2013). Requirements engineering within a large-scale security-oriented research project: lessons learned. Requirements Engineering, 18(1), 43-66.
[35] Hadar, I., Soffer, P., & Kenzi, K. (2014). The role of domain knowledge in requirements elicitation via interviews: an exploratory study. Requirements Engineering, 19(2), 143-159.
[36] Hajri, I., Goknil, A., Briand, L. C., & Stephany, T. (2015, September). Applying product line Use case modeling in an industrial automotive embedded system: Lessons learned and a refined approach. In Model Driven Engineering Languages and Systems (MODELS), 2015 ACM/IEEE 18th International Conference on (pp. 338-347). IEEE.
[37] Han, D., Yang, Q., Xing, J., Li, J., & Wang, H. (2016). FAME: A UML-based framework for modeling fuzzy self-adaptive software. Information and Software Technology, 76, 118-134.
[38] Hanafiah, M., & Abdullah, R. (2014, November). An evaluation on components of experience based factory model in requirement engineering process: A preliminary study. In?Information Technology and Multimedia (ICIMU), 2014 International Conference on?(pp. 308-313). IEEE.
[39] Heimdahl, M. P. E., & Leveson, N. G. (1996). Completeness and consistency in hierarchical state-based requirements. IEEE transactions on Software Engineering, 22(6), 363-377.
[40] Heisel, M., & Souquieres, J. (1999, November). A method for requirements elicitation and formal specification. In International Conference on Conceptual Modeling (pp. 309-325). Springer Berlin Heidelberg.
[41] Hickey, A. M., & Davis, A. M. (2004). A unified model of requirements elicitation. Journal of Management Information Systems, 20(4), 65-84.
[42] Hofmann, H. F., & Lehner, F. (2001). Requirements engineering as a success factor in software projects. IEEE software, 18(4), 58.
[43] Holzmann, G. J. (1997). The model checker SPIN.?IEEE Transactions on software engineering,?23(5), 279.
[44] Horkoff, J., & Yu, E. (2016). Interactive goal model analysis for early requirements engineering. Requirements Engineering, 21(1), 29-61.
[45] Huertas, C., Gomez-Ruelas, M., Juarez-Ramirez, R., & Plata, H. (2011, August). A formal approach for measuring the lexical ambiguity degree in natural language requirement specification: Polysemes and Homonyms focused. In Uncertainty Reasoning and Knowledge Engineering (URKE), 2011 International Conference on (Vol. 1, pp. 115-118). IEEE.
[46] Hull, E., Jackson, K., & Dick, J. (2010). Requirements engineering. Springer Science & Business Media.
[47] Jurkiewicz, J., Nawrocki, J., Ochodek, M., & G?owacki, T. (2015). HAZOP-based identification of events in use cases. Empirical Software Engineering, 20(1), 82-109.
[48] Kakeshita, T., & Yamashita, S. (2015, July). A Requirement Management Education Support Tool for Requirement Elicitation Process of REBOK. In Applied Computing and Information Technology/2nd International Conference on Computational Science and Intelligence (ACIT-CSI), 2015 3rd International Conference on (pp. 40-45). IEEE.
[49] Kamp, H., & Reyle, U. (2013). From discourse to logic: Introduction to modeltheoretic semantics of natural language, formal logic and discourse representation theory (Vol. 42). Springer Science & Business Media.
[50] Khokhar, M. N., Mansoor, A., Khokhar, M. N., Rehman, S. U., & Rauf, A. (2010, June). MECA: Software process improvement for small organizations. In Information and Emerging Technologies (ICIET), 2010 International Conference on (pp. 1-6). IEEE.
[51] Kiyavitskaya, N., Zeni, N., Mich, L., & Berry, D. M. (2008). Requirements for tools for ambiguity identification and measurement in natural language requirements specifications. Requirements Engineering, 13(3), 207-239.
[52] Kruchten, P. B. (1995). The 4+ 1 view model of architecture. IEEE software, 12(6), 42-50.
[53] Kulak, D., & Guiney, E. (2012). Use cases: requirements in context. Addison-Wesley.
[54] Kulkarni, N., Parachuri, D., Dasa, M., & Kumar, A. (2012, December). Automated Analysis of Textual Use-Cases: Does NLP Components and Pipelines Matter?. In 2012 19th Asia-Pacific Software Engineering Conference (Vol. 1, pp. 326-329). IEEE.
[55] Kumar, D. D., & Sanyal, R. (2008, December). Static UML model generator from analysis of requirements (SUGAR). In?Advanced Software Engineering and Its Applications, 2008. ASEA 2008?(pp. 77-84). IEEE.
[56] Lami, G., & Ferguson, R. W. (2007). An empirical study on the impact of automation on the requirements analysis process. Journal of Computer Science and Technology, 22(3), 338-347.
[57] Manning, C. D., Surdeanu, M., Bauer, J., Finkel, J. R., Bethard, S., & McClosky, D. (2014, June). The Stanford CoreNLP Natural Language Processing Toolkit. In ACL (System Demonstrations) (pp. 55-60).
[58] Martini, A., Pareto, L., & Bosch, J. (2013, August). Communication factors for speed and reuse in large-scale agile software development. In Proceedings of the 17th international software product line conference (pp. 42-51). ACM.
[59] Massey, A. K., Rutledge, R. L., Anton, A. I., & Swire, P. P. (2014, August). Identifying and classifying ambiguity for regulatory requirements. In 2014 IEEE 22nd International Requirements Engineering Conference (RE) (pp. 83-92). IEEE.
[60] Misbhauddin, M., & Alshayeb, M. (2015). Extending the UML use case metamodel with behavioral information to facilitate model analysis and interchange. Software & Systems Modeling, 14(2), 813-838.
[61] Moketar, N. A., Kamalrudin, M., Sidek, S., Robinson, M., & Grundy, J. (2016, August). An automated collaborative requirements engineering tool for better validation of requirements. In Proceedings of the 31st IEEE/ACM International Conference on Automated Software Engineering (pp. 864-869). ACM.
[62] Ngai, E. W., & Chan, E. W. C. (2005). Evaluation of knowledge management tools using AHP. Expert systems with applications, 29(4), 889-899.
[63] Niu, N., Da Xu, L., & Bi, Z. (2013). Enterprise information systems architecture—Analysis and evaluation. IEEE Transactions on Industrial Informatics, 9(4), 2147-2154.
[64] Olmos, K., & Rodas, J. (2014). KMoS-RE: knowledge management on a strategy to requirements engineering. Requirements Engineering, 19(4), 421-440.
[65] Osborne, M., & MacNish, C. K. (1996, April). Processing natural language software requirement specifications. In Requirements Engineering, 1996., Proceedings of the Second International Conference on (pp. 229-236). IEEE.
[66] Overmyer, S. P., Lavoie, B., & Rambow, O. (2001, July). Conceptual modeling through linguistic analysis using LIDA. In Proceedings of the 23rd international conference on Software engineering (pp. 401-410). IEEE Computer Society.
[67] Pacheco, C., & Garcia, I. (2012). A systematic literature review of stakeholder identification methods in requirements elicitation. Journal of Systems and Software, 85(9), 2171-2181.
[68] Petre, M. (2013, May). UML in practice. In Proceedings of the 2013 International Conference on Software Engineering (pp. 722-731). IEEE Press.
[69] Petre, M. (2014). “No shit” or “Oh, shit!”: responses to observations on the use of UML in professional practice. Software & Systems Modeling, 13(4), 1225-1235.
[70] Philippo, E. J., Heijstek, W., Kruiswijk, B., Chaudron, M. R., & Berry, D. M. (2013, April). Requirement ambiguity not as important as expected—results of an empirical evaluation. In International Working Conference on Requirements Engineering: Foundation for Software Quality (pp. 65-79). Springer Berlin Heidelberg.
[71] Pittke, F., Leopold, H., & Mendling, J. (2015). Automatic detection and resolution of lexical ambiguity in process models. IEEE Transactions on Software Engineering, 41(6), 526-544.
[72] Rago, A., Marcos, C., & Diaz-Pace, J. A. (2016). Identifying duplicate functionality in textual use cases by aligning semantic actions. Software & Systems Modeling, 15(2), 579-603.
[73] Reggio, G., Ricca, F., & Leotta, M. (2014, August). Improving the quality and the comprehension of requirements: disciplined use cases and mockups. In 2014 40th EUROMICRO Conference on Software Engineering and Advanced Applications (pp. 262-266). IEEE.
[74] Robertson, S., & Robertson, J. (2012). Mastering the requirements process: Getting requirements right. Addison-wesley.
[75] Rosenkranz, C., Vranesic, H., & Holten, R. (2014). Boundary interactions and motors of change in requirements elicitation: a dynamic perspective on knowledge sharing. Journal of the Association for Information Systems, 15(6), 306.
[76] Sandhu, G., & Sikka, S. (2015, May). State-of-art practices to detect inconsistencies and ambiguities from software requirements. In Computing, Communication & Automation (ICCCA), 2015 International Conference on (pp. 812-817). IEEE.
[77] Sargent, R. G. (2013). Verification and validation of simulation models. Journal of simulation, 7(1), 12-24.
[78] Schobbens, P. Y., Heymans, P., & Trigaux, J. C. (2006, September). Feature diagrams: A survey and a formal semantics. In 14th IEEE International Requirements Engineering Conference (RE′06) (pp. 139-148). IEEE.
[79] Shah, U. S., & Jinwala, D. C. (2015). Resolving ambiguities in natural language software requirements: a comprehensive survey. ACM SIGSOFT Software Engineering Notes, 40(5), 1-7.
[80] Sharma, S., & Pandey, S. K. (2014, March). Requirements elicitation: Issues and challenges. In Computing for Sustainable Global Development (INDIACom), 2014 International Conference on (pp. 151-155). IEEE.
[81] Simons, A. J. (1999, July). Use cases considered harmful. In Technology of Object-Oriented Languages and Systems, 1999. Proceedings of (pp. 194-203). IEEE.
[82] Sindre, G., & Opdahl, A. L. (2005). Eliciting security requirements with misuse cases. Requirements engineering, 10(1), 34-44.
[83] Slankas, J., & Williams, L. (2013, May). Automated extraction of non-functional requirements in available documentation. In Natural Language Analysis in Software Engineering (NaturaLiSE), 2013 1st International Workshop on (pp. 9-16). IEEE.
[84] Some, S. S. (2006). Supporting use case based requirements engineering. Information and Software Technology, 48(1), 43-58.
[85] Subramaniam, K., Liu, D., Far, B. H., & Eberlein, A. (2004, June). UCDA: Use Case Driven Development Assistant Tool for Class Model Generation. In?SEKE(pp. 324-329).
[86] Torre, D. (2015, November). On validating UML consistency rules. In Software Reliability Engineering Workshops (ISSREW), 2015 IEEE International Symposium on (pp. 59-60). IEEE.
[87] Torre, D., Labiche, Y., & Genero, M. (2014, May). UML consistency rules: a systematic mapping study. In Proceedings of the 18th International Conference on Evaluation and Assessment in Software Engineering (p. 6). ACM.
[88] Tuunanen, T. (2003). A new perspective on requirements elicitation methods. JITTA: Journal of Information Technology Theory and Application, 5(3), 45.
[89] Van Lamsweerde, A., & Letier, E. (2000). Handling obstacles in goal-oriented requirements engineering.?IEEE Transactions on Software Engineering,?26(10), 978-1005.
[90] Wiegers, K., & Beatty, J. (2013).?Software requirements. Pearson Education.
[91] Wiesner, S., Peruzzini, M., Hauge, J. B., & Thoben, K. D. (2015). Requirements engineering. In Concurrent Engineering in the 21st Century (pp. 103-132). Springer International Publishing.
[92] Yang, H., Willis, A., De Roeck, A., & Nuseibeh, B. (2010, September). Automatic detection of nocuous coordination ambiguities in natural language requirements. In Proceedings of the IEEE/ACM international conference on Automated software engineering (pp. 53-62). ACM.
[93] Yue, T., Briand, L. C., & Labiche, Y. (2015). aToucan: an automated framework to derive UML analysis models from use case models. ACM Transactions on Software Engineering and Methodology (TOSEM), 24(3), 13.
[94] Zave, P. (1997). Classification of research efforts in requirements engineering. ACM Computing Surveys (CSUR), 29(4), 315-321.
[95] Zave, P., & Jackson, M. (1997). Four dark corners of requirements engineering. ACM transactions on Software Engineering and Methodology (TOSEM), 6(1), 1-30.

指導教授

陳仲儼(Chung-Yang Chen)

審核日期

2017-4-18

推文