Defining the language of the software application using the vocabulary of the domain
DOI:
https://doi.org/10.24215/15146774e013Keywords:
LEL, vocabulary, Requirements, application domain, software applicationAbstract
Requirements engineering is one the most critical stages in software development. If the requirements are not correct the software development team will produce an artifact that will not satisfy the needs, wishes and expectations of the client. Requirements (and knowledge in general) are spread among many stakeholders. Natural language is widely used since it is an adequate tool con-sidering non-technical stakeholder. Nevertheless communication problems arise with the use of natural language. The software development team members need to learn about the application domain and this process of learning means focusing on the features to be included in the software application, while leav-ing apart the elements out of the boundaries of the application. This process is not easy when people face a new application domain. Thus, this paper proposes an approach to define the software application language from a vocabulary of the application domain.
Downloads
Published
Issue
Section
License
Copyright (c) 2023 Leandro Antonelli, Julio Leite, Alejandro Oliveros, Gustavo Rossi
This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.
Those authors who have publications with this journal, agree with the following terms:
a. Authors will retain its copyright and will ensure the rights of first publication of its work to the journal, which will be at the same time subject to the Creative Commons Atribución-NoComercial-CompartirIgual 4.0 Internacional (CC BY-NC-SA 4.0) allowing third parties to share the work as long as the author and the first publication on this journal is indicated.
b. Authors may elect other non-exclusive license agreements of the distribution of the published work (for example: locate it on an institutional telematics file or publish it on an monographic volume) as long as the first publication on this journal is indicated,
c. Authors are allowed and suggested to disseminate its work through the internet (for example: in institutional telematics files or in their website) before and during the submission process, which could produce interesting exchanges and increase the references of the published work. (see The effect of open Access)
