| 研究生: |
李依珊 Li, Yi-Shan |
|---|---|
| 論文名稱: |
善用軟體發行管理以達到市場佔有率之最佳化 Optimizing Market Share in Software Release Management |
| 指導教授: |
焦惠津
Jiau, Hewijin Christine |
| 學位類別: |
碩士 Master |
| 系所名稱: |
電機資訊學院 - 電腦與通信工程研究所 Institute of Computer & Communication Engineering |
| 論文出版年: | 2020 |
| 畢業學年度: | 108 |
| 語文別: | 英文 |
| 論文頁數: | 36 |
| 中文關鍵詞: | 顧客滿意度 、市場佔有率最佳化 、需求排序 、軟體發行管理 |
| 外文關鍵詞: | Customer Satisfaction, Market Share Optimization, Requirements Prioritization, Software Release Management |
| 相關次數: | 點閱:105 下載:0 |
| 分享至: |
| 查詢本校圖書館目錄 查詢臺灣博碩士論文知識加值系統 勘誤回報 |
在高度競爭的軟體市場中,如何維持市場競爭力是每間軟體公司都必須面對的重大課題。當一間軟體公司能夠善用軟體發行管理時,它能夠最大化地滿足目標客群的需求,進而達到市場佔有率之最佳化的目標。在進行軟體發行管理時,軟體公司需要對目標客群的需求排定優先順序,並基於多方考量選擇最佳的軟體發行方案。許多需求排序的技術利用加權法 (Weighted sum model) 的方式,先計算目標客群對發行方案之滿意度或需求程度的加權總分,再基於發行方案的加權總分排定其優先順序。然而,加權法並未針對軟體發行管理中的兩大重要議題提供解決辦法。第一、各項產品的最終發行方案應該使該產品所指向之每一類目標客戶都感到滿意。第二、應避免各項產品之間產生非預期的內部競爭。當一間軟體公司為了加速軟體的推出而採用軟體生產線的作法開發軟體時,這兩項議題將變得愈發嚴峻。由於軟體生產線是透過大量的軟體重用以降低開發的成本及時間,此作法之下開發出的產品,相較於其他作法,更容易導致產品之間的高度相似性。故軟體公司需要透過適當的軟體發行管理,才能讓軟體生產線的作法發揮最大的效果。針對上述兩項議題,本論文以加權法為基礎,透過結合個別顧客滿意度,提出一套新模型以應用於需求排序的技術中。文中更利用三個真實個案驗證此新模型之有效性。驗證結果顯示,透過此新模型篩選出來的軟體發行方案,除了能夠使各產品指向之目標客戶群感到滿意,亦能避免公司內部產品之間的非預期競爭關係。
Satisfying target customer needs the most to optimize market share with proper release management is critical for keeping the competitiveness of software companies. Many requirements prioritization techniques, which support release management, use the weighted sum model (WSM) to deal with customer satisfaction. However, the WSM does not address two important issues in release management. The first issue is that each product should satisfy every target customer of the product. The second issue lies in avoiding unexpected competition between products. These two issues are especially severe when software companies adopt software product line practices to support software reuse. While software product line practices significantly reduce the development cost and time, the high similarity between products due to software reuse increases the complexity of release management. To resolve these two issues, this thesis proposes a model that combines the WSM and individual customer satisfaction. The model is evaluated through three real-world case studies. The results show that the model identifies all release plans that not only satisfy every target customer within a product but also avoid unexpected competition between products.
[1] P. Achimugu, A. Selamat, R. Ibrahim, and M. N. Mahrin. A systematic literature review of software requirements prioritization research. Information and Software Technology, 56(6):568-585, Jun. 2014.
[2] A. Aurum and C. Wohlin. A value-based approach in requirements engineering: Explaining some of the fundamental concepts. In P. Sawyer, B. Paech, and P. Heymans, editors, Proceedings of the International Working Conference on Requirements Engineering: Foundation for Software Quality, pages 109-115, Berlin, Germany, 2007. Springer-Verlag.
[3] P. Bajaj and V. Arora. Multi-person decision-making for requirements prioritization using fuzzy AHP. ACM SIGSOFT Software Engineering Notes, 38(5):1-6, Aug. 2013.
[4] P. Berander. Evolving prioritization for software product management. PhD thesis, Department of Systems and Software Engineering, Blekinge Institute of Technology, Blekinge, Sweden, 2007.
[5] P. Berander and A. Andrews. Requirements prioritization. In A. Aurum and C. Wohlin, editors, Engineering and Managing Software Requirements, pages 69-94. Springer-Verlag, Berlin, Germany, 2005.
[6] P. Chatzipetrou, L. Angelis, P. Rovegård, and C. Wohlin. Prioritization of issues and requirements by cumulative voting: A compositional data analysis framework. In Proceedings of the 36th EUROMICRO Conference on Software Engineering and Advanced Applications, pages 361-370, Los Alamitos, CA, USA, 2010. IEEE Comput. Soc. Press.
[7] P. C. Clements, L. G. Jones, L. M. Northrop, and J. D. McGregor. Project management in a software product line organization. IEEE Software, 22(5):54-62, Sep./ Oct. 2005.
[8] J. R. F. dos Santos, A. B. Albuquerque, and P. R. Pinheiro. Requirements prioritization in market-driven software: A survey based on large numbers of stakeholders and requirements. In Proceedings of the 2016 10th International Conference on the Quality Information and Communications Technology, pages 67-72, Los Alamitos, CA, USA, 2016. IEEE Comput. Soc. Press.
[9] D. Firesmith. Prioritizing requirements. Journal of Object Technology, 3(8):35-47, Sep. 2004.
[10] D. Greer and G. Ruhe. Software release planning: an evolutionary and iterative approach. Information and Software Technology, 46(4):243-253, Mar. 2004.
[11] F. Hujainah, R. B. A. Bakar, M. A. Abdulgabber, and K. Z. Zamli. Software requirements prioritisation: A systematic literature review on significance, stakeholders,
techniques and challenges. IEEE Access, 6:71497-71523, 2018.
[12] M. R. Karim and G. Ruhe. Bi-objective genetic search for release planning in support of themes. In C. Le Goues and S. Yoo, editors, Proceedings of the International Symposium on Search Based Software Engineering, pages 123-137, Cham, Switzerland, 2014. Springer-Verlag.
[13] J. Karlsson, C. Wohlin, and B. Regnell. An evaluation of methods for prioritizing software requirements. Information and Software Technology, 39(14-15):939-947, 1998.
[14] L. Karlsson, M. Höst, and B. Regnell. Evaluating the practical use of different measurement scales in requirements prioritisation. In Proceedings of the 2006 ACM/IEEE International Symposium on Empirical Software Engineering, pages 326-335, New York, NY, USA, 2006. Association for Computing Machinery.
[15] M. Komssi, M. Kauppinen, H. Töhönen, L. Lehtola, and A. M. Davis. Roadmapping problems in practice: Value creation from the perspective of the customers. Requirements Engineering, 20(1):45-69, Mar. 2015.
[16] C. K. Kwong, X. G. Luo, and J. F. Tang. A multiobjective optimization approach for product line design. IEEE Transactions on Engineering Management, 58(1):97-108, May/ Jun. 2011.
[17] D. Leffingwell and D. Widrig. Managing Software Requirements: A Use Case Approach. Pearson Education, London, England, 2 edition, 2003.
[18] L. Lehtola, M. Kauppinen, and S. Kujala. Requirements prioritization challenges in practice. In F. Bomarius and H. Iida, editors, Proceedings of the International Conference on Product Focused Software Process Improvement, pages 497-508, Berlin, Germany, 2004. Springer-Verlag.
[19] D. C. Lima, F. Freitas, G. Campos, and J. Souza. A fuzzy approach to requirements prioritization. In M. B. Cohen and M. Ó. Cinnéide, editors, Proceedings of the International Symposium on Search Based Software Engineering, pages 64-69, Berlin, Germany, 2011. Springer-Verlag.
[20] J. D. McGregor, D. Muthig, K. Yoshimura, and P. Jensen. Guest editors' introduction: Successful software product line practices. IEEE Software, 27(3):16-21, May/ Jun. 2010.
[21] K. Mohan, B. Ramesh, and V. Sugumaran. Integrating software product line engineering and agile development. IEEE Software, 27(3):48-55, May/ Jun. 2010.
[22] M. Nayebi and G. Ruhe. Asymmetric release planning: Compromising satisfaction against dissatisfaction. IEEE Transactions on Software Engineering, 45(9):839-857, Sep. 2019.
[23] A. Ngo-The and G. Ruhe. Optimized resource allocation for software release planning. IEEE Transactions on Software Engineering, 35(1):109-123, Jan./ Feb. 2009.
[24] J. A. Pereira, K. Constantino, and E. Figueiredo. A systematic literature review of software product line management tools. In I. Schaefer and I. Stamelos, editors, Proceedings of the International Conference on Software Reuse, pages 73-89, Cham, Switzerland, 2014. Springer-Verlag.
[25] A. Perini, A. Susi, and P. Avesani. A machine learning approach to software requirements prioritization. IEEE Transactions on Software Engineering, 39(4):445-461, Apr. 2013.
[26] G. Ruhe and D. Greer. Quantitative studies in software release planning under risk and resource constraints. In Proceedings of the 2003 International Symposium on Empirical Software Engineering, pages 262-270, Los Alamitos, CA, USA, 2003. IEEE Comput. Soc. Press.
[27] T. L. Saaty. The Analytic Hierarchy Process: Planning, Priority Setting, Resource Allocation. McGraw-Hill, New York, NY, USA, 1980.
[28] K. Schmid and E. S. de Almeida. Product line engineering. IEEE Software, 30(4):24-30, Jul./ Aug. 2013.
[29] K. Schmid and M. Verlage. The economic impact of product line adoption and evolution. IEEE Software, 19(4):50-57, Jul./ Aug. 2002.
[30] P. Tonella, A. Susi, and F. Palma. Interactive requirements prioritization using a genetic algorithm. Information and Software Technology, 55(1):173-187, Jan. 2013.
[31] E. Triantaphyllou. Multi-criteria decision making methods. In Multi-criteria Decision Making Methods: A Comparative Study, pages 5-21. Springer-Verlag, Boston, MA, USA, 2000.
[32] P. Voola and A. Vinaya Babu. Interval evidential reasoning algorithm for requirements prioritization. In S. C. Satapathy, P. S. Avadhani, and A. Abraham, editors, Proceedings of the International Conference on Information Systems Design and Intelligent Applications, pages 915-922, Berlin, Germany, 2012. Springer-Verlag.
[33] K. E. Wiegers. First things first: Prioritizing requirements. Software Development, 7(9):48-53, Sep. 1999.
校內:2025-01-06公開