ABSTRACT
Software requirements are generally expressed in Natural Language. NL is intrinsically ambiguous, and this is seen as a possible source of problems in the later interpretation of requirements. However, ambiguity or under-specification at requirements level can in some cases give an indication of possible variability, either in design choice, in implementation choices or configurability. Taking into account the results of previous analyses conducted on different requirements documents with NL analysis tools, we attempt a first classification of the forms of ambiguity that indicate variation points, and we indicate an approach to achieve automated support to variability elicitation.
- V. Ambriola, V. Gervasi, On the Systematic Analysis of Natural Language Requirements with CIRCE, Automated Software Engineering, Volume 13, Issue 1, pp 107--167, 2006. Google ScholarDigital Library
- M. Antkiewicz, K. Bąk, A. Murashkin, R. Olaechea, J. H. Liang, and K. Czarnecki. Clafer Tools for Product Line Engineering. 17th International Software Product Lines Conference, SPLC 2013, volume 2, pages 130--135.Google Scholar
- N. H. Bakar, Z. M. Kasirun, and N. Salleh, Feature extraction approaches from natural language requirements for reuse in software product lines: A systematic literature review, J. Syst. Softw., vol. 106, pp. 132--149, 2015. Google ScholarDigital Library
- G. Bécan, R. Behjati, A. Gotlieb, M. Acher, Synthesis of attributed feature models from product descriptions, 19th International Software Product Lines Conference, SPLC 2015: pp. 1--10.Google Scholar
- G. Bécan, N. Sannier, M. Acher, O. Barais, A. Blouin, B.Baudry, Automating the formalization of product comparison matrices, ACM/IEEE International Conference on Automated Software Engineering, ASE, 2014, pp. 433--444.Google ScholarDigital Library
- D.M. Berry, Ambiguity in Natural Language Requirements Documents, Lecture Notes in Computer Science 5320, 2008, pp. 1--7. Google ScholarDigital Library
- D. M. Berry, A. Bucchiarone, S. Gnesi, G. Lami , G. Trentanni, A new quality model for natural language requirements specifications . 12th International Working Conference on Requirements Engineering: Foundation for Software Quality (REFSQ) 2006, pp. 115--128.Google Scholar
- A. Bucchiarone, S. Gnesi, A. Fantechi, G. Trentanni, An experience in using a tool for evaluating a large set of natural language requirements. ACM Symposium on Applied Computing (SAC) 2010: pp. 281--286. Google ScholarDigital Library
- A. Fantechi, S. Gnesi, Formal Modeling for Product Families Engineering. 12th International Software Product Lines Conference, SPLC 2008, pp. 193--202.Google Scholar
- A. Ferrari, G. O. Spagnolo, and F. Dell'Orletta, Mining commonalities and variabilities from natural language documents, in Proc. 17th International Software Product Lines Conference, SPLC 2013, pp. 116--120.Google Scholar
- A. Ferrari, F. Dell'Orletta, A.Esuli, V. Gervasi, S. Gnesi, Natural Language Requirements Processing: A 4D Vision, IEEE Software, to appear.Google Scholar
- V. Gervasi, D. Zowghi, On the Role of Ambiguity in RE, Requirements Engineering: Foundation for Software Quality: 16th International Working Conference, (REFSQ), LNCS 6182, 2010, pp. 248--254.Google Scholar
- S. Gnesi, G. Lami, G. Trentanni, An automatic tool for the analysis of natural language requirements, Comput. Syst. Sci. Eng., 20, 1, 2005.Google Scholar
- B. Gleich, O. Creighton, and L. Kof, Ambiguity Detection: Towards a Tool Explaining Ambiguity Sources, Requirements Engineering: Foundation for Software Quality, (REFSQ) LNCS 6182, Springer, 2010, pp. 218--232.Google Scholar
- K. C. Kang, S. G. Cohen, J. A. Hess, W. E. Novak, A. S. Peterson, Feature-Oriented Domain Analysis (FODA) Feasibility Study, Tech. rep., Carnegie-Mellon University Software Engineering Institute , 1990.Google ScholarCross Ref
- N. Itzik, I. Reinhartz-Berger, Y. Wand, Variability Analysis of Requirements: Considering Behavioral Differences and Reflecting Stakeholders Perspectives IEEE Transactions on Software Engineering, 42, 7, July 2016, pp. 687--706.Google Scholar
- B. Rosadini, A. Ferrari, G. Gori, A. Fantechi, S. Gnesi, I. Trotta, and S. Bacherini, Using NLP to Detect Requirements Defects: an Industrial Experience in the Railway Domain, to appear on Proceedings Requirements Engineering: Foundation for Software Quality: 23rd International Working Conference, (REFSQ),2017.Google Scholar
- N. Sannier, M. Acher, B. Baudry: From comparison matrix to Variability Model: The Wikipedia case study. 28th IEEE/ACM International Conference on Automated Software Engineering, ASE, 2013, pp. 580--585.Google ScholarDigital Library
- S.F. Tjong, and D.M. Berry, The Design of SREE-A Prototype Potential Ambiguity Finder for Requirements Specifications and Lessons Learned, Requirements Engineering: Foundation for Software Quality, (REFSQ), Lecture Notes in Computer Science 7830, 2013, pp 80--95.Google Scholar
Index Terms
- Ambiguity defects as variation points in requirements
Recommendations
Hacking an Ambiguity Detection Tool to Extract Variation Points: an Experience Report
VAMOS '18: Proceedings of the 12th International Workshop on Variability Modelling of Software-Intensive SystemsNatural language (NL) requirements documents can be a precious source to identify variability information. This information can be later used to define feature models from which different systems can be instantiated. In this paper, we are interested in ...
Analysing anaphoric ambiguity in natural language requirements
Special Issue on Best Papers of RE'10: Requirements Engineering in a Multi-faceted WorldMany requirements documents are written in natural language (NL). However, with the flexibility of NL comes the risk of introducing unwanted ambiguities in the requirements and misunderstandings between stakeholders. In this paper, we describe an ...
Reducing Requirements Ambiguity via Gamification: Comparison with Traditional Techniques
Requirements elicitation is one of the most significant activities of requirements engineering (RE) process. Poorly specified requirements can lead to a failed project. Various elicitation techniques are used to elicit requirements from the users and ...
Comments