探討採購管理系統開發過程之需求變更

Exploring the changing requirements in the development process of the procurement management system.

謝旻芳(Min-Fang Shieh)

指導教授 ： 游佳萍

淡江大學/商管學院/資訊管理學系碩士班/碩士(2019年)

https://doi.org/10.6846/TKU.2019.00131

摘要

本研究之主要目的為了解在系統開發過程中，需求發生變動的過程和最後的結果。本研究以一個開發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.

並列關鍵字

Requirement Change ； requirement type ； grounding theory ； procurement management system

參考文獻

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.