The paper presents a new approach to managing software requirement elicitation techniques with a high level of analyses based on domain ontology techniques, where we established a mapping between user scenario, structured requirement, and domain ontology techniques to improve many attributes such as requirement consistency, completeness and eliminating duplicate requirements to reduce risk of overrun time and budgets. One of the main targets of requirement engineering is to develop a requirement document with high quality. So, we proposed a user interface to collect all vital information about the project directly from the regular user and requirement engineering; After that, the proposal will generate an ontology based on semantic relations and rules. Requirements Engineering tries to keep requirements throughout a project’s life cycle consistent necessities clear, and up to date. This prototype allows mapping requirement scenarios into ontology elements for semantically interrupted. The general points of our prototype are to guarantee the identification requirements and improved nature of the Software Requirements Specification (SRS) by solving incomplete and conflicting information in the requirements specification.
References
[1]
Joseph, E. (2017) Survey on Requirement Elicitation Techniques: Its Effect on Software Engineering. International Journal of Innovative Research in Computer and Communication Engineering, 5, 9201-9215.
[2]
Wiegers, K.E. (2013) Software Requirements. 3rd Edition, Microsoft Press, Redmond.
[3]
Van Lamsweerde, A., Darimont, R. and Letier, E. (1998) Managing Conflicts in Goal-Driven Requirements Engineering. IEEE Transactions on Software Engineering, 24, 908-926. https://doi.org/10.1109/32.730542
[4]
Amyot, D. (2003) Introduction to the User Requirements Notation: Learning by Example. Computer Networks, 42, 285-301. https://www.sciencedirect.com/science/article/pii/S1389128603002445
[5]
Leffingwell, D. and Widrig, D. (2003) Managing Software Requirements—A User Case Approach. 2nd Edition, Addison-Wesley, Boston.
[6]
Loucopoulos, P. and Karakostas, V. (1995) System Requirements Engineering. McGraw Hill, London.
[7]
Gavrilova, T. and Andreeva, T. (2012) Knowledge Elicitation Techniques in a Knowledge Management Context. Journal of Knowledge Management, 16, 523-537. https://doi.org/10.1108/13673271211246112
[8]
Bourque, P. and Fairley, R.E. (2014) Guide to the Software Engineering Body of Knowledge (SWEBOK (R)). Version 3.0. IEEE Computer Society Press, Washington DC.
[9]
Davis, A.M. (1992) Operational Prototyping: A New Development Approach. IEEE Software, 9, 70-78. https://doi.org/10.1109/52.156899
[10]
Sajjad, U. and Hanif, M. (2010) Issues and Challenges of Requirement Elicitation in Large Web Projects. School of Computing, Blekinge Institute of Technology, Ronneby.
[11]
Mohd Kasirun, Z. (2005) A Survey on the Requirements Elicitation Practices among Courseware Developers. Malaysian Journal of Computer Science, 18, 70-77.
[12]
Zhu, X. and Jin, Z. (2005) Inconsistency Measurement of Software Requirements Specifications: An Ontology-Based Approach. 10th IEEE International Conference on Engineering of Complex Computer Systems (ICECCS’05), Shanghai 16-20 June 2005, 402-410. https://doi.org/10.1109/ICECCS.2005.55
[13]
Loucopoulos, P. and Katsouli, E. (1992) Modelling Business Rules in an Office Environment. SIGOIS Bulletin, 13, 28-37. https://doi.org/10.1145/134376.134384
[14]
Taye, M.M. (2009) Ontology Alignment Mechanisms for Improving Web-Based Searching. Ph.D. Thesis, De Montfort University, United Kingdom, England.
[15]
Taye, M.M. (2010) State-of-the-Art: Ontology Matching Techniques and Ontology Mapping Systems. The International Journal of ACM Jordan, 1, 68.
[16]
Aßmann, U., Zschaler, S. and Wagner, G. (2006) Ontologies, Metamodels, and the Model-Driven Paradigm. In: Calero, C., Ruiz, F. and Piattini, M., Eds., Ontologies for Software Engineering and Software Technology, Springer, Berlin, 249-273. https://doi.org/10.1007/3-540-34518-3_9
[17]
[IEEE-830] Institute of Electrical and Electronics Engineers (1998) IEEE Recommended Practice for Software Requirements Specifications. IEEE Std 830-1998, Institute of Electrical and Electronics Engineers, New York.
[18]
Alsanad, A.A., Chikh, A. and Mirza, A. (2019) A Domain Ontology for Software Requirements Change Management in Global Software Development Environment. IEEE Access, 7, 49352-49361. https://doi.org/10.1109/ACCESS.2019.2909839
[19]
Dermeval, D., Vilela, J., Bittencourt, I.I., et al. (2016) Applications of Ontologies in Requirements Engineering: A Systematic Review of the Literature. Requirements Engineering, 21, 405-437. https://doi.org/10.1007/s00766-015-0222-6
[20]
Breitman, K.K. and Prado Leite, J.C.S. (2003) Ontology as a Requirements Engineering Product. International Requirements Engineering Conference, Monterey Bay, CA, 12 September 2003, 309-319.
[21]
Zowghi, D. and Coulin, C. (2005) Requirements Elicitation: A Survey of Technique, Approaches and Tools. In: Aurum, A. and Wohlin, C., Eds., Engineering and Managing Software Requirements, Springer, Berlin, 19-46.
[22]
Siegemund, K. (2014) Contributions to Ontology-Driven Requirements Engineering. Dissertation, Technischen Universitat Dresden, Dresden, 236 p.
[23]
Thamrongchote, C. and Vatanawood, W. (2016) Business Process Ontology for Defining User Story. 2016 IEEE/ACIS 15th International Conference on Computer and Information Science (ICIS), Okayama, 26-29 June 2016, 1-4. https://doi.org/10.1109/ICIS.2016.7550829
[24]
Bhatia, M.P.S., Kumar, A. and Beniwal, R. (2015) Ontologies for Software Engineering: Past, Present and Future. Indian Journal of Science and Technology, 9, 1-16. https://doi.org/10.17485/ijst/2016/v9i9/71384
[25]
Murugesh, S. and Jaya, A. (2015) Construction of Ontology for Software Requirements Elicitation. Indian Journal of Science and Technology, 8, 1-5. https://doi.org/10.17485/ijst/2015/v8i29/86271
[26]
Robeer, M., Lucassen, G., et al. (2016) Automated Extraction of Conceptual Models from User Stories via NLP. 24th International Requirements Engineering (RE) Conference, Beijing, 12-16 September 2016, 196-205. https://doi.org/10.1109/RE.2016.40
[27]
Sitthithanasakul, S. and Choosri, N. (2016) Using Ontology to Enhance Requirement Engineering in Agile Software Process. 2016 10th International Conference on Software, Knowledge, Information Management & Applications (SKIMA), Chengdu, 15-17 December 2016, 181-186. https://doi.org/10.1109/SKIMA.2016.7916218
[28]
Avdeenko, T.V. and Pustovalova, N.V. (2015) The Ontology-Based Approach to Support the Completeness and Consistency of the Requirements Specification. International Siberian Conference on Control and Communications (SIBCON2015), Vol. 9, 1-4. https://doi.org/10.1109/SIBCON.2015.7147184
[29]
Verhodubs, O. and Grundspenkis, J. (2013) Ontology Merging in the Context of Semantic Web Expert System. 4th Conference, KESW 2013, St. Petersburg, 7-9 October 2013, 191-201. https://doi.org/10.1007/978-3-642-41360-5_15
[30]
Castañeda, V., Ballejos, L., Caliusco, M.L. and Galli, M.R. (2010) The Use of Ontologies in Requirements Engineering. Global Journal of Researches in Engineering, 10, 2-8.
[31]
Siegemund, K., Thomas, E.J., Zhao, Y., Pan, J. and Assmann, U. (2011) Towards Ontology-Driven Requirements Engineering. 10th International Semantic Web Conference (ISWC), Bonn, Bonn, 1-6.
[32]
Awal, A., et al. (2018) Ontology Development for the Domain of Software Requirement Elicitation Technique. International Journal of Engineering Research & Technology (IJERT), 7, 334-338. https://doi.org/10.17577/IJERTV7IS040237
[33]
Hull, E., Jackson, K. and Dick, J. (2005) Requirements Engineering. Springer, Berlin.
Chen, X., Yin, B. and Jin, Z. (2011) Ontology-Guided Requirements Modeling Based on Problem Frames Approach. Journal of Software, 22, 177-194. https://doi.org/10.3724/SP.J.1001.2011.03755
[36]
Hitzler, P., Krötzsch, M., Parsia, B., et al. (2012) OWL 2 Web Ontology Language Primer. Second Edition.
[37]
Gruber, T.R. (1993) A Translation Approach to Portable Ontologies. Knowledge Acquisition, 5, 199-220. https://doi.org/10.1006/knac.1993.1008
