應用本體論來協助軟體專案進行流程調適

Applying Ontology to Software Process Tailoring

蔡文隆(Wen-Lung Tsai)；陳仲儼(Chung-Yang Chen)；李明達(Irwan Lika)

本體論 ； 軟體專案 ； 軟體流程調適 ； 知識密集 ； 決策支援 ； Ontology ； software project ； process tailoring ； knowledge-intensive ； decision support

資訊管理學報

23卷4期（2016 / 10 / 01）

377 - 405

繁體中文

對於軟體開發管理而言，組織通常會建立流程標準來讓各軟體專案據以執行。但鑒於軟體開發的獨特性，並非一套標準流程就可以完全套用在所有的軟體專案上。因此，企業組織需要訂定一套流程調適準則，讓專案成員根據不同專案所面臨的情境，依據調適準則而去調整實際的作法。然而，軟體流程調適是一個知識密集的活動，調適準則的制定或引用乃需要組織經驗方能提供適切的調適建議。故本研究嘗試建立一個以規則為基底的決策支援系統，運用本體論（Ontology）來建置一個知識與經驗導向的軟體流程本體模型，並據以發展出軟體專案流程調適推薦系統（Ontology-based software process tailoringrecommendation system; OntoSPRS）。本系統透過推論規則的設計，收集調適經驗，並以推論引擎對知識本體進行推論並產生調適策略，可協助專案成員在軟體開發過程中能更完整地將組織經驗帶入而導出具體實作方方式。本研究並以一國內物流公司雲端企業資源規劃系統之實際案例來展示本研究所建構的軟體流程本體。

Purpose - Owing to the uniqueness in software development, this study develops an ontology-based software process tailoring recommendation system to manage quality and consistency in software development. Design/methodology/approach - The system includes a knowledge- intensive software process ontology model and features a rule inference engine for deriving tailoring strategies. Findings - This study found that the proposed system was able to improve tailoring recommendation outputs and make the underlying tailored strategy knowledge structure more accurate. Research limitations/implications - Due to high project variability and complicated influence factors, more new research is needed in the future. Furthermore, the interactions among tailoring factors will derive even more tailoring rules in practice. Practical implications - Since the system developed is specifically configured to work with the case company, the system may not be able to meet all organizational requirements. In practice, individual organizations should customize the content of ontology, based on the organizational characteristics and its own process standard. Originality/value - This study is the first develop a rule-based decision support system for software process tailoring. The study assists project specialists with project tailoring that complies with the organizational tailoring standard.

1. 陳仲儼、黃永福(2009)。運用模糊專家系統來協助軟體專案進行流程調適。電子商務學報，11(1)，235-258。
   連結：
2. Singh, R. (1996), 'International Standard ISO/IEC 12207 Software Life Cycle Process', available at http://www.abelia.com/docs/12207cpt.pdf (accessed 15 April 2015).
3. Aaen, I.(2008).Essence: facilitating software innovation.European Journal of Information Systems,17(5),543-553.
4. Alegria, J.A.H.,Bastarrica, M.C.,Quispe, A.,Ochoa, S.F.(2014).MDE-based process tailoring strategy.Journal of Software: Evolution and Process,26(4),386-403.
5. Chen, C.Y.,Liu, H.A.,Song, J.Y.(2013).Integrated projects planning in IS departments: a multi-period multi-project selection and assignment approach with a computerized implementation.European Journal of Operational R,229(3),683-694.
6. Chen, C.Y.,Tsai, W.L.(2011).Toward Single-sourcing of Software Project Documented Contents: A Preliminary Study.International Journal of Electronic Business Management,9(1),37-45.
7. Chi, Y.L.(2010).Rule-based ontological knowledge base for monitoring partners across supply networks.Expert Systems with Applications,37(2),1400-1407.
8. Chi, Y.L.,Chen, C.Y.(2009).Project teaming: Knowledge-intensive design for composing team members.Expert Systems with Applications,36(5),9479-9487.
9. Clarke, P.,O'Connor, R.V.(2012).The situational factors that affect the software development process: Towards a comprehensive reference framework.Information and Software Technology,54(5),433-447.
10. CMMI Product Team(2010).CMMI® for Development Version 1.3- Improving processes for developing better products and services.Pittsburgh, USA.:Software Engineering Institute, Carnegie Mellon University.
11. Darke, P.,Shanks, G.,Broadbent, M.(1998).Successfully completing case study research: combining rigour, relevance and pragmatism.Information systems journal,8(4),273-289.
12. Ebert, C.,De Man, J.(2008).Effectively utilizing project, product and process knowledge.Information and Software Technology,50(6),579-594.
13. Elbanna, A.(2013).Top management support in multiple-project environments: an inpractice view.European Journal of Information Systems,22(3),278-294.
14. Ginsberg, M.P.,Quinn, L.H.(1995).Process Tailoring and the Software Capability Maturity Model.Pittsburgh, USA:Software Engineering Institute, Carnegie Mellon University.
15. Haghighi, P.D.,Burstein, F.,Zaslavsky, A.,Arbon, P.(2013).Development and evaluation of ontology for intelligent decision support in medical emergency management for mass gatherings.Decision Support Systems,54(2),1192-1204.
16. Horrocks, I.,Patel-Schneider, P.F.,Bechhofer, S.,Tsarkov, D.(2005).OWL rules: A proposal and prototype implementation.Web Semantics: Science, Services and Agents on the World Wide Web,3(1),23-40.
17. Kalus, G.,Kuhrmann, M.(2013).Criteria for software process tailoring: a systematic review.Proceedings of the 2013 International Conference on Software and System Process (ICSSP 2013),San Francisco, USA:
18. Kaur, R.,Sengupta, J.(2013).Software process models and analysis on failure of software development projects.International Journal of Scientific and Engineering Research,2(2),1-4.
19. Liu, J.Y.C.,Chen, H.G.,Chen, C.C.,Sheu, T.S.(2011).Relationships among interpersonal conflict, requirements uncertainty, and software project performance.International Journal of Project Management,29(5),547-556.
20. Lorenz, W.G.,Brasil, M.B.,Fontoura, L.M.,Pereira, G.V.(2014).Activity-Based Software Process Lines Tailoring.International Journal of Software Engineering and Knowledge Engineering,24(9),1357-1381.
21. Martínez-Ruiz, T.,Münch, J.,García, F.,Piattini, M.(2012).Requirements and constructors for tailoring software processes: a systematic literature review.Software Quality Journal,20(1),229-260.
22. Myers, M.D.,Newman, M.(2007).The qualitative interview in IS research: Examining the craft.Information and Organization,17(1),2-26.
23. Na, K.S.,Simpson, J.T.,Li, X.,Singh, T.,Kim, K.Y.(2007).Software development risk and project performance measurement: Evidence in Korea.Journal of Systems and Software,80(4),596-605.
24. Nidumolu, S.R.(1996).Standardization, requirements uncertainty and software project performance.Information & Management,31(3),135-150.
25. Oh, S.,Yeom H.Y.,Ahn, J.(2011).Cohesion and coupling metrics for ontology modules.Information Technology and Management,12(2),81-96.
26. Park, S.,Na, H.,Park, S.,Sugumaran, V.(2006).A semi-automated filtering technique for software process tailoring using neural network.Expert Systems with Applications,30(2),179-189.
27. Park, S.H.,Bae, D.H.(2013).Tailoring a large-sized software process using process slicing and case-based reasoning technique.IET Software,7(1),47-55.
28. Prikladnicki, R.,Audy, J.L.N.,Damian, D.,de Oliveira, T.C.(2007).Distributed software development: practices and challenges in different business strategies of offshoring and onshoring.Proceedings of the 2nd IEEE International Conference on Global Software Engineering (ICGSE 2007),Munich, Germany:
29. Recker, J.,Rosemann, M.,Green, P.F.,Indulska, M.(2011).Do Ontological Deficiencies in Modeling Grammars Matter?.MIS Quarterly,35(1),57-79.
30. Reich, B.H.,Gemino, A.,Sauer, C.(2012).Knowledge management and projectbased knowledge in it projects: A model and preliminary empirical results.International Journal of Project Management,30(6),663-674.
31. Samuel, B.M.,Watkins, L.,Ehle, A.,Khatri, V.(2015).Customizing the Representation Capabilities of Process Models: Understanding the Effects of Perceived Modeling Impediments.IEEE Transactions on Software Engineering,41(1),19-39.
32. Seaman, C.B.(1999).Qualitative methods in empirical studies of software engineering.IEEE Transactions on Software Engineering,25(4),557-572.
33. Simperl, E.,Bürger, T.,Hangl, S.,Worgl, S.,Popov, I.O.(2012).ONTOCOM: A reliable cost estimation method for ontology development projects.Journal of Web Semantics,16,1-16.
34. Sulayman, M.,Mendes, E.,Urquhart, C.,Riaz, M.,Tempero, E.(2014).Towards a theoretical framework of SPI success factors for small and medium web companies.Information and Software Technology,56(7),807-820.
35. Tsai, W.T.,Wu, B.,Jin, Z. Huang, Y.,Li, W.(2013).Ontology patterns for serviceoriented software development.Software: Practice and Experience,43(7),867-883.
36. Venkatesh, V.,Davis, F.D.(2000).A theoretical extension of the technology acceptance model: four longitudinal field studies.Management Science,46(2),186-204.
37. Williams, L.,Cockburn, A.(2003).Agile software development: It's about feedback and change.IEEE Computer Society,36(6),39-43.
38. Xu, P.,Ramesh, B.(2007).Software process tailoring: an empirical investigation.Journal of Management Information Systems,24(2),293-328.
39. Xu, P.,Ramesh, B.(2008).Impact of Knowledge Support on the Performance of Software Process Tailoring.Journal of Management Information Systems,25(3),277-314.
40. Yan, T.,Dooley, K.J.(2014).Buyer-Supplier Collaboration Quality in New Product Development Projects.Journal of Supply Chain Management,50(2),59-83.
41. Yan, T.,Dooley, K.J.(2013).Communication intensity, goal congruence, and uncertainty in buyer-supplier new product development.Journal of Operations Management,31(7),523-542.
42. Young, R.,Poon, S.(2013).Top management support-almost always necessary and sometimes sufficient for success: Findings from a fuzzy set analysis.International Journal of Project Management,31(7),943-957.

1. 黃妍恆,陳鴻基,張伊婷(2023)。適應性領導於數位轉型專案團隊能力與效益實現之探討。資訊管理學報，30(2)，107-136。