The Communication Between Client-Developer in the Process of Requirements Elicitation for a Software Project
Communication is a fundamental part of the requirements elicitation process for a software project, but the constant changes in the requirements make it difficult to complete a project successfully, and sometimes the customer’s expectations are not met. The problem of communication has different rea...
Kaydedildi:
| Yazar: | |
|---|---|
| Diğer Yazarlar: | , , , , |
| Materyal Türü: | article |
| Dil: | eng |
| Baskı/Yayın Bilgisi: |
2021
|
| Online Erişim: | https://link.springer.com/chapter/10.1007/978-3-030-72654-6_4 https://hdl.handle.net/20.500.14809/3266 |
| Etiketler: |
Etiketle
Etiket eklenmemiş, İlk siz ekleyin!
|
| _version_ | 1859049574993231872 |
|---|---|
| author | Álvarez, Sebatián |
| author2 | Duy, Kevin Zapata, Mireya Galarza, Jorge Martínez, Danilo Puco, Carlos |
| author2_role | author author author author author |
| author_facet | Álvarez, Sebatián Duy, Kevin Zapata, Mireya Galarza, Jorge Martínez, Danilo Puco, Carlos |
| author_role | author |
| collection | Repositorio Universidad Tecnológica Indoamérica |
| dc.creator.none.fl_str_mv | Álvarez, Sebatián Duy, Kevin Zapata, Mireya Galarza, Jorge Martínez, Danilo Puco, Carlos |
| dc.date.none.fl_str_mv | 2021 2022-06-20T02:59:34Z 2022-06-20T02:59:34Z |
| dc.identifier.none.fl_str_mv | https://link.springer.com/chapter/10.1007/978-3-030-72654-6_4 https://hdl.handle.net/20.500.14809/3266 |
| dc.language.none.fl_str_mv | eng |
| dc.publisher.none.fl_str_mv | Advances in Intelligent Systems and Computing. Volume 1368 AISC, Pages 36 - 45. World Conference on Information Systems and Technologies, WorldCIST 2021. Terceira Island. 30 March 2021 through 2 April 2021 |
| dc.rights.none.fl_str_mv | https://creativecommons.org/licenses/by/4.0/ info:eu-repo/semantics/openAccess |
| dc.source.none.fl_str_mv | reponame:Repositorio Universidad Tecnológica Indoamérica instname:Universidad Tecnológica Indoamérica instacron:UTI |
| dc.title.none.fl_str_mv | The Communication Between Client-Developer in the Process of Requirements Elicitation for a Software Project |
| dc.type.none.fl_str_mv | info:eu-repo/semantics/publishedVersion info:eu-repo/semantics/article |
| description | Communication is a fundamental part of the requirements elicitation process for a software project, but the constant changes in the requirements make it difficult to complete a project successfully, and sometimes the customer’s expectations are not met. The problem of communication has different reasons, among them, the shortcomings in the process by which the requirements engineer contacts the customer and the customer does not always have a clear idea of what he really needs. In order to identify the reasons for the communication problems between the requirements engineer and the customer, we have carried out a survey with the participation of employees from two software development companies. The results show the comparison and contrast of the effectiveness of the traditional processes against the current processes in the same way, we can highlight the preference of the experts when choosing a method of elicitation against another one and the advantages and disadvantages that each one represents. We also get results about how to improve the processes that present the greatest number of problems. In addition, it is worth mentioning that results were also obtained regarding how professionals recognize when there is a problem between the developer and the client or vice versa and the possible solution that should be applied to avoid some kind of conflict in the medium or long term in the software’s development project. |
| eu_rights_str_mv | openAccess |
| format | article |
| id | UTI_bc7ced04a2864c4a75d954d7cb7c1daf |
| instacron_str | UTI |
| institution | UTI |
| instname_str | Universidad Tecnológica Indoamérica |
| language | eng |
| network_acronym_str | UTI |
| network_name_str | Repositorio Universidad Tecnológica Indoamérica |
| oai_identifier_str | oai:repositorio.uti.edu.ec:20.500.14809/3266 |
| publishDate | 2021 |
| publisher.none.fl_str_mv | Advances in Intelligent Systems and Computing. Volume 1368 AISC, Pages 36 - 45. World Conference on Information Systems and Technologies, WorldCIST 2021. Terceira Island. 30 March 2021 through 2 April 2021 |
| reponame_str | Repositorio Universidad Tecnológica Indoamérica |
| repository.mail.fl_str_mv | . |
| repository.name.fl_str_mv | Repositorio Universidad Tecnológica Indoamérica - Universidad Tecnológica Indoamérica |
| repository_id_str | 0 |
| rights_invalid_str_mv | https://creativecommons.org/licenses/by/4.0/ |
| spelling | The Communication Between Client-Developer in the Process of Requirements Elicitation for a Software ProjectÁlvarez, SebatiánDuy, KevinZapata, MireyaGalarza, JorgeMartínez, DaniloPuco, CarlosCommunication is a fundamental part of the requirements elicitation process for a software project, but the constant changes in the requirements make it difficult to complete a project successfully, and sometimes the customer’s expectations are not met. The problem of communication has different reasons, among them, the shortcomings in the process by which the requirements engineer contacts the customer and the customer does not always have a clear idea of what he really needs. In order to identify the reasons for the communication problems between the requirements engineer and the customer, we have carried out a survey with the participation of employees from two software development companies. The results show the comparison and contrast of the effectiveness of the traditional processes against the current processes in the same way, we can highlight the preference of the experts when choosing a method of elicitation against another one and the advantages and disadvantages that each one represents. We also get results about how to improve the processes that present the greatest number of problems. In addition, it is worth mentioning that results were also obtained regarding how professionals recognize when there is a problem between the developer and the client or vice versa and the possible solution that should be applied to avoid some kind of conflict in the medium or long term in the software’s development project.Advances in Intelligent Systems and Computing. Volume 1368 AISC, Pages 36 - 45. World Conference on Information Systems and Technologies, WorldCIST 2021. Terceira Island. 30 March 2021 through 2 April 20212022-06-20T02:59:34Z2022-06-20T02:59:34Z2021info:eu-repo/semantics/publishedVersioninfo:eu-repo/semantics/articlehttps://link.springer.com/chapter/10.1007/978-3-030-72654-6_4https://hdl.handle.net/20.500.14809/3266enghttps://creativecommons.org/licenses/by/4.0/info:eu-repo/semantics/openAccessreponame:Repositorio Universidad Tecnológica Indoaméricainstname:Universidad Tecnológica Indoaméricainstacron:UTI2022-06-20T20:24:26Zoai:repositorio.uti.edu.ec:20.500.14809/3266Institucionalhttps://repositorio.uti.edu.ec/Institución privadahttps://indoamerica.edu.ec/https://repositorio.uti.edu.ec/oai.Ecuador...opendoar:02022-06-20T20:24:26Repositorio Universidad Tecnológica Indoamérica - Universidad Tecnológica Indoaméricafalse |
| spellingShingle | The Communication Between Client-Developer in the Process of Requirements Elicitation for a Software Project Álvarez, Sebatián |
| status_str | publishedVersion |
| title | The Communication Between Client-Developer in the Process of Requirements Elicitation for a Software Project |
| title_full | The Communication Between Client-Developer in the Process of Requirements Elicitation for a Software Project |
| title_fullStr | The Communication Between Client-Developer in the Process of Requirements Elicitation for a Software Project |
| title_full_unstemmed | The Communication Between Client-Developer in the Process of Requirements Elicitation for a Software Project |
| title_short | The Communication Between Client-Developer in the Process of Requirements Elicitation for a Software Project |
| title_sort | The Communication Between Client-Developer in the Process of Requirements Elicitation for a Software Project |
| url | https://link.springer.com/chapter/10.1007/978-3-030-72654-6_4 https://hdl.handle.net/20.500.14809/3266 |