本研究之主要目的為了解在系統開發過程中，需求發生變動的過程和最後的結果。本研究以一個開發18個月的客製化採購管理系統專案為對象進行研究，依照紮根理論的方法，分成三個步驟來歸納分析系統開發過程中的文件資料。此外，本研究更進一步將資料按照系統開發生命週期，分成規劃階段、分析設計階段以及實作安裝與維護階段三個部分進行觀察分析。
本研究發現如下：一、在客製化系統的專案中，使用者是一個關鍵核心。二、客製化系統的開發過程中，主要是由技術配合實務。三、技術需求變更會在系統開發之初，大量被提出改進。四、若只考慮技術上的變動原因，技術需求的變更會隨系統發展而降低。五、技術需求的變更次數到系統開發後期沒有大幅降低，是因為其中有部分為新增加的技術需求。六、企業流程將依循系統的發展逐漸適應系統產生合適的流程。
根據研究結果本研究建議：(1)使用單位在指派關鍵使用者時要慎重，確保由業務經驗豐富、熟悉業務流程且表達能力良好的使用者擔任。(2)在客製化系統專案中，技術人員要優先讓系統達成使用者期望的結果。(3)由熟練的技術人員對使用者需求進行評估比較有參考價值，可以提早分析出無法達成的需求，避免浪費人力又造成專案進度壓力。(4)估算出準確的開發工時，有助於專案管理員安排專案時程。(5)專案管理員可以在開發後期預留一些時間給可能出現的需求改進，並在系統分析設計一開始，優先釐清系統的流程與權限。

The main objective of this study is to understand the process and the final result of requirements change during system development. This research is based on an 18-month customized procurement management system project. According to the grounded theory, it is divided into three steps to summarize and analyze the documents in the process of system development. In addition, the data is divided into three parts according to the System Development Life Cycle: Planning Stage, analysis and design stage and implementation, installation and maintenance stage. The conclusions of this study are as follows:
    1. The user was a key core in the customization project. 2. In the development process of customization system, it was mainly made up of technology and practice 3. Changes in technical requirements were often introduced at the beginning of system development. 4. If only the reasons for technical changes were taken into account, changes in technical requirements would decrease with the development of the system. 5. The number of changes in technology requirements did not decrease significantly towards the end of the system development period because some of these changes were due to additional technology requirements. 6. The enterprise process would follow the development of the system to gradually adapt to the system to produce appropriate processes. 
    Based on our findings, first, we suggested the organizations should be careful in assigning key users, ensuring that they are filled by users with business experience, familiarity with business processes, and good presentation skills. Second, for the customization system project, the technical personnel should give priority to the system to achieve the user's desired results. Third, skilled technical personnel evaluate the user's needs and analyze the unmet requirements ahead of time to avoid wasting manpower and causing project schedule pressure. Thus, estimating the exact development time will help the project manager to schedule the project. Finally, the project manager can set aside some time for possible improvements later in the development phase and clarify system processes and permissions in the beginning of the system development process.

目錄
第一章	緒論	1
1.1.	研究背景與動機	1
1.2.	研究目的	2
 第二章	 文獻探討	4
2.1.	需求變更	5
2.2.	需求的分類	7
 第三章	 研究方法	10
3.1.	研究個案	10
3.2.	資料蒐集過程	12
3.3.	紮根理論分析流程	15
3.3.1.	開放性編碼	15
3.3.2.	主軸編碼	23
3.3.3.	選擇性編碼	24
3.4.	信度與效度衡量	24
 第四章 	資料分析	27
4.1.	開放性編碼	27
4.2.	主軸編碼	32
4.3.	選擇性編碼	40
 第五章 	結論	46
5.1.	研究結論	46
5.2.	研究貢獻	47
5.3.	研究限制	48
參考文獻	50

 
表目錄
表 3 1文件與參與單位於系統開發命週期中的對應關係	12
表 3 2規劃階段至分析與設計階段之文件建立時間與版本關係	14
表 3 3變更需求單文件建立時間與版本關係	15
表 3 4研究編碼定義表	17
表 4 1因實務需求而影響功能需求的細項編碼發生次數統計	33
表 4 2因實務需求而影響技術需求的細項編碼發生次數統計	34
表 4 3因技術需求而影響技術需求的細項編碼發生次數統計	36
表 4 4因功能需求而影響功能需求的細項編碼發生次數統計	37
表 4 5因功能需求而影響技術需求的細項編碼發生次數統計	38
表 4 6細項編碼在個案中作為變動原因與受影響目標發生次數統計	40
表 4 7以實務需求為原因的需求變動發生次數統計	41
表 4 8以技術需求為原因的需求變動發生次數統計	41
表 4 9以功能需求為原因的需求變動發生次數統計	42
 
圖目錄
圖 4 1需求變動的原因(類別次數)	27
圖 4 2需求變動的影響(類別次數)	28
圖 4 3需求變動的原因(分階段之類別次數)	29
圖 4 4需求變動的影響(分階段之類別次數)	30
圖 4 5需求變動因果關係之次數統計	42
圖 4 6以系統開發生命週期分三階段之需求變動因果關係次數統計	44

Ali, H. O., Rozan, M. Z. A., & Sharif, A. M. (2012, May). Identifying challenges of change impact analysis for software projects. In 2012 International Conference on Innovation Management and Technology Research (pp. 407-411). IEEE.
Ali, K. (2017). A Study of Software Development Life Cycle Process Models. International Journal of Advanced Research in Computer Science, 8(1).
Ali, N., & Lai, R. (2016). A method of requirements change management for global software development. Information and Software Technology, 70, 49-67.
Aljohani, M. D., & Qureshi, M. R. J. (2016). Management of Changes in Software Requirements during Development Phases. International Journal of Education and Management Engineering (IJEME), 6(6), 12-26.
Arnold, R. S., & Bohner, S. A. (1993, September). Impact analysis-towards a framework for comparison. In 1993 Conference on Software Maintenance (pp. 292-301). IEEE.
Babar, M. I., Ghazali, M., Jawawi, D. N., & Elsafi, A. (2014). Stakeholder management in value-based software development: systematic review. IET Software, 8(5), 219-231. 
Bohner, S. A., & Arnold, R. S. (1996). Software change impact analysis (Vol. 6, p. 277). Los Alamitos: IEEE Computer Society Press.
Cronholm, S., & Goldkuhl, G. (2006). Involving Novice Users in Document-Driven System Requirements Analysis. Journal of Information, Information Technology & Organizations, 1.
Dubé, L., & Paré, G. (2003). Rigor in information systems positivist case research: current practices, trends, and recommendations. MIS quarterly, 597-636.
Edberg, D., & Olfman, L. (2001, January). Organizational learning through the process of enhancing information systems. In Proceedings of the 34th Annual Hawaii International Conference on System Sciences (pp. 10-pp). IEEE.
Firesmith, D. (2007). Common Requirements Problems, Their Negative Consequences, and the Industry Best Practices to Help Solve Them. Journal of Object Technology, 6(1), 17-33.
Glaser, B. G., Strauss, A. L., & Strutzel, E. (1968). The discovery of grounded theory; strategies for qualitative research. Nursing research, 17(4), 364.
Goknil, A., Kurtev, I., Van Den Berg, K., & Spijkerman, W. (2014). Change impact analysis for requirements: A metamodeling approach. Information and Software Technology, 56(8), 950-972.
Hsia, T. L., Wu, J. H., & Li, E. Y. (2008). The e-commerce value matrix and use case model: A goal-driven methodology for eliciting B2C application requirements. Information & Management, 45(5), 321-330.
Jackson, M. (1995). Software Requirements and Specifications: A lexicon of practice, principles and prejudices. Addison-Wesley.
Kagdi, H., Gethers, M., Poshyvanyk, D., & Collard, M. L. (2010, October). Blending conceptual and evolutionary couplings to support change impact analysis in source code. In 2010 17th Working Conference on Reverse Engineering (pp. 119-128). IEEE.
King, W. R., & Teo, T. S. (1996). Key dimensions of facilitators and inhibitors for the strategic use of information technology. Journal of Management Information Systems, 12(4), 35-53.
Lee, W. T., Deng, W. Y., Lee, J., & Lee, S. J. (2010). Change impact analysis with a goal‐driven traceability‐based approach. International Journal of Intelligent Systems, 25(8), 878-908.
McManus, J. (2004, October). A stakeholder perspective within software engineering projects. In 2004 IEEE International Engineering Management Conference (IEEE Cat. No. 04CH37574) (Vol. 2, pp. 880-884). IEEE.
Perumal, S. A., & Kavitha, M. G. (2011). Changing requirements-Correlated to risk or quality?. International Journal of Engineering and Technology, 3(1), 22.
Rovegård, P., Angelis, L., & Wohlin, C. (2008). An empirical study on views of importance of change impact analysis issues. IEEE Transactions on Software Engineering, 34(4), 516-530.
Saiedian, H., & Dale, R. (2000). Requirements engineering: making the connection between the software developer and customer. Information and software technology, 42(6), 419-428.
Shahid, M., & Ibrahim, S. (2016, January). Change impact analysis with a software traceability approach to support software maintenance. In 2016 13th International Bhurban conference on applied sciences and technology (IBCAST) (pp. 391-396). IEEE.
Sommerville, I. (2011). Software engineering 9th Edition. ISBN-10137035152.
Talha, M. (2018). Critical Requirements Engineering Errors Leads to Fails Software Project. The Educational Review, USA, 2(2), 174-180.
Theofanos, M. F., & Pfleeger, S. L. (1996). Wavefront: a goal-driven requirements process model. Information and Software Technology, 38(8), 507-519.
Tomyim, J., & Pohthong, A. (2016, August). Requirements change management based on object-oriented software engineering with unified modeling language. In 2016 7th IEEE International Conference on Software Engineering and Service Science (ICSESS) (pp. 7-10). IEEE.
Tsumaki, T., & Tamai, T. (2006). Framework for matching requirements elicitation techniques to project characteristics. Software Process: Improvement and Practice, 11(5), 505-519.
Wang, J., He, K., Gong, P., Wang, C., Peng, R., & Li, B. (2008, May). RGPS: A unified requirements meta-modeling frame for networked software. In Proceedings of the 3rd international workshop on Applications and advances of problem frames (pp. 29-35). ACM.
Zowghi, D., & Gervasi, V. (2003). On the interplay between consistency, completeness, and correctness in requirements evolution. Information and Software technology, 45(14), 993-1009.