Renán Darío Gonzales Apaza
ABSTRACT
The nature of the software requirements is subjective and varied. For this reason the level of complexity increases according to the volume, especially when the requirements are made in a natural language. Therefore obtain quality software requirements that are understandable and unambiguous in the Spanish language becomes a necessity. First, a controlled syntax was proposed to express software requirements taking into account the static and dynamic behavior among the different actors of the system, where the expressions are elaborated based on the Backus-Naur form (BNF). Then a set of writing rules were adapted to the Spanish language, creating four additional rules. Finally, the results of the case study had high accuracy in understandability; also the ambiguity of requirements elicitation was reduced. In addition to improving the development of software engineering activities, since there are no tools available for the elicitation of software requirements with language Spanish.
- Philip Achimugu, Ali Selamat, Roliana Ibrahim, and Mohd Naz'ri Mahrin. 2014. A systematic literature review of software requirements prioritization research. Inf. Softw. Technol. 56, 6 (June 2014), 568--585. Google Scholar
Digital Library
- Peter Braun, Manfred Broy, Frank Houdek, Matthias Kirchmayr, Mark Müller, Birgit Penzenstadler, Klaus Pohl, and Thorsten Weyer. 2014. Guiding requirements engineering for software-intensive embedded systems in the automotive industry. Comput. Sci. 29, 1 (February 2014), 21--43. Google ScholarDigital Library
- Geetha, S and Mala, GS Anandha. Extraction of key attributes from natural language requirements specification text. 2013. IET Chennai Fourth International Conference on Sustainable Energy and Intelligent Systems (SEISCON 2013).Google Scholar
- Irum Inayat, Siti Salwah Salim, Sabrina Marczak, Maya Daneva, and Shahaboddin Shamshirband. 2015. A systematic literature review on agile requirements engineering practices and challenges. Comput. Hum. Behav. 51, PB (October 2015), 915--929. Google ScholarDigital Library
- Fernandez, D Mendez and Wagner, Stefan and Kalinowski, Marcos and Felderer, Michael and Mafra, Priscilla and Vetrò, Antonio and Conte, Tayana and Christiansson, M-T and Greer, Desmond and Lassenius, Casper and others. 2017. Naming the pain in requirements engineering. Empirical Software Engineering (October 2017), 2298--2338. Google ScholarDigital Library
- Henning Femmer, Daniel Méndez Fernández, Elmar Juergens, Michael Klose, Ilona Zimmer, and Jörg Zimmer. 2014. Rapid requirements checks with requirements smells: two case studies. In Proceedings of the 1st International Workshop on Rapid Continuous Software Engineering (RCoSE 2014). ACM, New York, NY, USA, 10--19. Google ScholarDigital Library
- A. Fatwanto. 2013. Software requirements specification analysis using natural language processing technique. 2013 International Conference on QiR. (June 2013), 105--110.Google ScholarCross Ref
- C. Maria Keet and Langa Khumalo. 2017. Toward a knowledge-to-text controlled natural language of isiZulu. Lang. Resour. Eval. 51, 1 (March 2017), 131--157. Google ScholarDigital Library
- N. M. Minhas and S. Majeed and Z. Qayyum and M. Aasem. 2011. Controlled vocabulary based software requirements classification. In 2011 Malaysian Conference in Software Engineering. (December 2011), 31--36.Google ScholarCross Ref
- S. Ramzan and I. S. Bajwa and I. Ul Haq and M. A. Naeem. 2014. A model transformation from NL to SBVR. In Ninth International Conference on Digital Information Management (ICDIM 2014).(September 2014), 220--225.Google Scholar
- Thongglin, Kanjana and Cardey, Sylviane and Greenfield, Peter. 2013. Thai software requirements specification pattern. In 2013 IEEE 12th International Conference on Intelligent Software Methodologies, Tools and Techniques (SoMeT). (September 2013), 179--184.Google Scholar
- Umber, Ashfa and Bajwa, Imran. 2012. A Step Towards Ambiguity Less Natural Language Software Requirements Specifications. In International Journal of Web Applications (IJWA). 12--21.Google Scholar
- Thongglin, Kanjana and Cardey, Sylviane and Greenfield, Peter. 2012. Controlled Syntax for Thai Software Requirements Specification. In Proceedings of the 2012 IEEE 24th International Conference on Tools with Artificial Intelligence - Volume 01. 964--969. Google ScholarDigital Library
- Goran Glavaš, Krešimir Fertalj, and Jan Šnajder. 2012. From requirements to code: syntax-based requirements analysis for data-driven application development. In Proceedings of the 17th international conference on Applications of Natural Language Processing and Information Systems (NLDB'12), Gosse Bouma, Ashwin Ittoo, Elisabeth Métais, and Hans Wortmann (Eds.). Springer-Verlag, Berlin, Heidelberg, 339--344. Google ScholarDigital Library
- S. Gulia and T. Choudhury. 2016. An efficient automated design to generate UML diagram from Natural Language Specifications. In 2016 6th International Conference - Cloud System and Big Data Engineering (Confluence). (July 2016), 641--648.Google ScholarCross Ref
Index Terms
- ERS-TOOL: hybrid model for software requirements elicitation in Spanish language
Recommendations
Model-based prioritization in business-process-driven software development
RE '12: Proceedings of the 2012 IEEE 20th International Requirements Engineering Conference (RE)Requirements engineers in business-process-driven software development are faced with the challenge of letting stakeholders determine which requirements are actually relevant for early business success and should be considered first or even at all ...
Guest Editors' Introduction: Stakeholders in Requirements Engineering
The growing attention being paid to stakeholders' needs and desires reflects the growing importance of requirements engineering(RE) in software and systems development. This introduction reviews the RE process: identifying the stakeholders in a project,...
Specifying Safety Requirements with GORE languages
SBES '17: Proceedings of the XXXI Brazilian Symposium on Software EngineeringContext: A suitable representation of Safety-Critical Systems (SCS) requirements is crucial to avoid misunderstandings in safety requirements and issues in safety specification. However, current general requirements specification languages do not fully ...
Comments